From: David Jeffery <david_jeffery@adaptec.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 2.6] ips 2/2: minor fixes
Date: Thu, 15 Jan 2004 14:13:01 -0500 [thread overview]
Message-ID: <1074193981.607.51.camel@blackmagic> (raw)
In-Reply-To: <1074189041.1867.121.camel@mulgrave>
On Thu, 2004-01-15 at 12:50, James Bottomley wrote:
> I'll take this, but you are thinking about converting the driver away
> from /proc to sysfs, aren't you?
>
> James
Yes, long term I do. But not in the short term.
Going forward, this driver is intended to cover 2.6 and become the
source for future 2.4 driver updates. As support for 2.4 fades, at some
point the 2.4 driver will split off and become critical fixes only.
Until then, since sysfs doesn't exist in 2.4 I currently plan to keep
using proc with a unified driver instead of having to go ahead and split
2.4 and 2.6 and perform dual maintenance.
And I don't think anyone wants to add the sysfs code to a unified driver
and then #ifdef in the proc code for 2.4 and #ifdef in the sysfs code
for 2.6. That would be the ugliest solution.
In summary, the current plan is to keep using the proc file for the next
few releases. Once the 2.4 support goes into hard maintenance mode like
the rest of the 2.4 kernel, the plan is to replace the proc code with
sysfs.
David Jeffery
prev parent reply other threads:[~2004-01-15 19:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-15 17:41 [PATCH 2.6] ips 2/2: minor fixes David Jeffery
2004-01-15 17:50 ` James Bottomley
2004-01-15 19:13 ` David Jeffery [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=1074193981.607.51.camel@blackmagic \
--to=david_jeffery@adaptec.com \
--cc=James.Bottomley@SteelEye.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