From: Miquel Raynal <miquel.raynal@bootlin.com>
To: "Kyeongrho.Kim" <kr.kim@skyhighmemory.com>
Cc: Mohamed Sardi <moh.sardi@skyhighmemory.com>,
"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>,
Mohammad Nada <Mohammad.nada@skyhighmemory.com>,
"Changsub.Shim" <changsub.shim@skyhighmemory.com>
Subject: Re: [SkyHigh Memory SPI NAND Driver]
Date: Thu, 11 Jan 2024 08:38:38 +0100 [thread overview]
Message-ID: <20240111083838.7f215daf@xps-13> (raw)
In-Reply-To: <SE2P216MB2102316F0F2D8134C755C37283682@SE2P216MB2102.KORP216.PROD.OUTLOOK.COM>
Hi Kim,
> > 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'.
>
> [KR] Simply, you can only support for our patch to the latest version. Is that right?
Well, there is only one "mainline", and your contributions must match
the state of this mainline. When applying the patch, the next kernel
and all others following will have support for your chips.
>
> > 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.
>
> [KR] Is it possible to apply the patch to old version of Linux community?
On your side you can provide a diff for each kernel version that you
want to support which does not contain your patch series. For all
kernel versions after your changes have been merged, there is nothing
additional to do on your side (besides posting updates/fixes maybe).
You cannot backport a feature to older (stable) kernels.
Thanks,
Miquèl
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2024-01-11 7:38 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 ` [SkyHigh Memory SPI NAND Driver] Miquel Raynal
2024-01-08 19:05 ` Mohamed Sardi
[not found] ` <SE2P216MB2102316F0F2D8134C755C37283682@SE2P216MB2102.KORP216.PROD.OUTLOOK.COM>
2024-01-11 7:38 ` Miquel Raynal [this message]
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=20240111083838.7f215daf@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