On Tue, Aug 30, 2022 at 3:48 PM Greg Kroah-Hartman
<gregkh@xxxxxxxxxxxxxxxxxxx> wrote:
> On Tue, Aug 30, 2022 at 03:38:27PM +0300, Andy Shevchenko wrote:
> > On Tue, Aug 30, 2022 at 3:31 PM Greg Kroah-Hartman
> > <gregkh@xxxxxxxxxxxxxxxxxxx> wrote:
> > > On Thu, Aug 25, 2022 at 12:17:05PM +0300, Ilpo Järvinen wrote:
...
> > I'm wondering how to tell stable maintainers about dependencies of
> > (not yet applied) patches? In practice I saw that contributors use
> > Fixes tag for the entire chain (for the preparatory patches + the real
> > fix) when it's not easy / in a nice way to rebase to have a one-patch
> > fix followed by refactoring, etc.
>
> It's as if no one has ever had this issue before and wrote it down for
> all to read and know what to do in the future.
>
> {sigh}
>
> Please read:
> https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
> for how to do this properly.
>
> If you don't know the git id, just use the subject line and it should
> work the same.
>
> greg "why even write documentation?" k-h
It's good we have it, thanks for writing!
>From time to time even experienced developers need to re-read documentation.
--
With Best Regards,
Andy Shevchenko
