From: Christoph Hellwig <hch@infradead.org>
To: Jay Denebeim <denebeim@deepthot.org>
Cc: linux-scsi@vger.kernel.org
Subject: Re: Porting high level device drivers to 2.6
Date: Tue, 24 Feb 2004 22:38:44 +0000 [thread overview]
Message-ID: <20040224223844.A29520@infradead.org> (raw)
In-Reply-To: <c1gg8q$84t$1@dent.deepthot.org>; from denebeim@deepthot.org on Tue, Feb 24, 2004 at 09:38:34PM +0000
On Tue, Feb 24, 2004 at 09:38:34PM +0000, Jay Denebeim wrote:
> I was wondering if there is any documentation on porting high level
> device drivers from 2.4 to 2.6. I've looked at the changes in st.c
> and there seems to be more changes than are documented in either the
> 2.6 docbook or the lwn articles.
There's no good guid on this. If you post the source to the list
I could help your bringing it forward, though.
next prev parent reply other threads:[~2004-02-24 22:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-24 21:38 Porting high level device drivers to 2.6 Jay Denebeim
2004-02-24 22:05 ` Jay Denebeim
2004-02-24 22:38 ` Christoph Hellwig [this message]
2004-02-24 22:43 ` Jay Denebeim
-- strict thread matches above, loose matches on Subject: below --
2004-02-24 22:00 Jay Denebeim
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=20040224223844.A29520@infradead.org \
--to=hch@infradead.org \
--cc=denebeim@deepthot.org \
--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