From: David Miller <davem@davemloft.net>
To: gregory.v.rose@intel.com
Cc: netdev@vger.kernel.org
Subject: Re: [RFC V3 PATCH] rtnetlink: Fix problem with buffer allocation
Date: Mon, 20 Feb 2012 00:54:51 -0500 (EST) [thread overview]
Message-ID: <20120220.005451.548532173290909435.davem@davemloft.net> (raw)
In-Reply-To: <20120216235218.6381.51539.stgit@gitlad.jf.intel.com>
From: Greg Rose <gregory.v.rose@intel.com>
Date: Thu, 16 Feb 2012 15:52:18 -0800
> + for (h = 0; h < NETDEV_HASHENTRIES; h++) {
> + head = &net->dev_index_head[h];
> + hlist_for_each_entry_rcu(dev, node, head, index_hlist) {
list_for_each_entry_rcu(dev, &net->dev_base_head, dev_list)
next prev parent reply other threads:[~2012-02-20 5:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 23:52 [RFC V3 PATCH] rtnetlink: Fix problem with buffer allocation Greg Rose
2012-02-20 5:54 ` David Miller [this message]
2012-02-21 16:15 ` Rose, Gregory V
2012-02-21 17:46 ` Rose, Gregory V
2012-02-21 19:49 ` David Miller
2012-02-21 19:51 ` Rose, Gregory V
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=20120220.005451.548532173290909435.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=gregory.v.rose@intel.com \
--cc=netdev@vger.kernel.org \
/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).