From: Kalle Valo <kvalo@codeaurora.org>
To: YueHaibing <yuehaibing@huawei.com>
Cc: <davem@davemloft.net>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-wireless@vger.kernel.org>,
YueHaibing <yuehaibing@huawei.com>
Subject: Re: atmel: use memdup_user to simplify the code
Date: Wed, 27 Jun 2018 16:06:28 +0000 (UTC) [thread overview]
Message-ID: <20180627160628.1ECF660AFF@smtp.codeaurora.org> (raw)
In-Reply-To: <20180604103210.23984-1-yuehaibing@huawei.com>
YueHaibing <yuehaibing@huawei.com> wrote:
> use existing memdup_user() helper function instead of open-coding
>
> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
Patch applied to wireless-drivers-next.git, thanks.
8668f9a57c8c atmel: use memdup_user to simplify the code
--
https://patchwork.kernel.org/patch/10446299/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2018-06-27 16:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 10:32 [PATCH] atmel: use memdup_user to simplify the code YueHaibing
2018-06-27 16:06 ` Kalle Valo [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=20180627160628.1ECF660AFF@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yuehaibing@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).