Skip to contentSkip to conversation

README: Alternative configuration commands does not mention make listnewconfig

PATCH In review Regid Ichira 3 participants 4 messages Sep 12, 2013

lore
Share & tools
lore

Regid Ichira

author Applied
#0 lore raw

PATCH 1/1 README: Alternative configuration commands does not mention make listnewconfig

Applied to the tip of linux.git,
VERSION = 3 PATCHLEVEL = 11 SUBLEVEL = 0

---
 README | 4 ++++
 1 file changed, 4 insertions(+)
README +4 -0
index a24ec89..f10c16f 100644
@@ -228,6 +228,10 @@ CONFIGURING the kernel:
      "make localyesconfig" Similar to localmodconfig, except it will convert
                            all module options to built in (=y) options.
 
+     "make listnewconfig"  Based on the contents of your existing ./.config
+                        file, print all the new config symbols.  One at a
+                        line.
+
    You can find more information on using the Linux kernel config tools
    in Documentation/kbuild/kconfig.txt.
 
Signature · 1 line
1.8.4.rc3
#1 lore raw
Quoted 12 lines · Regid Ichira

Applied to the tip of linux.git,
VERSION = 3 PATCHLEVEL = 11 SUBLEVEL = 0

---
 README | 4 ++++
 1 file changed, 4 insertions(+)
README +0 -0
index a24ec89..f10c16f 100644

README CONFIGURING the kernel: · line 232

Quoted 5 lines
README +2 -0
@@ -228,6 +228,10 @@ CONFIGURING the kernel:
      "make localyesconfig" Similar to localmodconfig, except it will convert
                            all module options to built in (=y) options.
 
+     "make listnewconfig"  Based on the contents of your existing ./.config
+                        file, print all the new config symbols.  One at a

, one per line.

Wow, that's going to be a ton of symbols to read.

And about ./.config, does using O=<build-directory> apply to this (these) commands?

Quoted 6 lines
README +2 -0
+                        line.
+
    You can find more information on using the Linux kernel config tools
    in Documentation/kbuild/kconfig.txt.
 
Signature · 1 line
~Randy
#2 lore raw
In reply to Regid Ichira
Quoted 24 lines · Regid Ichira

Applied to the tip of linux.git,
VERSION = 3 PATCHLEVEL = 11 SUBLEVEL = 0

---
 README | 4 ++++
 1 file changed, 4 insertions(+)
README +0 -0
index a24ec89..f10c16f 100644
@@ -228,6 +228,10 @@ CONFIGURING the kernel:
      "make localyesconfig" Similar to localmodconfig, except it will  

convert
all module options to built in (=y)
options.

+ "make listnewconfig" Based on the contents of your existing
./.config
+ file, print all the new config symbols. One
at a

README +2 -0
+                        line.
+
    You can find more information on using the Linux kernel config  
Quoted 2 lines

tools
in Documentation/kbuild/kconfig.txt.

"make help" does, though. Possibly the README should point people at that instead of trying to keep a (third?) copy of this info in sync?

Rob

#3 lore raw
Quoted 31 lines · Rob Landley
Quoted 24 lines · Regid Ichira

Applied to the tip of linux.git,
VERSION = 3 PATCHLEVEL = 11 SUBLEVEL = 0

---
README | 4 ++++

1 file changed, 4 insertions(+)
README +0 -0
index a24ec89..f10c16f 100644
@@ -228,6 +228,10 @@ CONFIGURING the kernel:
     "make localyesconfig" Similar to localmodconfig, except it

will convert
all module options to built in (=y)
options.

+ "make listnewconfig" Based on the contents of your existing
./.config
+ file, print all the new config symbols.
One at a

README +2 -0
+                        line.
+
   You can find more information on using the Linux kernel config
Quoted 2 lines

tools
in Documentation/kbuild/kconfig.txt.

"make help" does, though. Possibly the README should point people at that instead of trying to keep a (third?) copy of this info in sync?

Quoted 1 line

Rob

1) If make help is the second copy of this info, and the README is the third, where is the first, master, copy?
2) Doesn't the README have slightly more information on each option than make help, or that the README info is somewhat better to beginners? Perhaps the README entries should first be combined into make help?