From: Ralf Baechle <ralf@linux-mips.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: mips tree build failure
Date: Wed, 17 Jun 2009 08:24:13 +0100 [thread overview]
Message-ID: <20090617072413.GA13467@linux-mips.org> (raw)
In-Reply-To: <20090617163549.84cfc4b6.sfr@canb.auug.org.au>
On Wed, Jun 17, 2009 at 04:35:49PM +1000, Stephen Rothwell wrote:
> Yesterday's linux-next build (mips defconfig) failed like this:
>
> arch/mips/lib/delay.c:54: error: 'us' undeclared (first use in this function)
>
> Caused by commit 5636919b5c909fee54a6ef5226475ecae012ad02 ("MIPS: Outline
> udelay and fix a few issues") which is now in Linus' tree (sorry I didn't
> report it earlier).
This is already fixed and will go upstream with my next pull request.
Thanks for reporting!
Ralf
prev parent reply other threads:[~2009-06-17 7:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 6:35 linux-next: mips tree build failure Stephen Rothwell
2009-06-17 7:24 ` Ralf Baechle [this message]
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=20090617072413.GA13467@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-kernel@vger.kernel.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).