From: Viswas G <Viswas.G@microchip.com.com>
To: <linux-scsi@vger.kernel.org>
Cc: <Vasanthalakshmi.Tharmarajan@microchip.com>,
<Viswas.G@microchip.com>, <deepak.ukey@microchip.com>,
<martin.petersen@oracle.com>, <yuuzheng@google.com>,
<auradkar@google.com>, <vishakhavc@google.com>,
<bjashnani@google.com>, <radha@google.com>,
<akshatzen@google.com>
Subject: [PATCH v8 0/2] pm80xx : Updates for the driver version 0.1.39.
Date: Fri, 21 Aug 2020 00:21:21 +0530 [thread overview]
Message-ID: <20200820185123.27354-1-Viswas.G@microchip.com.com> (raw)
From: Viswas G <Viswas.G@microchip.com>
This patch set includes some bug fixes and features for pm80xx driver.
Changes from v7:
For "Staggered spin up support"
- Fixed "reference preceded by free" reported by coccinelle.
Changes from v6:
For "Staggered spin up support."
-Changed DECLARE_COMPLETION to DECLARE_COMPLETION_ONSTACK
in pm8001_scan_start function.
Viswas G (2):
pm80xx : Support for get phy profile functionality.
pm80xx : Staggered spin up support.
drivers/scsi/pm8001/pm8001_ctl.h | 33 ++++++
drivers/scsi/pm8001/pm8001_defs.h | 3 +
drivers/scsi/pm8001/pm8001_hwi.c | 14 ++-
drivers/scsi/pm8001/pm8001_init.c | 58 ++++++++++-
drivers/scsi/pm8001/pm8001_sas.c | 36 ++++++-
drivers/scsi/pm8001/pm8001_sas.h | 18 ++++
drivers/scsi/pm8001/pm80xx_hwi.c | 210 ++++++++++++++++++++++++++++++++++----
drivers/scsi/pm8001/pm80xx_hwi.h | 2 +
8 files changed, 348 insertions(+), 26 deletions(-)
--
2.16.3
next reply other threads:[~2020-08-20 18:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-20 18:51 Viswas G [this message]
2020-08-20 18:51 ` [PATCH v8 1/2] pm80xx : Support for get phy profile functionality Viswas G
2020-09-02 1:19 ` Martin K. Petersen
2020-09-02 6:35 ` Viswas.G
2020-09-03 1:17 ` Martin K. Petersen
2020-09-09 10:15 ` Viswas.G
2020-08-20 18:51 ` [PATCH v8 2/2] pm80xx : Staggered spin up support Viswas G
2020-09-02 1:20 ` Martin K. Petersen
2020-09-02 6:38 ` Viswas.G
2020-09-11 5:41 ` Viswas.G
2020-09-11 7:30 ` John Garry
[not found] ` <SN6PR11MB348877970A45BA993C95D14D9D5B0@SN6PR11MB3488.namprd11.prod.outlook.com>
2020-09-02 14:05 ` Jinpu Wang
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=20200820185123.27354-1-Viswas.G@microchip.com.com \
--to=viswas.g@microchip.com.com \
--cc=Vasanthalakshmi.Tharmarajan@microchip.com \
--cc=Viswas.G@microchip.com \
--cc=akshatzen@google.com \
--cc=auradkar@google.com \
--cc=bjashnani@google.com \
--cc=deepak.ukey@microchip.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=radha@google.com \
--cc=vishakhavc@google.com \
--cc=yuuzheng@google.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