From: Jes Sorensen <jes@wildopensource.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] more dead headers
Date: Mon, 06 Oct 2003 18:57:06 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106546697024143@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106467172926098@msgid-missing>
>>>>> "Christoph" = Christoph Hellwig <hch@lst.de> writes:
Christoph> On Sun, Oct 05, 2003 at 12:41:03PM -0400, Jes Sorensen
Christoph> wrote:
>> fetchop.h and ioc4.h are for GPL'ed drivers that have already been
>> published for 2.4 - they just need to be ported to 2.6. We can take
>> them out now and stick them back in later if you prefer but doing
>> so seems silly to me.
Christoph> It's still the wrong place for them. And the ioc4 driver
Christoph> including most of the header is so utter junk that it needs
Christoph> a complete rewrite anyway.
I don't have a problem moving fetchop.h, it's very hardware specific
though. ioc4 will have to migrate to relying a lot more on existing
infrastructure.
Jes
prev parent reply other threads:[~2003-10-06 18:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-27 14:07 [PATCH] more dead headers Christoph Hellwig
2003-10-05 16:41 ` Jes Sorensen
2003-10-06 12:03 ` Christoph Hellwig
2003-10-06 18:57 ` Jes Sorensen [this message]
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-106546697024143@msgid-missing \
--to=jes@wildopensource.com \
--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