public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Patrick Ringl <patrick_@freenet.de>
To: linux-kernel@vger.kernel.org
Cc: torvalds@osdl.org, linux-kbuild@vger.kernel.org,
	Roman Zippel <zippel@linux-m68k.org>,
	Sam Ravnborg <sam@ravnborg.org>
Subject: PATCH: README - Fix misleading pointer to the defconf directory [NEW]
Date: Fri, 12 Jun 2009 13:58:36 +0200	[thread overview]
Message-ID: <4A3242EC.7020602@freenet.de> (raw)
In-Reply-To: <4A321A3C.6030400@gmx.de>

Hello again,

after Arnd's short review and appropriate suggestions of change (thank 
you), here is an updated version of my earlier patch:


Signed-off-by: Patrick Ringl <patrick_@freenet.de>

<---->

--- linux.orig/README	2009-06-10 05:05:27.000000000 +0200
+++ linux/README	2009-06-12 13:47:38.000000000 +0200
@@ -175,7 +175,15 @@
  			   Like above, but avoids cluttering the screen
  			   with questions already answered.
  	"make defconfig"   Create a ./.config file by using the default
-			   symbol values from arch/$ARCH/defconfig.
+			   symbol values from either arch/$ARCH/defconfig
+			   or arch/$ARCH/configs/${PLATFORM}_defconfig,
+			   depending on the architecture.
+	"make ${PLATFORM}_defconfig"
+			   Create a ./.config file by using the default
+			   symbol values from
+			   arch/$ARCH/configs/${PLATFORM}_defconfig.
+			   Use "make help" to get a list of all available
+			   platforms of your architecture.
  	"make allyesconfig"
  			   Create a ./.config file by setting symbol
  			   values to 'y' as much as possible.

<---->


regards,
Patrick

  parent reply	other threads:[~2009-06-12 11:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-12  9:05 PATCH: README - Fix misleading pointer to the defconf directory Patrick Ringl
2009-06-12  9:50 ` Arnd Bergmann
2009-06-12 10:07   ` Patrick Ringl
2009-06-12 11:58 ` Patrick Ringl [this message]
2009-06-14 20:20   ` PATCH: README - Fix misleading pointer to the defconf directory [NEW] Sam Ravnborg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A3242EC.7020602@freenet.de \
    --to=patrick_@freenet.de \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=torvalds@osdl.org \
    --cc=zippel@linux-m68k.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox