public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: kernel test robot <lkp@intel.com>,
	Gautam Menghani <gautam@linux.ibm.com>
Cc: stable@vger.kernel.org, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH] arch/powerpc/kvm: Fix doorbell emulation by adding DPDES support
Date: Thu, 23 May 2024 12:05:03 +1000	[thread overview]
Message-ID: <87msoh2shc.fsf@mail.lhotse> (raw)
In-Reply-To: <Zk2tjEcFtINQhCag@9ce27862b6d0>

kernel test robot <lkp@intel.com> writes:
> Hi,
>
> Thanks for your patch.

I found this report confusing.

It seems like it's saying a patch with "Fixes: ..." *must* include a
"Cc: stable" tag, but that is wrong, it's up to the developer to decide.

What it's trying to say is that the patch was Cc'ed via mail to
stable@vger.kernel.org and that is not the correct way to request stable
inclusion.

So can I suggest the report begins with something like:

  Your patch was Cc'ed via mail to stable@vger.kernel.org but that is
  not the correct way to requestion stable inclusion, the correct method
  is ....

> FYI: kernel test robot notices the stable kernel rule is not satisfied.
>
> The check is based on https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html#option-1
>
> Rule: add the tag "Cc: stable@vger.kernel.org" in the sign-off area to have the patch automatically included in the stable tree.
> Subject: [PATCH] arch/powerpc/kvm: Fix doorbell emulation by adding DPDES support
> Link: https://lore.kernel.org/stable/20240522082838.121769-1-gautam%40linux.ibm.com


cheers

  reply	other threads:[~2024-05-23  2:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-22  8:28 [PATCH] arch/powerpc/kvm: Fix doorbell emulation by adding DPDES support Gautam Menghani
2024-05-22  8:32 ` kernel test robot
2024-05-23  2:05   ` Michael Ellerman [this message]
2024-05-23  2:30     ` Yujie Liu
2024-05-23  8:16     ` Yujie Liu
2024-05-31  5:24 ` Gautam Menghani
2024-05-31  6:09   ` Greg KH
2024-05-31  7:01     ` Gautam Menghani

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=87msoh2shc.fsf@mail.lhotse \
    --to=mpe@ellerman.id.au \
    --cc=gautam@linux.ibm.com \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox