From: Cong Wang <amwang@redhat.com>
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, Eric Dumazet <eric.dumazet@gmail.com>,
Vlad Yasevich <vyasevic@redhat.com>,
Stephen Hemminger <stephen@networkplumber.org>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [Patch net-next v5] netpoll: fix some sparse warnings in various places
Date: Tue, 19 Feb 2013 09:28:20 +0800 [thread overview]
Message-ID: <1361237300.25055.0.camel@cr0> (raw)
In-Reply-To: <20130218170126.GA1576@minipsycho.orion>
On Mon, 2013-02-18 at 18:01 +0100, Jiri Pirko wrote:
> >- return bond->dev->npinfo;
> >+ return rcu_access_pointer(bond->dev->npinfo) != NULL;
> ^^^^^^^^
> this is not necessary
> (sorry for nitpick)
No problem. Then let's drop this patch. :)
prev parent reply other threads:[~2013-02-19 1:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 3:22 [Patch net-next v5] netpoll: fix some sparse warnings in various places Cong Wang
2013-02-18 17:01 ` Jiri Pirko
2013-02-19 1:28 ` Cong Wang [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=1361237300.25055.0.camel@cr0 \
--to=amwang@redhat.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=vyasevic@redhat.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).