From: Dan Carpenter <error27@gmail.com>
To: Hungyu Lin <dennylin0707@gmail.com>
Cc: gregkh@linuxfoundation.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] staging: rtl8723bs: convert update_attrib_sec_info to return errno
Date: Mon, 15 Jun 2026 10:42:31 +0300 [thread overview]
Message-ID: <ai-s56iJLJzQljp_@stanley.mountain> (raw)
In-Reply-To: <20260614182309.96110-4-dennylin0707@gmail.com>
On Sun, Jun 14, 2026 at 06:23:08PM +0000, Hungyu Lin wrote:
> Convert update_attrib_sec_info() to return 0 on success and
> a negative errno on failure. Update update_attrib() to
> propagate the returned error code.
>
> No functional change intended.
>
> Signed-off-by: Hungyu Lin <dennylin0707@gmail.com>
> ---
> drivers/staging/rtl8723bs/core/rtw_xmit.c | 11 ++++++-----
> 1 file changed, 6 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/staging/rtl8723bs/core/rtw_xmit.c b/drivers/staging/rtl8723bs/core/rtw_xmit.c
> index 7d10caf8cbfe..b6d9332958f5 100644
> --- a/drivers/staging/rtl8723bs/core/rtw_xmit.c
> +++ b/drivers/staging/rtl8723bs/core/rtw_xmit.c
> @@ -519,7 +519,7 @@ static s32 update_attrib_sec_info(struct adapter *padapter, struct pkt_attrib *p
^^^
Change this to int. I wouldn't have commented on this except for the
change to update_attrib()...
> pattrib->encrypt = 0;
>
> if ((pattrib->ether_type != 0x888e) && !check_fwstate(pmlmepriv, WIFI_MP_STATE))
> - return _FAIL;
> + return -EINVAL;
> } else {
> GET_ENCRY_ALGO(psecuritypriv, psta, pattrib->encrypt, bmcast);
>
> @@ -558,7 +558,7 @@ static s32 update_attrib_sec_info(struct adapter *padapter, struct pkt_attrib *p
> pattrib->icv_len = 4;
>
> if (psecuritypriv->busetkipkey == _FAIL)
> - return _FAIL;
> + return -EINVAL;
>
> if (bmcast)
> TKIP_IV(pattrib->iv, psta->dot11txpn, pattrib->key_idx);
> @@ -596,7 +596,7 @@ static s32 update_attrib_sec_info(struct adapter *padapter, struct pkt_attrib *p
> else
> pattrib->bswenc = false;
>
> - return _SUCCESS;
> + return 0;
> }
>
> u8 qos_acm(u8 acm_mask, u8 priority)
> @@ -754,9 +754,10 @@ static s32 update_attrib(struct adapter *padapter, struct sk_buff *pkt, struct p
> return _FAIL;
>
> spin_lock_bh(&psta->lock);
> - if (update_attrib_sec_info(padapter, pattrib, psta) == _FAIL) {
> + ret = update_attrib_sec_info(padapter, pattrib, psta);
> + if (ret) {
> spin_unlock_bh(&psta->lock);
> - return _FAIL;
> + return ret;
This should have stayed as _FAIL and then been updated in the next
patch. It doesn't break anything, but lets still do it that way.
Let's never mix _FAIL and standard error codes.
regards,
dan carpenter
next prev parent reply other threads:[~2026-06-15 7:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-14 18:23 [PATCH 0/4] staging: rtl8723bs: convert update_attrib path to errno Hungyu Lin
2026-06-14 18:23 ` [PATCH 1/4] staging: rtl8723bs: simplify update_attrib_sec_info control flow Hungyu Lin
2026-06-14 18:23 ` [PATCH 2/4] staging: rtl8723bs: simplify update_attrib " Hungyu Lin
2026-06-14 18:23 ` [PATCH 3/4] staging: rtl8723bs: convert update_attrib_sec_info to return errno Hungyu Lin
2026-06-15 7:42 ` Dan Carpenter [this message]
2026-06-14 18:23 ` [PATCH 4/4] staging: rtl8723bs: convert update_attrib " Hungyu Lin
2026-06-15 7:43 ` Dan Carpenter
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=ai-s56iJLJzQljp_@stanley.mountain \
--to=error27@gmail.com \
--cc=dennylin0707@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@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