From: James Smart <James.Smart@Emulex.Com>
To: Jing Huang <huangj@Brocade.COM>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
Greg KH <greg@kroah.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
Ramkumar Vadivelu <rvadivel@Brocade.COM>,
"Srikanth Rayas (CW)" <srayas@Brocade.COM>,
Vinodh Ravindran <vravindr@Brocade.COM>
Subject: Re: [PATCH 5/6] bfa: Brocade BFA FC SCSI driver submission (2ndtry)
Date: Fri, 26 Sep 2008 07:07:48 -0400 [thread overview]
Message-ID: <48DCC284.3040408@emulex.com> (raw)
In-Reply-To: <4C94DE2070B172459E4F1EE14BD2364E01F280A3@HQ-EXCH-5.corp.brocade.com>
We are finally finishing up CT/ELS passthru in the FC transport; SCSI
passthru exists, but via the scsi_generic driver (so it's not part of
the transport or LLDD); and async event notification is already present
in the fc transport.
-- james s
Jing Huang wrote:
> Hi James,
>
> It is encouraging to know that we can discuss and add new feature into
> existing fc transport. I guess this is opensource all about. I didn't
> have linux opensource experience before, so I was not quite sure how
> easy to request new features in fc transport such as mechanism to create
> multiple subdirectories for different level of statistics info in
> addition to the snia fc statitistics we already have, and other features
> such as CT/SCSI passthru and asynchronous event notification etc.
>
> Thanks
>
> Jing
next prev parent reply other threads:[~2008-09-26 11:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-26 1:06 [PATCH 5/6] bfa: Brocade BFA FC SCSI driver submission (2nd try) Jing Huang
2008-09-26 2:55 ` Greg KH
2008-09-26 4:49 ` [PATCH 5/6] bfa: Brocade BFA FC SCSI driver submission (2ndtry) Jing Huang
2008-09-26 6:02 ` James Bottomley
2008-09-26 6:30 ` Jing Huang
2008-09-26 11:07 ` James Smart [this message]
2008-09-26 16:11 ` Jing Huang
2008-09-26 15:50 ` 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=48DCC284.3040408@emulex.com \
--to=james.smart@emulex.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=greg@kroah.com \
--cc=huangj@Brocade.COM \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rvadivel@Brocade.COM \
--cc=srayas@Brocade.COM \
--cc=vravindr@Brocade.COM \
/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