From: dmitry.torokhov@gmail.com (Dmitry Torokhov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/6] AT91 drivers Kconfig cleanup
Date: Wed, 21 Mar 2012 09:32:12 -0700 [thread overview]
Message-ID: <2721722.1bE9GCKTjd@dtor-d630.eng.vmware.com> (raw)
In-Reply-To: <4F69B159.5030101@atmel.com>
On Wednesday, March 21, 2012 11:45:45 AM Nicolas Ferre wrote:
> On 03/15/2012 05:50 PM, Dmitry Torokhov :
> > 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.
>
> Ok, good: I have "Acknowledgement" by several maintainers: so yes, I
> will send this series via arm-soc.
>
> Is this means that I can add your "Acked-by"?
Yes, please.
Acked-by: Dmitry Torokhov <dtor@mail.ru>
Thanks.
--
Dmitry
WARNING: multiple messages have this Message-ID (diff)
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: Wed, 21 Mar 2012 09:32:12 -0700 [thread overview]
Message-ID: <2721722.1bE9GCKTjd@dtor-d630.eng.vmware.com> (raw)
In-Reply-To: <4F69B159.5030101@atmel.com>
On Wednesday, March 21, 2012 11:45:45 AM Nicolas Ferre wrote:
> On 03/15/2012 05:50 PM, Dmitry Torokhov :
> > 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.
>
> Ok, good: I have "Acknowledgement" by several maintainers: so yes, I
> will send this series via arm-soc.
>
> Is this means that I can add your "Acked-by"?
Yes, please.
Acked-by: Dmitry Torokhov <dtor@mail.ru>
Thanks.
--
Dmitry
next prev parent reply other threads:[~2012-03-21 16:32 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 15:57 [PATCH 0/6] AT91 drivers Kconfig cleanup Nicolas Ferre
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-15 15:57 ` Nicolas Ferre
2012-03-16 3:13 ` Vinod Koul
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-15 15:57 ` Nicolas Ferre
2012-03-21 9:59 ` Ludovic Desroches
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-15 15:57 ` Nicolas Ferre
2012-03-21 10:02 ` Ludovic Desroches
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 ` 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 ` Nicolas Ferre
2012-03-15 15:57 ` [PATCH 6/6] hwrng: Kconfig: remove dependency for atmel-rng driver Nicolas Ferre
2012-03-15 15:57 ` Nicolas Ferre
2012-03-15 23:54 ` Herbert Xu
2012-03-15 23:54 ` Herbert Xu
2012-03-15 16:50 ` [PATCH 0/6] AT91 drivers Kconfig cleanup Dmitry Torokhov
2012-03-15 16:50 ` Dmitry Torokhov
2012-03-21 10:45 ` Nicolas Ferre
2012-03-21 10:45 ` Nicolas Ferre
2012-03-21 16:32 ` Dmitry Torokhov [this message]
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=2721722.1bE9GCKTjd@dtor-d630.eng.vmware.com \
--to=dmitry.torokhov@gmail.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.