From: Marek Vasut <marek.vasut@gmail.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Marek Vasut <marek.vasut+renesas@gmail.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: Re: [PATCH V2 3/4] gpio: Add ROHM BD9571MWV-M PMIC GPIO driver
Date: Tue, 25 Apr 2017 20:33:30 +0200 [thread overview]
Message-ID: <4c5e1df7-bde3-a18c-a6db-4a3ae0de2174@gmail.com> (raw)
In-Reply-To: <20170425140113.vnvhyhdgymcnm3tt@dell>
On 04/25/2017 04:01 PM, Lee Jones wrote:
> On Tue, 25 Apr 2017, Marek Vasut wrote:
>
>> On 04/25/2017 02:21 PM, Lee Jones wrote:
>>> On Tue, 25 Apr 2017, Marek Vasut wrote:
>>>
>>>> On 04/25/2017 11:32 AM, Linus Walleij wrote:
>>>>> On Mon, Apr 24, 2017 at 5:21 PM, Marek Vasut <marek.vasut@gmail.com> wrote:
>>>>>
>>>>>> Add driver for the GPIO block in the ROHM BD9571MWV-W MFD PMIC.
>>>>>> This block is pretty trivial and supports setting GPIO direction
>>>>>> as Input/Output and in case of Output, supports setting value.
>>>>>>
>>>>>> Signed-off-by: Marek Vasut <marek.vasut+renesas@gmail.com>
>>>>>> Cc: linux-gpio@vger.kernel.org
>>>>>> Cc: Geert Uytterhoeven <geert+renesas@glider.be>
>>>>>> Cc: Linus Walleij <linus.walleij@linaro.org>
>>>>>> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
>>>>>> ---
>>>>>> V2: Use linux/gpio/driver.h instead of linux/gpio.h
>>>>>
>>>>> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
>>>>>
>>>>> Are you merging this through MFD?
>>>>
>>>> I thought that was a question for Lee initially , IMO it'd make sense if
>>>> this went through one tree.
>>>
>>> Because your mailer is broken, I know have no idea which thread this
>>> mail belongs to. Please fix your mailer to reply 'threaded'.
>>
>> You just were not on CC for the whole series, just the MFD part,
>> probably that was the mistake, sorry. PW links below:
>
> Okay, understood.
>
>> https://patchwork.kernel.org/patch/9696589/
>> https://patchwork.kernel.org/patch/9696591/
>> https://patchwork.kernel.org/patch/9696597/
>> https://patchwork.kernel.org/patch/9696593/
>
> This is not the way we do business.
We?
> If you want me to take them (and
> there is a suitable reason for me to do so i.e. a build-time
> dependency), then you're going to have to submit them again as
> [RESEND]s with me in Cc.
Done
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2017-04-25 18:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170424152130.32410-1-marek.vasut+renesas@gmail.com>
2017-04-24 15:21 ` [PATCH V2 3/4] gpio: Add ROHM BD9571MWV-M PMIC GPIO driver Marek Vasut
2017-04-25 9:32 ` Linus Walleij
2017-04-25 9:35 ` Marek Vasut
2017-04-25 12:21 ` Lee Jones
2017-04-25 13:41 ` Marek Vasut
2017-04-25 14:01 ` Lee Jones
2017-04-25 18:33 ` Marek Vasut [this message]
2017-04-26 8:46 ` Lee Jones
2017-04-27 18:35 ` Marek Vasut
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=4c5e1df7-bde3-a18c-a6db-4a3ae0de2174@gmail.com \
--to=marek.vasut@gmail.com \
--cc=geert+renesas@glider.be \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=marek.vasut+renesas@gmail.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;
as well as URLs for NNTP newsgroup(s).