From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: linux-arm-kernel@lists.infradead.org, plagnioj@jcrosoft.com,
linux-kernel@vger.kernel.org, ludovic.desroches@atmel.com,
mpm@selenic.com, herbert@gondor.hengli.com.au,
vinod.koul@intel.com, a.zummo@towertech.it
Subject: Re: [PATCH 0/6] AT91 drivers Kconfig cleanup
Date: Thu, 15 Mar 2012 09:50:31 -0700 [thread overview]
Message-ID: <7104123.IANagkT9hm@dtor-d630.eng.vmware.com> (raw)
In-Reply-To: <cover.1331826095.git.nicolas.ferre@atmel.com>
On Thursday, March 15, 2012 04:57:16 PM Nicolas Ferre wrote:
> This is a series which deals with AT91 drivers Kconfig entries. Its goal is
> to remove too restrictive dependencies on SoC names.
> This will allow to add support for newer SoC seamlessly.
>
> One question remains: should I submit those patches through dedicated
> sub-maintainer's git trees or can I queue the whole series in arm-soc?
I'm fine if you queue input piece through arm-soc.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2012-03-15 16:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 15:57 Nicolas Ferre
2012-03-15 15:57 ` [PATCH 1/6] dmaengine: Kconfig: fix Atmel at_hdmac entry Nicolas Ferre
2012-03-16 3:13 ` Vinod Koul
2012-03-15 15:57 ` [PATCH 2/6] mmc: Kconfig: remove choice between at91_mci and atmel-mci Nicolas Ferre
2012-03-21 9:59 ` Ludovic Desroches
2012-03-15 15:57 ` [PATCH 3/6] mmc: atmel-mci: remove the need for CONFIG_MMC_ATMELMCI_DMA Nicolas Ferre
2012-03-21 10:02 ` Ludovic Desroches
2012-03-15 15:57 ` [PATCH 4/6] rtc: Kconfig: remove dependency for AT91 rtc driver Nicolas Ferre
2012-03-15 15:57 ` [PATCH 5/6] Input: Kconfig: remove dependency for atmel_tsadcc driver Nicolas Ferre
2012-03-15 15:57 ` [PATCH 6/6] hwrng: Kconfig: remove dependency for atmel-rng driver Nicolas Ferre
2012-03-15 23:54 ` Herbert Xu
2012-03-15 16:50 ` Dmitry Torokhov [this message]
2012-03-21 10:45 ` [PATCH 0/6] AT91 drivers Kconfig cleanup Nicolas Ferre
2012-03-21 16:32 ` Dmitry Torokhov
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=7104123.IANagkT9hm@dtor-d630.eng.vmware.com \
--to=dmitry.torokhov@gmail.com \
--cc=a.zummo@towertech.it \
--cc=herbert@gondor.hengli.com.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@atmel.com \
--cc=mpm@selenic.com \
--cc=nicolas.ferre@atmel.com \
--cc=plagnioj@jcrosoft.com \
--cc=vinod.koul@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®