From: Florian Westphal <fw@strlen.de>
To: David Howells <dhowells@redhat.com>
Cc: Florian Westphal <fw@strlen.de>,
netdev@vger.kernel.org, linux-afs@lists.infradead.org,
eric.dumazet@gmail.com
Subject: Re: [PATCH net-next 3/7] afs: switch to in_dev_for_each_ifa_rcu
Date: Wed, 29 May 2019 15:57:07 +0200 [thread overview]
Message-ID: <20190529135707.thwqw5ibitmwsnom@breakpoint.cc> (raw)
In-Reply-To: <20802.1559137779@warthog.procyon.org.uk>
David Howells <dhowells@redhat.com> wrote:
> Actually, whilst thanks are due for doing the work - it looks nicer now - I'm
> told that there's not really any point populating the list. Current OpenAFS
> ignores it, as does AuriStor - and IBM AFS 3.6 will do the right thing.
[..]
> On that basis, feel free to make it an empty list and remove all the interface
> enumeration.
Ok, will wait for others to comment before doing this in v2.
next prev parent reply other threads:[~2019-05-29 13:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 11:43 [PATCH net-next 0/7] net: add rcu annotations for ifa_list Florian Westphal
2019-05-29 11:43 ` [PATCH net-next 1/7] net: inetdevice: provide replacement iterators for in_ifaddr walk Florian Westphal
2019-05-29 11:43 ` [PATCH net-next 2/7] devinet: use in_dev_for_each_ifa_rcu in more places Florian Westphal
2019-05-29 11:43 ` [PATCH net-next 3/7] afs: switch to in_dev_for_each_ifa_rcu Florian Westphal
2019-05-29 13:49 ` David Howells
2019-05-29 13:57 ` Florian Westphal [this message]
2019-05-29 11:43 ` [PATCH net-next 4/7] netfilter: use in_dev_for_each_ifa_rcu Florian Westphal
2019-05-29 11:43 ` [PATCH net-next 5/7] net: use new in_dev_ifa iterators Florian Westphal
2019-05-29 11:43 ` [PATCH net-next 6/7] drivers: use in_dev_for_each_ifa_rtnl/rcu Florian Westphal
2019-05-29 11:43 ` [PATCH net-next 7/7] net: ipv4: provide __rcu annotation for ifa_list Florian Westphal
2019-05-30 21:23 ` [PATCH net-next 0/7] net: add rcu annotations " 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=20190529135707.thwqw5ibitmwsnom@breakpoint.cc \
--to=fw@strlen.de \
--cc=dhowells@redhat.com \
--cc=eric.dumazet@gmail.com \
--cc=linux-afs@lists.infradead.org \
--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).