From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Hannes Reinecke <hare@suse.de>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
"Jeremy Linton" <jlinton@tributary.com>,
"Kay Sievers" <kay@vrfy.org>,
"Kai Mäkisara (Kolumbus)" <kai.makisara@kolumbus.fi>,
"James Bottomley" <jbottomley@parallels.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"Doug Gilbert" <dgilbert@interlog.com>
Subject: Re: [PATCH] st: Do not rewind for SG_IO
Date: Thu, 06 Feb 2014 08:50:03 -0500 [thread overview]
Message-ID: <yq161osuz90.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <52F38D78.2070002@suse.de> (Hannes Reinecke's message of "Thu, 06 Feb 2014 14:26:16 +0100")
>>>>> "Hannes" == Hannes Reinecke <hare@suse.de> writes:
>> My patch provides both the original VPD 0x83 and 0x80 bits as well as
>> a handle identical to /sbin/scsi_id.
>>
Hannes> Bah, don't do that. That should better be handled by udev
Hannes> rules. I've got a set of patches moving from scsi_id to sg_inq,
Hannes> which can be easily adapted to using sysfs directly.
I just want to get out of the "userland sending random SCSI commands"
business. That is a world of pain right now.
I wanted to provide a handle that was guaranteed to be compatible with
existing tooling. If you have worked around that in udev rules I guess
that's OK with me.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2014-02-06 13:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 8:46 [PATCH] st: Do not rewind for SG_IO Hannes Reinecke
2014-01-31 16:36 ` Jeremy Linton
2014-01-31 16:43 ` Jeremy Linton
2014-02-01 14:06 ` Hannes Reinecke
2014-02-01 15:23 ` "Kai Mäkisara (Kolumbus)"
2014-02-02 11:42 ` Hannes Reinecke
2014-02-02 19:15 ` "Kai Mäkisara (Kolumbus)"
2014-02-03 6:55 ` Hannes Reinecke
2014-02-03 14:50 ` Jeremy Linton
2014-02-03 15:06 ` Hannes Reinecke
2014-02-03 15:08 ` Jeremy Linton
2014-02-03 20:51 ` Kay Sievers
2014-02-03 21:11 ` James Bottomley
2014-02-03 21:58 ` Jeremy Linton
2014-02-03 22:15 ` Kay Sievers
2014-02-03 22:26 ` Jeremy Linton
2014-02-06 13:10 ` Hannes Reinecke
2014-02-06 13:21 ` Martin K. Petersen
2014-02-06 13:26 ` Hannes Reinecke
2014-02-06 13:50 ` Martin K. Petersen [this message]
2014-02-06 14:38 ` James Bottomley
2014-02-06 15:13 ` Hannes Reinecke
2014-02-06 19:21 ` Douglas Gilbert
2014-02-03 21:16 ` Douglas Gilbert
2014-02-03 21:24 ` Kay Sievers
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=yq161osuz90.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=dgilbert@interlog.com \
--cc=hare@suse.de \
--cc=jbottomley@parallels.com \
--cc=jlinton@tributary.com \
--cc=kai.makisara@kolumbus.fi \
--cc=kay@vrfy.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 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.