From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [AT91 PULL v2] defconfig pull request
Date: Thu, 24 Nov 2011 15:00:52 +0000 [thread overview]
Message-ID: <201111241500.52871.arnd@arndb.de> (raw)
In-Reply-To: <20111124140658.GH15531@game.jcrosoft.org>
On Thursday 24 November 2011, Jean-Christophe PLAGNIOL-VILLARD wrote:
> Hi,
>
> this a split of the previous pull request that containt onlythe
> defconfig
>
> the gpio part will for 3.2
>
> this pull request will introduce a defconfig per soc with all machine
> enabled (today we can not compile multiple soc together we work on it)
>
> This will allow us to check that we break no board
>
> v2:
> update patch as sugested by Arnd
Ok, pulled into 'fixes' now. I ended up rebasing to v3.2-rc2 to have a
clean base instead of a random point between rc2 and rc3.
Arnd
prev parent reply other threads:[~2011-11-24 15:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-02 15:58 [AT91 PULL] defconfig pullrequest Jean-Christophe PLAGNIOL-VILLARD
2011-11-09 14:41 ` Jean-Christophe PLAGNIOL-VILLARD
2011-11-09 16:01 ` Olof Johansson
2011-11-10 0:37 ` Jean-Christophe PLAGNIOL-VILLARD
2011-11-10 1:29 ` Jean-Christophe PLAGNIOL-VILLARD
2011-11-10 1:35 ` Olof Johansson
2011-11-23 14:35 ` Nicolas Ferre
2011-11-23 21:15 ` Arnd Bergmann
2011-11-24 10:47 ` Jean-Christophe PLAGNIOL-VILLARD
2011-11-24 13:58 ` [PATCH 1/3] ARM: at91: rename defconfig files appropriately Jean-Christophe PLAGNIOL-VILLARD
2011-11-24 13:58 ` [PATCH 2/3] ARM: at91: refresh soc defconfig files for 3.2 Jean-Christophe PLAGNIOL-VILLARD
2011-11-24 13:58 ` [PATCH 3/3] ARM: at91: enable additional boards in existing soc defconfig files Jean-Christophe PLAGNIOL-VILLARD
[not found] ` <20111124140658.GH15531@game.jcrosoft.org>
2011-11-24 15:00 ` Arnd Bergmann [this message]
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=201111241500.52871.arnd@arndb.de \
--to=arnd@arndb.de \
--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).