public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Sumit Saxena <sumit.saxena@avagotech.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-scsi@vger.kernel.org, thenzl@redhat.com,
	martin.petersen@oracle.com, jbottomley@parallels.com,
	Kashyap Desai <kashyap.desai@avagotech.com>
Subject: RE: [PATCH v3 9/18] megaraid_sas : Support for Avago's Single server High Availability product
Date: Mon, 11 May 2015 15:10:56 +0530	[thread overview]
Message-ID: <0b14766f13fa5bd085122e7abcb690b3@mail.gmail.com> (raw)
In-Reply-To: <20150511091948.GH28820@infradead.org>

>-----Original Message-----
>From: Christoph Hellwig [mailto:hch@infradead.org]
>Sent: Monday, May 11, 2015 2:50 PM
>To: Sumit.Saxena@avagotech.com
>Cc: linux-scsi@vger.kernel.org; thenzl@redhat.com;
>martin.petersen@oracle.com; jbottomley@parallels.com;
>kashyap.desai@avagotech.com
>Subject: Re: [PATCH v3 9/18] megaraid_sas : Support for Avago's Single
server
>High Availability product
>
>Did you test this on non-x86?  It seems like the dmi functions are
properly
>stubbed out, but I'd really prefer an explicit statement that it is known
to
>work.

SSHA feature is limited to x86 platform only. This code is tested for non
x86 platforms(tested on PPC). We don't need buffer returned by
"dmi_get_system_info()" on non x86 platforms as we don't support SSHA for
non x86 platforms.

      reply	other threads:[~2015-05-11  9:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-23 11:02 [PATCH v3 9/18] megaraid_sas : Support for Avago's Single server High Availability product Sumit.Saxena
2015-05-11  9:19 ` Christoph Hellwig
2015-05-11  9:40   ` Sumit Saxena [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=0b14766f13fa5bd085122e7abcb690b3@mail.gmail.com \
    --to=sumit.saxena@avagotech.com \
    --cc=hch@infradead.org \
    --cc=jbottomley@parallels.com \
    --cc=kashyap.desai@avagotech.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=thenzl@redhat.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