From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Subject: [linux-review:Kumar-Kaushlendra/RE-PATCH-thermal-int340x-Fix-sysfs-group-leak-on-DLVR-registration-failure/20260211-162504 1/1] checkpatch: WARNING:BAD_SIGN_OFF: Unexpected content after email: 'rafael@kernel.org; daniel.lezcano@linaro.org; Zhang, Rui <rui.zhang@intel.com>; lukasz.luba@arm.com', should be: '"rafael@kernel.org; daniel.lezcano@linaro.org; Zhang, Rui" <rui.zhang@inte...
Date: Wed, 11 Feb 2026 09:46:38 +0100 [thread overview]
Message-ID: <202602110958.Ln5M0uke-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "high confidence checkpatch report"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: "Kumar, Kaushlendra" <kaushlendra.kumar@intel.com>
tree: https://github.com/intel-lab-lkp/linux/commits/Kumar-Kaushlendra/RE-PATCH-thermal-int340x-Fix-sysfs-group-leak-on-DLVR-registration-failure/20260211-162504
head: ade87aea43f5652ebf85094e172949d6cf7d4a86
commit: ade87aea43f5652ebf85094e172949d6cf7d4a86 [1/1] thermal: int340x: Fix sysfs group leak on DLVR registration failure
:::::: branch date: 20 minutes ago
:::::: commit date: 20 minutes ago
reproduce: (https://download.01.org/0day-ci/archive/20260211/202602110958.Ln5M0uke-lkp@intel.com/reproduce)
# many are suggestions rather than must-fix
WARNING:BAD_SIGN_OFF: Unexpected content after email: 'rafael@kernel.org; daniel.lezcano@linaro.org; Zhang, Rui <rui.zhang@intel.com>; lukasz.luba@arm.com', should be: '"rafael@kernel.org; daniel.lezcano@linaro.org; Zhang, Rui" <rui.zhang@intel.com> (; lukasz.luba@arm.com)'
#16:
To: rafael@kernel.org; daniel.lezcano@linaro.org; Zhang, Rui <rui.zhang@intel.com>; lukasz.luba@arm.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-02-11 8: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=202602110958.Ln5M0uke-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 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.