From: Gabriel Paubert <paubert@iram.es>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: LinuxPPC <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] Allow selecting mv643xx_eth on Pegasos again
Date: Mon, 18 May 2009 19:33:52 +0200 [thread overview]
Message-ID: <20090518173352.GA11767@iram.es> (raw)
In-Reply-To: <1242617089.18075.25.camel@pasglop>
On Mon, May 18, 2009 at 01:24:49PM +1000, Benjamin Herrenschmidt wrote:
> On Fri, 2009-05-15 at 20:18 +0200, Gabriel Paubert wrote:
> > Since PPC_MUTIPLATFORM was removed, it was impossible to select the
> > driver for mv643xx_eth on the Pegasos. Fix by allowing to select
> > the driver on CHRP platforms; Pegasos is a CHRP platform and the driver
> > will not work wihtout arch/powerpc/platforms/chrp/pegasos_eth.
> >
> > The patch also removes all references to MV64360 config option which
> > no more exists.
> >
> > Signed-off-by: Gabriel Paubert <paubert@iram.es>
>
> Please break that up into 2 different patches. The arch/powerpc one that
> removes the reference from IRQ_ALL_CPUs and the drivers/net/ one which
> should be set to the netdev mailing list.
>
Ok, but I have a doubt about the PPC one, should MV64360 be removed or
changed to MV64X60?
In any case, I can't test it.
Gabriel
next prev parent reply other threads:[~2009-05-18 17:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 18:18 [PATCH] Allow selecting mv643xx_eth on Pegasos again Gabriel Paubert
2009-05-18 3:24 ` Benjamin Herrenschmidt
2009-05-18 17:33 ` Gabriel Paubert [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-05-18 17:37 Gabriel Paubert
2009-05-18 17:48 ` Medve Emilian-EMMEDVE1
2009-05-18 18:47 ` Gabriel Paubert
2009-05-18 20:15 ` Medve Emilian-EMMEDVE1
2009-05-18 22:18 ` Gabriel Paubert
2009-05-18 22:53 ` Medve Emilian-EMMEDVE1
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=20090518173352.GA11767@iram.es \
--to=paubert@iram.es \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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).