From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Jing Huang <huangj@Brocade.COM>
Cc: Greg KH <greg@kroah.com>,
linux-kernel@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 08:50:49 -0700 [thread overview]
Message-ID: <1222444249.3971.4.camel@localhost.localdomain> (raw)
In-Reply-To: <4C94DE2070B172459E4F1EE14BD2364E01F280A3@HQ-EXCH-5.corp.brocade.com>
On Thu, 2008-09-25 at 23:30 -0700, Jing Huang wrote:
> 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.
Well, this is open source ... you don't get to request new features; you
get to implement them, so if you need something that SCSI or the FC
transport doesn't provide, you just add it (rather than coding either a
fix or an enhancement for your driver alone).
However, you're quite lucky. So far, as James Smart said, I haven't
seen you ask for any features that we don't either provide or are in
process of agreeing the implementation of.
James
prev parent reply other threads:[~2008-09-26 15:51 UTC|newest]
Thread overview: 11+ 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 4:49 ` Jing Huang
2008-09-26 6:02 ` James Bottomley
2008-09-26 6:30 ` Jing Huang
2008-09-26 6:30 ` Jing Huang
2008-09-26 11:07 ` James Smart
2008-09-26 16:11 ` Jing Huang
2008-09-26 16:11 ` Jing Huang
2008-09-26 15:50 ` James Bottomley [this message]
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=1222444249.3971.4.camel@localhost.localdomain \
--to=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 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.