From: David Miller <davem@davemloft.net>
To: tgraf@suug.ch
Cc: netdev@vger.kernel.org, herbert@gondor.apana.org.au, kaber@trash.net
Subject: Re: [PATCH net 0/2 v2] rhashtable rehashing fixes
Date: Wed, 22 Apr 2015 14:21:44 -0400 (EDT) [thread overview]
Message-ID: <20150422.142144.1668540092291085139.davem@davemloft.net> (raw)
In-Reply-To: <cover.1429688383.git.tgraf@suug.ch>
From: Thomas Graf <tgraf@suug.ch>
Date: Wed, 22 Apr 2015 09:41:44 +0200
> Some rhashtable rehashing bugs found while testing with the
> next rhashtable self-test queued up for the next devel cycle:
>
> https://github.com/tgraf/net-next/commits/rht
>
> v2:
> - Moved schedule_work() call into rhashtable_insert_rehash()
Series applied, thanks guys.
prev parent reply other threads:[~2015-04-22 18:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-22 7:41 [PATCH net 0/2 v2] rhashtable rehashing fixes Thomas Graf
2015-04-22 7:41 ` [PATCH net 1/2] rhashtable: Schedule async resize when sync realloc fails Thomas Graf
2015-04-22 7:43 ` Herbert Xu
2015-04-22 7:41 ` [PATCH net 2/2] rhashtable: Do not schedule more than one rehash if we can't grow further Thomas Graf
2015-04-22 18:21 ` 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=20150422.142144.1668540092291085139.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=kaber@trash.net \
--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).