From: Joe Eykholt <jeykholt@cisco.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Abhijeet Joglekar <abjoglek@cisco.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 6/6] fnic: Patch MAINTAINERS, scsi Makefile, scsi Kconfig
Date: Thu, 25 Jun 2009 12:04:42 -0700 [thread overview]
Message-ID: <4A43CA4A.9050609@cisco.com> (raw)
In-Reply-To: <1245949235.4170.63.camel@mulgrave.site>
James Bottomley wrote:
> On Fri, 2009-04-17 at 18:33 -0700, Abhijeet Joglekar wrote:
>> Patch MAINTAINERS file, add fnic module to scsi Makefile and Kconfig
>>
>> Signed-off-by: Abhijeet Joglekar <abjoglek@cisco.com>
>> Signed-off-by: Joe Eykholt <jeykholt@cisco.com>
>> Signed-off-by: Mike Christie <michaelc@cs.wisc.edu>
>> ---
>> MAINTAINERS | 8 ++++++++
>> drivers/scsi/Kconfig | 11 +++++++++++
>> drivers/scsi/Makefile | 1 +
>> 3 files changed, 20 insertions(+), 0 deletions(-)
>>
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index ebaf77e..405f574 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -1167,6 +1167,14 @@ P: Nils Faerber (port to kernel 2.4)
>> M: Nils Faerber <nils@kernelconcepts.de>
>> S: Maintained
>>
>> +CISCO FCOE HBA DRIVER
>> +P: Abhijeet Joglekar
>> +M: abjoglek@cisco.com
>> +P: Joe Eykholt
>> +M: jeykholt@cisco.com
>> +L: linux-scsi@vger.kernel.org
>> +S: Supported
>> +
>> CODA FILE SYSTEM
>> P: Jan Harkes
>> M: jaharkes@cs.cmu.edu
>> diff --git a/drivers/scsi/Kconfig b/drivers/scsi/Kconfig
>> index 876cd20..d45f3ad 100644
>> --- a/drivers/scsi/Kconfig
>> +++ b/drivers/scsi/Kconfig
>> @@ -628,6 +628,17 @@ config FCOE
>> ---help---
>> Fibre Channel over Ethernet module
>>
>> +config FCOE_FNIC
>> + tristate "Cisco FNIC Driver"
>> + depends on PCI && X86
>
> Why is this marked X86 only? Surely as a PCIe card it should work on
> any architecture?
It isn't a standard PCIe card. Currently that device is only used
in the Cisco UCS systems in a proprietary form-factor.
Mainly we don't want to test-build on all the other architectures
since it won't be usable on them.
Regards,
Joe
prev parent reply other threads:[~2009-06-25 19:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-18 1:32 [PATCH 0/6] fnic driver patches for 2.6.30 Abhijeet Joglekar
2009-04-18 1:32 ` [PATCH 1/6] fnic: add main file with module infrastructure, fnic structure, Makefile Abhijeet Joglekar
2009-04-27 15:44 ` James Bottomley
2009-04-27 16:05 ` Mike Christie
2009-04-27 17:30 ` [PATCH 1/6] fnic: add main file with module infrastructure,fnic " Abhijeet Arvind Joglekar (abjoglek)
2009-05-23 18:07 ` [PATCH 1/6] fnic: add main file with module infrastructure, fnic " Rolf Eike Beer
2009-05-27 16:36 ` Abhijeet Joglekar (abjoglek)
2009-04-18 1:32 ` [PATCH 2/6] fnic: add SCSI FCP handling Abhijeet Joglekar
2009-04-18 1:32 ` [PATCH 3/6] fnic: Add support for Fibre Channel Services through libFC Abhijeet Joglekar
2009-04-18 1:33 ` [PATCH 4/6] fnic: adds resource allocation, interrupt interfaces Abhijeet Joglekar
2009-04-18 1:33 ` [PATCH 5/6] fnic: add descriptor, buffers, device interfaces Abhijeet Joglekar
2009-04-18 1:33 ` [PATCH 6/6] fnic: Patch MAINTAINERS, scsi Makefile, scsi Kconfig Abhijeet Joglekar
2009-06-25 17:00 ` James Bottomley
2009-06-25 19:04 ` Joe Eykholt [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=4A43CA4A.9050609@cisco.com \
--to=jeykholt@cisco.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=abjoglek@cisco.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox