From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Mohamed Sardi <moh.sardi@skyhighmemory.com>
Cc: "tudor.ambarus@microchip.com" <tudor.ambarus@microchip.com>,
"p.yadav@ti.com" <p.yadav@ti.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"richard@nod.at" <richard@nod.at>,
"Kyeongrho.Kim" <kr.kim@skyhighmemory.com>,
Mohammad Nada <Mohammad.nada@skyhighmemory.com>,
"Changsub.Shim" <changsub.shim@skyhighmemory.com>
Subject: Re: [SkyHigh Memory SPI NAND Driver]
Date: Mon, 8 Jan 2024 14:47:19 +0100 [thread overview]
Message-ID: <20240108144719.3198373e@xps-13> (raw)
In-Reply-To: <7C13C29F-DBE0-494F-8BA6-99BB68FD08AF@skyhighmemory.com>
Hi Mohamed,
moh.sardi@skyhighmemory.com wrote on Thu, 4 Jan 2024 18:21:52 +0000:
> Hello SPI NOR / NAND Flash Subsytem team,
>
> Please find attached the driver developed on Linux 5.4 and tested.. for our 1Gb/2Gb/4Gb SPI NAND…
>
> We would like to know
>
>
> 1. Who is in charge of supporting SPI NAND driver update and understand the process?
I'd like to say "the community", and that means anybody who wants to
interact on this topic. I will probably be the guy who eventually
applies the patch(es).
> 2. How many version of this driver we need to develop to support all version of Linux (now being 6.xxx)?
We only bring support to the latest mainline kernel, whatever version
it could be. So if you send a patch (please follow the contributing
guidelines in Documentation/) it should be a diff against the next -rc1
(so it will be v6.8-rc1 in two weeks). You can share diffs for other
versions as well on your own website but there is usually no backport
of 'new features'.
> For instance if the driver (attached is 5.4), can it be used up to 5.18… or should we modify it starting from version 5.4x.
If it compiles, it will probably work as well as the core has not
changed much since it's been created, but there is of course no
guarantee.
Thanks,
Miquèl
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next parent reply other threads:[~2024-01-08 13:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7C13C29F-DBE0-494F-8BA6-99BB68FD08AF@skyhighmemory.com>
2024-01-08 13:47 ` Miquel Raynal [this message]
2024-01-08 19:05 ` [SkyHigh Memory SPI NAND Driver] Mohamed Sardi
[not found] ` <SE2P216MB2102316F0F2D8134C755C37283682@SE2P216MB2102.KORP216.PROD.OUTLOOK.COM>
2024-01-11 7:38 ` Miquel Raynal
2024-01-23 1:01 ` Mohamed Sardi
2024-01-24 17:07 ` Miquel Raynal
2024-01-25 22:26 ` Mohamed Sardi
2024-02-01 19:40 ` Mohamed Sardi
2024-02-02 16:11 ` Miquel Raynal
2024-02-02 16:17 ` Mohamed Sardi
2024-02-02 17:51 ` Miquel Raynal
2024-02-21 4:07 ` Kyeongrho.Kim
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=20240108144719.3198373e@xps-13 \
--to=miquel.raynal@bootlin.com \
--cc=Mohammad.nada@skyhighmemory.com \
--cc=changsub.shim@skyhighmemory.com \
--cc=kr.kim@skyhighmemory.com \
--cc=linux-mtd@lists.infradead.org \
--cc=moh.sardi@skyhighmemory.com \
--cc=p.yadav@ti.com \
--cc=richard@nod.at \
--cc=tudor.ambarus@microchip.com \
/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