From: Linus Walleij <linus.walleij@linaro.org>
To: Wei Yongjun <weiyj.lk@gmail.com>, Lee Jones <lee.jones@linaro.org>
Cc: Alexandre Courbot <gnurou@gmail.com>, Keerthy <j-keerthy@ti.com>,
Wei Yongjun <weiyongjun1@huawei.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH -next] gpio: lp873x: Use devm_gpiochip_add_data() for gpio registration
Date: Tue, 13 Sep 2016 10:34:42 +0200 [thread overview]
Message-ID: <CACRpkdZ3-H5ekHn2p3owhEmpBFLkWxPUJP_a2jgq_DUz2D+Dbw@mail.gmail.com> (raw)
In-Reply-To: <CACRpkdZnfUfPj19Wts1pd5Nxqi-Zp+kTxZCvXrsSM6DjjJpHUQ@mail.gmail.com>
On Tue, Sep 13, 2016 at 10:27 AM, Linus Walleij
<linus.walleij@linaro.org> wrote:
> On Sat, Sep 10, 2016 at 2:04 PM, Wei Yongjun <weiyj.lk@gmail.com> wrote:
>
>> From: Wei Yongjun <weiyongjun1@huawei.com>
>>
>> Use devm_gpiochip_add_data() for GPIO registration and remove the need
>> of driver callback .remove.
>>
>> Signed-off-by: Wei Yongjun <weiyongjun1@huawei.com>
>> ---
>> drivers/gpio/gpio-lp873x.c | 12 +-----------
>
> This patch is in Lee's MFD tree, either send it to him so he can merge it
> or defer to after the merge window and I can take it.
>
> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
>
> (Yeah I know I can also pull in Lee's immutable branch, just
> want to avoid the complexity.)
Changed my mind: pulled in Lee's immutable branch and applied
this on top. Much better idea. Thanks both Wei and Lee.
Yours,
Linus Walleij
next prev parent reply other threads:[~2016-09-13 8:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-10 12:04 [PATCH -next] gpio: lp873x: Use devm_gpiochip_add_data() for gpio registration Wei Yongjun
2016-09-13 8:27 ` Linus Walleij
2016-09-13 8:34 ` Linus Walleij [this message]
2016-09-13 8:45 ` Lee Jones
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=CACRpkdZ3-H5ekHn2p3owhEmpBFLkWxPUJP_a2jgq_DUz2D+Dbw@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=gnurou@gmail.com \
--cc=j-keerthy@ti.com \
--cc=lee.jones@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=weiyj.lk@gmail.com \
--cc=weiyongjun1@huawei.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).