From: Thomas Graf <tgraf@suug.ch>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, herbert@gondor.apana.org.au,
daniel@iogearbox.net
Subject: [PATCH 0/3 net-next] Minor rhashtable fixes
Date: Fri, 13 Mar 2015 15:45:18 +0100 [thread overview]
Message-ID: <cover.1426257747.git.tgraf@suug.ch> (raw)
Thomas Graf (3):
rhashtable: Avoid calculating hash again to unlock
rhashtable: Use spin_lock_bh_nested() consistently
rhashtable: Annotate RCU locking of walkers
lib/rhashtable.c | 21 +++++++++++----------
1 file changed, 11 insertions(+), 10 deletions(-)
---
Applies on top of Herbert's fixes:
("[PATCH 0/6] rhashtable: Fixes + cleanups + preparation for multiple rehash")
next reply other threads:[~2015-03-13 14:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 14:45 Thomas Graf [this message]
2015-03-13 14:45 ` [PATCH 1/3 net-next] rhashtable: Avoid calculating hash again to unlock Thomas Graf
2015-03-14 2:20 ` Herbert Xu
2015-03-13 14:45 ` [PATCH 2/3 net-next] rhashtable: Use spin_lock_bh_nested() consistently Thomas Graf
2015-03-13 16:54 ` David Miller
2015-03-14 2:21 ` Herbert Xu
2015-03-16 8:44 ` Thomas Graf
2015-03-13 14:45 ` [PATCH 3/3 net-next] rhashtable: Annotate RCU locking of walkers Thomas Graf
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=cover.1426257747.git.tgraf@suug.ch \
--to=tgraf@suug.ch \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.