From: Greg KH <greg@kroah.com>
To: Pu Lehui <pulehui@huaweicloud.com>
Cc: kernel test robot <lkp@intel.com>,
stable@vger.kernel.org, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH 5.10] bpf: Fix mismatch memory accounting for devmap maps
Date: Fri, 27 Sep 2024 09:56:15 +0200 [thread overview]
Message-ID: <2024092751-thrift-squander-0036@gregkh> (raw)
In-Reply-To: <2bd9fdba-d916-4453-a0d9-a1a5b827a454@huaweicloud.com>
On Mon, Sep 23, 2024 at 02:38:07PM +0800, Pu Lehui wrote:
>
>
> On 2024/9/20 18:37, kernel test robot wrote:
> > Hi,
> >
> > Thanks for your patch.
> >
> > 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-3
> >
> > Rule: The upstream commit ID must be specified with a separate line above the commit text.
> > Subject: [PATCH 5.10] bpf: Fix mismatch memory accounting for devmap maps
> > Link: https://lore.kernel.org/stable/20240920103950.3931497-1-pulehui%40huaweicloud.com
> >
> > Please ignore this mail if the patch is not relevant for upstream.
> >
>
> This fix only involves 5.10, other versions are no problem.
why? If this is true, then you need to get the relevant bpf maintainers
to review and ack it.
thanks,
greg k-h
next prev parent reply other threads:[~2024-09-27 7:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-20 10:39 [PATCH 5.10] bpf: Fix mismatch memory accounting for devmap maps Pu Lehui
2024-09-20 10:37 ` kernel test robot
2024-09-23 6:38 ` Pu Lehui
2024-09-27 7:56 ` Greg KH [this message]
2024-09-27 7:56 ` Greg Kroah-Hartman
2024-09-27 8:03 ` Pu Lehui
2024-09-27 8:11 ` Greg Kroah-Hartman
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=2024092751-thrift-squander-0036@gregkh \
--to=greg@kroah.com \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pulehui@huaweicloud.com \
--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