From: Christoph Hellwig <hch@infradead.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: James Bottomley <James.Bottomley@suse.de>,
Tejun Heo <htejun@gmail.com>, Hans de Goede <hdegoede@redhat.com>,
SCSI development list <linux-scsi@vger.kernel.org>
Subject: Re: [RFC] Pass information about device open/close to low-level driver
Date: Mon, 26 Sep 2011 16:12:16 -0400 [thread overview]
Message-ID: <20110926201216.GA18666@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1109261543240.1773-100000@iolanthe.rowland.org>
On Mon, Sep 26, 2011 at 04:10:32PM -0400, Alan Stern wrote:
> James:
>
> Something like the patch below has been requested by the virtualization
> people.
Who are "the virtualization people"?
Either way this idea is a really bad one, and if you check history long
enough you'd notice we had all that crap in kernel before 2.6 and got
rid of it all.
next prev parent reply other threads:[~2011-09-26 20:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 20:10 [RFC] Pass information about device open/close to low-level driver Alan Stern
2011-09-26 20:12 ` Christoph Hellwig [this message]
2011-09-27 1:39 ` Alan Stern
2011-09-27 7:19 ` Hans de Goede
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=20110926201216.GA18666@infradead.org \
--to=hch@infradead.org \
--cc=James.Bottomley@suse.de \
--cc=hdegoede@redhat.com \
--cc=htejun@gmail.com \
--cc=linux-scsi@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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