From: David Miller <davem@davemloft.net>
To: herbert@gondor.apana.org.au
Cc: tom@quantonium.net, netdev@vger.kernel.org, rohit@quantonium.net
Subject: Re: [PATCH v2 net-next 0/5] rhashtable: New features in walk and bucket
Date: Mon, 11 Dec 2017 10:10:08 -0500 (EST) [thread overview]
Message-ID: <20171211.101008.1546938509376306919.davem@davemloft.net> (raw)
In-Reply-To: <20171211120324.GP12014@gondor.apana.org.au>
From: Herbert Xu <herbert@gondor.apana.org.au>
Date: Mon, 11 Dec 2017 23:03:24 +1100
> On Tue, Dec 05, 2017 at 02:47:58PM -0500, David Miller wrote:
>>
>> I'll allow Herbert time to think about this some more as he requested
>> in comments against the first version of this series.
>
> Sorry for the late response. Tom's changes look good to me.
>
> We should also fix up all existing rhashtable users that dump
> through netlink to use the new peek interface.
Thanks for reviewing Herbert, series applied.
Thanks everyone.
prev parent reply other threads:[~2017-12-11 15:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 18:31 [PATCH v2 net-next 0/5] rhashtable: New features in walk and bucket Tom Herbert
2017-12-04 18:31 ` [PATCH v2 net-next 1/5] rhashtable: Change rhashtable_walk_start to return void Tom Herbert
2017-12-11 12:02 ` Herbert Xu
2017-12-04 18:31 ` [PATCH v2 net-next 2/5] rhashtable: Add rhastable_walk_peek Tom Herbert
2017-12-11 12:02 ` Herbert Xu
2017-12-04 18:31 ` [PATCH v2 net-next 3/5] rhashtable: abstract out function to get hash Tom Herbert
2017-12-04 18:31 ` [PATCH v2 net-next 4/5] spinlock: Add library function to allocate spinlock buckets array Tom Herbert
2017-12-04 18:31 ` [PATCH v2 net-next 5/5] rhashtable: Call library function alloc_bucket_locks Tom Herbert
2017-12-05 19:47 ` [PATCH v2 net-next 0/5] rhashtable: New features in walk and bucket David Miller
2017-12-11 12:03 ` Herbert Xu
2017-12-11 15:10 ` 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=20171211.101008.1546938509376306919.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
--cc=rohit@quantonium.net \
--cc=tom@quantonium.net \
/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).