From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Subject: [norov:bitmap-for-next 23/24] checkpatch: WARNING:BAD_SIGN_OFF: Unexpected content after email: 'Madhavan Srinivasan <maddy@linux.ibm.com> for powerpc patch', should be: 'Madhavan Srinivasan <maddy@linux.ibm.com> (for powerpc patch)'
Date: Tue, 07 Apr 2026 20:37:41 +0200 [thread overview]
Message-ID: <202604072034.bEN8vrkT-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "high confidence checkpatch report"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: Yury Norov <yury.norov@gmail.com>
tree: https://github.com/norov/linux bitmap-for-next
head: 916aedc424155719a4cacf55b6d88ba556c1bd0e
commit: 2a0be80c5a620ab380ef483c2c20c6cc3325e311 [23/24] powerpc/xive: simplify xive_spapr_debug_show()
:::::: branch date: 2 hours ago
:::::: commit date: 5 days ago
reproduce: (https://download.01.org/0day-ci/archive/20260407/202604072034.bEN8vrkT-lkp@intel.com/reproduce)
# many are suggestions rather than must-fix
WARNING:BAD_SIGN_OFF: Unexpected content after email: 'Madhavan Srinivasan <maddy@linux.ibm.com> for powerpc patch', should be: 'Madhavan Srinivasan <maddy@linux.ibm.com> (for powerpc patch)'
#11:
Acked-by: Madhavan Srinivasan <maddy@linux.ibm.com> for powerpc patch
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-04-07 18:38 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=202604072034.bEN8vrkT-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.