From: David Miller <davem@davemloft.net>
To: hannes@stressinduktion.org
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Introduce support to lazy initialize mostly static keys v2
Date: Sat, 05 Oct 2013 22:55:43 -0400 (EDT) [thread overview]
Message-ID: <20131005.225543.1900911827217618002.davem@davemloft.net> (raw)
In-Reply-To: <1381015258-7667-1-git-send-email-hannes@stressinduktion.org>
Please in the future use "[PATCH 0/8] " as a subject prefix for
postings such as this one which introduces a patch set.
Thanks.
prev parent reply other threads:[~2013-10-06 2:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-05 23:20 Introduce support to lazy initialize mostly static keys v2 Hannes Frederic Sowa
2013-10-05 23:20 ` [PATCH net-next v2 1/8] ipv4: split inet_ehashfn to hash functions per compilation unit Hannes Frederic Sowa
2013-10-05 23:20 ` [PATCH net-next v2 2/8] ipv6: split inet6_ehashfn " Hannes Frederic Sowa
2013-10-05 23:20 ` [PATCH net-next v2 3/8] x86/jump_label: expect default_nop if static_key gets enabled on boot-up Hannes Frederic Sowa
2013-10-06 0:05 ` Steven Rostedt
2013-10-06 0:12 ` Hannes Frederic Sowa
2013-10-06 18:29 ` [PATCH] static_key: WARN on usage before jump_label_init was called Hannes Frederic Sowa
2013-10-07 15:51 ` Steven Rostedt
2013-10-07 16:57 ` [PATCH v2] " Hannes Frederic Sowa
2013-10-05 23:20 ` [PATCH net-next v2 4/8] net: introduce new macro net_get_random_once Hannes Frederic Sowa
2013-10-05 23:20 ` [PATCH net-next v2 5/8] inet: split syncookie keys for ipv4 and ipv6 and initialize with net_get_random_once Hannes Frederic Sowa
2013-10-05 23:20 ` [PATCH net-next v2 6/8] inet: convert inet_ehash_secret and ipv6_hash_secret to net_get_random_once Hannes Frederic Sowa
2013-10-05 23:20 ` [PATCH net-next v2 7/8] tcp: switch tcp_fastopen key generation " Hannes Frederic Sowa
2013-10-05 23:20 ` [PATCH net-next v2 8/8] net: switch net_secret " Hannes Frederic Sowa
2013-10-06 2:55 ` 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=20131005.225543.1900911827217618002.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hannes@stressinduktion.org \
--cc=linux-kernel@vger.kernel.org \
--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).