From: Ping-Ke Shih <pkshih@realtek.com>
To: kernel test robot <lkp@intel.com>, "kvalo@kernel.org" <kvalo@kernel.org>
Cc: "llvm@lists.linux.dev" <llvm@lists.linux.dev>,
"oe-kbuild-all@lists.linux.dev" <oe-kbuild-all@lists.linux.dev>,
DeanKu <ku920601@realtek.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: [PATCH 1/6] wifi: rtw89: coex: Add WiFi role info format version 8
Date: Tue, 12 Mar 2024 00:51:27 +0000 [thread overview]
Message-ID: <6c753d964f5e462a8a9afa63c2777cf0@realtek.com> (raw)
In-Reply-To: <202403112247.DlQU3eaG-lkp@intel.com>
> -----Original Message-----
> From: kernel test robot <lkp@intel.com>
> Sent: Monday, March 11, 2024 10:49 PM
> To: Ping-Ke Shih <pkshih@realtek.com>; kvalo@kernel.org
> Cc: llvm@lists.linux.dev; oe-kbuild-all@lists.linux.dev; DeanKu <ku920601@realtek.com>;
> linux-wireless@vger.kernel.org
> Subject: Re: [PATCH 1/6] wifi: rtw89: coex: Add WiFi role info format version 8
>
> Hi Ping-Ke,
>
> kernel test robot noticed the following build warnings:
>
> [auto build test WARNING on wireless-next/main]
> [also build test WARNING on next-20240308]
> [cannot apply to wireless/main linus/master v6.8]
> [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/Ping-Ke-Shih/wifi-rtw89-coex-Add-WiFi-role-info-format-
> version-8/20240306-115058
> base: https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git main
> patch link: https://lore.kernel.org/r/20240306034558.19648-2-pkshih%40realtek.com
> patch subject: [PATCH 1/6] wifi: rtw89: coex: Add WiFi role info format version 8
> config: x86_64-allmodconfig
> (https://download.01.org/0day-ci/archive/20240311/202403112247.DlQU3eaG-lkp@intel.com/config)
> compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project
> 6009708b4367171ccdbf4b5905cb6a803753fe18)
> reproduce (this is a W=1 build):
> (https://download.01.org/0day-ci/archive/20240311/202403112247.DlQU3eaG-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/202403112247.DlQU3eaG-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
> >> drivers/net/wireless/realtek/rtw89/coex.c:5480:20: warning: variable 'cnt_2g' set but not used
> [-Wunused-but-set-variable]
> 5480 | u8 i, j, cnt = 0, cnt_2g = 0, cnt_5g = 0;
> | ^
> >> drivers/net/wireless/realtek/rtw89/coex.c:5480:32: warning: variable 'cnt_5g' set but not used
> [-Wunused-but-set-variable]
> 5480 | u8 i, j, cnt = 0, cnt_2g = 0, cnt_5g = 0;
> | ^
> 2 warnings generated.
>
These two counters are prepared to support coming MLO, so I will add necessary
debug messages ahead to avoid these warnings.
Ping-Ke
prev parent reply other threads:[~2024-03-12 0:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240306034558.19648-2-pkshih@realtek.com>
2024-03-11 14:48 ` [PATCH 1/6] wifi: rtw89: coex: Add WiFi role info format version 8 kernel test robot
2024-03-12 0:51 ` Ping-Ke Shih [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=6c753d964f5e462a8a9afa63c2777cf0@realtek.com \
--to=pkshih@realtek.com \
--cc=ku920601@realtek.com \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--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).