linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Nathan Lynch <ntl@pobox.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH 2/2] move pSeries nvram code to neutral location
Date: Wed, 24 Jan 2007 19:04:53 -0600	[thread overview]
Message-ID: <20070125010453.GN16486@localdomain> (raw)
In-Reply-To: <5FE26120-8464-4431-8F0D-EEBB4B896419@kernel.crashing.org>

Segher Boessenkool wrote:
> >Move arch/powerpc/platforms/pseries/nvram.c to
> >arch/powerpc/sysdev/rtas_nvram.c so other platforms with RTAS support
> >for manipulating nvram can use it.
> >
> >Add a RTAS_NVRAM Kconfig option which triggers the build of
> >arch/powerpc/sysdev/rtas_nvram.o.
> >
> >Select RTAS_NVRAM for pSeries and Maple platforms.
> 
> The patch seems to select it for pSeries and iSeries, instead?

Aw crap, evidently damage introduced when rebasing (Kconfig files seem
so fragile in this regard).

> >+config RTAS_NVRAM
> >+	bool
> >+	default n
> 
> No need for "default n", all defaults are "n" by default ;-)

Duh, will fix.


> >--- a/arch/powerpc/platforms/pseries/nvram.c
> >+++ /dev/null
> 
> >--- /dev/null
> >+++ b/arch/powerpc/sysdev/rtas_nvram.c
> 
> You can do a "git diff -M" -- that way, we can see that you're
> not trying to sneak in any changes ;-) (and it makes you patch
> much more legible and smaller, too).

Thanks for the tip, I'll try it that way.

      reply	other threads:[~2007-01-25  1:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-25  0:18 [PATCH 2/2] move pSeries nvram code to neutral location Nathan Lynch
2007-01-25  0:57 ` Segher Boessenkool
2007-01-25  1:04   ` Nathan Lynch [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=20070125010453.GN16486@localdomain \
    --to=ntl@pobox.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.org \
    --cc=segher@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).