linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: plagnioj@jcrosoft.com (Jean-Christophe PLAGNIOL-VILLARD)
To: linux-arm-kernel@lists.infradead.org
Subject: [AT91 PULL] defconfig pullrequest
Date: Wed, 9 Nov 2011 15:41:26 +0100	[thread overview]
Message-ID: <20111109144126.GE31737@game.jcrosoft.org> (raw)
In-Reply-To: <20111102155803.GE7136@game.jcrosoft.org>

HI,

	when do you pull this one?

	can it go to the 3.2?

Best Regards,
J.
On 16:58 Wed 02 Nov     , Jean-Christophe PLAGNIOL-VILLARD wrote:
> HI,
> 
> 	this a split of the previous pull request that containt only the
> 	defconfig
> 
> 	the gpio part will for 3.3
> 
> 	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
> 
> Please pull
> The following changes since commit 5430cfc583fd8ec5e1bb2d211de29b23743122e4:
> 
>   at91: at91-ohci: configure overcurrent pins as input GPIOs (2011-09-07 17:15:19 +0200)
> 
> are available in the git repository at:
>   git://github.com/at91linux/linux-at91.git j/for-arnd-defconfig
> 
> Jean-Christophe PLAGNIOL-VILLARD (4):
>       ARM: at91: rename at91sam9rlek_defconfig to at91sam9rl_defconfig
>       ARM: at91: rename at91cap9adk_defconfig to at91cap9_defconfig
>       ARM: at91: rename at91sam9g20ek_defconfig to at91sam9g20_defconfig
>       ARM: at91: rename at91sam9260ek_defconfig to at91sam9260_defconfig
> 
>  .../{at91cap9adk_defconfig => at91cap9_defconfig}  |    5 -----
>  ...91sam9260ek_defconfig => at91sam9260_defconfig} |   14 ++++++++++----
>  ...91sam9g20ek_defconfig => at91sam9g20_defconfig} |   19 ++++++++++---------
>  ...at91sam9rlek_defconfig => at91sam9rl_defconfig} |    5 -----
>  4 files changed, 20 insertions(+), 23 deletions(-)
>  rename arch/arm/configs/{at91cap9adk_defconfig => at91cap9_defconfig} (95%)
>  rename arch/arm/configs/{at91sam9260ek_defconfig => at91sam9260_defconfig} (89%)
>  rename arch/arm/configs/{at91sam9g20ek_defconfig => at91sam9g20_defconfig} (93%)
>  rename arch/arm/configs/{at91sam9rlek_defconfig => at91sam9rl_defconfig} (94%)
> 
> Best Regarfds,
> J.

  reply	other threads:[~2011-11-09 14:41 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 [this message]
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                 ` [AT91 PULL v2] defconfig pull request Arnd Bergmann

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=20111109144126.GE31737@game.jcrosoft.org \
    --to=plagnioj@jcrosoft.com \
    --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).