Re: [PATCH] docs: doc-guide: add hint to review patch
From: Manuel Ebner
Date: Mon Nov 16 2026 - 04:38:33 EST
On Mon, 2026-11-16 at 02:10 -0700, Jonathan Corbet wrote:
> Manuel Ebner <manuelebnerli@xxxxxxxxxxx> writes:
>
> > For the case of a duplicate patch, review the other patch instead of
> > sending own patch.
> >
> > Signed-off-by: Manuel Ebner <manuelebnerli@xxxxxxxxxxx>
> > ---
> > Documentation/doc-guide/contributing.rst | 4 +++-
> > 1 file changed, 3 insertions(+), 1 deletion(-)
> >
> > diff --git a/Documentation/doc-guide/contributing.rst b/Documentation/doc-guide/contributing.rst
> > index 46a44b39d6..ee2f896a21 100644
> > --- a/Documentation/doc-guide/contributing.rst
> > +++ b/Documentation/doc-guide/contributing.rst
> > @@ -129,7 +129,9 @@ looked like this::
> > The entire process only took a few minutes. Of course, I then found that
> > somebody else had fixed it in a separate tree, highlighting another lesson:
> > always check linux-next to see if a problem has been fixed before you dig
> > -into it.
> > +into it. If the other patch isn't applied yet it's good to give it a
> > +'Reviewed-by:' tag to help it get applied. This way your effort is not in
> > +vain.
>
> Should we perhaps be explicit and say that the person involved should
> actually review the patch?
Makes sense. I'll change it to:
into it. If the other patch isn't applied yet it's good to review it and
state that by replying with the 'Reviewed-by:' tag. This helps getting the
patch applied, so your effort is not in vain after all.
Thanks
Manuel
>
> jon