Re: [PATCH v1] mtd: rawnand: meson: fix bitmask for length in command word
From: Miquel Raynal
Date: Wed Mar 29 2023 - 03:35:02 EST
Hello,
avkrasnov@xxxxxxxxxxxxxx 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@xxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxx
Thanks,
Miquèl