From: Matthew Wilcox <matthew@wil.cx>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>, linux-next@vger.kernel.org
Subject: Re: linux-next: m68k/semaphore build failure
Date: Sat, 31 May 2008 11:20:59 -0600 [thread overview]
Message-ID: <20080531172059.GF28074@parisc-linux.org> (raw)
In-Reply-To: <20080528160406.4fceb036.sfr@canb.auug.org.au>
On Wed, May 28, 2008 at 04:04:06PM +1000, Stephen Rothwell wrote:
> > I'd swear I reported this to Willy the first time it appeared, but according
> > to my mail logs, I never did...
You did ... I was just slack.
> I have added the following patch to linux-next for today, but I am
> assuming the Willy will fix his semaphore tree shortly.
Fixed now. Thanks!
--
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2008-05-31 17:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-27 10:10 linux-next: m68k/semaphore build failure Stephen Rothwell
2008-05-27 16:10 ` Geert Uytterhoeven
2008-05-28 6:04 ` Stephen Rothwell
2008-05-31 17:20 ` Matthew Wilcox [this message]
2008-06-01 2:18 ` 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=20080531172059.GF28074@parisc-linux.org \
--to=matthew@wil.cx \
--cc=geert@linux-m68k.org \
--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).