From: Ingo Molnar <mingo@kernel.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>, Jason Baron <jbaron@akamai.com>
Subject: Re: [PATCH net-next v4 3/9] static_key: WARN on usage before jump_label_init was called
Date: Thu, 7 Nov 2013 10:08:44 +0100 [thread overview]
Message-ID: <20131107090844.GA719@gmail.com> (raw)
In-Reply-To: <20131106200200.7847535d@gandalf.local.home>
* Steven Rostedt <rostedt@goodmis.org> wrote:
> On Thu, 7 Nov 2013 01:50:27 +0100
> Hannes Frederic Sowa <hannes@stressinduktion.org> wrote:
>
> > On Wed, Nov 06, 2013 at 04:16:49PM -0500, Steven Rostedt wrote:
> > > Sorry for the late reply, but this was sent while I was getting ready
> > > for my two week conference trip.
> > >
> > > Note, this should not go through the net tree, but instead should go
> > > through tip, as it deals with jump labels and not networking.
> > >
> > > Otherwise, this patch looks good.
> > >
> > > Reviewed-by: Steven Rostedt <rostedt@goodmis.org>
> >
> > Thanks for the review!
> >
> > The patch already got queued up in net-next. Is this ok or what do you
> > suggest to resolve this?
> >
>
> I'm fine, but really. Changes need to go through the trees they are
> maintained by. Would Dave Miller like it if I pushed patches that
> touched the net directory without a single Ack?
I second that concern.
Thanks,
Ingo
next prev parent reply other threads:[~2013-11-07 9:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-19 19:48 [PATCH net-next v4 0/9] Introduce support to lazy initialize mostly static keys Hannes Frederic Sowa
2013-10-19 19:48 ` [PATCH net-next v4 1/9] ipv4: split inet_ehashfn to hash functions per compilation unit Hannes Frederic Sowa
2013-10-19 19:48 ` [PATCH net-next v4 2/9] ipv6: split inet6_ehashfn " Hannes Frederic Sowa
2013-10-19 19:48 ` [PATCH net-next v4 3/9] static_key: WARN on usage before jump_label_init was called Hannes Frederic Sowa
2013-11-06 21:16 ` Steven Rostedt
2013-11-07 0:50 ` Hannes Frederic Sowa
2013-11-07 1:02 ` Steven Rostedt
2013-11-07 9:08 ` Ingo Molnar [this message]
2013-10-19 19:48 ` [PATCH net-next v4 4/9] x86/jump_label: expect default_nop if static_key gets enabled on boot-up Hannes Frederic Sowa
2013-10-19 19:48 ` [PATCH net-next v4 5/9] net: introduce new macro net_get_random_once Hannes Frederic Sowa
2013-10-19 19:48 ` [PATCH net-next v4 6/9] inet: split syncookie keys for ipv4 and ipv6 and initialize with net_get_random_once Hannes Frederic Sowa
2013-10-19 19:48 ` [PATCH net-next v4 7/9] inet: convert inet_ehash_secret and ipv6_hash_secret to net_get_random_once Hannes Frederic Sowa
2013-10-19 19:48 ` [PATCH net-next v4 8/9] tcp: switch tcp_fastopen key generation " Hannes Frederic Sowa
2013-10-19 19:48 ` [PATCH net-next v4 9/9] net: switch net_secret " Hannes Frederic Sowa
2013-10-19 23:46 ` [PATCH net-next v4 0/9] Introduce support to lazy initialize mostly static keys David Miller
2013-10-20 3:33 ` Hannes Frederic Sowa
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=20131107090844.GA719@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=andi@firstfloor.org \
--cc=hannes@stressinduktion.org \
--cc=jbaron@akamai.com \
--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 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.