From: David Miller <davem@davemloft.net>
To: roy.qing.li@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH][net-next] ipv6: replace write lock with read lock in addrconf_permanent_addr
Date: Mon, 14 Mar 2016 12:25:34 -0400 (EDT) [thread overview]
Message-ID: <20160314.122534.345751583747280951.davem@davemloft.net> (raw)
In-Reply-To: <1457948108-24837-1-git-send-email-roy.qing.li@gmail.com>
From: roy.qing.li@gmail.com
Date: Mon, 14 Mar 2016 17:35:08 +0800
> From: Li RongQing <roy.qing.li@gmail.com>
>
> nothing of idev is changed, so read lock is enough
>
> Signed-off-by: Li RongQing <roy.qing.li@gmail.com>
We need it for the modifications made by fixup_permanent_addr().
next prev parent reply other threads:[~2016-03-14 16:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 9:35 [PATCH][net-next] ipv6: replace write lock with read lock in addrconf_permanent_addr roy.qing.li
2016-03-14 16:25 ` David Miller [this message]
2016-03-15 0:36 ` Li RongQing
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=20160314.122534.345751583747280951.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=roy.qing.li@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