From: Kalle Valo <kvalo@kernel.org>
To: Su Hui <suhui@nfschina.com>
Cc: pkshih@realtek.com, Su Hui <suhui@nfschina.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH wireless-next 01/11] wifi: rtlwifi: add calculate_bit_shift()
Date: Thu, 21 Dec 2023 14:40:50 +0000 (UTC) [thread overview]
Message-ID: <170316964846.1243375.3938053797242635689.kvalo@kernel.org> (raw)
In-Reply-To: <20231219065739.1895666-2-suhui@nfschina.com>
Su Hui <suhui@nfschina.com> wrote:
> There are many same functions like _rtl88e_phy_calculate_bit_shift(),
> _rtl92c_phy_calculate_bit_shift() and so on. And these functions can
> cause undefined bitwise shift behavior. Add calculate_bit_shift() to
> replace them and fix undefined behavior in subsequent patches.
>
> Signed-off-by: Su Hui <suhui@nfschina.com>
> Acked-by: Ping-Ke Shih <pkshih@realtek.com>
11 patches applied to wireless-next.git, thanks.
52221dfddbbf wifi: rtlwifi: add calculate_bit_shift()
acefef7a7e7a wifi: rtlwifi: rtl8821ae: phy: using calculate_bit_shift()
969bc926f04b wifi: rtlwifi: rtl8188ee: phy: using calculate_bit_shift()
1dedc3a6699d wifi: rtlwifi: rtl8192c: using calculate_bit_shift()
f4088c8fcbab wifi: rtlwifi: rtl8192cu: using calculate_bit_shift()
3d03e8231031 wifi: rtlwifi: rtl8192ce: using calculate_bit_shift()
b8b2baad2e65 wifi: rtlwifi: rtl8192de: using calculate_bit_shift()
63526897fc0d wifi: rtlwifi: rtl8192ee: using calculate_bit_shift()
ac32b9317063 wifi: rtlwifi: rtl8192se: using calculate_bit_shift()
98d9c7731dbb wifi: rtlwifi: rtl8723_common: using calculate_bit_shift()
5c16618bc06a wifi: rtlwifi: rtl8723{be,ae}: using calculate_bit_shift()
--
https://patchwork.kernel.org/project/linux-wireless/patch/20231219065739.1895666-2-suhui@nfschina.com/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2023-12-21 14:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 6:57 [PATCH wireless-next 00/11] using calculate_bit_shift() to fix undefined bitwise shift behavior Su Hui
2023-12-19 6:57 ` [PATCH wireless-next 01/11] wifi: rtlwifi: add calculate_bit_shift() Su Hui
2023-12-20 6:47 ` Ping-Ke Shih
2023-12-21 14:40 ` Kalle Valo [this message]
2023-12-19 6:57 ` [PATCH wireless-next 02/11] wifi: rtlwifi: rtl8821ae: phy: using calculate_bit_shift() Su Hui
2023-12-19 6:57 ` [PATCH wireless-next 03/11] wifi: rtlwifi: rtl8188ee: " Su Hui
2023-12-19 6:57 ` [PATCH wireless-next 04/11] wifi: rtlwifi: rtl8192c: " Su Hui
2023-12-19 6:57 ` [PATCH wireless-next 05/11] wifi: rtlwifi: rtl8192cu: " Su Hui
2023-12-19 6:57 ` [PATCH wireless-next 06/11] wifi: rtlwifi: rtl8192ce: " Su Hui
2023-12-19 6:57 ` [PATCH wireless-next 07/11] wifi: rtlwifi: rtl8192de: " Su Hui
2023-12-19 6:57 ` [PATCH wireless-next 08/11] wifi: rtlwifi: rtl8192ee: " Su Hui
2023-12-19 6:57 ` [PATCH wireless-next 09/11] wifi: rtlwifi: rtl8192se: " Su Hui
2023-12-19 6:57 ` [PATCH wireless-next 10/11] wifi: rtlwifi: rtl8723_common: " Su Hui
2023-12-19 6:57 ` [PATCH wireless-next 11/11] wifi: rtlwifi: rtl8723{be,ae}: " Su Hui
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=170316964846.1243375.3938053797242635689.kvalo@kernel.org \
--to=kvalo@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.com \
--cc=suhui@nfschina.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.