mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jing Huang <jhuang007@gmail.com>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: Krishna Gudipati <kgudipat@brocade.com>,
	huangj@brocade.com, linux-kernel@vger.kernel.org,
	linux-scsi@vger.kernel.org, nkattang@brocade.com,
	rvadivel@brocade.com, vravindr@brocade.com
Subject: Re: [PATCH 4/5] bfa: Brocade BFA FC SCSI driver (makefile)
Date: Sat, 4 Apr 2009 20:41:36 +0800	[thread overview]
Message-ID: <b674f4c50904040541l523c489eh3556819a022c1ed7@mail.gmail.com> (raw)
In-Reply-To: <1238679361.3383.4.camel@mulgrave.int.hansenpartnership.com>

On Thu, Apr 2, 2009 at 9:36 PM, James Bottomley
<James.Bottomley@hansenpartnership.com> wrote:
> On Wed, 2009-04-01 at 20:35 -0700, Krishna Gudipati wrote:
>> From: Krishna Chaitanya Gudipati <kgudipat@brocade.com>
>>
>> This patch contains Makefile and Kconfig file for scsi and bfa.Fixed
>> the code review comments from previous submission.
>>
>> Signed-off-by: Krishna Chaitanya Gudipati <kgudipat@brocade.com>
>> ---
>>  Kconfig      |    9 +++++++++
>>  Makefile     |    1 +
>>  bfa/Makefile |   27 +++++++++++++++++++++++++++
>>  3 files changed, 37 insertions(+)
>>
>> diff -urpN orig/drivers/scsi/Kconfig patch/drivers/scsi/Kconfig
>> --- orig/drivers/scsi/Kconfig 2009-04-01 20:08:49.271161000 -0700
>> +++ patch/drivers/scsi/Kconfig        2009-04-01 20:08:44.003822000 -0700
>> @@ -1797,6 +1797,15 @@ config SCSI_SRP
>>         To compile this driver as a module, choose M here: the
>>         module will be called libsrp.
>>
>> +config SCSI_BFA_FC
>> +     tristate "Brocade BFA Fibre Channel Support"
>> +     depends on PCI && SCSI
>> +     help
>> +       This bfa driver supports all Brocade PCIe Fibre Channel host adapters.
>> +
>> +       To compile this driver as a module, choose M here. The module will
>> +       be called bfa.
>> +
>
> You're still not using the FC transport class to export common sysfs FC
> information or to help make your driver smaller.  I thought you were
> going to fix this after this was noted in your first submission to
> linux-scsi on 24 September?
>
> James
>
>

Hi James,

We removed Brocade specific sysfs code after first linux-scsi
submission. Can you please
clarify where we are still not using the FC transport class to export
common sysfs FC
information? We do use the fc transport template to create the common
sysfs FC attributes
(in bfad_attr.c) under /sys/class/fc_host/<host#>

Thanks

Jing

  reply	other threads:[~2009-04-04 12:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-02  3:35 Krishna Gudipati
2009-04-02 13:36 ` James Bottomley
2009-04-04 12:41   ` Jing Huang [this message]
2009-04-04 13:19     ` James Bottomley
  -- strict thread matches above, loose matches on Subject: below --
2009-03-24  0:12 Krishna Gudipati
2009-03-14 19:58 Jing Huang
2009-03-14 21:02 ` Sam Ravnborg

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=b674f4c50904040541l523c489eh3556819a022c1ed7@mail.gmail.com \
    --to=jhuang007@gmail.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=huangj@brocade.com \
    --cc=kgudipat@brocade.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=nkattang@brocade.com \
    --cc=rvadivel@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

all inboxes | Powered by JetHome®