From: Phillip Susi <psusi@cfl.rr.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH] Export ahci eSATA attribute
Date: Sat, 13 Nov 2010 10:46:11 -0500 [thread overview]
Message-ID: <4CDEB2C3.20806@cfl.rr.com> (raw)
In-Reply-To: <4CDE2274.8060807@garzik.org>
On 11/13/2010 12:30 AM, Jeff Garzik wrote:
> As you noted in your previous mail, the entire PORT_CMD is already
> exported as a attribute. I don't see much point in exporting this
> information a second time.
Unfortunately it is not exported in a way that udev can make use of it.
Firstly because udev can only compare on specific value matches rather
than an individual bit, and secondly because it is in the weird
scsi_host device rather than the host device, so the attribute is not in
an ancestor device of the disk device. Placing this attribute this way
puts it in the ancestry of the disk device so it can be matched by a
udev ATTRS rule.
next prev parent reply other threads:[~2010-11-13 15:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-11 3:32 [PATCH] Export ahci eSATA attribute Phillip Susi
2010-11-11 5:06 ` Jeff Garzik
2010-11-12 15:04 ` Phillip Susi
2010-11-13 5:23 ` Phillip Susi
2010-11-13 5:30 ` Jeff Garzik
2010-11-13 15:46 ` Phillip Susi [this message]
2010-11-18 19:37 ` Phillip Susi
2011-01-20 16:08 ` Phillip Susi
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=4CDEB2C3.20806@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=jeff@garzik.org \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).