From: David Miller <davem@davemloft.net>
To: fw@strlen.de
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next 2/2] ipv6: addrconf: don't use rtnl mutex in RTM_GETADDR
Date: Wed, 11 Oct 2017 20:17:25 -0700 (PDT) [thread overview]
Message-ID: <20171011.201725.646380607630686644.davem@davemloft.net> (raw)
In-Reply-To: <20171011082801.12715-3-fw@strlen.de>
From: Florian Westphal <fw@strlen.de>
Date: Wed, 11 Oct 2017 10:28:01 +0200
> Similar to the previous patch, use the device lookup functions
> that bump device refcount and flag this as DOIT_UNLOCKED to avoid
> rtnl mutex.
>
> Signed-off-by: Florian Westphal <fw@strlen.de>
Applied.
prev parent reply other threads:[~2017-10-12 3:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 8:27 [PATCH net-next 0/2] ipv6: addrconf: make two more doit functions not use rtnl mutex Florian Westphal
2017-10-11 8:28 ` [PATCH net-next 1/2] ipv6: addrconf: don't use rtnl mutex in RTM_GETNETCONF Florian Westphal
2017-10-12 3:17 ` David Miller
2017-10-11 8:28 ` [PATCH net-next 2/2] ipv6: addrconf: don't use rtnl mutex in RTM_GETADDR Florian Westphal
2017-10-12 3:17 ` 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=20171011.201725.646380607630686644.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=fw@strlen.de \
--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).