From 0bcb961267a8164dd8e80eea4b1f2b501d47ce66 Mon Sep 17 00:00:00 2001 From: Randy Dunlap Date: Wed, 6 Dec 2006 20:39:14 -0800 Subject: [PATCH] --- yaml --- r: 42905 b: refs/heads/master c: 4e229beff7ee43d3d5e387ec91188b20f6267c00 h: refs/heads/master i: 42903: 188955ea1f7a8a1b5b4e9d7084a3fbfd4820d2a3 v: v3 --- [refs] | 2 +- trunk/REPORTING-BUGS | 4 +++- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/[refs] b/[refs] index d754bab6a1e8..fed0990648cc 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: c6f24f99cd70a383699bdb34ddd9e6e51c83304c +refs/heads/master: 4e229beff7ee43d3d5e387ec91188b20f6267c00 diff --git a/trunk/REPORTING-BUGS b/trunk/REPORTING-BUGS index f9da827a0c18..ac02e42a2627 100644 --- a/trunk/REPORTING-BUGS +++ b/trunk/REPORTING-BUGS @@ -40,7 +40,9 @@ summary from [1.]>" for easy identification by the developers. [1.] One line summary of the problem: [2.] Full description of the problem/report: [3.] Keywords (i.e., modules, networking, kernel): -[4.] Kernel version (from /proc/version): +[4.] Kernel information +[4.1.] Kernel version (from /proc/version): +[4.2.] Kernel .config file: [5.] Most recent kernel version which did not have the bug: [6.] Output of Oops.. message (if applicable) with symbolic information resolved (see Documentation/oops-tracing.txt)