From: Patrick Williams <patrick@stwcx.xyz>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH] mtd: aspeed-smc: improve probe resilience
Date: Thu, 30 Dec 2021 09:29:46 -0600 [thread overview]
Message-ID: <Yc3Qav+ULNdF5zRT@heinlein> (raw)
In-Reply-To: <20211229173411.l2bipmi4x3arqjoo@ti.com>
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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.ozlabs.org/pipermail/linux-aspeed/attachments/20211230/76fca388/attachment.sig>
next prev parent reply other threads:[~2021-12-30 15:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-29 14:33 [PATCH] mtd: aspeed-smc: improve probe resilience Patrick Williams
2021-12-29 17:34 ` Pratyush Yadav
2021-12-30 15:29 ` Patrick Williams [this message]
2021-12-31 10:26 ` Pratyush Yadav
2022-01-03 16:17 ` Miquel Raynal
2022-01-04 18:20 ` Patrick Williams
2022-01-05 6:32 ` Pratyush Yadav
2022-01-23 22:44 ` Cédric Le Goater
2022-01-24 15:36 ` Pratyush Yadav
2022-01-24 18:34 ` Cédric Le Goater
2022-01-24 20:37 ` Pratyush Yadav
2022-02-07 17:13 ` Cédric Le Goater
2022-02-08 19:06 ` Pratyush Yadav
2022-01-23 15:39 ` Miquel Raynal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Yc3Qav+ULNdF5zRT@heinlein \
--to=patrick@stwcx.xyz \
--cc=linux-aspeed@lists.ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).