From: Christoph Hellwig <hch@infradead.org>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: linux-scsi@vger.kernel.org, "Justin T. Gibbs" <gibbs@scsiguy.com>
Subject: Re: Aic7xxx v6.2.23 and Aic79xx v1.3.0Alpha3 in bitkeeper
Date: Mon, 16 Dec 2002 18:56:59 +0000 [thread overview]
Message-ID: <20021216185659.A10346@infradead.org> (raw)
In-Reply-To: <200212161746.gBGHkjE03623@localhost.localdomain>; from James.Bottomley@steeleye.com on Mon, Dec 16, 2002 at 11:46:45AM -0600
On Mon, Dec 16, 2002 at 11:46:45AM -0600, James Bottomley wrote:
> I've moved the previous aic7xxx repository to scsi-aic7xxx-old-2.5 and set up
> a brand new one in its place. This one should have the import of Justin's
> actual patch sets, so should be easier for us all to manage.
>
> The new repository is at
>
> http://linux-scsi.bkbits.net/scsi-aic7xxx-2.5
>From a first look it seems almost fine. There's a small problem in
the ->biosparam implementations, and at least a part of that is
probably my fault.
In aic7xxx there is a ahd_linux_biosparam prototype instead of
ahc_linux_biosparam and the actual implementation doesn't use the
sector_div wrapper I sent justing yet, so it probably fails on system
that are configured with 64bit block numbers. Also my cleanups to
get the ifdef mess down in ->biosparam don't seem to be there, maybe
my style doesn't match Justins (?).
I've seen Justin moved aic_sector_div into the common aiclib.c file,
which seems to be a good idea to me, and I think there's more in the
*_osm.c headers that should go this way. I think it should become
an module of it's own at least for the kernel tree, even if Adaptec
wants to keep it included in their tarballs.
Now I'll actually try to compile it..
next prev parent reply other threads:[~2002-12-16 18:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-16 17:46 Aic7xxx v6.2.23 and Aic79xx v1.3.0Alpha3 in bitkeeper James Bottomley
2002-12-16 18:56 ` Christoph Hellwig [this message]
2002-12-16 19:16 ` Justin T. Gibbs
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=20021216185659.A10346@infradead.org \
--to=hch@infradead.org \
--cc=James.Bottomley@steeleye.com \
--cc=gibbs@scsiguy.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