From: kernel test robot <lkp@intel.com>
To: Kiran K <kiran.k@intel.com>, linux-bluetooth@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, ravishankar.srivatsa@intel.com,
chethan.tumkur.narayan@intel.com, vijay.satija@intel.com,
Kiran <kiran.k@intel.com>
Subject: Re: [PATCH v2 1/3] Bluetooth: btintel_pcie: Print Firmware Sequencer information
Date: Fri, 17 May 2024 01:59:56 +0800 [thread overview]
Message-ID: <202405170103.plLziF5k-lkp@intel.com> (raw)
In-Reply-To: <20240516131510.904787-1-kiran.k@intel.com>
Hi Kiran,
kernel test robot noticed the following build warnings:
[auto build test WARNING on bluetooth-next/master]
[also build test WARNING on linus/master next-20240516]
[cannot apply to v6.9]
[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/Kiran-K/Bluetooth-btintel_pcie-Fix-irq-leak/20240516-210509
base: https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git master
patch link: https://lore.kernel.org/r/20240516131510.904787-1-kiran.k%40intel.com
patch subject: [PATCH v2 1/3] Bluetooth: btintel_pcie: Print Firmware Sequencer information
config: loongarch-randconfig-001-20240516 (https://download.01.org/0day-ci/archive/20240517/202405170103.plLziF5k-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240517/202405170103.plLziF5k-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/202405170103.plLziF5k-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from drivers/bluetooth/hci_ldisc.c:34:
>> drivers/bluetooth/btintel.h:378:13: warning: 'btintel_print_fseq_info' defined but not used [-Wunused-function]
378 | static void btintel_print_fseq_info(struct hci_dev *hdev)
| ^~~~~~~~~~~~~~~~~~~~~~~
vim +/btintel_print_fseq_info +378 drivers/bluetooth/btintel.h
377
> 378 static void btintel_print_fseq_info(struct hci_dev *hdev)
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
parent reply other threads:[~2024-05-16 18:00 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20240516131510.904787-1-kiran.k@intel.com>]
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=202405170103.plLziF5k-lkp@intel.com \
--to=lkp@intel.com \
--cc=chethan.tumkur.narayan@intel.com \
--cc=kiran.k@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ravishankar.srivatsa@intel.com \
--cc=vijay.satija@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 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 read-only IMAP folder(s) and NNTP newsgroup(s).