From: Linus Walleij <linus.walleij@linaro.org>
To: qiujiang <qiujiang@huawei.com>, Jamie Iles <jamie@jamieiles.com>,
Alan Tull <atull@altera.com>
Cc: Alexandre Courbot <gnurou@gmail.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
linuxarm@huawei.com, haifeng.wei@huawei.com,
charles.chenxin@huawei.com
Subject: Re: [PATCH v5 0/3] "gpio: designware: add gpio-signaled acpi event support for power button"
Date: Wed, 9 Mar 2016 09:26:10 +0700 [thread overview]
Message-ID: <CACRpkdZ6Uodt-WTrXjCmaGNQLMChRVXOzKLeGf4JoNtuTvNCGw@mail.gmail.com> (raw)
In-Reply-To: <1457077474-124064-1-git-send-email-qiujiang@huawei.com>
On Fri, Mar 4, 2016 at 2:44 PM, qiujiang <qiujiang@huawei.com> wrote:
> This patchset adds gpio-signaled acpi events support for power button on hisilicon
> D02 board.
>
> The three patches respectively:
> - convert device node to fwnode
> - add acpi binding
> - add gpio-signaled acpi event support
>
> This patchset is based on
> https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-gpio.git
> branch "devel"
>
> Changes v4 -> v5:
> - split into three patchs
> - add Andy's ACKs
>
> Changes v3 -> v4:
> - re-organize this two patchs by Andy's suggestion
>
> Changes v2 -> v3:
> - fixed the build error reported by Kbuild test robot
>
> Changes v1 -> v2:
> - rebase to branch "devel" of Linus Walleij's repository
> - split in two patch as suggested by Andy S
> - add Mika's ACKs
>
> qiujiang (3):
> gpio: designware: convert device node to fwnode
> gpio: designware: add acpi binding
> gpio: designware: add gpio-signaled acpi event support
I noticed that the original driver authors Jamie and Alan have not been
properly CC:ed on this patch. Jamie, Alan: can you look at this and
ACK it if you like what you see?
Yours,
Linus Walleij
next prev parent reply other threads:[~2016-03-09 2:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 7:44 [PATCH v5 0/3] "gpio: designware: add gpio-signaled acpi event support for power button" qiujiang
2016-03-04 7:44 ` [PATCH v5 1/3] gpio: designware: convert device node to fwnode qiujiang
2016-03-10 19:09 ` Alan Tull
2016-03-10 20:27 ` Andy Shevchenko
2016-03-11 0:48 ` Jiang Qiu
2016-03-15 12:56 ` Jiang Qiu
2016-03-23 11:41 ` Jiang Qiu
2016-03-23 16:20 ` Alan Tull
2016-03-24 1:24 ` Jiang Qiu
2016-03-11 0:44 ` Jiang Qiu
2016-03-22 10:38 ` Linus Walleij
2016-03-22 15:55 ` Mika Westerberg
2016-03-04 7:44 ` [PATCH v5 2/3] gpio: designware: add acpi binding qiujiang
2016-03-10 20:30 ` Andy Shevchenko
2016-03-04 7:44 ` [PATCH v5 3/3] gpio: designware: add gpio-signaled acpi event support qiujiang
2016-03-10 20:31 ` Andy Shevchenko
2016-03-09 2:26 ` Linus Walleij [this message]
2016-03-10 20:10 ` [PATCH v5 0/3] "gpio: designware: add gpio-signaled acpi event support for power button" Alan Tull
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=CACRpkdZ6Uodt-WTrXjCmaGNQLMChRVXOzKLeGf4JoNtuTvNCGw@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=andy.shevchenko@gmail.com \
--cc=atull@altera.com \
--cc=charles.chenxin@huawei.com \
--cc=gnurou@gmail.com \
--cc=haifeng.wei@huawei.com \
--cc=jamie@jamieiles.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mika.westerberg@linux.intel.com \
--cc=qiujiang@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).