* [PATCH 1/1] docs: submitting-patches: Emphasise the requirement to Cc: stable when using Fixes: tag
@ 2021-01-13 14:23 Lee Jones
2021-01-13 15:52 ` Greg Kroah-Hartman
0 siblings, 1 reply; 4+ messages in thread
From: Lee Jones @ 2021-01-13 14:23 UTC (permalink / raw)
To: lee.jones; +Cc: linux-kernel, Greg Kroah-Hartman, Jonathan Corbet, linux-doc
Clear-up any confusion surrounding the Fixes: tag with regards to the
need to Cc: the stable mailing list when submitting stable patch
candidates.
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org
Signed-off-by: Lee Jones <lee.jones@linaro.org>
---
Documentation/process/submitting-patches.rst | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst
index 7c97ad580e7d0..636ef067c1565 100644
--- a/Documentation/process/submitting-patches.rst
+++ b/Documentation/process/submitting-patches.rst
@@ -554,7 +554,8 @@ is used to make it easy to determine where a bug originated, which can help
review a bug fix. This tag also assists the stable kernel team in determining
which stable kernel versions should receive your fix. This is the preferred
method for indicating a bug fixed by the patch. See :ref:`describe_changes`
-for more details.
+for more details. Attaching a Fixes: tag does not replace the requirement to
+Cc: stable@vger.kernel.org on all stable patch candidates.
.. _the_canonical_patch_format:
--
2.25.1
^ permalink raw reply related [flat|nested] 4+ messages in thread
* Re: [PATCH 1/1] docs: submitting-patches: Emphasise the requirement to Cc: stable when using Fixes: tag
2021-01-13 14:23 [PATCH 1/1] docs: submitting-patches: Emphasise the requirement to Cc: stable when using Fixes: tag Lee Jones
@ 2021-01-13 15:52 ` Greg Kroah-Hartman
2021-01-13 16:08 ` Lee Jones
0 siblings, 1 reply; 4+ messages in thread
From: Greg Kroah-Hartman @ 2021-01-13 15:52 UTC (permalink / raw)
To: Lee Jones; +Cc: linux-kernel, Jonathan Corbet, linux-doc
On Wed, Jan 13, 2021 at 02:23:47PM +0000, Lee Jones wrote:
> Clear-up any confusion surrounding the Fixes: tag with regards to the
> need to Cc: the stable mailing list when submitting stable patch
> candidates.
>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: linux-doc@vger.kernel.org
> Signed-off-by: Lee Jones <lee.jones@linaro.org>
> ---
> Documentation/process/submitting-patches.rst | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst
> index 7c97ad580e7d0..636ef067c1565 100644
> --- a/Documentation/process/submitting-patches.rst
> +++ b/Documentation/process/submitting-patches.rst
> @@ -554,7 +554,8 @@ is used to make it easy to determine where a bug originated, which can help
> review a bug fix. This tag also assists the stable kernel team in determining
> which stable kernel versions should receive your fix. This is the preferred
> method for indicating a bug fixed by the patch. See :ref:`describe_changes`
> -for more details.
> +for more details. Attaching a Fixes: tag does not replace the requirement to
> +Cc: stable@vger.kernel.org on all stable patch candidates.
Want to just link to the "stable kernel rules" document here to show
the proper way to do this is documented there?
thanks,
greg k-h
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH 1/1] docs: submitting-patches: Emphasise the requirement to Cc: stable when using Fixes: tag
2021-01-13 15:52 ` Greg Kroah-Hartman
@ 2021-01-13 16:08 ` Lee Jones
2021-01-13 16:22 ` Greg Kroah-Hartman
0 siblings, 1 reply; 4+ messages in thread
From: Lee Jones @ 2021-01-13 16:08 UTC (permalink / raw)
To: Greg Kroah-Hartman; +Cc: linux-kernel, Jonathan Corbet, linux-doc
On Wed, 13 Jan 2021, Greg Kroah-Hartman wrote:
> On Wed, Jan 13, 2021 at 02:23:47PM +0000, Lee Jones wrote:
> > Clear-up any confusion surrounding the Fixes: tag with regards to the
> > need to Cc: the stable mailing list when submitting stable patch
> > candidates.
> >
> > Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > Cc: Jonathan Corbet <corbet@lwn.net>
> > Cc: linux-doc@vger.kernel.org
> > Signed-off-by: Lee Jones <lee.jones@linaro.org>
> > ---
> > Documentation/process/submitting-patches.rst | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst
> > index 7c97ad580e7d0..636ef067c1565 100644
> > --- a/Documentation/process/submitting-patches.rst
> > +++ b/Documentation/process/submitting-patches.rst
> > @@ -554,7 +554,8 @@ is used to make it easy to determine where a bug originated, which can help
> > review a bug fix. This tag also assists the stable kernel team in determining
> > which stable kernel versions should receive your fix. This is the preferred
> > method for indicating a bug fixed by the patch. See :ref:`describe_changes`
> > -for more details.
> > +for more details. Attaching a Fixes: tag does not replace the requirement to
> > +Cc: stable@vger.kernel.org on all stable patch candidates.
>
> Want to just link to the "stable kernel rules" document here to show
> the proper way to do this is documented there?
I think this needs to be clearly stated here.
What if we linked to the rules document *as well*?
--
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH 1/1] docs: submitting-patches: Emphasise the requirement to Cc: stable when using Fixes: tag
2021-01-13 16:08 ` Lee Jones
@ 2021-01-13 16:22 ` Greg Kroah-Hartman
0 siblings, 0 replies; 4+ messages in thread
From: Greg Kroah-Hartman @ 2021-01-13 16:22 UTC (permalink / raw)
To: Lee Jones; +Cc: linux-kernel, Jonathan Corbet, linux-doc
On Wed, Jan 13, 2021 at 04:08:59PM +0000, Lee Jones wrote:
> On Wed, 13 Jan 2021, Greg Kroah-Hartman wrote:
>
> > On Wed, Jan 13, 2021 at 02:23:47PM +0000, Lee Jones wrote:
> > > Clear-up any confusion surrounding the Fixes: tag with regards to the
> > > need to Cc: the stable mailing list when submitting stable patch
> > > candidates.
> > >
> > > Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > > Cc: Jonathan Corbet <corbet@lwn.net>
> > > Cc: linux-doc@vger.kernel.org
> > > Signed-off-by: Lee Jones <lee.jones@linaro.org>
> > > ---
> > > Documentation/process/submitting-patches.rst | 3 ++-
> > > 1 file changed, 2 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst
> > > index 7c97ad580e7d0..636ef067c1565 100644
> > > --- a/Documentation/process/submitting-patches.rst
> > > +++ b/Documentation/process/submitting-patches.rst
> > > @@ -554,7 +554,8 @@ is used to make it easy to determine where a bug originated, which can help
> > > review a bug fix. This tag also assists the stable kernel team in determining
> > > which stable kernel versions should receive your fix. This is the preferred
> > > method for indicating a bug fixed by the patch. See :ref:`describe_changes`
> > > -for more details.
> > > +for more details. Attaching a Fixes: tag does not replace the requirement to
> > > +Cc: stable@vger.kernel.org on all stable patch candidates.
> >
> > Want to just link to the "stable kernel rules" document here to show
> > the proper way to do this is documented there?
>
> I think this needs to be clearly stated here.
>
> What if we linked to the rules document *as well*?
Sure, that works for me.
thanks,
greg k-h
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2021-01-13 16:22 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-01-13 14:23 [PATCH 1/1] docs: submitting-patches: Emphasise the requirement to Cc: stable when using Fixes: tag Lee Jones
2021-01-13 15:52 ` Greg Kroah-Hartman
2021-01-13 16:08 ` Lee Jones
2021-01-13 16:22 ` Greg Kroah-Hartman
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.