linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Andi Kleen <andi@firstfloor.org>,
	jolsa@kernel.org, linux-kernel@vger.kernel.org,
	Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH] perf, tools, stat: Include asm/bug.h for WARN_ON
Date: Wed, 17 Feb 2016 22:22:48 +0100	[thread overview]
Message-ID: <20160217212247.GC5083@two.firstfloor.org> (raw)
In-Reply-To: <20160217192444.GB9909@kernel.org>

On Wed, Feb 17, 2016 at 04:24:44PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Wed, Feb 17, 2016 at 08:15:35PM +0100, Andi Kleen escreveu:
> > On Wed, Feb 17, 2016 at 03:56:21PM -0300, Arnaldo Carvalho de Melo wrote:
> > > Em Wed, Feb 17, 2016 at 03:52:09PM -0300, Arnaldo Carvalho de Melo escreveu:
> > > > Em Wed, Feb 17, 2016 at 10:39:08AM -0800, Andi Kleen escreveu:
> > > > > In my set up (separate objdir, DEBUG=1) tip perf doesn't build without this change.
> > > > > It may be that in some other setups asm/bug.h is implicitely included.
> > >  
> > > > Thanks, applying your fix, after making it build on acme/perf/core:
> > > 
> > > I take that back, it is already there:
> > 
> > Ok, but not in tip/perf/core. Can you push it there please?
> 
> Huh? I can't, this is not my tree, its Ingo's. But lemme check there...

Never mind. Ended up being a local problem. Thanks for checking.

-Andi

      reply	other threads:[~2016-02-17 21:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-17 18:39 [PATCH] perf, tools, stat: Include asm/bug.h for WARN_ON Andi Kleen
2016-02-17 18:52 ` Arnaldo Carvalho de Melo
2016-02-17 18:56   ` Arnaldo Carvalho de Melo
2016-02-17 19:15     ` Andi Kleen
2016-02-17 19:24       ` Arnaldo Carvalho de Melo
2016-02-17 21:22         ` Andi Kleen [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=20160217212247.GC5083@two.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@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).