From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Jamie Iles <jamie@jamieiles.com>
Cc: netdev@vger.kernel.org, Nicolas Ferre <nicolas.ferre@atmel.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/8] macb: unify at91 and avr32 platform data
Date: Fri, 11 Mar 2011 02:41:40 +0100 [thread overview]
Message-ID: <20110311014140.GI9351@game.jcrosoft.org> (raw)
In-Reply-To: <20110310131724.GG6198@pulham.picochip.com>
On 13:17 Thu 10 Mar , Jamie Iles wrote:
> On Thu, Mar 10, 2011 at 02:06:04PM +0100, Nicolas Ferre wrote:
> > On 3/10/2011 11:10 AM, Jamie Iles :
> > > --- a/drivers/net/macb.c
> > > +++ b/drivers/net/macb.c
> > > @@ -18,12 +18,10 @@
> > > #include <linux/netdevice.h>
> > > #include <linux/etherdevice.h>
> > > #include <linux/dma-mapping.h>
> > > +#include <linux/platform_data/macb.h>
> > > #include <linux/platform_device.h>
> > > #include <linux/phy.h>
> > >
> > > -#include <mach/board.h>
> > > -#include <mach/cpu.h>
> >
> > I did not bouble check but do we need no more cpu_is_ macros?
>
> No, I couldn't see any in there and it builds for all of the AT91
> targets and all of the AVR32 ones that I tried. I can't see any macros
> in there that are likely to use cpu_is_* internally either.
keep as we need to remove the #ifdef AT91 to cpu_is
I've patch for this
Best Regards,
J.
next prev parent reply other threads:[~2011-03-11 1:41 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 10:10 [PATCH 0/8] macb: add support for Cadence GEM Jamie Iles
2011-03-10 10:10 ` [PATCH 1/8] macb: unify at91 and avr32 platform data Jamie Iles
2011-03-10 13:06 ` Nicolas Ferre
2011-03-10 13:17 ` Jamie Iles
2011-03-11 1:41 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2011-03-11 8:56 ` Jamie Iles
2011-03-11 12:52 ` Jean-Christophe PLAGNIOL-VILLARD
2011-03-11 13:25 ` Jamie Iles
2011-03-11 13:37 ` Jean-Christophe PLAGNIOL-VILLARD
2011-03-11 13:53 ` Jamie Iles
2011-03-10 10:10 ` [PATCH 2/8] macb: detect hclk presence from " Jamie Iles
2011-03-10 10:15 ` Russell King - ARM Linux
2011-03-10 11:41 ` Jamie Iles
2011-03-10 11:45 ` Jamie Iles
2011-03-11 1:44 ` Jean-Christophe PLAGNIOL-VILLARD
2011-03-11 8:54 ` Jamie Iles
2011-03-11 12:47 ` Jean-Christophe PLAGNIOL-VILLARD
2011-03-11 13:08 ` Jamie Iles
2011-03-11 13:39 ` Jean-Christophe PLAGNIOL-VILLARD
2011-03-10 10:10 ` [PATCH 3/8] macb: convert printk to pr_ and friends Jamie Iles
2011-03-10 22:48 ` Joe Perches
2011-03-11 0:09 ` Jamie Iles
2011-03-11 12:53 ` Jean-Christophe PLAGNIOL-VILLARD
2011-03-10 10:10 ` [PATCH 4/8] macb: initial support for Cadence GEM Jamie Iles
2011-03-11 13:14 ` Jean-Christophe PLAGNIOL-VILLARD
2011-03-11 13:30 ` Jamie Iles
2011-03-11 13:34 ` Jean-Christophe PLAGNIOL-VILLARD
2011-03-11 14:08 ` Jamie Iles
2011-03-10 10:10 ` [PATCH 5/8] macb: handle HW address registers for GEM devices Jamie Iles
2011-03-10 10:10 ` [PATCH 6/8] macb: support higher rate GEM MDIO clock divisors Jamie Iles
2011-03-10 10:10 ` [PATCH 7/8] macb: support statistics for GEM devices Jamie Iles
2011-03-10 10:10 ` [PATCH 8/8] macb: support data bus widths > 32 bits Jamie Iles
2011-03-11 12:55 ` Jean-Christophe PLAGNIOL-VILLARD
2011-03-11 13:15 ` Jamie Iles
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=20110311014140.GI9351@game.jcrosoft.org \
--to=plagnioj@jcrosoft.com \
--cc=jamie@jamieiles.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@atmel.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;
as well as URLs for NNTP newsgroup(s).