netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: tklauser@distanz.ch
Cc: cmetcalf@tilera.com, netdev@vger.kernel.org
Subject: Re: [PATCH 1/2] net: tile: Remove unnecessary memset of netdev private data
Date: Fri, 30 May 2014 17:06:47 -0700 (PDT)	[thread overview]
Message-ID: <20140530.170647.451034663144296827.davem@davemloft.net> (raw)
In-Reply-To: <1401192231-26203-1-git-send-email-tklauser@distanz.ch>

From: Tobias Klauser <tklauser@distanz.ch>
Date: Tue, 27 May 2014 14:03:51 +0200

> The memory for private data is allocated using kzalloc/vzalloc in
> alloc_netdev_mqs, thus there is no need to zero it again in the driver.
> 
> Signed-off-by: Tobias Klauser <tklauser@distanz.ch>

Applied.

      parent reply	other threads:[~2014-05-31  0:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-27 12:03 [PATCH 1/2] net: tile: Remove unnecessary memset of netdev private data Tobias Klauser
2014-05-28 19:35 ` Chris Metcalf
2014-05-31  0:06 ` David Miller [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=20140530.170647.451034663144296827.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=cmetcalf@tilera.com \
    --cc=netdev@vger.kernel.org \
    --cc=tklauser@distanz.ch \
    /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).