[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdai_bEJ8K=Bo0KeARS=KF5BP4C8B0fGGAJQFZ6RMZRRsw@mail.gmail.com>
Date: Tue, 30 Oct 2018 14:22:59 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Wolfram Sang <wsa+renesas@...g-engineering.com>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Linux-Renesas <linux-renesas-soc@...r.kernel.org>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>
Subject: Re: [PATCH 1/5] pinctrl: intel: pinctrl-baytrail: simplify getting .driver_data
On Sun, Oct 21, 2018 at 10:00 PM Wolfram Sang
<wsa+renesas@...g-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@...g-engineering.com>
Acked-by: Linus Walleij <linus.walleij@...aro.org>
for all 3 Intel patches
Andy is collecting Intel pin control patches so he will
pick these 3 up I think, let me know if all works out!
Yours,
Linus Walleij
Powered by blists - more mailing lists