public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Luben Tuikov <luben_tuikov@adaptec.com>
To: dougg@torque.net
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 2.6.13 2/14] sas-class: README
Date: Tue, 13 Sep 2005 09:20:06 -0400	[thread overview]
Message-ID: <4326D206.4050100@adaptec.com> (raw)
In-Reply-To: <43269A7A.3080602@torque.net>

On 09/13/05 05:23, Douglas Gilbert wrote:
> Luben Tuikov wrote:
>>The questiong is _what_ to do on this event.  This is a complex
>>answer and I'd rather have a _SES_ layer (or at least a logical
>>module/library) to handle those as storage vendors want this,
>>_right now_.
> 
> 
> Simple answer: generate a hotplug event and let a
> user application that cares worry about it. No
> need for a SES layer in the kernel.

Well, that sounds ok, but it maybe the case that the SES
device wants to say something about the SAS devices
on the same level.  So even if userspace gets it, it would
have nothing to do with it, because of the _type_ of SES
device/event/etc.
(User space can be notified anyway, which is perfectly fine).

>>In fact, I've some patches to submit regarding SES devices
>>on the domain, but I wanted to _trim *down*_ the politics,
>>_not_ escalate them.
> 
> 
> Oh no, not a sysfs representation of SES abstractions :-)

No, not that.

	Luben


  reply	other threads:[~2005-09-13 13:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-09 19:39 [PATCH 2.6.13 2/14] sas-class: README Luben Tuikov
2005-09-11  1:44 ` Douglas Gilbert
2005-09-12 16:56   ` Luben Tuikov
2005-09-13  9:23     ` Douglas Gilbert
2005-09-13 13:20       ` Luben Tuikov [this message]
2005-09-12  9:00 ` Douglas Gilbert
2005-09-12 18:38   ` Luben Tuikov
2005-09-13 10:13     ` Douglas Gilbert
2005-09-13 13:30       ` Luben Tuikov
2005-09-13 14:29         ` Luben Tuikov
2005-09-13 10:17   ` Christoph Hellwig

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=4326D206.4050100@adaptec.com \
    --to=luben_tuikov@adaptec.com \
    --cc=dougg@torque.net \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox