public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Christie <michaelc@cs.wisc.edu>
To: Martin Peschke3 <MPESCHKE@de.ibm.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH RFC 0/3] add fc transport events
Date: Thu, 27 May 2004 15:12:01 -0700	[thread overview]
Message-ID: <40B667B1.2040805@cs.wisc.edu> (raw)
In-Reply-To: <OFA5D56AC9.541248A2-ONC1256EA1.006DA3A1@de.ibm.com>

Martin Peschke3 wrote:
> 
> 
> 
>>03-convert-fc-class.patch - converts the fc class from a class_device
>>scsi_device to a kobject and adds a basic link_up/down event fucntion.
>>
>>(I did not convert the spi class yet, becuase I wasn't sure how people
>>would feel about such a change)
> 
> 
> Looks promising as to FC. We can add these calls in the zfcp lldd
> provided the patch makes it into the kernel. Then, what would be still
> missing are the required hotplug scripts, I guess.

There are still some other large outstanding issues. For example the
kobject_hotplug function must be called from a process context. I was not
sure if the transport class should provide this, or is it the drivers
responsibilty (some drivers have threads for work already),
or should SCSI ML supply this as it may have to if it is going
to provide events too.

> Martin
> 



  reply	other threads:[~2004-05-27 22:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-27 20:14 [PATCH RFC 0/3] add fc transport events Martin Peschke3
2004-05-27 22:12 ` Mike Christie [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-05-28  7:46 Martin Peschke3
2004-05-28  8:18 ` Mike Christie
2004-05-27  7:25 Mike Christie

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=40B667B1.2040805@cs.wisc.edu \
    --to=michaelc@cs.wisc.edu \
    --cc=MPESCHKE@de.ibm.com \
    --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