On Sun, Oct 21, 2018 at 10:00:29PM +0200, Wolfram Sang 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> Acked-by: Mika Westerberg <mika.westerberg@xxxxxxxxxxxxxxx>
Re: [PATCH 3/5] pinctrl: intel: pinctrl-intel: simplify getting .driver_data
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [PATCH 3/5] pinctrl: intel: pinctrl-intel: simplify getting .driver_data
- From: Mika Westerberg <mika.westerberg@xxxxxxxxxxxxxxx>
- Date: Mon, 22 Oct 2018 11:17:58 +0300
- In-reply-to: <20181021200032.1833-4-wsa+renesas@sang-engineering.com>
- Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo
- References: <20181021200032.1833-1-wsa+renesas@sang-engineering.com> <20181021200032.1833-4-wsa+renesas@sang-engineering.com>
- User-agent: Mutt/1.10.1 (2018-07-13)
- References:
- [PATCH 0/5] pinctrl: simplify getting .driver_data
- From: Wolfram Sang
- [PATCH 3/5] pinctrl: intel: pinctrl-intel: simplify getting .driver_data
- From: Wolfram Sang
- [PATCH 0/5] pinctrl: simplify getting .driver_data
- Prev by Date: Re: [PATCH 2/5] pinctrl: intel: pinctrl-cherryview: simplify getting .driver_data
- Next by Date: Re: [PATCH v2 3/3] pinctrl: upboard: Add UP2 pinctrl and gpio driver
- Previous by thread: [PATCH 3/5] pinctrl: intel: pinctrl-intel: simplify getting .driver_data
- Next by thread: [PATCH 1/5] pinctrl: intel: pinctrl-baytrail: simplify getting .driver_data
- Index(es):
 |