From: Eric Dumazet <eric.dumazet@gmail.com>
To: Jiri Pirko <jpirko@redhat.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, jbrouer@redhat.com,
paulmck@linux.vnet.ibm.com, wfg@linux.intel.com
Subject: Re: [patch net-next] team: do RCU update path fixups
Date: Wed, 20 Jun 2012 21:14:03 +0200 [thread overview]
Message-ID: <1340219643.4604.1641.camel@edumazet-glaptop> (raw)
In-Reply-To: <1340217579-1478-1-git-send-email-jpirko@redhat.com>
On Wed, 2012-06-20 at 20:39 +0200, Jiri Pirko wrote:
> Use rcu_access_pointer and rcu_dereference_protected
> to access RCU pointer by updater.
> Use RCU_INIT_POINTER for NULL assignment of RCU pointer.
>
> Signed-off-by: Jiri Pirko <jpirko@redhat.com>
> ---
> drivers/net/team/team_mode_activebackup.c | 8 ++++++--
> drivers/net/team/team_mode_loadbalance.c | 14 ++++++++++----
> 2 files changed, 16 insertions(+), 6 deletions(-)
Seems good to me, thanks.
Acked-by: Eric Dumazet <edumazet@google.com>
next prev parent reply other threads:[~2012-06-20 19:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 18:39 [patch net-next] team: do RCU update path fixups Jiri Pirko
2012-06-20 19:14 ` Eric Dumazet [this message]
2012-06-20 21:05 ` David Miller
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=1340219643.4604.1641.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=jbrouer@redhat.com \
--cc=jpirko@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=wfg@linux.intel.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