public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Narsimhulu Musini (nmusini)" <nmusini@cisco.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"hare@suse.de" <hare@suse.de>
Subject: Re: [PATCH v5 0/9] snic:initial submission of snic driver for Cisco SCSI HBA
Date: Mon, 18 May 2015 04:21:34 +0000	[thread overview]
Message-ID: <D17F6556.25AFA%nmusini@cisco.com> (raw)
In-Reply-To: <1431707688.26877.3.camel@HansenPartnership.com>

Hi James,

     Added dependency in Kconfig for x86 to avoid its inclusion on other
architectures. Will it be help, if it is changed to x86_64?.

Thanks
simha

On 15/05/15 10:04 pm, "James Bottomley"
<James.Bottomley@HansenPartnership.com> wrote:

>On Fri, 2015-05-15 at 16:08 +0000, Narsimhulu Musini (nmusini) wrote:
>> Hi James,
>> 
>> >>This doesn't build on 32 bits.  Is it supposed to be 64 bit only?
>> Yes please, x86_64 arch only.
>
>For the kernel, we don't usually accept architectural restrictions.
>You're perfectly entitled to support only the architectures you wish
>(and put a warning in the driver if you want) but we do need the code to
>be endian and bitwidth clean because we find it helps with maintenance
>and checking (the ppc build systems pick up quite a few snafus that the
>x86 ones don't).
>
>James
>
>


  reply	other threads:[~2015-05-18  4:21 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-22  9:23 [PATCH v5 0/9] snic:initial submission of snic driver for Cisco SCSI HBA Narsimhulu Musini
2015-04-22  9:23 ` [PATCH v5 1/9] snic: snic module infrastructure Narsimhulu Musini
2015-05-11 17:55   ` Hannes Reinecke
2015-04-22  9:23 ` [PATCH v5 2/9] snic:Add interrupt, resource firmware interfaces Narsimhulu Musini
2015-05-11 17:55   ` Hannes Reinecke
2015-04-22  9:23 ` [PATCH v5 3/9] snic:Add meta request, handling of meta requests Narsimhulu Musini
2015-05-11 17:56   ` Hannes Reinecke
2015-04-22  9:23 ` [PATCH v5 4/9] snic:Add snic target discovery Narsimhulu Musini
2015-05-11 17:58   ` Hannes Reinecke
2015-04-22  9:23 ` [PATCH v5 5/9] snic:add SCSI handling, AEN, and fwreset handling Narsimhulu Musini
2015-05-11 18:00   ` Hannes Reinecke
2015-04-22  9:23 ` [PATCH v5 6/9] snic:Add low level queuing interfaces Narsimhulu Musini
2015-05-11 18:01   ` Hannes Reinecke
2015-04-22  9:24 ` [PATCH v5 7/9] snic:Add sysfs entries to list stats and trace data Narsimhulu Musini
2015-05-11 18:02   ` Hannes Reinecke
2015-04-22  9:24 ` [PATCH v5 8/9] snic:Add event tracing to capture IO events Narsimhulu Musini
2015-05-11 18:03   ` Hannes Reinecke
2015-04-22  9:24 ` [PATCH v5 9/9] snic:Add Makefile, patch Kconfig, MAINTAINERS Narsimhulu Musini
2015-05-11 18:03   ` Hannes Reinecke
2015-05-15 15:49 ` [PATCH v5 0/9] snic:initial submission of snic driver for Cisco SCSI HBA James Bottomley
2015-05-15 16:08   ` Narsimhulu Musini (nmusini)
2015-05-15 16:34     ` James Bottomley
2015-05-18  4:21       ` Narsimhulu Musini (nmusini) [this message]
2015-05-18 14:35         ` 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=D17F6556.25AFA%nmusini@cisco.com \
    --to=nmusini@cisco.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=hare@suse.de \
    --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