From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/3] Add support for mini-box.com picoSAM9G45 board
Date: Wed, 2 Nov 2011 16:06:03 +0000 [thread overview]
Message-ID: <20111102160603.GA12913@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20111102154935.GC7136@game.jcrosoft.org>
On Wed, Nov 02, 2011 at 04:49:35PM +0100, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 14:28 Wed 02 Nov , Russell King - ARM Linux wrote:
> > Before Nicu puts these into the patch system (which is being attempted
> > right now)...
> As announce at the kernel summit no new board for 9gx series will be merged
> except pending one. The new board will have to go via DT.
Well, we now have patches for this board in the patch system:
7148/1? Add picosam9g45 board to 3.1? 14:25:18?
Makefile
7147/1? Add kernel configuration option 3.1? 14:25:17?
for picosam9g45 board
7146/1? Add support for mini-box.com 3.1? 14:25:16?
picoSAM9G45 board
along with these old ones:
6862/1? Add Board Support for Siemens L1 2.6.39-rc1? 04 Apr 2011?
Board
6861/1? Add Board Support for Siemens L0 2.6.39-rc1? 04 Apr 2011?
Board
So, it sounds like I should just discard the three new ones - what about
the old ones? Those too? I've not seen/heard anything further on them.
next prev parent reply other threads:[~2011-11-02 16:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-31 15:53 [PATCH v2 1/3] Add support for mini-box.com picoSAM9G45 board Nicu Pavel
2011-10-31 15:53 ` [PATCH v2 2/3] Add kernel configuration option for picosam9g45 board Nicu Pavel
2011-10-31 15:53 ` [PATCH v2 3/3] Add picosam9g45 board to Makefile Nicu Pavel
2011-11-02 14:28 ` [PATCH v2 1/3] Add support for mini-box.com picoSAM9G45 board Russell King - ARM Linux
2011-11-02 15:49 ` Jean-Christophe PLAGNIOL-VILLARD
2011-11-02 16:06 ` Russell King - ARM Linux [this message]
2011-11-02 18:30 ` Jean-Christophe PLAGNIOL-VILLARD
2011-11-04 15:57 ` Jochen Friedrich
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=20111102160603.GA12913@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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).