From: Jiri Kosina <jikos@kernel.org>
To: Yang Yingliang <yangyingliang@huawei.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
benjamin.tissoires@redhat.com
Subject: Re: [PATCH -next] HID: thrustmaster: Switch to kmemdup() when allocate change_request
Date: Fri, 25 Jun 2021 14:11:27 +0200 (CEST) [thread overview]
Message-ID: <nycvar.YFH.7.76.2106251411200.18969@cbobk.fhfr.pm> (raw)
In-Reply-To: <20210511113033.3760555-1-yangyingliang@huawei.com>
On Tue, 11 May 2021, Yang Yingliang wrote:
> Use kmemdup() helper instead of open-coding to
> simplify the code when allocate change_request.
>
> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
Applied, thanks.
--
Jiri Kosina
SUSE Labs
prev parent reply other threads:[~2021-06-25 12:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 11:30 [PATCH -next] HID: thrustmaster: Switch to kmemdup() when allocate change_request Yang Yingliang
2021-06-25 12:11 ` Jiri Kosina [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=nycvar.YFH.7.76.2106251411200.18969@cbobk.fhfr.pm \
--to=jikos@kernel.org \
--cc=benjamin.tissoires@redhat.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yangyingliang@huawei.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;
as well as URLs for NNTP newsgroup(s).