All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Christie <mikenc@us.ibm.com>
To: Mike Anderson <andmike@us.ibm.com>
Cc: James Bottomley <James.Bottomley@steeleye.com>,
	"Infante, Jon" <Jon.Infante@Emulex.Com>,
	Martin Peschke3 <MPESCHKE@de.ibm.com>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: How to resurrect offlined SCSI devices?
Date: Wed, 26 May 2004 10:26:58 -0700	[thread overview]
Message-ID: <40B4D362.1080901@us.ibm.com> (raw)
In-Reply-To: <20040526171514.GA1332@us.ibm.com>

Mike Anderson wrote:
> James Bottomley [James.Bottomley@steeleye.com] wrote:
> 
>>I'd really like to see all fibre events (like loop up/down, device
>>add/remove) handled inside the FC transport class.  From there, it
>>probably still make sense to use hotplug as the mechanism for importing
>>user policy.
> 
> 
> Currently there are no hotplug events generated from SCSI except those
> from add / remove of sysfs related structures. Are you suggesting that
> SCSI should call call_usermodehelper and generate events?

What about kobject_hotplug()?

Mike

  reply	other threads:[~2004-05-26 17:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-26 16:17 How to resurrect offlined SCSI devices? Infante, Jon
2004-05-26 16:55 ` James Bottomley
2004-05-26 17:15   ` Mike Anderson
2004-05-26 17:26     ` Mike Christie [this message]
2004-05-26 17:48       ` Mike Anderson
2004-05-26 17:37     ` James Bottomley
2004-05-26 18:02       ` Mike Anderson
  -- strict thread matches above, loose matches on Subject: below --
2004-05-27 20:05 Martin Peschke3
2004-05-27 20:04 Martin Peschke3
2004-05-26 16:48 Salyzyn, Mark
2004-05-26 15:04 Martin Peschke3
2004-05-26 15:11 ` James Bottomley
2004-05-26 13:14 Martin Peschke3
2004-05-26 14:45 ` James Bottomley

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=40B4D362.1080901@us.ibm.com \
    --to=mikenc@us.ibm.com \
    --cc=James.Bottomley@steeleye.com \
    --cc=Jon.Infante@Emulex.Com \
    --cc=MPESCHKE@de.ibm.com \
    --cc=andmike@us.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 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.