From: Eyal Lebedinsky <eyal@eyal.emu.id.au>
To: Andrea Arcangeli <andrea@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.23aa1 - scsi/pcmcia qlogic still does not build (m)
Date: Fri, 05 Dec 2003 23:01:22 +1100 [thread overview]
Message-ID: <3FD07392.A47A0A6D@eyal.emu.id.au> (raw)
In-Reply-To: 20031205022225.GA1565@dualathlon.random
Andrea Arcangeli wrote:
>
> This should be the last 2.4-aa kernel ;)
I guess nobody volunteered to fix it since -pre6aa2...
It builds just fine in vanilla 2.4.23.
--
Eyal Lebedinsky (eyal@eyal.emu.id.au) <http://samba.org/eyal/>
next prev parent reply other threads:[~2003-12-05 12:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-05 2:22 2.4.23aa1 Andrea Arcangeli
2003-12-05 2:38 ` 2.4.23aa1 Mike Fedyk
2003-12-05 2:51 ` 2.4.23aa1 Andrea Arcangeli
2003-12-05 12:01 ` Eyal Lebedinsky [this message]
2003-12-05 23:09 ` 2.4.23aa1 - scsi/pcmcia qlogic still does not build (m) Andrea Arcangeli
2003-12-06 0:50 ` Eyal Lebedinsky
2003-12-06 2:25 ` Eyal Lebedinsky
2003-12-09 14:11 ` Andrea Arcangeli
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=3FD07392.A47A0A6D@eyal.emu.id.au \
--to=eyal@eyal.emu.id.au \
--cc=andrea@suse.de \
--cc=linux-kernel@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).