From: Jes Sorensen <jes@trained-monkey.org>
To: linux-ia64@vger.kernel.org
Subject: Re: QLogic drivers in 2.4
Date: Thu, 25 Sep 2003 07:21:24 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106447503610716@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106399415917430@msgid-missing>
>>>>> "Christoph" = Christoph Hellwig <hch@infradead.org> writes:
Christoph> Well, that someone is qlogic. But I don's see why it
Christoph> should go into the ia64 tree. Once qlogic got the driver
Christoph> in shape it and/or the feral driver should go into
Christoph> mainline. This is actually on the 2.6 should-fix list.
Hi,
I am a little wary of pushing the Feral driver to mainstraim in it's
current state (well at least the state it was in a few months ago when
I last looked). It's register access macros suffers from being
multi-OS wrappers and it got memory ordering and posted writes
completely wrong. It's certainly fixable, but if we push it for
mainline, I'd really like to see someone swing the club over it a bit
and convince it to be a little more Linuxy.
I understand the heritage of the Feral driver, so please don't take
this as a rant, it's merely an issue of what the target for the driver
is.
Cheers,
Jes
next prev parent reply other threads:[~2003-09-25 7:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-19 17:47 QLogic drivers in 2.4 Bjorn Helgaas
2003-09-19 18:01 ` Chen, Kenneth W
2003-09-19 18:08 ` Bjorn Helgaas
2003-09-19 18:11 ` Christoph Hellwig
2003-09-19 18:17 ` Bill Nottingham
2003-09-19 18:20 ` Bill Nottingham
2003-09-19 18:21 ` Martin K. Petersen
2003-09-19 18:23 ` Chen, Kenneth W
2003-09-19 18:40 ` Grant Grundler
2003-09-19 18:43 ` Chen, Kenneth W
2003-09-20 7:20 ` Christoph Hellwig
2003-09-25 7:16 ` Jes Sorensen
2003-09-25 7:21 ` Jes Sorensen [this message]
2003-09-25 20:29 ` Grant Grundler
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=marc-linux-ia64-106447503610716@msgid-missing \
--to=jes@trained-monkey.org \
--cc=linux-ia64@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