From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: Arnd Bergmann <arnd@arndb.de>, "arm@kernel.org" <arm@kernel.org>,
Bo Shen <voice.shen@atmel.com>, Mark Brown <broonie@kernel.org>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] MAINTAINERS: add atmel ssc driver maintainer entry
Date: Wed, 22 Oct 2014 05:32:56 +0800 [thread overview]
Message-ID: <20141021213256.GA27750@kroah.com> (raw)
In-Reply-To: <544672A6.9090101@atmel.com>
On Tue, Oct 21, 2014 at 04:50:14PM +0200, Nicolas Ferre wrote:
> On 29/09/2014 10:36, Nicolas Ferre :
> > On 28/09/2014 03:57, Bo Shen :
> >> Signed-off-by: Bo Shen <voice.shen@atmel.com>
> >
> > Sure:
> > Acked-by: Nicolas Ferre <nicolas.ferre@atmel.com>
> >
> > Thanks.
>
> Greg or Arnd,
>
> This MAINTAINER's update didn't make it during merge window (on the
> other hand, I didn't build a pull-request with it neither...).
>
> Do you want that I take it in one of my "fixes" pull-requests to arm-soc
> for 3.18 or do you feel like taking the patch directly? I think it makes
> sense to not wait for the 3.19 for this kind of useful information.
Feel free to take it in one of your "fixes" pull requests.
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: gregkh@linuxfoundation.org (Greg Kroah-Hartman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] MAINTAINERS: add atmel ssc driver maintainer entry
Date: Wed, 22 Oct 2014 05:32:56 +0800 [thread overview]
Message-ID: <20141021213256.GA27750@kroah.com> (raw)
In-Reply-To: <544672A6.9090101@atmel.com>
On Tue, Oct 21, 2014 at 04:50:14PM +0200, Nicolas Ferre wrote:
> On 29/09/2014 10:36, Nicolas Ferre :
> > On 28/09/2014 03:57, Bo Shen :
> >> Signed-off-by: Bo Shen <voice.shen@atmel.com>
> >
> > Sure:
> > Acked-by: Nicolas Ferre <nicolas.ferre@atmel.com>
> >
> > Thanks.
>
> Greg or Arnd,
>
> This MAINTAINER's update didn't make it during merge window (on the
> other hand, I didn't build a pull-request with it neither...).
>
> Do you want that I take it in one of my "fixes" pull-requests to arm-soc
> for 3.18 or do you feel like taking the patch directly? I think it makes
> sense to not wait for the 3.19 for this kind of useful information.
Feel free to take it in one of your "fixes" pull requests.
thanks,
greg k-h
next prev parent reply other threads:[~2014-10-21 21:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-28 1:57 [PATCH 1/2] MAINTAINERS: add atmel ssc driver maintainer entry Bo Shen
2014-09-28 1:57 ` Bo Shen
2014-09-28 1:57 ` Bo Shen
2014-09-28 1:57 ` [PATCH 2/2] MAINTAINERS: add atmel audio alsa " Bo Shen
2014-09-28 1:57 ` Bo Shen
2014-09-28 1:57 ` Bo Shen
2014-09-28 10:41 ` Mark Brown
2014-09-28 10:41 ` Mark Brown
2014-09-29 8:36 ` Nicolas Ferre
2014-09-29 8:36 ` Nicolas Ferre
2014-09-29 8:36 ` Nicolas Ferre
2014-09-29 8:36 ` [PATCH 1/2] MAINTAINERS: add atmel ssc " Nicolas Ferre
2014-09-29 8:36 ` Nicolas Ferre
2014-09-29 8:36 ` Nicolas Ferre
2014-10-21 14:50 ` Nicolas Ferre
2014-10-21 14:50 ` Nicolas Ferre
2014-10-21 14:50 ` Nicolas Ferre
2014-10-21 21:32 ` Greg Kroah-Hartman [this message]
2014-10-21 21:32 ` Greg Kroah-Hartman
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=20141021213256.GA27750@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alsa-devel@alsa-project.org \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--cc=voice.shen@atmel.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 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.