linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: sfr@canb.auug.org.au
Cc: linux-next@vger.kernel.org
Subject: Re: linux-next: sparc build failure
Date: Mon, 12 May 2008 00:40:31 -0700 (PDT)	[thread overview]
Message-ID: <20080512.004031.205637810.davem@davemloft.net> (raw)
In-Reply-To: <20080512173658.01dc993f.sfr@canb.auug.org.au>

From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Mon, 12 May 2008 17:36:58 +1000

> Seems to have been introduced by commit
> 28e6103665301ce60634e8a77f0b657c6cc099de ("sparc: Fix debugger syscall
> restart interactions") which went into Linus' tree recently ("bool" seems
> to be missing a definition).

Fixed in current sparc-2.6.git


  reply	other threads:[~2008-05-12  7:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-12  7:36 linux-next: sparc build failure Stephen Rothwell
2008-05-12  7:40 ` David Miller [this message]
2008-05-12  7:43   ` Stephen Rothwell
2008-08-28  6:51 Stephen Rothwell
2008-08-28  6:57 ` Ingo Molnar
2008-08-28  7:12   ` Stephen Rothwell
2008-08-28  7:25     ` Ingo Molnar

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=20080512.004031.205637810.davem@davemloft.net \
    --to=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 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).