From: Andi Kleen <andi@firstfloor.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Hannes Frederic Sowa <hannes@stressinduktion.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Andi Kleen <andi@firstfloor.org>
Subject: Re: [PATCH net-next v3 3/9] static_key: WARN on usage before jump_label_init was called
Date: Fri, 18 Oct 2013 02:50:57 +0200 [thread overview]
Message-ID: <20131018005057.GL2592@two.firstfloor.org> (raw)
In-Reply-To: <20131017171940.173bab09@gandalf.local.home>
On Thu, Oct 17, 2013 at 05:19:40PM -0400, Steven Rostedt wrote:
> On Thu, 17 Oct 2013 07:31:57 +0200
> Hannes Frederic Sowa <hannes@stressinduktion.org> wrote:
>
> > Based on a patch from Andi Kleen.
>
> I'm fine with the patch, but the change log needs a lot more work.
> Like, why is this needed? I know, but does anyone else?
Or just merge the orininal patch. While being less verbose
in the warning it had a full changelog.
-Andi
next prev parent reply other threads:[~2013-10-18 0:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-17 5:31 [PATCH net-next v3 0/9] Introduce support to lazy initialize mostly static keys Hannes Frederic Sowa
2013-10-17 5:31 ` [PATCH net-next v3 1/9] ipv4: split inet_ehashfn to hash functions per compilation unit Hannes Frederic Sowa
2013-10-17 5:31 ` [PATCH net-next v3 2/9] ipv6: split inet6_ehashfn " Hannes Frederic Sowa
2013-10-17 5:31 ` [PATCH net-next v3 3/9] static_key: WARN on usage before jump_label_init was called Hannes Frederic Sowa
2013-10-17 21:19 ` Steven Rostedt
2013-10-18 0:01 ` Hannes Frederic Sowa
2013-10-18 0:50 ` Andi Kleen [this message]
2013-10-18 1:16 ` Hannes Frederic Sowa
2013-10-17 5:31 ` [PATCH net-next v3 4/9] x86/jump_label: expect default_nop if static_key gets enabled on boot-up Hannes Frederic Sowa
2013-10-17 5:31 ` [PATCH net-next v3 5/9] net: introduce new macro net_get_random_once Hannes Frederic Sowa
2013-10-17 5:32 ` [PATCH net-next v3 6/9] inet: split syncookie keys for ipv4 and ipv6 and initialize with net_get_random_once Hannes Frederic Sowa
2013-10-17 5:32 ` [PATCH net-next v3 7/9] inet: convert inet_ehash_secret and ipv6_hash_secret to net_get_random_once Hannes Frederic Sowa
2013-10-17 5:32 ` [PATCH net-next v3 8/9] tcp: switch tcp_fastopen key generation " Hannes Frederic Sowa
2013-10-17 5:32 ` [PATCH net-next v3 9/9] net: switch net_secret " Hannes Frederic Sowa
2013-10-18 20:32 ` [PATCH net-next v3 0/9] Introduce support to lazy initialize mostly static keys David Miller
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=20131018005057.GL2592@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=a.p.zijlstra@chello.nl \
--cc=hannes@stressinduktion.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rostedt@goodmis.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).