From: Greg KH <gregkh@linuxfoundation.org>
To: Vasyl Gomonovych <gomonovych@gmail.com>
Cc: sfr@canb.auug.org.au, arnd@arndb.de, sudeep.dutt@intel.com,
ashutosh.dixit@intel.com, dan.carpenter@oracle.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] misc: mic: Use memdup_user() as a cleanup
Date: Tue, 19 Dec 2017 10:17:01 +0100 [thread overview]
Message-ID: <20171219091701.GA31059@kroah.com> (raw)
In-Reply-To: <1513202470-29700-1-git-send-email-gomonovych@gmail.com>
On Wed, Dec 13, 2017 at 11:01:08PM +0100, Vasyl Gomonovych wrote:
> Fix coccicheck warning which recommends to use memdup_user():
>
> drivers/misc/mic/vop/vop_vringh.c:940:14-21: WARNING opportunity for memdup_user
> drivers/misc/mic/vop/vop_vringh.c:998:8-15: WARNING opportunity for memdup_user
> Generated by: scripts/coccinelle/memdup_user/memdup_user.cocci
>
> Signed-off-by: Vasyl Gomonovych <gomonovych@gmail.com>
> ---
> I'm not sure if this still valid, maybe warning was fixed already.
> In that case sorry for this disturbing noise.
Seems to already be in the tree.
thanks,
greg k-h
next prev parent reply other threads:[~2017-12-19 9:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 3:39 linux-next: build warning after merge of the char-misc tree Stephen Rothwell
2017-12-12 10:40 ` [PATCH v2] misc: mic: Use memdup_user() as a cleanup Vasyl Gomonovych
2017-12-12 11:49 ` Greg KH
2017-12-12 13:22 ` Gomonovych, Vasyl
2017-12-13 9:30 ` Greg KH
2017-12-13 22:01 ` [PATCH v3] " Vasyl Gomonovych
2017-12-19 9:17 ` Greg KH [this message]
2017-12-12 11:49 ` linux-next: build warning after merge of the char-misc tree Greg KH
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=20171219091701.GA31059@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=ashutosh.dixit@intel.com \
--cc=dan.carpenter@oracle.com \
--cc=gomonovych@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=sudeep.dutt@intel.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 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.