From: Ben Romer <benjamin.romer@unisys.com>
To: Hugo Camboulive <hugo.camboulive@gmail.com>,
<david.kershner@unisys.com>, <gregkh@linuxfoundation.org>,
<Timothy.Sell@unisys.com>, <nhorman@redhat.com>
Cc: <sparmaintainer@unisys.com>, <devel@driverdev.osuosl.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] staging: unisys: visornic: remove useless memset
Date: Tue, 26 Jan 2016 14:44:52 -0500 [thread overview]
Message-ID: <1453837492.4209.8.camel@unisys.com> (raw)
In-Reply-To: <1453753336-20230-1-git-send-email-hugo.camboulive@gmail.com>
On Mon, 2016-01-25 at 20:22 +0000, Hugo Camboulive wrote:
> alloc_etherdev() calls alloc_netdev_mqs(), which
> already uses kzalloc/vzalloc.
>
> This clears a sparse warning :
> drivers/staging/unisys/visornic/visornic_main.c:1366:15: warning:
> memset with byte count of 1460112
>
> Signed-off-by: Hugo Camboulive <hugo.camboulive@gmail.com>
Tested, works fine. :)
Signed-off-by: Benjamin Romer <benjamin.romer@unisys.com>
prev parent reply other threads:[~2016-01-26 19:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 20:22 [PATCH] staging: unisys: visornic: remove useless memset Hugo Camboulive
2016-01-26 19:44 ` Ben Romer [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=1453837492.4209.8.camel@unisys.com \
--to=benjamin.romer@unisys.com \
--cc=Timothy.Sell@unisys.com \
--cc=david.kershner@unisys.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=hugo.camboulive@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nhorman@redhat.com \
--cc=sparmaintainer@unisys.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).