From: Kalle Valo <kvalo@kernel.org>
To: Jeff Johnson <quic_jjohnson@quicinc.com>
Cc: kernel test robot <lkp@intel.com>,
Rajat Soni <quic_rajson@quicinc.com>,
<oe-kbuild-all@lists.linux.dev>,
Jeff Johnson <jjohnson@kernel.org>,
<ath12k@lists.infradead.org>,
Roopni Devanathan <quic_rdevanat@quicinc.com>
Subject: Re: [ath:pending 8/12] drivers/net/wireless/ath/ath12k/debugfs_htt_stats.c:2515:77: warning: left shift count >= width of type
Date: Mon, 07 Oct 2024 18:50:21 +0300 [thread overview]
Message-ID: <87iku352v6.fsf@kernel.org> (raw)
In-Reply-To: <9db6842d-ddc6-4f0e-a818-c13298eedd8b@quicinc.com> (Jeff Johnson's message of "Mon, 7 Oct 2024 08:40:30 -0700")
Jeff Johnson <quic_jjohnson@quicinc.com> writes:
> On 10/3/2024 11:37 AM, kernel test robot wrote:
>
>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/ath/ath.git pending
>> head: 08dd5d93509f962500dc983864b4effb2600831a
>> commit: f6a46bc3719cc6b445cb071a7dd6968891ffb169 [8/12] wifi: ath12k: Support DMAC Reset Stats
>> config: i386-allmodconfig
>> (https://download.01.org/0day-ci/archive/20241004/202410040200.Mwb85JzQ-lkp@intel.com/config)
>> compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
>> reproduce (this is a W=1 build):
>> (https://download.01.org/0day-ci/archive/20241004/202410040200.Mwb85JzQ-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/202410040200.Mwb85JzQ-lkp@intel.com/
>>
>> All warnings (new ones prefixed by >>):
>>
>> drivers/net/wireless/ath/ath12k/debugfs_htt_stats.c: In function 'ath12k_htt_print_dmac_reset_stats_tlv':
>>>> drivers/net/wireless/ath/ath12k/debugfs_htt_stats.c:2515:77: warning: left shift count >= width of type [-Wshift-count-overflow]
>> 2515 | time = ((unsigned long)le32_to_cpu(htt_stats_buf->reset_time_hi_ms) << 32) |
>> | ^~
>> drivers/net/wireless/ath/ath12k/debugfs_htt_stats.c:2519:81:
>> warning: left shift count >= width of type [-Wshift-count-overflow]
>> 2519 | time = ((unsigned long)le32_to_cpu(htt_stats_buf->disengage_time_hi_ms) << 32) |
>> | ^~
>> drivers/net/wireless/ath/ath12k/debugfs_htt_stats.c:2523:78:
>> warning: left shift count >= width of type [-Wshift-count-overflow]
>> 2523 | time = ((unsigned long)le32_to_cpu(htt_stats_buf->engage_time_hi_ms) << 32) |
>> | ^~
>
> Out of curiosity is there a way to tell if this is a 32-bit build vs a 64-bit
> build? I just want to verify that the issue is that unsigned long is 32-bits
> and not that the shift occurs before the typecast
The config is i386-allmodconfig so it has to be 32-bit. The report also
includes link to the actual .config file.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2024-10-07 15:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-03 18:37 [ath:pending 8/12] drivers/net/wireless/ath/ath12k/debugfs_htt_stats.c:2515:77: warning: left shift count >= width of type kernel test robot
2024-10-07 15:40 ` Jeff Johnson
2024-10-07 15:50 ` Kalle Valo [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=87iku352v6.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath12k@lists.infradead.org \
--cc=jjohnson@kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=quic_jjohnson@quicinc.com \
--cc=quic_rajson@quicinc.com \
--cc=quic_rdevanat@quicinc.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.