All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: James Smart <James.Smart@Emulex.Com>
Cc: Christoph Hellwig <hch@infradead.org>,
	linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] fc transport: Add support for events
Date: Wed, 22 Feb 2006 17:45:33 +0000	[thread overview]
Message-ID: <20060222174533.GA20794@infradead.org> (raw)
In-Reply-To: <43FCA2CF.6080903@emulex.com>

On Wed, Feb 22, 2006 at 12:43:43PM -0500, James Smart wrote:
> It would have been nice to have had this response on the RFC.
> 
> I'm actually looking into netlink for the CT pass thru, ELS and rnid
> functions.
> 
> Does it make sense to move forward with some event support - namely
> the events attributes minus the kobject_uevent() stuff ?

Actually the events attributes are what I don't like at all.  kobject_uevent
already is a wrapper around netlink, it just doesn't allow to transport
all the nessecary data.


  reply	other threads:[~2006-02-22 17:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-22 16:09 [PATCH] fc transport: Add support for events James Smart
2006-02-22 17:21 ` Christoph Hellwig
2006-02-22 17:43   ` James Smart
2006-02-22 17:45     ` Christoph Hellwig [this message]
2006-02-22 18:01       ` Mike Anderson

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=20060222174533.GA20794@infradead.org \
    --to=hch@infradead.org \
    --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.