From: David Miller <davem@davemloft.net>
To: neilb@suse.com
Cc: tgraf@suug.ch, herbert@gondor.apana.org.au,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] rhashtable_walk fixes
Date: Fri, 30 Mar 2018 10:18:26 -0400 (EDT) [thread overview]
Message-ID: <20180330.101826.1844442556880257787.davem@davemloft.net> (raw)
In-Reply-To: <152228607974.16370.14544827502467836789.stgit@noble>
From: NeilBrown <neilb@suse.com>
Date: Thu, 29 Mar 2018 12:19:09 +1100
> These two patches apply on top of my previous "rhashtable: reset iter
> when rhashtable_walk_start sees new table" patch.
>
> The first fixes a bug that I found in rhltable_insert().
>
> The second is an alternate to my "rhashtable: allow a walk of the hash
> table without missing object."
> This version doesn't require an API change and should be reliable for
> rhltables too (my first version didn't handle these correctly).
Neil, please don't mix and match patches.
Also when you need to change a patch in a series, please post the entire
new series not just the patch that changes.
Patch #1 in this series is unnecessary. As Herbert explained this has
been fixed already.
So please repost freshly the patches that are relevant and you want me
to consider for inclusion. Also be explicit and clear about which of
my two networking trees you are targetting these changes.
Thank you.
next prev parent reply other threads:[~2018-03-30 14:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-29 1:19 [PATCH 0/2] rhashtable_walk fixes NeilBrown
2018-03-29 1:19 ` [PATCH 1/2] rhashtable: fix insertion of in rhltable when duplicate found NeilBrown
2018-03-29 5:40 ` Herbert Xu
2018-03-29 1:19 ` [PATCH 2/2] rhashtable: improve rhashtable_walk stability when stop/start used NeilBrown
2018-03-29 5:50 ` Herbert Xu
2018-03-30 14:18 ` David Miller [this message]
2018-04-03 2:23 ` [PATCH 0/2] rhashtable_walk fixes NeilBrown
2018-04-03 2:34 ` 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=20180330.101826.1844442556880257787.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.com \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
/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).