From: Greg KH <gregkh@linuxfoundation.org>
To: 2023060904@ycu.edu.cn
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
guagua210311@qq.com
Subject: Re: [PATCH v5 1/3] rtl8723bs: io: Add independent rtw_check_continual_io_error function
Date: Sun, 11 Jan 2026 14:04:16 +0100 [thread overview]
Message-ID: <2026011156-progeny-ecard-4fc1@gregkh> (raw)
In-Reply-To: <2048B07E5179CB78+20260111032136.7078-2-2023060904@ycu.edu.cn>
On Sun, Jan 11, 2026 at 11:21:34AM +0800, 2023060904@ycu.edu.cn wrote:
> From: Changjun Zheng <2023060904@ycu.edu.cn>
>
> Add a new function to check if the error count exceeds the MAX_CONTINUAL_IO_ERR
> threshold. This function follows the single responsibility principle and
> prepares for the subsequent removal of the global continual_io_error variable.
>
> Signed-off-by: Changjun Zheng <2023060904@ycu.edu.cn>
> ---
This patch is corrupted and can not be applied:
checking file drivers/staging/rtl8723bs/core/rtw_io.c
patch: **** malformed patch at line 228: }
So something went wrong.
Also, make sure that each commit builds properly, I think this one will
break the build, right?
And finally, please use git send-email to send all of these out
together, your 0/3 email does not show up as properly threaded here.
See the result on lore.kernel.org as proof of that:
https://lore.kernel.org/all/12B32ED3FD2801A5+20260111032136.7078-1-2023060904@ycu.edu.cn/
thanks,
greg k-h
next prev parent reply other threads:[~2026-01-11 13:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260111032136.7078-1-2023060904@ycu.edu.cn>
2026-01-11 3:21 ` [PATCH v5 1/3] rtl8723bs: io: Add independent rtw_check_continual_io_error function 2023060904
2026-01-11 13:04 ` Greg KH [this message]
2026-01-12 7:55 ` Dan Carpenter
2026-01-11 3:21 ` [PATCH v5 2/3] rtl8723bs: sdio: Use local error_count instead of global variable 2023060904
2026-01-11 3:21 ` [PATCH v5 3/3] rtl8723bs: io: Remove redundant global continual_io_error variable 2023060904
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=2026011156-progeny-ecard-4fc1@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=2023060904@ycu.edu.cn \
--cc=guagua210311@qq.com \
--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