From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: David Miller <davem@davemloft.net>, linux-next@vger.kernel.org
Subject: Re: linux-next: sparc64 build failure
Date: Fri, 20 Jun 2008 17:53:11 +1000 [thread overview]
Message-ID: <20080620175311.3ef1ea8b.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20080620073444.GA23126@uranus.ravnborg.org>
[-- Attachment #1: Type: text/plain, Size: 744 bytes --]
Hi Sam,
On Fri, 20 Jun 2008 09:34:44 +0200 Sam Ravnborg <sam@ravnborg.org> wrote:
>
> On Thu, Jun 19, 2008 at 05:55:20PM -0700, David Miller wrote:
> > From: Stephen Rothwell <sfr@canb.auug.org.au>
> > Date: Fri, 20 Jun 2008 10:43:52 +1000
> >
> > > Yesterday's linux-next build (sparc64 allmodconfig) failed like this:
> >
> > Sam knowingly added this problem :-)
> Yes - this is all my fault.
> It must hurt a little before it becomes good!
Yep, OK.
Seriously, though the sparc64 allmodconfig has been broken by this for
two days and we really don't want any deliberate bisection breakage if we
can avoid it.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-06-20 7:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-20 0:43 linux-next: sparc64 build failure Stephen Rothwell
2008-06-20 0:55 ` David Miller
2008-06-20 1:11 ` Stephen Rothwell
2008-06-20 7:34 ` Sam Ravnborg
2008-06-20 7:53 ` Stephen Rothwell [this message]
2008-06-20 8:34 ` Sam Ravnborg
2008-06-21 0:02 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2008-07-09 11:15 Stephen Rothwell
2008-07-09 21:23 ` Sam Ravnborg
2008-07-08 9:08 Stephen Rothwell
2008-07-08 9:13 ` David Miller
2008-05-29 7:53 Stephen Rothwell
2008-05-29 22:01 ` Greg KH
2008-05-30 5:38 ` Stephen Rothwell
2008-05-30 14:10 ` Greg KH
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=20080620175311.3ef1ea8b.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=davem@davemloft.net \
--cc=linux-next@vger.kernel.org \
--cc=sam@ravnborg.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).