Re: [PATCH v2 1/2] pinctrl: ocelot: Fix the pincfg resource.

From: Horatiu Vultur <horatiu.vultur@microchip.com>
To: Michael Walle <michael@walle.cc>
Cc: <andriy.shevchenko@linux.intel.com>,
	<colin.foster@in-advantage.com>, <linus.walleij@linaro.org>,
	<linux-gpio@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] pinctrl: ocelot: Fix the pincfg resource.
Date: Tue, 8 Mar 2022 09:30:23 +0100	[thread overview]
Message-ID: <20220308083023.frr7qz2xga2tas5r@soft-dev3-1.localhost> (raw)
In-Reply-To: <20220307124501.3487932-1-michael@walle.cc>

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@in-advantage.com>
> > Fixes: ad96111e658a95 ("pinctrl: ocelot: combine get resource and ioremap into single call")
> > Signed-off-by: Horatiu Vultur <horatiu.vultur@microchip.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?

> 
> FWIW, there is also this one:
> https://lore.kernel.org/linux-gpio/20220216122727.1005041-1-michael@walle.cc/
> 
> -michael

-- 
/Horatiu