linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Thumshirn <jthumshirn@suse.de>
To: Chaitra P B <chaitra.basappa@broadcom.com>
Cc: JBottomley@Parallels.com, jejb@kernel.org, hch@infradead.org,
	martin.petersen@oracle.com, linux-scsi@vger.kernel.org,
	Sathya.Prakash@broadcom.com, kashyap.desai@broadcom.com,
	krishnaraddi.mankani@broadcom.com, linux-kernel@vger.kernel.org,
	suganath-prabu.subramani@broadcom.com,
	sreekanth.reddy@broadcom.com
Subject: Re: [PATCH 0/4] mpt3sas driver Enhancements and
Date: Fri, 20 Jan 2017 09:53:42 +0100	[thread overview]
Message-ID: <20170120085342.GC3279@linux-x5ow.site> (raw)
In-Reply-To: <1484840950-13656-1-git-send-email-chaitra.basappa@broadcom.com>

On Thu, Jan 19, 2017 at 09:19:06PM +0530, Chaitra P B wrote:
> Here is the change list:
> Posting 4 patches for mpt3sas driver enhancement and defect fixes.
>   * Handle cable event for notifying degraded speed.
>   * Performance improvement for Crusader.
>   * Fix Firmware fault state 0x2100 during heavy 4K RR
>     FIO stress test.
>   * Updated driver version to 15.100.00.00
> 
> Chaitra P B (4):
>   mpt3sas: Added print to notify cable running at a      degraded
>     speed.
>   mpt3sas: Fix for Crusader to achieve product targets with      SAS
>     devices.
>   mpt3sas: Fix Firmware fault state 0x2100 during heavy 4K RR      FIO
>     stress test.
>   mpt3sas: Bump driver version to 15.100.00.00
> 
>  drivers/scsi/mpt3sas/mpi/mpi2_ioc.h  |    2 +
>  drivers/scsi/mpt3sas/mpt3sas_base.c  |   20 ++++++++++++++
>  drivers/scsi/mpt3sas/mpt3sas_base.h  |    7 +++--
>  drivers/scsi/mpt3sas/mpt3sas_ctl.c   |    4 ++-
>  drivers/scsi/mpt3sas/mpt3sas_scsih.c |   47 +++++++++++++++++++++++++++++----
>  5 files changed, 70 insertions(+), 10 deletions(-)

Please be sure you have appropriate Signed-off-by lines on all of your
patches, thanks.

-- 
Johannes Thumshirn                                          Storage
jthumshirn@suse.de                                +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850

      parent reply	other threads:[~2017-01-20  8:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-19 15:49 [PATCH 0/4] mpt3sas driver Enhancements and Chaitra P B
2017-01-19 15:49 ` [PATCH 1/4] mpt3sas: Added print to notify cable running at a degraded speed Chaitra P B
2017-01-20  8:51   ` Johannes Thumshirn
2017-01-19 15:49 ` [PATCH 2/4] mpt3sas: Fix for Crusader to achieve product targets with SAS devices Chaitra P B
2017-01-19 16:05   ` Bart Van Assche
2017-01-19 15:49 ` [PATCH 3/4] mpt3sas: Fix Firmware fault state 0x2100 during heavy 4K RR FIO stress test Chaitra P B
2017-01-19 15:49 ` [PATCH 4/4] mpt3sas: Bump driver version to 15.100.00.00 Chaitra P B
2017-01-20  8:53 ` Johannes Thumshirn [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=20170120085342.GC3279@linux-x5ow.site \
    --to=jthumshirn@suse.de \
    --cc=JBottomley@Parallels.com \
    --cc=Sathya.Prakash@broadcom.com \
    --cc=chaitra.basappa@broadcom.com \
    --cc=hch@infradead.org \
    --cc=jejb@kernel.org \
    --cc=kashyap.desai@broadcom.com \
    --cc=krishnaraddi.mankani@broadcom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=sreekanth.reddy@broadcom.com \
    --cc=suganath-prabu.subramani@broadcom.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;
as well as URLs for NNTP newsgroup(s).