public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: Jim Nelson <james4765@verizon.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: More patches to arch/sparc/Kconfig [2 of 5]
Date: Sun, 31 Oct 2004 02:49:53 +0200	[thread overview]
Message-ID: <20041031004953.GK9592@mars.ravnborg.org> (raw)
In-Reply-To: <20041018224429.GH5607@holomorphy.com>

On Mon, Oct 18, 2004 at 03:44:29PM -0700, William Lee Irwin III wrote:
> On Mon, Oct 18, 2004 at 06:41:25PM -0400, Jim Nelson wrote:
> > You may be right about openpromfs.  How's this instead:
> > diff -u  arch/sparc/Kconfig.orig arch/sparc/Kconfig
> > --- arch/sparc/Kconfig.orig	2004-10-16 09:53:49.626021592 -0400
> > +++ arch/sparc/Kconfig	2004-10-18 18:38:05.125374024 -0400
> > @@ -248,7 +248,10 @@
> >  	  -t openpromfs none /proc/openprom".
> >  
> >  	  To compile the /proc/openprom support as a module, choose M here: the
> > -	  module will be called openpromfs.  If unsure, choose M.
> > +	  module will be called openpromfs.
> > +
> > +	  Only choose N if you know in advance that you will not need to modify
> > +	  OpenPROM settings on the running system.
> >  
> >  source "fs/Kconfig.binfmt"
> 
> This looks fine to me.

I took these five aptches in via my tree.
Next time I prefer _all_ patches to be inlined as plain text and
generated so they uses patch -p1 when being applied.

	Sam

      reply	other threads:[~2004-10-30 23:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-18  9:41 More patches to arch/sparc/Kconfig [2 of 5] Jim Nelson
2004-10-18 10:27 ` William Lee Irwin III
2004-10-18 22:41   ` Jim Nelson
2004-10-18 22:44     ` William Lee Irwin III
2004-10-31  0:49       ` Sam Ravnborg [this message]

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=20041031004953.GK9592@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=james4765@verizon.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wli@holomorphy.com \
    /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