From: kernel test robot <lkp@intel.com>
To: alison@she-devel.com, johan@kernel.org
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
alison@she-devel.com, achaiken@aurora.tech
Subject: Re: [PATCH 1/2] gnss: ubx: customize serial device open to set U-Blox Zed-F9P baud
Date: Sun, 30 Apr 2023 08:20:11 +0800 [thread overview]
Message-ID: <202304300819.u0hfUj33-lkp@intel.com> (raw)
In-Reply-To: <20230429224349.1935029-2-alison@she-devel.com>
Hi,
kernel test robot noticed the following build warnings:
[auto build test WARNING on robh/for-next]
[also build test WARNING on linus/master v6.3 next-20230428]
[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/alison-she-devel-com/gnss-ubx-customize-serial-device-open-to-set-U-Blox-Zed-F9P-baud/20230430-065242
base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next
patch link: https://lore.kernel.org/r/20230429224349.1935029-2-alison%40she-devel.com
patch subject: [PATCH 1/2] gnss: ubx: customize serial device open to set U-Blox Zed-F9P baud
config: i386-randconfig-a001 (https://download.01.org/0day-ci/archive/20230430/202304300819.u0hfUj33-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-12) 11.3.0
reproduce (this is a W=1 build):
# https://github.com/intel-lab-lkp/linux/commit/743f5061f999abbdc0b6f366cf4b85a5a8685014
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review alison-she-devel-com/gnss-ubx-customize-serial-device-open-to-set-U-Blox-Zed-F9P-baud/20230430-065242
git checkout 743f5061f999abbdc0b6f366cf4b85a5a8685014
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=i386 olddefconfig
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash drivers/gnss/
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202304300819.u0hfUj33-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gnss/ubx.c:246:37: warning: 'ubx_gserial_ops' defined but not used [-Wunused-const-variable=]
246 | static const struct gnss_serial_ops ubx_gserial_ops = {
| ^~~~~~~~~~~~~~~
vim +/ubx_gserial_ops +246 drivers/gnss/ubx.c
1ad69f10e3a58d Johan Hovold 2018-06-01 245
55570f1a441787 Colin Ian King 2018-07-16 @246 static const struct gnss_serial_ops ubx_gserial_ops = {
1ad69f10e3a58d Johan Hovold 2018-06-01 247 .set_power = ubx_set_power,
1ad69f10e3a58d Johan Hovold 2018-06-01 248 };
1ad69f10e3a58d Johan Hovold 2018-06-01 249
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
next parent reply other threads:[~2023-04-30 0:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230429224349.1935029-2-alison@she-devel.com>
2023-04-30 0:20 ` kernel test robot [this message]
2023-05-09 3:09 ` [PATCH 1/2] gnss: ubx: customize serial device open to set U-Blox Zed-F9P baud kernel test robot
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=202304300819.u0hfUj33-lkp@intel.com \
--to=lkp@intel.com \
--cc=achaiken@aurora.tech \
--cc=alison@she-devel.com \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@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;
as well as URLs for NNTP newsgroup(s).