From: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
To: linux-wireless@vger.kernel.org
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kvalo@kernel.org, tony0620emma@gmail.com,
Ping-Ke Shih <pkshih@realtek.com>, Neo Jou <neojou@gmail.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Subject: [PATCH v1 wireless-next 0/2] wifi: rtw88: two small error propagation fixes
Date: Sun, 26 Feb 2023 23:10:02 +0100 [thread overview]
Message-ID: <20230226221004.138331-1-martin.blumenstingl@googlemail.com> (raw)
While updating the rtw88 sdio patches I found two more improvements for
the existing code. This series targets wireless-next and is meant to be
applied on top of my previous series v2 "rtw88: Add additional SDIO
support bits" from [0]. I decide to target wireless-next because these
patches are not fixing any issues visible to the end user. Worst case
is that the code is shadowing some error codes.
The next series that I'll send after this is the addition of the rtw88
SDIO HCI and adding the first driver(s) to utilize this code.
[0] https://lore.kernel.org/lkml/20230218152944.48842-1-martin.blumenstingl@googlemail.com/
Martin Blumenstingl (2):
wifi: rtw88: mac: Return the original error from rtw_pwr_seq_parser()
wifi: rtw88: mac: Return the original error from
rtw_mac_power_switch()
drivers/net/wireless/realtek/rtw88/mac.c | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
--
2.39.2
next reply other threads:[~2023-02-26 22:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-26 22:10 Martin Blumenstingl [this message]
2023-02-26 22:10 ` [PATCH v1 wireless-next 1/2] wifi: rtw88: mac: Return the original error from rtw_pwr_seq_parser() Martin Blumenstingl
2023-03-01 1:51 ` Ping-Ke Shih
2023-03-06 10:09 ` Kalle Valo
2023-02-26 22:10 ` [PATCH v1 wireless-next 2/2] wifi: rtw88: mac: Return the original error from rtw_mac_power_switch() Martin Blumenstingl
2023-03-01 1:51 ` Ping-Ke Shih
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=20230226221004.138331-1-martin.blumenstingl@googlemail.com \
--to=martin.blumenstingl@googlemail.com \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=neojou@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pkshih@realtek.com \
--cc=tony0620emma@gmail.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
all inboxes | Powered by JetHome®