From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Subject: [jpoimboe:klp-build-arm64 15/35] checkpatch: WARNING:REPEATED_WORD: Possible repeated word: 'to'
Date: Mon, 06 Apr 2026 08:04:33 +0200 [thread overview]
Message-ID: <202604060702.TZc0gkKF-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "high confidence checkpatch report"
:::::: Manual check reason: "only suspicious fbc files changed"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: Josh Poimboeuf <jpoimboe@kernel.org>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jpoimboe/linux.git klp-build-arm64
head: 145dd0bef91c33be9d60ff43cc59020e4c809a71
commit: 48e9e660f49bf14cf9b7ae57559de9324decd06a [15/35] objtool/klp: Fix position-dependent checksums for non-relocated jumps/calls
:::::: branch date: 15 minutes ago
:::::: commit date: 23 minutes ago
reproduce: (https://download.01.org/0day-ci/archive/20260406/202604060702.TZc0gkKF-lkp@intel.com/reproduce)
# many are suggestions rather than must-fix
WARNING:REPEATED_WORD: Possible repeated word: 'to'
#13:
alternative, which from objtool's perspective are jumps to to the end of
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-04-06 6:05 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=202604060702.TZc0gkKF-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