From: Jeff Garzik <jgarzik@pobox.com>
To: Justin Cormack <justin@street-vision.com>
Cc: Kernel mailing list <linux-kernel@vger.kernel.org>,
mort@wildopensource.com
Subject: Re: [PATCH] libata transport attributes
Date: Wed, 31 Mar 2004 16:07:31 -0500 [thread overview]
Message-ID: <406B3313.3080607@pobox.com> (raw)
In-Reply-To: <1080752942.27347.43.camel@lotte.street-vision.com>
Justin Cormack wrote:
> Here is a rough patch to add libata transport attributes, along the
> lines of fibre channel and parallel scsi. I wrote it as it seemed to be
> the cleanest way of extracting ata-specific information (currently drive
> model, serial number and firmware revision) from sysfs (in
> /sys/class/libata_transport/). There are a few issues, in particular:
>
> 1. it wont compile modular, as libata depends on scsi_transport_libata
> and vice-versa at the moment. I am not sure how you are supposed to get
> around this (and there arent any significant number of drivers in tree
> using the transport modules yet).
>
> 2. It would be nice if the device directory in sysfs had a symlink to
> the transport attributes directory, not just the other way round.
>
> 3. I couldnt work out what scsi_transport_template.size was the size of,
> as I couldnt see where it was used anywhere...
>
> patch against 2.6.5-rc3-libata1 but probably applies against most recent
> kernels.
Did you see the comments I posted WRT mort's patch?
Since libata is leaving SCSI in 2.7, I would rather not add superfluous
stuff like this at all.
Further, you can already retrieve the information you export with _zero_
new code.
Jeff
next prev parent reply other threads:[~2004-03-31 21:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-31 17:09 [PATCH] libata transport attributes Justin Cormack
2004-03-31 21:07 ` Jeff Garzik [this message]
2004-04-01 11:56 ` Justin Cormack
2004-04-01 18:10 ` Jeff Garzik
2004-04-02 14:40 ` Justin Cormack
-- strict thread matches above, loose matches on Subject: below --
2004-04-04 15:06 Dieter Stueken
2004-04-05 1:34 ` Jeff Garzik
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=406B3313.3080607@pobox.com \
--to=jgarzik@pobox.com \
--cc=justin@street-vision.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mort@wildopensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.