[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <691cc39a667d6284fa25bc47f6855152@walle.cc>
Date: Tue, 08 Mar 2022 09:31:58 +0100
From: Michael Walle <michael@...le.cc>
To: Horatiu Vultur <horatiu.vultur@...rochip.com>
Cc: andriy.shevchenko@...ux.intel.com, colin.foster@...advantage.com,
linus.walleij@...aro.org, linux-gpio@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 1/2] pinctrl: ocelot: Fix the pincfg resource.
Am 2022-03-08 09:30, schrieb Horatiu Vultur:
> The 03/07/2022 13:45, Michael Walle wrote:
>> EXTERNAL EMAIL: Do not click links or open attachments unless you know
>> the content is safe
>>
>> > The pincfg resources are in the second memory resource. But the driver
>> > still tries to access the first memory resource to get the pincfg. This
>> > is wrong therefore fix to access the second memory resource.
>> >
>> > Reviewed-by: Colin Foster <colin.foster@...advantage.com>
>> > Fixes: ad96111e658a95 ("pinctrl: ocelot: combine get resource and ioremap into single call")
>> > Signed-off-by: Horatiu Vultur <horatiu.vultur@...rochip.com>
>>
>> There is already this patch pending, which does exactly
>> the same:
>> https://lore.kernel.org/linux-gpio/20220216082020.981797-1-michael@walle.cc/
>
> Sorry, I have missed your patch.
> Should I resend this series where I will drop this patch? What is the
> correct approach?
Actually, I don't know. Maybe you don't need to do anything, Linus?
-michael
Powered by blists - more mailing lists