All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] ARM: OMAP: second set of PRCM cleanups for 3.8
Date: Wed, 7 Nov 2012 09:06:09 -0800	[thread overview]
Message-ID: <20121107170608.GD6801@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1211071655000.20704@utopia.booyaka.com>

* Paul Walmsley <paul@pwsan.com> [121107 08:57]:
> On Wed, 7 Nov 2012, Paul Walmsley wrote:
> 
> > On Tue, 6 Nov 2012, Tony Lindgren wrote:
> > 
> > > I'm getting errors with the allnoconfig ones, there are total four
> > > omap defconfigs there not counting the randconfigs.
> > 
> > That might indeed explain the discrepancy; so far only have been building 
> > his oldconfig seeds here.  Will add his allnoconfig seeds and test again.
> 
> Can reproduce this here.  Thanks for catching this.  Will fix and send a 
> new pull request today and ensure that the two allnoconfigs are added to 
> the build tests from now on.

OK thanks!

Tony

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: OMAP: second set of PRCM cleanups for 3.8
Date: Wed, 7 Nov 2012 09:06:09 -0800	[thread overview]
Message-ID: <20121107170608.GD6801@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1211071655000.20704@utopia.booyaka.com>

* Paul Walmsley <paul@pwsan.com> [121107 08:57]:
> On Wed, 7 Nov 2012, Paul Walmsley wrote:
> 
> > On Tue, 6 Nov 2012, Tony Lindgren wrote:
> > 
> > > I'm getting errors with the allnoconfig ones, there are total four
> > > omap defconfigs there not counting the randconfigs.
> > 
> > That might indeed explain the discrepancy; so far only have been building 
> > his oldconfig seeds here.  Will add his allnoconfig seeds and test again.
> 
> Can reproduce this here.  Thanks for catching this.  Will fix and send a 
> new pull request today and ensure that the two allnoconfigs are added to 
> the build tests from now on.

OK thanks!

Tony

  reply	other threads:[~2012-11-07 17:06 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-01 12:17 [GIT PULL] ARM: OMAP: second set of PRCM cleanups for 3.8 Paul Walmsley
2012-11-01 12:17 ` Paul Walmsley
2012-11-06 22:08 ` Tony Lindgren
2012-11-06 22:08   ` Tony Lindgren
2012-11-07  1:53   ` Paul Walmsley
2012-11-07  1:53     ` Paul Walmsley
2012-11-07  1:58     ` Tony Lindgren
2012-11-07  1:58       ` Tony Lindgren
2012-11-07  2:39       ` Paul Walmsley
2012-11-07  2:39         ` Paul Walmsley
2012-11-07 16:55         ` Paul Walmsley
2012-11-07 16:55           ` Paul Walmsley
2012-11-07 17:06           ` Tony Lindgren [this message]
2012-11-07 17:06             ` Tony Lindgren
2012-11-08 17:59           ` Paul Walmsley
2012-11-08 17:59             ` Paul Walmsley
2012-11-07 18:19         ` Paul Walmsley
2012-11-07 18:19           ` Paul Walmsley
2012-11-07 18:22           ` Tony Lindgren
2012-11-07 18:22             ` Tony Lindgren

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=20121107170608.GD6801@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.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.