From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Zhang Wei-r63237 <Wei.Zhang@freescale.com>,
linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>,
linux-kernel@vger.kernel.org
Subject: Re: Please pull from 'for_paulus' branch of powerpc
Date: Thu, 29 Jun 2006 19:10:52 +1000 [thread overview]
Message-ID: <1151572252.28229.21.camel@localhost.localdomain> (raw)
In-Reply-To: <BDF5A6D5-E7F4-4CDF-9B34-13A66A0B7C99@kernel.crashing.org>
> > Even though other 86xx platforms have no these PCI chips, these
> > codes will not take effect.
>
> Its code bloat for systems that dont need it.
Well... it depends :) If it's totally unlikely to ever have this chip in
those platforms, then yes. But if it's common enough, it's fair to have
the quirk in a generic place (provided that Whang is right and the fixup
is indeed the same for all 86xx platforms)
Ben.
next prev parent reply other threads:[~2006-06-29 9:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-29 3:33 Please pull from 'for_paulus' branch of powerpc Zhang Wei-r63237
2006-06-29 5:08 ` Kumar Gala
2006-06-29 9:10 ` Benjamin Herrenschmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-29 6:13 Zhang Wei-r63237
2006-06-28 6:26 Zhang Wei-r63237
2006-06-28 13:19 ` Kumar Gala
2006-06-28 6:01 Kumar Gala
2006-06-28 22:44 ` Jon Loeliger
2006-05-04 21:28 Kumar Gala
2006-05-04 22:09 ` Segher Boessenkool
2006-05-04 22:10 ` Kumar Gala
2006-05-04 22:36 ` Segher Boessenkool
2006-05-04 22:49 ` Paul Mackerras
2006-05-05 4:59 ` Kumar Gala
2006-04-04 21:14 Kumar Gala
2006-04-05 0:28 ` Stephen Rothwell
2006-04-05 1:23 ` Kumar Gala
2006-04-05 3:05 ` Stephen Rothwell
2006-04-05 4:33 ` Kumar Gala
2006-03-31 5:43 Kumar Gala
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=1151572252.28229.21.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=Wei.Zhang@freescale.com \
--cc=galak@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.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