From: Christophe Leroy <christophe.leroy@c-s.fr>
To: Fuqian Huang <huangfq.daxian@gmail.com>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 09/30] macintosh: Use kmemdup rather than duplicating its implementation
Date: Wed, 3 Jul 2019 15:19:59 +0200 [thread overview]
Message-ID: <d8ef6578-d879-9222-3feb-92264b8275ec@c-s.fr> (raw)
In-Reply-To: <20190703131452.25085-1-huangfq.daxian@gmail.com>
Le 03/07/2019 à 15:14, Fuqian Huang a écrit :
> kmemdup is introduced to duplicate a region of memory in a neat way.
> Rather than kmalloc/kzalloc + memset, which the programmer needs to
> write the size twice (sometimes lead to mistakes), kmemdup improves
> readability, leads to smaller code and also reduce the chances of mistakes.
> Suggestion to use kmemdup rather than using kmalloc/kzalloc + memset.
s/memset/memcpy/
>
> Signed-off-by: Fuqian Huang <huangfq.daxian@gmail.com>
> ---
> drivers/macintosh/adbhid.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/macintosh/adbhid.c b/drivers/macintosh/adbhid.c
> index 75482eeab2c4..5d14bebfb58f 100644
> --- a/drivers/macintosh/adbhid.c
> +++ b/drivers/macintosh/adbhid.c
> @@ -789,7 +789,8 @@ adbhid_input_register(int id, int default_id, int original_handler_id,
>
> switch (default_id) {
> case ADB_KEYBOARD:
> - hid->keycode = kmalloc(sizeof(adb_to_linux_keycodes), GFP_KERNEL);
> + hid->keycode = kmemdup(adb_to_linux_keycodes,
> + sizeof(adb_to_linux_keycodes), GFP_KERNEL);
> if (!hid->keycode) {
> err = -ENOMEM;
> goto fail;
> @@ -797,8 +798,6 @@ adbhid_input_register(int id, int default_id, int original_handler_id,
>
> sprintf(hid->name, "ADB keyboard");
>
> - memcpy(hid->keycode, adb_to_linux_keycodes, sizeof(adb_to_linux_keycodes));
> -
> switch (original_handler_id) {
> default:
> keyboard_type = "<unknown>";
>
prev parent reply other threads:[~2019-07-03 13:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-03 13:14 [PATCH 09/30] macintosh: Use kmemdup rather than duplicating its implementation Fuqian Huang
2019-07-03 13:19 ` Christophe Leroy [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=d8ef6578-d879-9222-3feb-92264b8275ec@c-s.fr \
--to=christophe.leroy@c-s.fr \
--cc=huangfq.daxian@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
/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