From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Subject: Re: [PATCH] staging: rtl8723bs: fix heap buffer overflow in cfg80211_rtw_add_key
Date: Wed, 8 Apr 2026 22:46:49 +0200 [thread overview]
Message-ID: <202604082249.CcWXI0B7-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "high confidence checkpatch report"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <adQ4yU-Pc0uHXtb5@ans-MacBook-Pro.local>
References: <adQ4yU-Pc0uHXtb5@ans-MacBook-Pro.local>
TO: Feng Ning <feng@innora.ai>
TO: gregkh@linuxfoundation.org
Hi Feng,
kernel test robot noticed the following build warnings:
[auto build test WARNING on staging/staging-testing]
url: https://github.com/intel-lab-lkp/linux/commits/Feng-Ning/staging-rtl8723bs-fix-heap-buffer-overflow-in-cfg80211_rtw_add_key/20260408-172928
base: staging/staging-testing
patch link: https://lore.kernel.org/r/adQ4yU-Pc0uHXtb5%40ans-MacBook-Pro.local
patch subject: [PATCH] staging: rtl8723bs: fix heap buffer overflow in cfg80211_rtw_add_key
:::::: branch date: 11 hours ago
:::::: commit date: 11 hours ago
reproduce: (https://download.01.org/0day-ci/archive/20260408/202604082249.CcWXI0B7-lkp@intel.com/reproduce)
# many are suggestions rather than must-fix
WARNING:BAD_SIGN_OFF: Unexpected content after email: 'linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org', should be: 'linux-staging@lists.linux.dev (linux-kernel@vger.kernel.org)'
#13:
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-04-08 20:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202604082249.CcWXI0B7-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@lists.linux.dev \
/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