All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Sumit.Saxena@avagotech.com, linux-scsi@vger.kernel.org
Cc: thenzl@redhat.com, martin.petersen@oracle.com, hch@infradead.org,
	jbottomley@parallels.com, kashyap.desai@avagotech.com
Subject: Re: [PATCH RESEND 9/18] megaraid_sas : Support for Avago's Single server High Availability product
Date: Tue, 21 Apr 2015 12:28:44 +0200	[thread overview]
Message-ID: <5536265C.303@suse.de> (raw)
In-Reply-To: <201504201236.t3KCa2D0016595@palmhbs0.lsi.com>

On 04/20/2015 02:33 PM, Sumit.Saxena@avagotech.com wrote:
> This patch will add support for Single Server High Availability(SSHA) cluster support.
> Here is the short decsription of changes done to add support for SSHA-
> 1) Host will send system's Unique ID based on DMI_PRODUCT_UUID to firmware.
> 2) Toggle the devhandle in LDIO path for Remote LDs.  
> 
> Signed-off-by: Kashyap Desai <kashyap.desai@avagotech.com>
> Signed-off-by: Sumit Saxena <sumit.saxena@avagotech.com>
> 
> ---
Reviewed-by: Hannes Reinecke <hare@suse.de>

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@suse.de			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2015-04-21 10:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-20 12:33 [PATCH RESEND 9/18] megaraid_sas : Support for Avago's Single server High Availability product Sumit.Saxena
2015-04-21 10:28 ` Hannes Reinecke [this message]
2015-04-21 12:09 ` Tomas Henzl
2015-04-21 12:54   ` Sumit Saxena

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=5536265C.303@suse.de \
    --to=hare@suse.de \
    --cc=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 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.