From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adam Ford Subject: Re: [PATCH 10/61] gpio: simplify getting .drvdata Date: Thu, 7 Mar 2019 14:13:29 -0600 Message-ID: References: <20180419140641.27926-1-wsa+renesas@sang-engineering.com> <20180419140641.27926-11-wsa+renesas@sang-engineering.com> <20180430092947.GC2270@ulmo> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: In-Reply-To: <20180430092947.GC2270@ulmo> Sender: linux-kernel-owner@vger.kernel.org To: Thierry Reding Cc: Linus Walleij , Grygorii Strashko , Wolfram Sang , "linux-kernel@vger.kernel.org" , Linux-Renesas , kernel-janitors@vger.kernel.org, Hoan Tran , Santosh Shilimkar , Kevin Hilman , Jonathan Hunter , Michal Simek , "open list:GPIO SUBSYSTEM" , Linux-OMAP , linux-tegra@vger.kernel.org, Linux ARM List-Id: linux-gpio@vger.kernel.org On Mon, Apr 30, 2018 at 4:30 AM Thierry Reding wrote: > > On Mon, Apr 30, 2018 at 11:03:25AM +0200, Linus Walleij wrote: > > On Thu, Apr 19, 2018 at 5:14 PM, Grygorii Strashko > > wrote: > > > On 04/19/2018 09:05 AM, Wolfram Sang wrote: > > >> > > >> We should get drvdata from struct device directly. Going via > > >> platform_device is an unneeded step back and forth. > > >> > > >> Signed-off-by: Wolfram Sang > > >> --- > > >> > > >> Build tested only. buildbot is happy. Please apply individually. > > > > > > > > > for gpio-omap.c: > > > Reviewed-by: Grygorii Strashko > > > > Hm I only see the responses not the actual patch, I guess I will find it > > sooner or later. > > > > Wolfram: if I don't find it, poke me with something sharp so I get to apply it. > > I had the same problem, turned out this got classified as spam by Google > for some reason. Maybe try your spam folder? It's been almost a year later, and several Linux revisions, and this still seems stuck somewhere/somehow. adam > > Thierry