From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Subject: Re: [PATCH v2 2/2] LoongArch: Batch icache maintenance for jump_label
Date: Wed, 8 Apr 2026 16:01:50 +0200 [thread overview]
Message-ID: <202604081503.dLDO4IWF-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: <20260405021227.532599-2-youling.tang@linux.dev>
References: <20260405021227.532599-2-youling.tang@linux.dev>
TO: Youling Tang <youling.tang@linux.dev>
TO: Huacai Chen <chenhuacai@kernel.org>
Hi Youling,
kernel test robot noticed the following build warnings:
[auto build test WARNING on linus/master]
[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/Youling-Tang/LoongArch-Batch-icache-maintenance-for-jump_label/20260408-092520
base: linus/master
patch link: https://lore.kernel.org/r/20260405021227.532599-2-youling.tang%40linux.dev
patch subject: [PATCH v2 2/2] LoongArch: Batch icache maintenance for jump_label
:::::: branch date: 12 hours ago
:::::: commit date: 12 hours ago
reproduce: (https://download.01.org/0day-ci/archive/20260408/202604081503.dLDO4IWF-lkp@intel.com/reproduce)
# many are suggestions rather than must-fix
WARNING:ONE_SEMICOLON: Statements terminations use 1 semicolon
#31: FILE: arch/loongarch/include/asm/cacheflush.h:42:
+ asm volatile ("ibar\t0\n"::);;
WARNING:ONE_SEMICOLON: Statements terminations use 1 semicolon
#36: FILE: arch/loongarch/include/asm/cacheflush.h:47:
+ asm volatile ("ibar\t0\n"::);;
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-04-08 14:02 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=202604081503.dLDO4IWF-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