linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: kiko@linaro.org (Christian Robottom Reis)
To: linux-arm-kernel@lists.infradead.org
Subject: snowball does not compile on linux-next
Date: Tue, 3 Jan 2012 11:20:33 -0200	[thread overview]
Message-ID: <20120103132033.GD9771@async.com.br> (raw)
In-Reply-To: <CACRpkdZfaOA0suxO8Gp7mw-VGPFju2dCJwDocO_K7Dx4-2z0Rw@mail.gmail.com>

On Tue, Jan 03, 2012 at 08:19:37AM +0100, Linus Walleij wrote:
> On Mon, Jan 2, 2012 at 4:25 PM, Christian Robottom Reis <kiko@linaro.org> wrote:
> > On Mon, Jan 02, 2012 at 01:59:10PM +0100, Linus Walleij wrote:
> >> On Mon, Jan 2, 2012 at 12:49 PM, Daniel Lezcano
> >> <daniel.lezcano@linaro.org> wrote:
> >>
> >> > the kernel does not compile when
> >> > CONFIG_CLKSRC_DBX500_PRCMU_SCHED_CLOCK is set.
> >
> > Should this be in our default configs, or one of our tested configs, so
> > we can catch this in a CI loop?
> 
> It should be in the defconfig already, the problem showed up
> for Daniel exactly because it was configured in.

Okay, then the question is what do we need to do to make a box go red
and have people notified when it breaks?
-- 
Christian Robottom Reis, Engineering VP
Brazil (GMT-3) | [+55] 16 9112 6430 | [+1] 612 216 4935
Linaro.org: Open Source Software for ARM SoCs

  reply	other threads:[~2012-01-03 13:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-02 11:49 snowball does not compile on linux-next Daniel Lezcano
2012-01-02 12:59 ` Linus Walleij
2012-01-02 13:55   ` Daniel Lezcano
2012-01-02 14:00     ` Linus Walleij
2012-01-02 14:00     ` Daniel Lezcano
2012-01-02 15:25   ` Christian Robottom Reis
2012-01-03  7:19     ` Linus Walleij
2012-01-03 13:20       ` Christian Robottom Reis [this message]
2012-01-04  9:44         ` Linus Walleij

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=20120103132033.GD9771@async.com.br \
    --to=kiko@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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).