All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: David Miller <davem@davemloft.net>, linux-next@vger.kernel.org
Subject: Re: linux-next: sparc64 build failure
Date: Fri, 20 Jun 2008 10:34:43 +0200	[thread overview]
Message-ID: <20080620083443.GA23523@uranus.ravnborg.org> (raw)
In-Reply-To: <20080620175311.3ef1ea8b.sfr@canb.auug.org.au>

On Fri, Jun 20, 2008 at 05:53:11PM +1000, Stephen Rothwell wrote:
> 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.

I have not looked into it yet. But I assume this is a merge issue.
sparc-next.git is OK
kbuild-next.git is OK

But when merged we break sparc64.
So I need to feed David a patch so I do not break it with kbuild-next.git,
or I need to do something in kbuil-next.git to avoid the breakage.

I will sort it out in the weekend.

	Sam

  reply	other threads:[~2008-06-20  8:33 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
2008-06-20  8:34       ` Sam Ravnborg [this message]
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=20080620083443.GA23523@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=davem@davemloft.net \
    --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.