From: Roger <rogerable@realtek.com>
To: Chris Ball <chris@printf.net>, Andrew Morton <akpm@linux-foundation.org>
Cc: Lee Jones <lee.jones@linaro.org>,
Samuel Ortiz <sameo@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Maxim Levitsky <maximlevitsky@gmail.com>,
Alex Dubov <oakad@yahoo.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
<linux-kernel@vger.kernel.org>, <linux-mmc@vger.kernel.org>,
<driverdev-devel@linuxdriverproject.org>,
<wei_wang@realsil.com.cn>, <micky_ching@realsil.com.cn>
Subject: Re: [PATCH v4 1/3] mfd: Add realtek USB card reader driver
Date: Mon, 24 Feb 2014 10:56:19 +0800 [thread overview]
Message-ID: <530AB4D3.4090103@realtek.com> (raw)
In-Reply-To: <20140217120326.GC20218@lee--X1>
On 02/17/2014 08:03 PM, Lee Jones wrote:
>>>>>>>> From: Roger Tseng <rogerable@realtek.com>
>>>>>>>>
>>>>>>>> Realtek USB card reader provides a channel to transfer command or data to flash
>>>>>>>> memory cards. This driver exports host instances for mmc and memstick subsystems
>>>>>>>> and handles basic works.
>>>>>>>>
>>>>>>>> Signed-off-by: Roger Tseng <rogerable@realtek.com>
>>>>>>>> ---
>>>>>>>> drivers/mfd/Kconfig | 10 +
>>>>>>>> drivers/mfd/Makefile | 1 +
>>>>>>>> drivers/mfd/rtsx_usb.c | 760 +++++++++++++++++++++++++++++++++++++++++++
>>>>>>>> include/linux/mfd/rtsx_usb.h | 628 +++++++++++++++++++++++++++++++++++
>>>>>>>> 4 files changed, 1399 insertions(+)
>>>>>>>> create mode 100644 drivers/mfd/rtsx_usb.c
>>>>>>>> create mode 100644 include/linux/mfd/rtsx_usb.h
>>>>>>>
>>>>>>> Applied again, thanks.
>>>>>>>
>>>>>> Would you also apply patch 2/3 and 3/3 that to make the device fully
>>>>>> operational for users? Or should they be applied by maintainers of
>>>>>> mmc/memstick subsystems?
>>>>>>
>>>>>> Chris, would you give some comment?
>>>>>
>>>>> I can apply them, but I need the other Maintainer Acks.
>>>>>
>>>>> If they are build orthogonal i.e. there are no build dependencies
>>>>> between them, it's probably better that they go into their associated
>>>>> trees separately.
>>>>>
>>>> I think it would be better to apply them together since the later
>>>> patches really depend on the 1st one,so now we are waiting for Acks
>>> >from mmc/memstick subsystems.
>>>
>>> When you say "depend on", do you mean as a build depenency, or won't
>>> run without the first patch applied?
>>
>> The later 2 patches actually invoke symbols defined in the first
>> patch and won't compile if it is not applied first. The Kconfig
>> changes for the later oness also specified this by "depends on".
>>
>> I'm not sure if this means "build dependency". Sorry for my unclear words.
>
> Yes, that sounds like a build dependency i.e. will not build without
> errors or warnings without the previous patch applied.
>
>>>> But there is no one specified for "memstick/host/" in MAINTAINERS.
>>>> Could anyone else Ack this?
>
> Andrew (CC'ed) has been Acking these thus far.
>
Hi Chris and Andrew,
Would you please help comment PATCH 2/3 and 3/3 (for mmc and memstick,
respectively) or give Acks? Thus we can proceed with applying or
revision if necessary.
next prev parent reply other threads:[~2014-02-24 2:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 10:00 [PATCH v4 0/3] Add modules for realtek USB card reader rogerable
2014-02-12 10:00 ` [PATCH v4 1/3] mfd: Add realtek USB card reader driver rogerable
2014-02-14 9:44 ` Lee Jones
2014-02-17 6:09 ` Roger
2014-02-17 8:22 ` Lee Jones
2014-02-17 9:16 ` Roger
2014-02-17 10:02 ` Lee Jones
2014-02-17 10:24 ` Roger
2014-02-17 12:03 ` Lee Jones
2014-02-24 2:56 ` Roger [this message]
2014-02-24 3:00 ` Chris Ball
2014-03-03 8:48 ` Roger
2014-03-11 3:28 ` Roger
2014-02-12 10:00 ` [PATCH v4 2/3] mmc: Add realtek USB sdmmc host driver rogerable
2014-02-12 10:24 ` Ulf Hansson
2014-02-12 10:00 ` [PATCH v4 3/3] memstick: Add realtek USB memstick " rogerable
2014-03-20 8:38 ` Roger
2014-03-20 23:19 ` Andrew Morton
2014-03-20 23:18 ` Andrew Morton
2014-03-21 6:43 ` Roger
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=530AB4D3.4090103@realtek.com \
--to=rogerable@realtek.com \
--cc=akpm@linux-foundation.org \
--cc=chris@printf.net \
--cc=dan.carpenter@oracle.com \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=maximlevitsky@gmail.com \
--cc=micky_ching@realsil.com.cn \
--cc=oakad@yahoo.com \
--cc=sameo@linux.intel.com \
--cc=ulf.hansson@linaro.org \
--cc=wei_wang@realsil.com.cn \
/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
Powered by JetHome