All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Stephen Warren <swarren@nvidia.com>
Subject: Re: mainline build failure (Was: Re: linux-next: build failure after merge of the regmap tree)
Date: Thu, 12 Apr 2012 16:46:50 +0100	[thread overview]
Message-ID: <20120412154649.GA3195@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20120412080714.1b9fe574b18adebcc8af0ff1@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 946 bytes --]

On Thu, Apr 12, 2012 at 08:07:14AM +1000, Stephen Rothwell wrote:

> So, what is this failure and what configs do you build?  And has a fix
> been submitted?

It's a build failure in the trace subsystem when perf isn't enabled; I
submitted a patch as soon as I noticed the issue which was either during
the merge window or just after -rc1 came out and resubmitted it again
this week.  In response to the reposting Steven Rostedt said he'd pick
the fix up but I'm not sure when that'll happen or how long it'll take
to propagate to mainline, this appears to be one of those areas where
things get processed in batch mode.

I mainly build an ARM config that I can run usefully on my development
boards which is mostly built in and a modular x86 config since x86 seems
to have lots of issues with modular stuff.  I should be able to adjust
the ARM config to build, I didn't yet mostly because I wasn't expecting
the issue to be ignored for so long.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2012-04-12 15:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-11  4:13 linux-next: build failure after merge of the regmap tree Stephen Rothwell
2012-04-11  8:17 ` Mark Brown
2012-04-11 22:07   ` mainline build failure (Was: Re: linux-next: build failure after merge of the regmap tree) Stephen Rothwell
2012-04-12 15:46     ` Mark Brown [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=20120412154649.GA3195@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=swarren@nvidia.com \
    /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.