[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yc3Qav+ULNdF5zRT@heinlein>
Date: Thu, 30 Dec 2021 09:29:46 -0600
From: Patrick Williams <patrick@...cx.xyz>
To: Pratyush Yadav <p.yadav@...com>, Joel Stanley <joel@....id.au>
Cc: Tudor Ambarus <tudor.ambarus@...rochip.com>,
Michael Walle <michael@...le.cc>,
Miquel Raynal <miquel.raynal@...tlin.com>,
Richard Weinberger <richard@....at>,
Vignesh Raghavendra <vigneshr@...com>,
Joel Stanley <joel@....id.au>,
Andrew Jeffery <andrew@...id.au>,
Potin Lai <potin.lai@...ntatw.com>,
linux-mtd@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org,
linux-aspeed@...ts.ozlabs.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mtd: aspeed-smc: improve probe resilience
On Wed, Dec 29, 2021 at 11:04:13PM +0530, Pratyush Yadav wrote:
> Hi,
>
> On 29/12/21 08:33AM, Patrick Williams wrote:
> The patch itself looks fine to me but we no longer want to maintain
> drivers under drivers/mtd/spi-nor/controllers/. They should be moved to
> implement the SPI MEM API (under drivers/spi/).
Is the linux-aspeed community aware of this? Are you saying you don't want to
take fixes for their driver into the MTD tree? Can it be pulled into the Aspeed
tree?
> Could you please volunteer to do the conversion for this driver?
I'm not personally going to be able to get to it for at least the next 3 months.
It looks like we don't have a dedicated maintainer for this driver other than
Joel by nature of him being listed as the maintainer of "ARM/ASPEED MACHINE
SUPPORT". I'm not sure if Aspeed themselves are planning on doing the necessary
refactoring here.
Joel, are you aware of this driver using a deprecated implementation? Were
there anyone planning to do the reworks that you are aware of? I'd like to get
this fix at least into the OpenBMC kernel tree because I'm seeing this fail in
the real world.
--
Patrick Williams
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists