From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 10/11] arm at91sam9260: Add missing AT91SAM_ETX2_ETX3_ALTERNATIVE define
Date: Fri, 9 Dec 2011 11:45:42 +0100 [thread overview]
Message-ID: <20111209104542.GM23884@game.jcrosoft.org> (raw)
In-Reply-To: <20111209101551.GF27267@pengutronix.de>
On 11:15 Fri 09 Dec , Sascha Hauer wrote:
> On Fri, Dec 09, 2011 at 06:33:08AM +0100, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > On 15:20 Thu 08 Dec , Jean-Christophe PLAGNIOL-VILLARD wrote:
> > > On 13:53 Wed 07 Dec , Sascha Hauer wrote:
> > > > Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> > > > ---
> > > > arch/arm/mach-at91/include/mach/board.h | 1 +
> > > > 1 files changed, 1 insertions(+), 0 deletions(-)
> > > >
> > > > diff --git a/arch/arm/mach-at91/include/mach/board.h b/arch/arm/mach-at91/include/mach/board.h
> > > > index 546fe90..5e23688 100644
> > > > --- a/arch/arm/mach-at91/include/mach/board.h
> > > > +++ b/arch/arm/mach-at91/include/mach/board.h
> > > > @@ -51,6 +51,7 @@ void at91_add_device_nand(struct atmel_nand_data *data);
> > > > #define AT91SAM_ETHER_MII (0 << 0)
> > > > #define AT91SAM_ETHER_RMII (1 << 0)
> > > > #define AT91SAM_ETHER_FORCE_LINK (1 << 1)
> > > > +#define AT91SAM_ETX2_ETX3_ALTERNATIVE (2 << 0
> > > this will not work too
> > >
> > > (1 << 1) = (1 << 0)
> > btw where does this come from
> >
> > I see no patch about it on the ML at All
>
> Sorry, I realized after the fact that Michael hasn't Cced the mailing
> list. I owe you a beer.
good tks
can he post them for review at least
because I don't like too much this new flags
and expect all the soc will updated
Best Regards,
J.
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2011-12-09 10:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 12:52 [PATCH] compile (and warning) fixes for -next Sascha Hauer
2011-12-07 12:52 ` [PATCH 01/11] mci s3c: remove unused code Sascha Hauer
2011-12-07 12:52 ` [PATCH 02/11] memory: do not try to reserve iomem on sandbox Sascha Hauer
2011-12-07 12:52 ` [PATCH 03/11] remove unused Kconfig variable HAS_CFI Sascha Hauer
2011-12-07 12:53 ` [PATCH 04/11] fix underscore count in bss_start/bss_stop Sascha Hauer
2011-12-07 12:53 ` [PATCH 05/11] console_simple: fix compiler warning Sascha Hauer
2011-12-07 12:53 ` [PATCH 06/11] net macb: remove unused variable Sascha Hauer
2011-12-07 13:19 ` Jean-Christophe PLAGNIOL-VILLARD
2011-12-07 12:53 ` [PATCH 07/11] pxa: add type to Kconfig choice Sascha Hauer
2011-12-07 12:53 ` [PATCH 08/11] ft_build: temporarily disable bootm oftree support Sascha Hauer
2011-12-07 12:53 ` [PATCH 09/11] arm eukrea boards: fix breakage after mach-types update Sascha Hauer
2011-12-07 12:53 ` [PATCH 10/11] arm at91sam9260: Add missing AT91SAM_ETX2_ETX3_ALTERNATIVE define Sascha Hauer
2011-12-08 14:20 ` Jean-Christophe PLAGNIOL-VILLARD
2011-12-09 5:33 ` Jean-Christophe PLAGNIOL-VILLARD
2011-12-09 10:15 ` Sascha Hauer
2011-12-09 10:45 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2011-12-07 12:53 ` [PATCH 11/11] x86: Fix linker script for magic vars Sascha Hauer
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=20111209104542.GM23884@game.jcrosoft.org \
--to=plagnioj@jcrosoft.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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