From: Willy Tarreau <willy@w.ods.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: andersen@codepoet.org, linux-ide@vger.kernel.org,
linux-kernel@vger.kernel.org,
Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Subject: Re: Final 2.4.x SATA updates
Date: Sun, 4 Dec 2005 16:59:11 +0100 [thread overview]
Message-ID: <20051204155911.GA5924@alpha.home.local> (raw)
In-Reply-To: <438FA62D.2040707@pobox.com>
Hi Jeff,
On Thu, Dec 01, 2005 at 08:41:01PM -0500, Jeff Garzik wrote:
> Erik Andersen wrote:
> >On Thu Dec 01, 2005 at 04:48:37PM -0500, Jeff Garzik wrote:
> >
> >>Now that ATAPI support is pretty stable, the 2.4 version of libata will
> >>be receiving its final updates soon. Here is the current backport,
> >>for testing and feedback.
> >
> >
> >Awesome. 2.4.x lacks KM_IRQ0 in kmap_types.h
> >
> >gcc -D__KERNEL__ -I/usr/src/linux-2.4.32/include -Wall
> >-Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common
> >-fomit-frame-pointer -Os -falign-functions=2 -falign-jumps=2
> >-falign-labels=2 -falign-loops=2 -pipe -mpreferred-stack-boundary=2
> >-march=i486 -DMODULE -nostdinc -iwithprefix include
> >-DKBUILD_BASENAME=libata_core -DEXPORT_SYMTAB -c libata-core.c
> >libata-core.c: In function `ata_sg_clean':
> >libata-core.c:2427: error: `KM_IRQ0' undeclared (first use in this
> >function)
> >libata-core.c:2427: error: (Each undeclared identifier is reported only
> >once
> >libata-core.c:2427: error: for each function it appears in.)
> >libata-core.c: In function `ata_sg_setup':
> >libata-core.c:2701: error: `KM_IRQ0' undeclared (first use in this
> >function)
> >make[2]: *** [libata-core.o] Error 1
>
> hmmm, interesting. Easy enough to fix. I guess I didn't build on a
> highmem box.
Same problem for me, but unfortunately, I don't know how to fix this. I've
seen that KM_IRQ* are not defined on x86. I don't know if I can use other
ones, not what would be the consequences. Would you please enlighten me a
bit on this, I'm willing to test it but don't know how to build it first.
Thanks in advance,
Willy
next prev parent reply other threads:[~2005-12-04 16:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-01 21:48 Final 2.4.x SATA updates Jeff Garzik
2005-12-01 23:10 ` Erik Andersen
2005-12-02 1:41 ` Jeff Garzik
[not found] ` <20051202022309.GA10639@codepoet.org>
[not found] ` <438FB468.6090504@pobox.com>
2005-12-02 12:35 ` Draft libata GET_IDENTITY and DRIVE_TASKFILE Erik Andersen
2005-12-04 15:59 ` Willy Tarreau [this message]
2005-12-04 17:42 ` [PATCH] 2.4.x SATA with highmem Willy Tarreau
2005-12-04 18:09 ` Willy Tarreau
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=20051204155911.GA5924@alpha.home.local \
--to=willy@w.ods.org \
--cc=andersen@codepoet.org \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
/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).