From: Johan Hovold <johan@kernel.org>
To: Marek Vasut <marex@denx.de>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-serial@vger.kernel.org,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Erwan Le Ray <erwan.leray@foss.st.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Valentin Caron <valentin.caron@foss.st.com>,
linux-arm-kernel@lists.infradead.org,
linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH v3] serial: stm32: Merge hard IRQ and threaded IRQ handling into single IRQ handler
Date: Thu, 12 Jan 2023 18:57:30 +0100 [thread overview]
Message-ID: <Y8BKCka8vZocuz65@hovoldconsulting.com> (raw)
In-Reply-To: <c2f69d59-7c10-53a2-44d3-e3d274da0892@denx.de>
On Thu, Jan 12, 2023 at 06:50:34PM +0100, Marek Vasut wrote:
> On 1/12/23 18:09, Johan Hovold wrote:
> > Fair enough. And it's not obvious that the stable team should backport
> > patches that only concern PREEMPT_RT either (e.g. as parts of it are
> > still out-of-tree).
> >
> > The stable tag is still missing from the final revision though.
>
> Please pardon my ignorance, which stable tag is missing ?
>
> Can you maybe just comment on the V4 and point this out to me ? I'll
> send a V5 then.
It's gone from my inbox.
But as per Documentation/process/stable-kernel-rules.rst:
To have the patch automatically included in the stable tree, add the tag
.. code-block:: none
Cc: stable@vger.kernel.org
in the sign-off area. Once the patch is merged it will be applied to
the stable tree without anything else needing to be done by the author
or subsystem maintainer.
A Fixes tag only indicates which commit introduced a bug, not
necessarily that the patch should be backported to stable (even if
autosel is likely to pick it up these days).
Johan
WARNING: multiple messages have this Message-ID (diff)
From: Johan Hovold <johan@kernel.org>
To: Marek Vasut <marex@denx.de>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-serial@vger.kernel.org,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Erwan Le Ray <erwan.leray@foss.st.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Valentin Caron <valentin.caron@foss.st.com>,
linux-arm-kernel@lists.infradead.org,
linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH v3] serial: stm32: Merge hard IRQ and threaded IRQ handling into single IRQ handler
Date: Thu, 12 Jan 2023 18:57:30 +0100 [thread overview]
Message-ID: <Y8BKCka8vZocuz65@hovoldconsulting.com> (raw)
In-Reply-To: <c2f69d59-7c10-53a2-44d3-e3d274da0892@denx.de>
On Thu, Jan 12, 2023 at 06:50:34PM +0100, Marek Vasut wrote:
> On 1/12/23 18:09, Johan Hovold wrote:
> > Fair enough. And it's not obvious that the stable team should backport
> > patches that only concern PREEMPT_RT either (e.g. as parts of it are
> > still out-of-tree).
> >
> > The stable tag is still missing from the final revision though.
>
> Please pardon my ignorance, which stable tag is missing ?
>
> Can you maybe just comment on the V4 and point this out to me ? I'll
> send a V5 then.
It's gone from my inbox.
But as per Documentation/process/stable-kernel-rules.rst:
To have the patch automatically included in the stable tree, add the tag
.. code-block:: none
Cc: stable@vger.kernel.org
in the sign-off area. Once the patch is merged it will be applied to
the stable tree without anything else needing to be done by the author
or subsystem maintainer.
A Fixes tag only indicates which commit introduced a bug, not
necessarily that the patch should be backported to stable (even if
autosel is likely to pick it up these days).
Johan
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-01-12 18:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 11:53 [PATCH v3] serial: stm32: Merge hard IRQ and threaded IRQ handling into single IRQ handler Marek Vasut
2022-12-16 11:53 ` Marek Vasut
2022-12-27 14:56 ` Johan Hovold
2022-12-27 14:56 ` Johan Hovold
2023-01-05 20:46 ` Marek Vasut
2023-01-05 20:46 ` Marek Vasut
2023-01-06 10:56 ` Johan Hovold
2023-01-06 10:56 ` Johan Hovold
2023-01-09 19:19 ` Marek Vasut
2023-01-09 19:19 ` Marek Vasut
2023-01-09 10:13 ` Sebastian Andrzej Siewior
2023-01-09 10:13 ` Sebastian Andrzej Siewior
2023-01-12 13:13 ` Johan Hovold
2023-01-12 13:13 ` Johan Hovold
2023-01-12 16:38 ` Marek Vasut
2023-01-12 16:38 ` Marek Vasut
2023-01-12 17:09 ` Johan Hovold
2023-01-12 17:09 ` Johan Hovold
2023-01-12 17:50 ` Marek Vasut
2023-01-12 17:50 ` Marek Vasut
2023-01-12 17:57 ` Johan Hovold [this message]
2023-01-12 17:57 ` Johan Hovold
2023-01-05 14:56 ` Valentin CARON
2023-01-05 14:56 ` Valentin CARON
2023-01-05 20:47 ` Marek Vasut
2023-01-05 20:47 ` Marek Vasut
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=Y8BKCka8vZocuz65@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=bigeasy@linutronix.de \
--cc=erwan.leray@foss.st.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=marex@denx.de \
--cc=mcoquelin.stm32@gmail.com \
--cc=tglx@linutronix.de \
--cc=valentin.caron@foss.st.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.