[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <19e48035-917c-7bb0-eef3-a7d6db4c1db2@xilinx.com>
Date: Mon, 23 Apr 2018 08:04:48 +0200
From: Michal Simek <michal.simek@...inx.com>
To: Wolfram Sang <wsa@...-dreams.de>,
Michal Simek <michal.simek@...inx.com>
CC: Wolfram Sang <wsa+renesas@...g-engineering.com>,
<linux-kernel@...r.kernel.org>,
<linux-renesas-soc@...r.kernel.org>,
<kernel-janitors@...r.kernel.org>, Hoan Tran <hotran@....com>,
Linus Walleij <linus.walleij@...aro.org>,
Grygorii Strashko <grygorii.strashko@...com>,
Santosh Shilimkar <ssantosh@...nel.org>,
Kevin Hilman <khilman@...nel.org>,
Thierry Reding <thierry.reding@...il.com>,
Jonathan Hunter <jonathanh@...dia.com>,
<linux-gpio@...r.kernel.org>, <linux-omap@...r.kernel.org>,
<linux-tegra@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH 10/61] gpio: simplify getting .drvdata
Hi Wolfram,
On 21.4.2018 18:23, Wolfram Sang wrote:
> Hi Michal,
>
> Thanks for the reviews!
>
>> There are two more occurences in this gpio-zynq driver.
>> zynq_gpio_resume, zynq_gpio_suspend. It wasn't detected because these
>> two lines are not together. But the same change can be applied for them too.
>
> Not really. The rule would have matched if there was just "something"
> inbetween. It did not match because the "something" involves the
> variable 'pdev', so we can't remove it. And just changing towards
> 'dev_get_drvdata' and keeping 'pdev' was not worth the hazzle in my
> book. Especially since I think the code should probably get refactored.
> Calling platform_get_irq() in suspend/resume paths in order to get the
> irq_data looks a little expensive to me, but I haven't tested it.
>
ok. Thanks. I have overlooked that.
Thanks,
Michal
Powered by blists - more mailing lists