From: David Miller <davem@davemloft.net>
To: neilb@suse.com
Cc: herbert@gondor.apana.org.au, tgraf@suug.ch,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/6] rhashtable: remove outdated comments about grow_decision etc
Date: Wed, 18 Apr 2018 21:47:37 -0400 (EDT) [thread overview]
Message-ID: <20180418.214737.1146004592657647139.davem@davemloft.net> (raw)
In-Reply-To: <878t9kqfhq.fsf@notabene.neil.brown.name>
From: NeilBrown <neilb@suse.com>
Date: Thu, 19 Apr 2018 09:09:05 +1000
> On Wed, Apr 18 2018, Herbert Xu wrote:
>
>> On Wed, Apr 18, 2018 at 04:47:01PM +1000, NeilBrown wrote:
>>> grow_decision and shink_decision no longer exist, so remove
>>> the remaining references to them.
>>>
>>> Signed-off-by: NeilBrown <neilb@suse.com>
>>
>> Acked-by: Herbert Xu <herbert@gondor.apana.org.au>
>
> Thanks. Is that Ack sufficient for this patch to go upstream, or is
> there something else that I need to do?
One patch being ACK'd does not release the whole series to be applied
and the whole series will be treated as a complete unit for that
purpose.
So if discussion is holding up one patch in the series, it holds up
the entire series.
So get the entire series in acceptable condition, or submit only one
change at a time individually and wait for that one to be accepted
before you submit and ask for feedback on the next one.
I hope that makes things clear for you.
next prev parent reply other threads:[~2018-04-19 1:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 6:47 [PATCH 0/6] Assorted rhashtable improvements. RESEND NeilBrown
2018-04-18 6:47 ` [PATCH 2/6] rhashtable: remove incorrect comment on r{hl, hash}table_walk_enter() NeilBrown
2018-04-18 14:28 ` Herbert Xu
2018-04-18 22:56 ` NeilBrown
2018-04-19 3:22 ` Herbert Xu
2018-04-23 1:39 ` NeilBrown
2018-04-23 8:06 ` Herbert Xu
2018-04-18 6:47 ` [PATCH 3/6] rhashtable: reset iter when rhashtable_walk_start sees new table NeilBrown
2018-04-18 6:47 ` [PATCH 1/6] rhashtable: remove outdated comments about grow_decision etc NeilBrown
2018-04-18 14:29 ` Herbert Xu
2018-04-18 23:09 ` NeilBrown
2018-04-19 1:47 ` David Miller [this message]
2018-04-23 1:41 ` NeilBrown
2018-04-18 6:47 ` [PATCH 5/6] rhashtable: further improve stability of rhashtable_walk NeilBrown
2018-04-18 6:47 ` [PATCH 4/6] rhashtable: improve rhashtable_walk stability when stop/start used NeilBrown
2018-04-18 6:47 ` [PATCH 6/6] rhashtable: add rhashtable_walk_prev() NeilBrown
2018-04-18 14:35 ` Herbert Xu
2018-04-18 23:08 ` NeilBrown
2018-04-23 8:07 ` Herbert Xu
-- strict thread matches above, loose matches on Subject: below --
2018-04-18 6:47 [PATCH 0/6] Assorted rhashtable improvements NeilBrown
2018-04-18 6:47 ` [PATCH 1/6] rhashtable: remove outdated comments about grow_decision etc NeilBrown
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=20180418.214737.1146004592657647139.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