From: kernel test robot <lkp@intel.com>
To: Arowa Suliman <arowa@chromium.org>, ath11k@lists.infradead.org
Cc: oe-kbuild-all@lists.linux.dev, linux-wireless@vger.kernel.org,
Arowa Suliman <arowa@google.com>
Subject: Re: [PATCH] wifi: ath11k: Add crash logging
Date: Wed, 14 Jun 2023 12:01:35 +0800 [thread overview]
Message-ID: <202306141105.c1e82Q0y-lkp@intel.com> (raw)
In-Reply-To: <20230614023125.284218-1-arowa@google.com>
Hi Arowa,
kernel test robot noticed the following build warnings:
[auto build test WARNING on kvalo-ath/ath-next]
[cannot apply to wireless/main wireless-next/main linus/master v6.4-rc6 next-20230613]
[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/Arowa-Suliman/wifi-ath11k-Add-crash-logging/20230614-103201
base: https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git ath-next
patch link: https://lore.kernel.org/r/20230614023125.284218-1-arowa%40google.com
patch subject: [PATCH] wifi: ath11k: Add crash logging
config: alpha-allyesconfig (https://download.01.org/0day-ci/archive/20230614/202306141105.c1e82Q0y-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 12.3.0
reproduce (this is a W=1 build):
mkdir -p ~/bin
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git remote add kvalo-ath https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git
git fetch kvalo-ath ath-next
git checkout kvalo-ath/ath-next
b4 shazam https://lore.kernel.org/r/20230614023125.284218-1-arowa@google.com
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.3.0 ~/bin/make.cross W=1 O=build_dir ARCH=alpha olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.3.0 ~/bin/make.cross W=1 O=build_dir ARCH=alpha SHELL=/bin/bash drivers/net/
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/202306141105.c1e82Q0y-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/net/wireless/ath/ath11k/mhi.c: In function 'ath11k_mhi_op_status_cb':
>> drivers/net/wireless/ath/ath11k/mhi.c:328:25: warning: passing argument 2 of 'ath11k_info' makes pointer from integer without a cast [-Wint-conversion]
328 | ath11k_info(ab, ATH11K_DBG_BOOT, "notify status reason %s\n",
| ^~~~~~~~~~~~~~~
| |
| int
In file included from drivers/net/wireless/ath/ath11k/mhi.c:14:
drivers/net/wireless/ath/ath11k/debug.h:76:69: note: expected 'const char *' but argument is of type 'int'
76 | __printf(2, 3) void ath11k_info(struct ath11k_base *ab, const char *fmt, ...);
| ~~~~~~~~~~~~^~~
vim +/ath11k_info +328 drivers/net/wireless/ath/ath11k/mhi.c
322
323 static void ath11k_mhi_op_status_cb(struct mhi_controller *mhi_cntrl,
324 enum mhi_callback cb)
325 {
326 struct ath11k_base *ab = dev_get_drvdata(mhi_cntrl->cntrl_dev);
327
> 328 ath11k_info(ab, ATH11K_DBG_BOOT, "notify status reason %s\n",
329 ath11k_mhi_op_callback_to_str(cb));
330
331 switch (cb) {
332 case MHI_CB_SYS_ERROR:
333 ath11k_warn(ab, "firmware crashed: MHI_CB_SYS_ERROR\n");
334 break;
335 case MHI_CB_EE_RDDM:
336 ath11k_warn(ab, "firmware crashed: MHI_CB_EE_RDDM\n");
337 if (!(test_bit(ATH11K_FLAG_UNREGISTERING, &ab->dev_flags)))
338 queue_work(ab->workqueue_aux, &ab->reset_work);
339 break;
340 default:
341 break;
342 }
343 }
344
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-06-14 4:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 2:29 [PATCH] wifi: ath11k: Add crash logging Arowa Suliman
2023-06-14 4:01 ` kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-10 23:04 Arowa Suliman
2023-07-11 6:40 ` Kalle Valo
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=202306141105.c1e82Q0y-lkp@intel.com \
--to=lkp@intel.com \
--cc=arowa@chromium.org \
--cc=arowa@google.com \
--cc=ath11k@lists.infradead.org \
--cc=linux-wireless@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).