Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <20220825091707.8112-1-ilpo.jarvinen@linux.intel.com>
 <20220825091707.8112-2-ilpo.jarvinen@linux.intel.com> <Yw4CP8y3b9E9XV0K@kroah.com>
 <CAHp75VfQHhPoO3Rpk=o1c2qPJB-tc_6G41n6iz3sv_gP44PLUw@mail.gmail.com> <Yw4HALWWOWabR/l9@kroah.com>
In-Reply-To: <Yw4HALWWOWabR/l9@kroah.com>
From:   Andy Shevchenko <andy.shevchenko@gmail.com>
Date:   Tue, 30 Aug 2022 15:53:43 +0300
Message-ID: <CAHp75VcdqwnKq80H7tzeyS_ior+FCHPH23wQZfvivn-6wRx1pA@mail.gmail.com>
Subject: Re: [PATCH 1/3] serial: Create uart_xmit_advance()
To:     Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc:     =?UTF-8?Q?Ilpo_J=C3=A4rvinen?= <ilpo.jarvinen@linux.intel.com>,
        Jiri Slaby <jirislaby@kernel.org>,
        "open list:SERIAL DRIVERS" <linux-serial@vger.kernel.org>,
        Stephen Warren <swarren@nvidia.com>,
        Alan Cox <alan@linux.intel.com>,
        Laxman Dewangan <ldewangan@nvidia.com>,
        Thierry Reding <treding@nvidia.com>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Tue, Aug 30, 2022 at 3:48 PM Greg Kroah-Hartman
<gregkh@linuxfoundation.org> 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@linuxfoundation.org> wrote:
> > > On Thu, Aug 25, 2022 at 12:17:05PM +0300, Ilpo J=C3=A4rvinen 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.ht=
ml
> 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=
.

--=20
With Best Regards,
Andy Shevchenko