From: kernel test robot <lkp@intel.com>
To: Gaosheng Cui <cuigaosheng1@huawei.com>
Cc: stable@vger.kernel.org, oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH 5.10 1/4] crypto: api - Fix built-in testing dependency failures
Date: Sat, 15 Apr 2023 18:14:09 +0800 [thread overview]
Message-ID: <ZDp48YsrIfYVFReR@96b608206aa4> (raw)
In-Reply-To: <20230415101158.1648486-2-cuigaosheng1@huawei.com>
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 5.10 1/4] crypto: api - Fix built-in testing dependency failures
Link: https://lore.kernel.org/stable/20230415101158.1648486-2-cuigaosheng1%40huawei.com
The check is based on https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
Please ignore this mail if the patch is not relevant for upstream.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
next prev parent reply other threads:[~2023-04-15 10:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-15 10:11 [PATCH 5.10 0/4] Fix built-in testing dependency failures Gaosheng Cui
2023-04-15 10:11 ` [PATCH 5.10 1/4] crypto: api - " Gaosheng Cui
2023-04-15 10:14 ` kernel test robot [this message]
2023-04-15 15:07 ` Greg KH
[not found] ` <3f6315cc-4684-2121-3556-0ace47c29b35@huawei.com>
2023-04-18 9:28 ` Greg KH
2023-04-18 13:51 ` cuigaosheng
2023-04-15 10:11 ` [PATCH 5.10 2/4] crypto: api - Do not create test larvals if manager is disabled Gaosheng Cui
2023-04-15 10:11 ` [PATCH 5.10 3/4] crypto: api - Export crypto_boot_test_finished Gaosheng Cui
2023-04-15 10:11 ` [PATCH 5.10 4/4] crypto: api - Fix boot-up crash when crypto manager is disabled Gaosheng Cui
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=ZDp48YsrIfYVFReR@96b608206aa4 \
--to=lkp@intel.com \
--cc=cuigaosheng1@huawei.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 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.