From: Matt Fleming <matt@codeblueprint.co.uk>
To: Geliang Tang <geliangtang@gmail.com>
Cc: Ivan Hu <ivan.hu@canonical.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] efi/efi_test: use memdup_user
Date: Fri, 5 May 2017 21:53:49 +0100 [thread overview]
Message-ID: <20170505205349.GC5225@codeblueprint.co.uk> (raw)
In-Reply-To: <d0d524b81d55b4e5f1708d5441e655c75365c0b8.1493383416.git.geliangtang@gmail.com>
On Sat, 29 Apr, at 09:42:52AM, Geliang Tang wrote:
> Use memdup_user() helper instead of open-coding to simplify the code.
>
> Signed-off-by: Geliang Tang <geliangtang@gmail.com>
> ---
> drivers/firmware/efi/test/efi_test.c | 11 +++--------
> 1 file changed, 3 insertions(+), 8 deletions(-)
This one looks fine. Ivan, do you want to ACK it?
next prev parent reply other threads:[~2017-05-05 20:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-29 1:42 [PATCH 1/2] efi/efi_test: use memdup_user Geliang Tang
2017-04-29 1:42 ` Geliang Tang
[not found] ` <d0d524b81d55b4e5f1708d5441e655c75365c0b8.1493383416.git.geliangtang-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-04-29 1:42 ` [PATCH 2/2] efi/efi_test: drop useless kfree Geliang Tang
2017-04-29 1:42 ` Geliang Tang
[not found] ` <427b03b5f10b41014818b9e78f79da9581b213df.1493383416.git.geliangtang-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-05-02 7:11 ` ivanhu
2017-05-02 7:11 ` ivanhu
[not found] ` <a8b99581-70e3-bf9a-bf62-4b13a8cc292c-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
2017-05-02 14:48 ` Geliang Tang
2017-05-02 14:48 ` Geliang Tang
2017-05-05 20:53 ` Matt Fleming [this message]
2017-05-08 8:18 ` [PATCH 1/2] efi/efi_test: use memdup_user ivanhu
[not found] ` <0d6b6b9e-de5c-4eb2-f46a-d26ae058fa42-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
2017-05-10 10:35 ` Matt Fleming
2017-05-10 10:35 ` Matt Fleming
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=20170505205349.GC5225@codeblueprint.co.uk \
--to=matt@codeblueprint.co.uk \
--cc=ard.biesheuvel@linaro.org \
--cc=geliangtang@gmail.com \
--cc=ivan.hu@canonical.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.