From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Subject: Re: [PATCH v5 2/2] x86/alternative: Patch a single alternative location only once
Date: Mon, 5 Jan 2026 13:44:52 +0100 [thread overview]
Message-ID: <202601051306.KfFREWM9-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: <20260105080452.5064-3-jgross@suse.com>
References: <20260105080452.5064-3-jgross@suse.com>
TO: Juergen Gross <jgross@suse.com>
Hi Juergen,
kernel test robot noticed the following build warnings:
[auto build test WARNING on tip/x86/core]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Juergen-Gross/x86-alternative-Use-helper-functions-for-patching-alternatives/20260105-161434
base: tip/x86/core
patch link: https://lore.kernel.org/r/20260105080452.5064-3-jgross%40suse.com
patch subject: [PATCH v5 2/2] x86/alternative: Patch a single alternative location only once
:::::: branch date: 5 hours ago
:::::: commit date: 5 hours ago
reproduce: (https://download.01.org/0day-ci/archive/20260105/202601051306.KfFREWM9-lkp@intel.com/reproduce)
# many are suggestions rather than must-fix
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
#48: FILE: arch/x86/kernel/alternative.c:614:
+static struct alt_instr * __init_or_module analyze_patch_site(struct patch_site *ps,
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-01-05 12:45 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=202601051306.KfFREWM9-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