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: Mon, 02 Apr 2018 22:34:04 -0400 (EDT) [thread overview]
Message-ID: <20180402.223404.1004723633191084443.davem@davemloft.net> (raw)
In-Reply-To: <8760591103.fsf@notabene.neil.brown.name>
From: NeilBrown <neilb@suse.com>
Date: Tue, 03 Apr 2018 12:23:40 +1000
> I'm sorry if I've caused some confusion, but I didn't think that I was
> submitting patches to you and know nothing about your two trees.
> I was submitting patches to Thomas and Herbert, the registered
> maintainers of rhashtable. I assumed they would review, respond, and
> take responsibility for getting them upstream, if that's what they
> decided, based on whatever arrangements they have in place.
>
> If it is appropriate I can resend all of my patches that receive an
> Ack as a coherent series, and send this to you nominating a particular
> tree, but I'm unlikely to do that unless asked and told which tree to
> nominate.
Herbert and Thomas generally review rhashtable patches, but rhashtable
itself is generally maintained in the networking tree(s). So once
they review and ACK it, I would apply it.
prev parent reply other threads:[~2018-04-03 2:34 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 ` [PATCH 0/2] rhashtable_walk fixes David Miller
2018-04-03 2:23 ` NeilBrown
2018-04-03 2:34 ` 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=20180402.223404.1004723633191084443.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).