From: kernel test robot <lkp@intel.com>
To: Eelco Chaudron <echaudro@redhat.com>
Cc: stable@vger.kernel.org, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH net v3] openvswitch: Fix flow lookup to use unmasked key
Date: Thu, 15 Dec 2022 22:50:00 +0800 [thread overview]
Message-ID: <Y5s0GEK+ylnDnpXP@416bcb91c936> (raw)
In-Reply-To: <167111551443.359845.7122827280135116424.stgit@ebuild>
Hi,
Thanks for your patch.
FYI: kernel test robot notices the stable kernel rule is not satisfied.
Rule: 'Cc: stable@vger.kernel.org' or 'commit <sha1> upstream.'
Subject: [PATCH net v3] openvswitch: Fix flow lookup to use unmasked key
Link: https://lore.kernel.org/stable/167111551443.359845.7122827280135116424.stgit%40ebuild
The check is based on https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next prev parent reply other threads:[~2022-12-15 15:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 14:46 [PATCH net v3] openvswitch: Fix flow lookup to use unmasked key Eelco Chaudron
2022-12-15 14:50 ` kernel test robot [this message]
2022-12-16 10:40 ` patchwork-bot+netdevbpf
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=Y5s0GEK+ylnDnpXP@416bcb91c936 \
--to=lkp@intel.com \
--cc=echaudro@redhat.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