From: "Justin T. Gibbs" <gibbs@scsiguy.com>
To: Arjan van de Ven <arjanv@redhat.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: aic7xxx strange code
Date: Thu, 01 Jan 2004 09:21:38 -0700 [thread overview]
Message-ID: <482322704.1072974098@aslan.scsiguy.com> (raw)
In-Reply-To: <20040101161731.GB18742@devserv.devel.redhat.com>
>> Unfortunately, fixing 2.4 and 2.6 now doesn't help in supporting older
>> kernels that are still in production. You can't change the past no
>> matter how hard we'd like to try.
>
> But vendors will update those kernels.....
Yes, but I can't remove support for these older kernels for quite
some time. So, I'd be more than happy to update the comments explaining
why the code is there and change the #ifdefs to further limit its use,
but the code needs to remain for the time being.
Are you planning an audit of the other platforms to ensure API compliance?
--
Justin
next prev parent reply other threads:[~2004-01-01 16:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-31 15:46 aic7xxx strange code Arjan van de Ven
2003-12-31 18:36 ` Justin T. Gibbs
2004-01-01 10:08 ` Arjan van de Ven
2004-01-01 16:16 ` Justin T. Gibbs
2004-01-01 16:17 ` Arjan van de Ven
2004-01-01 16:21 ` Justin T. Gibbs [this message]
2004-01-01 16:28 ` Arjan van de Ven
2004-01-01 22:31 ` Andi Kleen
2004-01-01 22:34 ` Arjan van de Ven
2004-01-01 23:14 ` Andi Kleen
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=482322704.1072974098@aslan.scsiguy.com \
--to=gibbs@scsiguy.com \
--cc=arjanv@redhat.com \
--cc=linux-scsi@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