From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Arseniy Krasnov <avkrasnov@sberdevices.ru>
Cc: Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
Liang Yang <liang.yang@amlogic.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Kevin Hilman <khilman@baylibre.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Jianxin Pan <jianxin.pan@amlogic.com>,
Yixun Lan <yixun.lan@amlogic.com>,
<linux-mtd@lists.infradead.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-amlogic@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <kernel@sberdevices.ru>,
<oxffffaa@gmail.com>
Subject: Re: [PATCH v1] mtd: rawnand: meson: fix bitmask for length in command word
Date: Wed, 29 Mar 2023 09:31:45 +0200 [thread overview]
Message-ID: <20230329093145.52790647@xps-13> (raw)
In-Reply-To: <2fed42ad-11cb-6199-6adb-d9272209f5e2@sberdevices.ru>
Hello,
avkrasnov@sberdevices.ru wrote on Wed, 29 Mar 2023 10:12:10 +0300:
> On 28.03.2023 23:25, Martin Blumenstingl wrote:
> > Hi Arseniy,
> >
> > On Tue, Mar 28, 2023 at 8:39 PM Arseniy Krasnov
> > <avkrasnov@sberdevices.ru> wrote:
> > [...]
> >>>
> >>> By the way any reason not to have Cc'ed stable?
> >>
> >> Sorry, what do You mean? I've included linux-mtd mailing lists, there is
> >> one more list for mtd reviews? I will appreciate if You can point me
> > "stable" typically refers to the stable tree where fixes for already
> > released kernel versions are maintained.
> > When Miquel applies the patch it will either land in the next -rc of
> > the current development cycle (typically applies to fixes - currently
> > 6.3-rc5) or -rc1 of the next kernel version (typically applies to new
> > features, cleanups, etc. - currently 6.4-rc1).
> >
> > Let's say you are fixing a bug now but want the fix to be included in
> > 6.1 LTS (long term stable) or other stable release.
> > In this case it's recommended to Cc the maintainers of the stable
> > trees as part of your patch, see [0].
> > That way once the commit with your fix hits Linus Torvalds linux tree
> > it will be backported by the stable team within a few days (assuming
> > of course that the patch applies cleanly to older versions, if not
> > they're notifying you).
> > Note: even without Cc'ing the stable maintainers your commit may be
> > backported (semi-automatically) if it has a Fixes tag and the stable
> > maintainers find your commit. But my understanding is that it's
> > easiest for them if they're explicitly Cc'ed on the patch.
> >
> > I hope this makes sense. If not: don't hesitate to ask.
That is an excellent summary, I should copy/paste it sometimes :)
>
> Hello! Thanks for this detailed explanation, that really helps!
So IOW, I am asking you to send a v2 with an additional line in the
commit, right next "Fixes":
Cc: stable@vger.kernel.org
Thanks,
Miquèl
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2023-03-29 7:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 18:42 [PATCH v1] mtd: rawnand: meson: fix bitmask for length in command word Arseniy Krasnov
2023-03-22 20:10 ` Martin Blumenstingl
2023-03-23 7:57 ` Arseniy Krasnov
2023-03-28 15:56 ` Arseniy Krasnov
2023-03-28 16:50 ` Miquel Raynal
2023-03-28 18:36 ` Arseniy Krasnov
2023-03-28 20:25 ` Martin Blumenstingl
2023-03-29 7:12 ` Arseniy Krasnov
2023-03-29 7:31 ` Miquel Raynal [this message]
2023-03-29 7:48 ` Arseniy Krasnov
2023-03-29 8:17 ` Dmitry Rokosov
2023-03-29 8:20 ` Tudor Ambarus
2023-03-29 9:55 ` Dmitry Rokosov
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=20230329093145.52790647@xps-13 \
--to=miquel.raynal@bootlin.com \
--cc=avkrasnov@sberdevices.ru \
--cc=jbrunet@baylibre.com \
--cc=jianxin.pan@amlogic.com \
--cc=kernel@sberdevices.ru \
--cc=khilman@baylibre.com \
--cc=liang.yang@amlogic.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=neil.armstrong@linaro.org \
--cc=oxffffaa@gmail.com \
--cc=richard@nod.at \
--cc=vigneshr@ti.com \
--cc=yixun.lan@amlogic.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;
as well as URLs for NNTP newsgroup(s).