From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: linux-next@vger.kernel.org
Subject: Re: linux-next: ide tree build failure
Date: Fri, 23 Jan 2009 09:14:57 +1100 [thread overview]
Message-ID: <20090123091457.ba39e548.sfr@canb.auug.org.au> (raw)
In-Reply-To: <200901221422.34187.bzolnier@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 385 bytes --]
Hi Bart,
On Thu, 22 Jan 2009 14:22:34 +0100 Bartlomiej Zolnierkiewicz <bzolnier@gmail.com> wrote:
>
> Yeah, ide-eh.c should explicitly include <linux/delay.h>
> (on x86 it gets pulled indirectly so I haven't noticed it).
Indeed.
> Should be fixed now.
Thanks.
--
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:[~2009-01-22 22:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 1:57 linux-next: ide tree build failure Stephen Rothwell
2009-01-22 13:22 ` Bartlomiej Zolnierkiewicz
2009-01-22 22:14 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-06-15 1:34 Stephen Rothwell
2009-06-15 5:35 ` Borislav Petkov
2009-06-15 16:14 ` Bartlomiej Zolnierkiewicz
2009-02-06 3:35 Stephen Rothwell
2008-12-08 2:16 Stephen Rothwell
2008-12-08 17:10 ` Bartlomiej Zolnierkiewicz
2008-12-08 17:49 ` Borislav Petkov
2008-12-09 0:12 ` Stephen Rothwell
2008-08-26 4:06 Stephen Rothwell
2008-08-26 20:04 ` Bartlomiej Zolnierkiewicz
2008-08-12 1:18 Stephen Rothwell
2008-08-12 7:36 ` Borislav Petkov
2008-08-12 9:15 ` Bartlomiej Zolnierkiewicz
2008-07-24 3:17 Stephen Rothwell
2008-07-24 18:41 ` Bartlomiej Zolnierkiewicz
2008-06-30 5:28 Stephen Rothwell
2008-06-30 18:38 ` Bartlomiej Zolnierkiewicz
2008-07-01 0:28 ` 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=20090123091457.ba39e548.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=bzolnier@gmail.com \
--cc=linux-next@vger.kernel.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).