From: kernel test robot <lkp@intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, Kees Cook <kees@kernel.org>,
Tony Luck <tony.luck@intel.com>,
"Guilherme G. Piccoli" <gpiccoli@igalia.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: [PATCH v1 1/1] pstore: Use match_string() helper to simplify the code
Date: Wed, 11 Nov 2026 12:30:56 +0800 [thread overview]
Message-ID: <202611111158.Qtw7vGo7-lkp@intel.com> (raw)
In-Reply-To: <20261110151844.661926-1-andriy.shevchenko@linux.intel.com>
Hi Andy,
kernel test robot noticed the following build warnings:
[auto build test WARNING on kees/for-next/pstore]
[also build test WARNING on kees/for-next/kspp aegl/next linus/master v7.4-rc2 next-20261110]
[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/Andy-Shevchenko/pstore-Use-match_string-helper-to-simplify-the-code/20261110-161844
base: https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git for-next/pstore
patch link: https://lore.kernel.org/r/20261110151844.661926-1-andriy.shevchenko%40linux.intel.com
patch subject: [PATCH v1 1/1] pstore: Use match_string() helper to simplify the code
config: arm-randconfig-1002-20261111 (https://download.01.org/0day-ci/archive/20261111/202611111158.Qtw7vGo7-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 15.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261111/202611111158.Qtw7vGo7-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202611111158.Qtw7vGo7-lkp@intel.com/
All warnings (new ones prefixed by >>):
fs/pstore/platform.c: In function 'pstore_name_to_type':
>> fs/pstore/platform.c:134:20: warning: suggest braces around empty body in an 'if' statement [-Wempty-body]
134 | if (i >= 0);
| ^
>> fs/pstore/platform.c:134:9: warning: this 'if' clause does not guard... [-Wmisleading-indentation]
134 | if (i >= 0);
| ^~
fs/pstore/platform.c:135:17: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the 'if'
135 | return i;
| ^~~~~~
vim +/if +134 fs/pstore/platform.c
128
129 enum pstore_type_id pstore_name_to_type(const char *name)
130 {
131 int i;
132
133 i = match_string(pstore_type_names, PSTORE_TYPE_MAX, name);
> 134 if (i >= 0);
135 return i;
136
137 return PSTORE_TYPE_MAX;
138 }
139 EXPORT_SYMBOL_GPL(pstore_name_to_type);
140
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2026-11-11 4:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 15:18 [PATCH v1 1/1] pstore: Use match_string() helper to simplify the code Andy Shevchenko
2026-11-11 2:20 ` kernel test robot
2026-11-11 4:30 ` kernel test robot [this message]
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=202611111158.Qtw7vGo7-lkp@intel.com \
--to=lkp@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gpiccoli@igalia.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tony.luck@intel.com \
/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.