All of lore.kernel.org
 help / color / mirror / Atom feed
From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] AT91 Kconfig rework
Date: Mon, 16 Nov 2009 16:30:51 +0100	[thread overview]
Message-ID: <4B01702B.4080107@atmel.com> (raw)

Hi Russell,

This is AT91 Kconfig rework for next merge window. After 
discussing it on the mailing-list and Ack by Andrew Victor, I 
send you this patchset. You can pull it from:

  git://github.com/at91linux/linux-2.6-at91.git for-rmk

And you will receive:

Jean-Christophe PLAGNIOL-VILLARD (2):
      at91: remove not needed depends on
      at91: Kconfig simplification

Nicolas Ferre (2):
      at91: at91sam9g20ek modify dual slot evaluation kit
      atmel_lcdfb Kconfig: remove long dependency line

 arch/arm/mach-at91/Kconfig                     |  107 ++++++++++++++----------
 arch/arm/mach-at91/board-sam9g20ek-2slot-mmc.c |   23 ++++--
 arch/avr32/Kconfig                             |    1 +
 drivers/video/Kconfig                          |    5 +-
 4 files changed, 83 insertions(+), 53 deletions(-)

The patch
"at91: at91sam9g20ek modify dual slot evaluation kit"
is also already sent directly to Linus for .32-final (not 
sure it can reach). Anyway, I guess that git can handle 
that...

Thanks. Best regards,
-- 
Nicolas Ferre

WARNING: multiple messages have this Message-ID (diff)
From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	"'linux-arm-kernel@lists.infradead.org'" 
	<linux-arm-kernel@lists.infradead.org>
Cc: Andrew Victor <linux@maxim.org.za>,
	Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Subject: [GIT PULL] AT91 Kconfig rework
Date: Mon, 16 Nov 2009 16:30:51 +0100	[thread overview]
Message-ID: <4B01702B.4080107@atmel.com> (raw)

Hi Russell,

This is AT91 Kconfig rework for next merge window. After 
discussing it on the mailing-list and Ack by Andrew Victor, I 
send you this patchset. You can pull it from:

  git://github.com/at91linux/linux-2.6-at91.git for-rmk

And you will receive:

Jean-Christophe PLAGNIOL-VILLARD (2):
      at91: remove not needed depends on
      at91: Kconfig simplification

Nicolas Ferre (2):
      at91: at91sam9g20ek modify dual slot evaluation kit
      atmel_lcdfb Kconfig: remove long dependency line

 arch/arm/mach-at91/Kconfig                     |  107 ++++++++++++++----------
 arch/arm/mach-at91/board-sam9g20ek-2slot-mmc.c |   23 ++++--
 arch/avr32/Kconfig                             |    1 +
 drivers/video/Kconfig                          |    5 +-
 4 files changed, 83 insertions(+), 53 deletions(-)

The patch
"at91: at91sam9g20ek modify dual slot evaluation kit"
is also already sent directly to Linus for .32-final (not 
sure it can reach). Anyway, I guess that git can handle 
that...

Thanks. Best regards,
-- 
Nicolas Ferre



             reply	other threads:[~2009-11-16 15:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-16 15:30 Nicolas Ferre [this message]
2009-11-16 15:30 ` [GIT PULL] AT91 Kconfig rework Nicolas Ferre
2009-11-19 23:01 ` Russell King - ARM Linux
2009-11-19 23:01   ` Russell King - ARM Linux
2009-11-20 12:42   ` Nicolas Ferre
2009-11-20 12:42     ` 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=4B01702B.4080107@atmel.com \
    --to=nicolas.ferre@atmel.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 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.