From: Linus Walleij <linus.walleij@linaro.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Michal Simek <michal.simek@xilinx.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 6/6] gpio: gpio-zynq: simplify getting .driver_data
Date: Tue, 30 Oct 2018 14:19:39 +0100 [thread overview]
Message-ID: <CACRpkdawU7QaQEmM0-o=FBB9=-EYBUs9Rt2=Y_ZTF5xiL69Rdg@mail.gmail.com> (raw)
In-Reply-To: <20181021200002.1472-7-wsa+renesas@sang-engineering.com>
On Sun, Oct 21, 2018 at 10:00 PM Wolfram Sang
<wsa+renesas@sang-engineering.com> wrote:
> We should get 'driver_data' from 'struct device' directly. Going via
> platform_device is an unneeded step back and forth.
>
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
Patch applied.
Yours,
Linus Walleij
prev parent reply other threads:[~2018-10-30 13:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-21 19:59 [PATCH 0/6] gpio: simplify getting .driver_data Wolfram Sang
2018-10-21 19:59 ` [PATCH 1/6] gpio: gpio-dwapb: " Wolfram Sang
2018-10-30 13:12 ` Linus Walleij
2018-10-21 19:59 ` [PATCH 2/6] gpio: gpio-lynxpoint: " Wolfram Sang
2018-10-30 13:14 ` Linus Walleij
2018-10-21 19:59 ` [PATCH 3/6] gpio: gpio-mxc: " Wolfram Sang
2018-10-30 13:15 ` Linus Walleij
2018-10-21 19:59 ` [PATCH 4/6] gpio: gpio-omap: " Wolfram Sang
2018-10-22 18:30 ` Grygorii Strashko
2018-10-30 13:18 ` Linus Walleij
2018-10-21 20:00 ` [PATCH 5/6] gpio: gpio-tegra: " Wolfram Sang
2018-10-22 8:01 ` Thierry Reding
2018-10-30 13:20 ` Linus Walleij
2018-10-21 20:00 ` [PATCH 6/6] gpio: gpio-zynq: " Wolfram Sang
2018-10-30 13:19 ` Linus Walleij [this message]
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='CACRpkdawU7QaQEmM0-o=FBB9=-EYBUs9Rt2=Y_ZTF5xiL69Rdg@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=wsa+renesas@sang-engineering.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).