From: Kalle Valo <kvalo@codeaurora.org>
To: Rajan Vaja <rajan.vaja@gmail.com>
Cc: j@w1.fi, linux-wireless@vger.kernel.org
Subject: Re: hostap: Use memdup_user() to reuse code
Date: Sat, 3 Sep 2016 09:55:13 +0000 (UTC) [thread overview]
Message-ID: <20160903095513.C099662017@smtp.codeaurora.org> (raw)
In-Reply-To: <1469088884-28469-1-git-send-email-rajan.vaja@gmail.com>
Rajan Vaja <rajan.vaja@gmail.com> wrote:
> Fix coccicheck warning which recommends to
> use memdup_user() instead of reimplementing its
> code.
>
> This patch fixes below coccicheck warnings:
>
> drivers/net/wireless/intersil/hostap/hostap_ioctl.c:3044:9-16: WARNING
> opportunity for memdup_user
> drivers/net/wireless/intersil/hostap/hostap_ioctl.c:3806:9-16: WARNING
> opportunity for memdup_user
>
> Signed-off-by: Rajan Vaja <rajan.vaja@gmail.com>
> Reviewed-by: Julian Calaby <julian.calaby@gmail.com>
Thanks, 1 patch applied to wireless-drivers-next.git:
8432ebd66205 hostap: Use memdup_user() to reuse code
--
Sent by pwcli
https://patchwork.kernel.org/patch/9241109/
prev parent reply other threads:[~2016-09-03 9:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-21 8:14 [PATCH] hostap: Use memdup_user() to reuse code Rajan Vaja
2016-07-22 0:29 ` Julian Calaby
2016-09-03 9:55 ` 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=20160903095513.C099662017@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=j@w1.fi \
--cc=linux-wireless@vger.kernel.org \
--cc=rajan.vaja@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;
as well as URLs for NNTP newsgroup(s).