Re: [PATCH 4/6] gpio: gpio-omap: simplify getting .driver_data

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Wolfram Sang <wsa+renesas@xxxxxxxxxxxxxxxxxxxx>
Subject: Re: [PATCH 4/6] gpio: gpio-omap: simplify getting .driver_data
From: Linus Walleij <linus.walleij@xxxxxxxxxx>
Date: Tue, 30 Oct 2018 14:18:06 +0100
Cc: "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, Linux-Renesas <linux-renesas-soc@xxxxxxxxxxxxxxx>, Grygorii Strashko <grygorii.strashko@xxxxxx>, Santosh Shilimkar <ssantosh@xxxxxxxxxx>, Kevin Hilman <khilman@xxxxxxxxxx>, Linux-OMAP <linux-omap@xxxxxxxxxxxxxxx>, "open list:GPIO SUBSYSTEM" <linux-gpio@xxxxxxxxxxxxxxx>
In-reply-to: <20181021200002.1472-5-wsa+renesas@sang-engineering.com>
References: <20181021200002.1472-1-wsa+renesas@sang-engineering.com> <20181021200002.1472-5-wsa+renesas@sang-engineering.com>

On Sun, Oct 21, 2018 at 10:00 PM Wolfram Sang
<wsa+renesas@xxxxxxxxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxxx>

Patch applied.

Yours,
Linus Walleij

References:
- [PATCH 0/6] gpio: simplify getting .driver_data
  - From: Wolfram Sang
- [PATCH 4/6] gpio: gpio-omap: simplify getting .driver_data
  - From: Wolfram Sang

Prev by Date: Re: [PATCH 4/5] pinctrl: pinctrl-amd: simplify getting .driver_data
Next by Date: Re: [PATCH 6/6] gpio: gpio-zynq: simplify getting .driver_data
Previous by thread: Re: [PATCH 4/6] gpio: gpio-omap: simplify getting .driver_data
Next by thread: [PATCH 6/6] gpio: gpio-zynq: simplify getting .driver_data
Index(es):
- Date
- Thread

[Index of Archives] [Linux Samsung SOC] [Linux Wireless] [Linux Kernel] [ATH6KL] [Linux Bluetooth] [Linux Netdev] [Kernel Newbies] [IDE] [Security] [Git] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Linux ATA RAID] [Samba] [Device Mapper]