From: Greg KH <gregkh@linuxfoundation.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] tracepoints: Do not trace when cpu is offline" failed to apply to 3.14-stable tree
Date: Wed, 24 Feb 2016 10:16:02 -0800 [thread overview]
Message-ID: <20160224181602.GA22773@kroah.com> (raw)
In-Reply-To: <20160224125033.5cfef465@gandalf.local.home>
On Wed, Feb 24, 2016 at 12:50:33PM -0500, Steven Rostedt wrote:
> On Wed, 24 Feb 2016 09:14:18 -0800
> Greg KH <gregkh@linuxfoundation.org> wrote:
>
> > On Wed, Feb 24, 2016 at 10:18:32AM -0500, Steven Rostedt wrote:
> > > On Tue, 23 Feb 2016 19:37:04 -0800
> > > Greg KH <gregkh@linuxfoundation.org> wrote:
> > >
> > >
> > > > Yes, it applies, sorry, but it breaks the build :(
> > > >
> > > > Same for 3.10-stable. It applies but can not compile.
> > > >
> > > > can you fix that up?
> > > >
> > >
> > > Bah. smp.h isn't enough for using raw_smp_processor_id(). One must also
> > > include percpu.h. That was fixed in mainline, but not in stable. But not
> > > a big deal. I'll included percpu.h in tracepoint.h as well.
> >
> > What was the commit id that did that change? Is it simple enough to
> > just take that patch instead?
> >
>
> Hmm, I don't know where the include is done. Perhaps something else
> included it and it was just a luck that this commit works in mainline.
Ok, I'll stick with what you sent, thanks.
greg k-h
prev parent reply other threads:[~2016-02-24 18:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 0:48 FAILED: patch "[PATCH] tracepoints: Do not trace when cpu is offline" failed to apply to 3.14-stable tree gregkh
2016-02-24 3:24 ` Steven Rostedt
2016-02-24 3:37 ` Greg KH
2016-02-24 14:21 ` Steven Rostedt
2016-02-24 17:07 ` Greg KH
2016-02-24 17:17 ` Steven Rostedt
2016-02-24 15:18 ` Steven Rostedt
2016-02-24 16:00 ` Steven Rostedt
2016-02-24 17:14 ` Greg KH
2016-02-24 17:50 ` Steven Rostedt
2016-02-24 18:16 ` Greg KH [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=20160224181602.GA22773@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=rostedt@goodmis.org \
--cc=stable@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