linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Viswas G <Viswas.G@microsemi.com>
To: linux-scsi@vger.kernel.org
Cc: Vasanthalakshmi.Tharmarajan@microsemi.com,
	Viswas.G@microsemi.com, deepak.ukey@microsemi.com,
	Raj.Dinesh@microsemi.com, jinpu.wang@profitbricks.com,
	martin.petersen@oracle.com
Subject: [PATCH V4 0/9] pm80xx updates
Date: Wed, 18 Oct 2017 11:39:06 +0530	[thread overview]
Message-ID: <20171018060915.8549-1-Viswas.G@microsemi.com> (raw)


This patch set include some bug fixes and enhancement for pm80xx driver.

Changes from V3:
	- Fixed kbuild warnings for patch 4 and 5.  

Changes from V2:
	- Corrected date.

Changes from V1:
        - sas_identify_frame_local structure moved to pm80xx_hwi.h
        - sata abort handling patch split to four patches.
                - tag allocation for phy control request.
                - cleanup in pm8001_abort_task function.
                - modified port reset timer value for PM8006 card
                - corrected SATA abort handling sequence.


Viswas G (9):
  pm80xx : redefine sas_identify_frame structure
  pm80xx : ILA and inactive firmware version through sysfs
  pm80xx : Different SAS addresses for phys.
  pm80xx : tag allocation for phy control request.
  pm80xx : cleanup in pm8001_abort_task function.
  pm80xx : modified port reset timer value for PM8006  card
  pm80xx : corrected SATA abort handling sequence.
  pm80xx : panic on ncq error cleaning up the read log.
  pm80xx : corrected linkrate value.

 drivers/scsi/pm8001/pm8001_ctl.c  |  54 +++++++++++++++++
 drivers/scsi/pm8001/pm8001_hwi.c  |  11 +++-
 drivers/scsi/pm8001/pm8001_init.c |  13 +++--
 drivers/scsi/pm8001/pm8001_sas.c  | 119 +++++++++++++++++++++++++-------------
 drivers/scsi/pm8001/pm8001_sas.h  |  10 ++++
 drivers/scsi/pm8001/pm80xx_hwi.c  |  62 ++++++++++++++++----
 drivers/scsi/pm8001/pm80xx_hwi.h  | 102 +++++++++++++++++++++++++++++++-
 7 files changed, 313 insertions(+), 58 deletions(-)

-- 
2.12.3

             reply	other threads:[~2017-10-18  6:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-18  6:09 Viswas G [this message]
2017-10-18  6:09 ` [PATCH V4 1/9] pm80xx : redefine sas_identify_frame structure Viswas G
2017-10-18  6:09 ` [PATCH V4 2/9] pm80xx : ILA and inactive firmware version through sysfs Viswas G
2017-10-18  6:09 ` [PATCH V4 3/9] pm80xx : Different SAS addresses for phys Viswas G
2017-10-18  6:09 ` [PATCH V4 4/9] pm80xx : tag allocation for phy control request Viswas G
2017-10-18  6:09 ` [PATCH V4 5/9] pm80xx : cleanup in pm8001_abort_task function Viswas G
2017-10-18  6:09 ` [PATCH V4 6/9] pm80xx : modified port reset timer value for PM8006 card Viswas G
2017-10-18  6:09 ` [PATCH V4 7/9] pm80xx : corrected SATA abort handling sequence Viswas G
2017-10-18  6:09 ` [PATCH V4 8/9] pm80xx : panic on ncq error cleaning up the read log Viswas G
2017-10-18  6:09 ` [PATCH V4 9/9] pm80xx : corrected linkrate value Viswas G
2017-10-18  8:10 ` [PATCH V4 0/9] pm80xx updates Jinpu Wang
2017-10-19  2:12 ` Martin K. Petersen

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=20171018060915.8549-1-Viswas.G@microsemi.com \
    --to=viswas.g@microsemi.com \
    --cc=Raj.Dinesh@microsemi.com \
    --cc=Vasanthalakshmi.Tharmarajan@microsemi.com \
    --cc=deepak.ukey@microsemi.com \
    --cc=jinpu.wang@profitbricks.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.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).