From: David Miller <davem@davemloft.net>
To: anish@chelsio.com
Cc: netdev@vger.kernel.org, hch@infradead.org, kxie@chelsio.com,
manojmalviya@chelsio.com, aaron.lu@intel.com,
xiyou.wangcong@gmail.com, fengguang.wu@intel.com
Subject: Re: [PATCH net-next] cxgb4i : remove spurious use of rcu
Date: Sat, 02 Aug 2014 20:34:27 -0700 (PDT) [thread overview]
Message-ID: <20140802.203427.334773977447118350.davem@davemloft.net> (raw)
In-Reply-To: <1407019844-21148-1-git-send-email-anish@chelsio.com>
From: Anish Bhatt <anish@chelsio.com>
Date: Sat, 2 Aug 2014 15:50:44 -0700
> As pointed out by the intel guys, there is no need to hold rcu read lock in
> cxgbi_inet6addr_handler(), this patch removes it.
>
> Fixes: 759a0cc5a3e1 ("cxgb4i: Add ipv6 code to driver, call into libcxgbi ipv6
> api")
> Signed-off-by: Anish Bhatt <anish@chelsio.com>
Applied, thanks.
prev parent reply other threads:[~2014-08-03 3:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-02 22:50 [PATCH net-next] cxgb4i : remove spurious use of rcu Anish Bhatt
2014-08-03 3:34 ` 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=20140802.203427.334773977447118350.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=aaron.lu@intel.com \
--cc=anish@chelsio.com \
--cc=fengguang.wu@intel.com \
--cc=hch@infradead.org \
--cc=kxie@chelsio.com \
--cc=manojmalviya@chelsio.com \
--cc=netdev@vger.kernel.org \
--cc=xiyou.wangcong@gmail.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).