From: "Ethan Tidmore" <ethantidmore06@gmail.com>
To: "Lin YuChen" <starpt.official@gmail.com>, <gregkh@linuxfoundation.org>
Cc: <linux-staging@lists.linux.dev>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] staging: rtl8723bs: replace kzalloc/memcpy with kmemdup
Date: Tue, 10 Mar 2026 22:21:11 -0500 [thread overview]
Message-ID: <DGZMOJPIMJM0.1FOEWT4HT0CYP@gmail.com> (raw)
In-Reply-To: <20260310192256.864370-1-starpt.official@gmail.com>
On Tue Mar 10, 2026 at 2:22 PM CDT, Lin YuChen wrote:
> Replace the open-coded kzalloc and memcpy combination with kmemdup()
> to make the code more concise and idiomatic.
>
> Signed-off-by: Lin YuChen <starpt.official@gmail.com>
> ---
This same change has recently been merged [1].
Thanks,
ET
[1] https://patch.msgid.link/20260305102318.43034-1-hossu.alexandru@gmail.com
prev parent reply other threads:[~2026-03-11 3:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 19:22 [PATCH v3] staging: rtl8723bs: replace kzalloc/memcpy with kmemdup Lin YuChen
2026-03-11 3:21 ` Ethan Tidmore [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=DGZMOJPIMJM0.1FOEWT4HT0CYP@gmail.com \
--to=ethantidmore06@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=starpt.official@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