From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: ppc-dev <linuxppc-dev@ozlabs.org>, paulus@samba.org
Subject: Re: [PATCH] [POWERPC] Remove CONFIG_PCI_LEGACY from some configs
Date: Fri, 28 Mar 2008 16:14:57 +1100 [thread overview]
Message-ID: <20080328161457.f21ec25b.sfr@canb.auug.org.au> (raw)
In-Reply-To: <6B9965AF-F6B7-427E-B1D9-68CBB7540372@kernel.crashing.org>
[-- Attachment #1: Type: text/plain, Size: 919 bytes --]
Hi Kumar,
On Thu, 27 Mar 2008 07:45:06 -0500 Kumar Gala <galak@kernel.crashing.org> wrote:
>
> On Mar 27, 2008, at 12:36 AM, Stephen Rothwell wrote:
> > This will remove some build warnings and doesn't stop us building any
> > drivers that we were building previously with these configs.
> >
> > Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
>
> Doesn't this hide issues on the defconfigs most often built for PPC?
Not sure what you mean. It removes some deprecated interfaces from the
builds for those configs. The only things that use those interfaces are
drivers that none of those configs built. People can still reenable
CONFIG_PCI_LEGACY on powerpc if they want to (and allmodconfig and
allyesconfig will do that).
So, the net effect is some less warnings in our builds.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2008-03-28 5:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 5:36 [PATCH] [POWERPC] Remove CONFIG_PCI_LEGACY from some configs Stephen Rothwell
2008-03-27 12:45 ` Kumar Gala
2008-03-28 5:14 ` Stephen Rothwell [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=20080328161457.f21ec25b.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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