From: Linus Walleij <linus.walleij@linaro.org>
To: Jiang Qiu <qiujiang@huawei.com>
Cc: Alexandre Courbot <gnurou@gmail.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Alan Tull <delicious.quinoa@gmail.com>,
Jamie Iles <jamie@jamieiles.com>,
charles.chenxin@huawei.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 <linuxarm@huawei.com>
Subject: Re: [PATCH v10 1/3] gpio: dwapb: remove name from dwapb_port_property
Date: Fri, 29 Apr 2016 11:22:21 +0200 [thread overview]
Message-ID: <CACRpkdaS3+6ZJS0MJk-j4J3j2mKC-MULgCbS8Dqy=4_toy-x9Q@mail.gmail.com> (raw)
In-Reply-To: <1461835923-68492-2-git-send-email-qiujiang@huawei.com>
On Thu, Apr 28, 2016 at 11:32 AM, Jiang Qiu <qiujiang@huawei.com> wrote:
> This patch removed the name property from dwapb_port_property.
> The name property is redundant, since we can get this info
> from dwapb_gpio dev node.
>
> Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
> Signed-off-by: Jiang Qiu <qiujiang@huawei.com>
Hmmm just applied another version. Oh well, applying this
instead.
Yours,
Linus Walleij
next prev parent reply other threads:[~2016-04-29 9:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-28 9:32 [PATCH v10 0/3] gpio: dwapb: add gpio-signaled acpi event support for power button Jiang Qiu
2016-04-28 9:32 ` Jiang Qiu
2016-04-28 9:32 ` [PATCH v10 1/3] gpio: dwapb: remove name from dwapb_port_property Jiang Qiu
2016-04-28 9:32 ` Jiang Qiu
2016-04-29 9:22 ` Linus Walleij [this message]
2016-05-03 3:38 ` Jiang Qiu
2016-05-03 3:38 ` Jiang Qiu
2016-04-28 9:32 ` [PATCH v10 2/3] gpio: dwapb: convert device node to fwnode Jiang Qiu
2016-04-28 9:32 ` Jiang Qiu
2016-04-29 9:24 ` Linus Walleij
2016-04-28 9:32 ` [PATCH v10 3/3] gpio: dwapb: add gpio-signaled acpi event support Jiang Qiu
2016-04-28 9:32 ` Jiang Qiu
2016-04-29 9:25 ` Linus Walleij
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='CACRpkdaS3+6ZJS0MJk-j4J3j2mKC-MULgCbS8Dqy=4_toy-x9Q@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=andy.shevchenko@gmail.com \
--cc=charles.chenxin@huawei.com \
--cc=delicious.quinoa@gmail.com \
--cc=gnurou@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.