All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, Dmitry Baryshkov <dbaryshkov@gmail.com>
Subject: Re: linux-next: arm build failure
Date: Sun, 22 Jun 2008 20:00:41 +0100	[thread overview]
Message-ID: <20080622190041.GB21340@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20080616173757.4d8ba97a.sfr@canb.auug.org.au>

On Mon, Jun 16, 2008 at 05:37:57PM +1000, Stephen Rothwell wrote:
> On Mon, 16 Jun 2008 08:29:16 +0100 Russell King <rmk@arm.linux.org.uk> wrote:
> >
> > On Mon, Jun 16, 2008 at 04:07:47PM +1000, Stephen Rothwell wrote:
> > > Hi Russell,
> > > 
> > > Today's linux-next build (x86_64 allmodconfig) failed like this:
> > 
> > Well, it's going to stay broken for the coming week.  I'm away from
> > today.
> 
> That's OK, I can keep reverting it (or I may try to figure out what
> dependencies it needs).
> 
> Thanks for letting me know.

Okay, this should now be fixed.  Please confirm when you run your next
linux-next build.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:

  reply	other threads:[~2008-06-22 19:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-16  6:07 linux-next: arm build failure Stephen Rothwell
2008-06-16  7:29 ` Russell King
2008-06-16  7:37   ` Stephen Rothwell
2008-06-22 19:00     ` Russell King [this message]
2008-06-23  8:11       ` Stephen Rothwell
2008-06-16 21:52 ` Dmitry Baryshkov
2008-06-17  4:52   ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2008-11-07  2:11 Stephen Rothwell
2008-11-09 10:26 ` Russell King
2008-11-09 10:45   ` Stephen Rothwell
2008-11-26  2:30 Stephen Rothwell
2008-11-26  4:53 ` Eric Miao
2009-03-19 23:27 Stephen Rothwell

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=20080622190041.GB21340@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=dbaryshkov@gmail.com \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.