From: Lee Jones <lee.jones@linaro.org>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: 冯锐 <rui_feng@realsil.com.cn>, "arnd@arndb.de" <arnd@arndb.de>,
"ulf.hansson@linaro.org" <ulf.hansson@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"ricky_wu@realtek.com" <ricky_wu@realtek.com>,
"bristot@redhat.com" <bristot@redhat.com>,
"Perry.Yuan@dell.com" <Perry.Yuan@dell.com>
Subject: Re: 答复: [PATCH v7,1/2] misc: rtsx: Move Realtek Card Reader Driver to misc
Date: Wed, 29 Nov 2017 09:45:09 +0000 [thread overview]
Message-ID: <20171129094509.5cxqrmcbo5q4bgdo@dell> (raw)
In-Reply-To: <20171128154254.GA7978@kroah.com>
On Tue, 28 Nov 2017, gregkh@linuxfoundation.org wrote:
> On Tue, Nov 28, 2017 at 09:33:23AM +0000, Lee Jones wrote:
> > On Tue, 28 Nov 2017, 冯锐 wrote:
> >
> > > > On Tue, 28 Nov 2017, Lee Jones wrote:
> > > >
> > > > > On Tue, 28 Nov 2017, Perry.Yuan@dell.com wrote:
> > > > > > Hi Greg.
> > > > > > The Patches have been tested basing on V4.15-rc1 successfully.
> > > > > > The sdcard function is working well.
> > > > >
> > > > > Not sure why you're a) top posting, b) doing so with an incompatible
> > > > > email client and c) sending this to Greg?
> > > > >
> > > > > There doesn't appear to be a Memstick Maintainer at the moment, which
> > > > > means we have all of the Maintainer Acks we need (Arnd Acked in Greg's
> > > > > place for Misc) to apply this patch.
> > > > >
> > > > > If no one objects, I plan to take this through the MFD tree and
> > > > > provide everyone else with a pull-request which they can do with as
> > > > > they see fit.
> > > >
> > > > OOI, where is [PATCH 2/2]? Are there dependencies?
> > > >
> > > [PATCH 2/2] is here:
> > > https://patchwork.kernel.org/patch/10076009/
> > > Because after the drivers moved from misc to mfd, the [PATCH 2/2] is only related to misc, so I send it without cc you.
> > > If needed, I will cc you in next version.
> >
> > Please resubmit the patch-set with me in Cc and I will pick them up.
>
> Can I just get an ack and I can take both of them? Or if you want to do
> it as it touches mfd, I can provide my ack for both of these:
I'd prefer to take them through my tree and send out a pull-request.
Unless of course you're willing to do the same? In which case:
Acked-by: Lee Jones <lee.jones@linaro.org>
> Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>
> This back-and-forth has gone on a long time :)
We've been waiting for Acks mainly, and one of the patches from this
submission wasn't sent to me, hence the request above.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2017-11-29 9:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 7:34 rui_feng
2017-11-28 2:53 ` Perry.Yuan
2017-11-28 8:10 ` Lee Jones
2017-11-28 8:11 ` Lee Jones
2017-11-28 8:23 ` 答复: " 冯锐
2017-11-28 9:33 ` Lee Jones
2017-11-28 15:42 ` gregkh
2017-11-29 9:45 ` Lee Jones [this message]
2017-11-29 9:52 ` 答复: " 冯锐
2017-11-29 10:12 ` Lee Jones
2017-11-29 10:13 ` Lee Jones
2017-11-28 8:40 ` 冯锐
2017-11-28 8:31 ` 冯锐
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=20171129094509.5cxqrmcbo5q4bgdo@dell \
--to=lee.jones@linaro.org \
--cc=Perry.Yuan@dell.com \
--cc=arnd@arndb.de \
--cc=bristot@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ricky_wu@realtek.com \
--cc=rui_feng@realsil.com.cn \
--cc=ulf.hansson@linaro.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
all inboxes | Powered by JetHome®