From: Greg KH <gregkh@linuxfoundation.org>
To: Alexandru Hossu <hossu.alexandru@gmail.com>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] staging: rtl8723bs: replace alloc+memcpy with kmemdup
Date: Wed, 4 Mar 2026 15:48:23 +0100 [thread overview]
Message-ID: <2026030402-enlarging-zipfile-6ed4@gregkh> (raw)
In-Reply-To: <20260304135914.38286-1-hossu.alexandru@gmail.com>
On Wed, Mar 04, 2026 at 02:59:14PM +0100, Alexandru Hossu wrote:
> Replace open-coded alloc+memcpy patterns with kmemdup().
>
> This simplifies the code and avoids manual size/copy handling.
>
> Signed-off-by: Alexandru Hossu <hossu.alexandru@gmail.com>
>
> v4:
> - Drop unrelated DT binding changes from earlier attempts.
> - Include both rtl8723bs changes in one staging-only patch.
> - Wrap long line reported by checkpatch.
>
> ---
> drivers/staging/rtl8723bs/hal/sdio_ops.c | 3 +--
> drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c | 3 +--
> 2 files changed, 2 insertions(+), 4 deletions(-)
Please slow down and read the documentation that my bot pointed you at.
The version information here is not done properly :(
next prev parent reply other threads:[~2026-03-04 14:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 13:07 [PATCH v2] staging: rtl8723bs: replace kzalloc/kmalloc+memcpy with kmemdup Alexandru Hossu
2026-03-04 13:24 ` Greg KH
2026-03-04 13:51 ` [PATCH v3] " Alexandru Hossu
2026-03-04 13:59 ` [PATCH v4] staging: rtl8723bs: replace alloc+memcpy " Alexandru Hossu
2026-03-04 14:48 ` Greg KH [this message]
2026-03-05 10:23 ` [PATCH v6] staging: rtl8723bs: use kmemdup() in rtw_cfg80211_set_wpa_ie Alexandru Hossu
2026-03-05 10:39 ` Dan Carpenter
2026-03-05 1:09 ` [PATCH v5] staging: rtl8723bs: replace alloc+memcpy with kmemdup Alexandru Hossu
2026-03-05 5:51 ` 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=2026030402-enlarging-zipfile-6ed4@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=hossu.alexandru@gmail.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