From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: openembedded-devel@lists.openembedded.org,
ulf.samuelsson@atmel.com, marcin@juszkiewicz.com.pl
Subject: Re: [PATCH] linux-2.6.30: add linux4sam patches
Date: Mon, 15 Mar 2010 13:18:06 +0100 [thread overview]
Message-ID: <4B9E257E.3000201@atmel.com> (raw)
In-Reply-To: <1268659726-20887-1-git-send-email-nicolas.ferre@atmel.com>
Le 15/03/2010 14:28, Nicolas Ferre :
> Introduce support for:
>
> + at91sam9260ek
> + at91sam9261ek
> + at91sam9g10ek
> + at91sam9g20ek
> + at91sam9g20ek_2mmc
> + at91sam9g45ekes
> + at91sam9m10ekes
> + at91sam9rlek
> + at91sam9xeek
>
> and apply the Atmel experimental patch series from Linux4sam.org. A different
> SRC_URI is created and the patches are bundled in a patch archive.
>
> AT91 specific bits are removed from the common 2.6.30 rule.
>
> Signed-off-by: Nicolas Ferre <nicolas.ferre@atmel.com>
> ---
> Marcin, what do you think of this patch architecture and URI management?
>
> The defconfig are not included in this patch and shall be sent in another
> patch series.
Of course Ulf, if other patches have to be included after those ones
feel free to add them in another OE patch (I am thinking about NAND
patitions and Kconfig changes).
Bye,
--
Nicolas Ferre
next prev parent reply other threads:[~2010-03-15 12:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-14 23:18 [PATCH 1/2] linux-2.6.30: Add linux4sam patches Ulf Samuelsson
2010-03-14 23:18 ` [PATCH 2/2] conf/checksum.ini: at91 linux + u-boot-2009.11 Ulf Samuelsson
2010-03-15 7:31 ` Frans Meulenbroeks
2010-03-15 6:38 ` [PATCH 1/2] linux-2.6.30: Add linux4sam patches Marcin Juszkiewicz
2010-03-15 13:28 ` [PATCH] linux-2.6.30: add " Nicolas Ferre
2010-03-15 12:18 ` Nicolas Ferre [this message]
2010-03-15 12:46 ` Marcin Juszkiewicz
2010-03-15 16:27 ` Nicolas Ferre
2010-03-15 10:03 ` [PATCH 1/2] linux-2.6.30: Add " Nicolas Ferre
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=4B9E257E.3000201@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=marcin@juszkiewicz.com.pl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=ulf.samuelsson@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.