From: Ping-Ke Shih <pkshih@realtek.com>
To: Lu jicong <jiconglu58@gmail.com>,
"kvalo@kernel.org" <kvalo@kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] rtlwifi: reduce duplicate decision
Date: Mon, 13 Feb 2023 09:20:55 +0000 [thread overview]
Message-ID: <95d88453d583421da774bbe105206bdf@realtek.com> (raw)
In-Reply-To: <20230212104640.2018995-1-jiconglu58@gmail.com>
> -----Original Message-----
> From: Lu jicong <jiconglu58@gmail.com>
> Sent: Sunday, February 12, 2023 6:47 PM
> To: Ping-Ke Shih <pkshih@realtek.com>; kvalo@kernel.org; davem@davemloft.net; edumazet@google.com;
> kuba@kernel.org; pabeni@redhat.com
> Cc: linux-wireless@vger.kernel.org; netdev@vger.kernel.org; linux-kernel@vger.kernel.org; Lu jicong
> <jiconglu58@gmail.com>
> Subject: [PATCH] rtlwifi: reduce duplicate decision
Need "wifi: " prefix.
Subject is too common. How about pointing out 'autoload' or something like that?
>
> This return can go in previous decision.
>
> Signed-off-by: Lu jicong <jiconglu58@gmail.com>
> ---
> drivers/net/wireless/realtek/rtlwifi/efuse.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/drivers/net/wireless/realtek/rtlwifi/efuse.c
> b/drivers/net/wireless/realtek/rtlwifi/efuse.c
> index 2e945554ed6d..70c4e22fc426 100644
> --- a/drivers/net/wireless/realtek/rtlwifi/efuse.c
> +++ b/drivers/net/wireless/realtek/rtlwifi/efuse.c
> @@ -1243,14 +1243,12 @@ int rtl_get_hwinfo(struct ieee80211_hw *hw, struct rtl_priv *rtlpriv,
> rtl_dbg(rtlpriv, COMP_ERR, DBG_WARNING,
> "EEPROM ID(%#x) is invalid!!\n", eeprom_id);
> rtlefuse->autoload_failflag = true;
> + return 1;
> } else {
> rtl_dbg(rtlpriv, COMP_INIT, DBG_LOUD, "Autoload OK\n");
> rtlefuse->autoload_failflag = false;
> }
>
> - if (rtlefuse->autoload_failflag)
> - return 1;
> -
Honestly, I prefer the original version that looks more clear, and we don't need
to stir this chunk.
> rtlefuse->eeprom_vid = *(u16 *)&hwinfo[params[1]];
> rtlefuse->eeprom_did = *(u16 *)&hwinfo[params[2]];
> rtlefuse->eeprom_svid = *(u16 *)&hwinfo[params[3]];
> --
> 2.30.2
prev parent reply other threads:[~2023-02-13 9:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-12 10:46 [PATCH] rtlwifi: reduce duplicate decision Lu jicong
2023-02-13 9:20 ` 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=95d88453d583421da774bbe105206bdf@realtek.com \
--to=pkshih@realtek.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jiconglu58@gmail.com \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 NNTP newsgroup(s).