From: David Miller <davem@davemloft.net>
To: fw@strlen.de
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH -next] rhashtable: remove insecure_elasticity
Date: Tue, 18 Apr 2017 13:49:38 -0400 (EDT) [thread overview]
Message-ID: <20170418.134938.272786427332860211.davem@davemloft.net> (raw)
In-Reply-To: <20170416005509.31784-1-fw@strlen.de>
From: Florian Westphal <fw@strlen.de>
Date: Sun, 16 Apr 2017 02:55:09 +0200
> commit 83e7e4ce9e93c3 ("mac80211: Use rhltable instead of rhashtable")
> removed the last user that made use of 'insecure_elasticity' parameter,
> i.e. the default of 16 is used everywhere.
>
> Replace it with a constant.
>
> Signed-off-by: Florian Westphal <fw@strlen.de>
Yeah if it's not used, we can kill it. If someone needs it again it is
trivial to add it back if necessary.
Applied, thanks Florian.
prev parent reply other threads:[~2017-04-18 17:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-16 0:55 [PATCH -next] rhashtable: remove insecure_elasticity Florian Westphal
2017-04-18 17:49 ` 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=20170418.134938.272786427332860211.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=fw@strlen.de \
--cc=netdev@vger.kernel.org \
/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).