All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Christie <michaelc@cs.wisc.edu>
To: James.Smart@Emulex.Com
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] [REPOST] SCSI and FC Transport: add netlink support for posting of transport events
Date: Sun, 20 Aug 2006 19:01:21 -0400	[thread overview]
Message-ID: <44E8E9C1.60003@cs.wisc.edu> (raw)
In-Reply-To: <44E8E398.8070904@cs.wisc.edu>

Mike Christie wrote:
> It is not vendor specific but it is driver specific and so we need a way
> to route the message to the proper userspace handler for similar reasons
> you may need a vendor id? For example qlogic handling may be slightly
> different in userspace then broadcom. So what I am saying is I thought
> the driver and vendor ids are similar, but vendor id may not work for
> iscsi_tcp/iser?

For now let's forget this issue. I have been using the sysfs lookup
scheme because I thought people would frown on not using sysfs since it
was there. If we are allowed to add a vendor or driver id to the event
then fc can call it what it wants and base it on the pci naming and
iscsi can handle its special cases how it needs to. No reason to force
our quirks on you guys :)


  parent reply	other threads:[~2006-08-21  0:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-18 21:30 [PATCH] [REPOST] SCSI and FC Transport: add netlink support for posting of transport events James Smart
2006-08-19  4:11 ` Mike Christie
2006-08-19 11:56   ` James Smart
2006-08-20  2:26     ` Mike Christie
2006-08-20 13:15       ` James Smart
2006-08-20 13:30         ` James Smart
2006-08-20 22:35         ` Mike Christie
2006-08-20 22:46           ` Mike Christie
2006-08-20 23:01           ` Mike Christie [this message]
2006-08-21  0:03         ` Mike Christie
2006-08-30 17:40 ` James Bottomley
2006-08-30 17:51   ` James Smart

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=44E8E9C1.60003@cs.wisc.edu \
    --to=michaelc@cs.wisc.edu \
    --cc=James.Smart@Emulex.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.