From: Viswas G <Viswas.G@microchip.com.com>
To: <linux-scsi@vger.kernel.org>
Cc: <Vasanthalakshmi.Tharmarajan@microchip.com>,
Ruksar Devadi <Ruksar.devadi@microchip.com>,
<Viswas.G@microchip.com>,
"peter chang --cc=yuuzheng @ google . com" <dpf@google.com>,
<vishakhavc@google.com>, <radha@google.com>,
<akshatzen@google.com>
Subject: [PATCH 0/4] pm80xx updates
Date: Mon, 12 Oct 2020 10:54:11 +0530 [thread overview]
Message-ID: <20201012052415.18963-1-Viswas.G@microchip.com.com> (raw)
From: Viswas G <Viswas.G@microchip.com>
This patch set include some bug fixes for pm80xx driver.
Viswas G (1):
pm80xx: make running_req atomic.
akshatzen (1):
pm80xx: Avoid busywait in FW ready check
peter chang (1):
pm80xx: make mpi_build_cmd locking consistent
yuuzheng (1):
pm80xx: make pm8001_mpi_set_nvmd_resp free of race condition
drivers/scsi/pm8001/pm8001_hwi.c | 86 +++++++++++++++++++------
drivers/scsi/pm8001/pm8001_init.c | 2 +-
drivers/scsi/pm8001/pm8001_sas.c | 11 ++--
drivers/scsi/pm8001/pm8001_sas.h | 2 +-
drivers/scsi/pm8001/pm80xx_hwi.c | 130 ++++++++++++++++++++++++++++++--------
drivers/scsi/pm8001/pm80xx_hwi.h | 6 ++
6 files changed, 185 insertions(+), 52 deletions(-)
--
2.16.3
next reply other threads:[~2020-10-12 5:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 5:24 Viswas G [this message]
2020-10-12 5:24 ` [PATCH 1/4] pm80xx: make mpi_build_cmd locking consistent Viswas G
2020-10-27 0:41 ` Martin K. Petersen
2020-10-12 5:24 ` [PATCH 2/4] pm80xx: make running_req atomic Viswas G
2020-10-12 5:24 ` [PATCH 3/4] pm80xx: Avoid busywait in FW ready check Viswas G
2020-10-12 5:24 ` [PATCH 4/4] pm80xx: make pm8001_mpi_set_nvmd_resp free of race condition Viswas G
-- strict thread matches above, loose matches on Subject: below --
2021-08-23 8:23 [PATCH 0/4] pm80xx updates Ajish Koshy
2020-09-25 6:16 Viswas G
2020-09-25 6:13 ` Jinpu Wang
2020-09-25 6:36 ` Viswas.G
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=20201012052415.18963-1-Viswas.G@microchip.com.com \
--to=viswas.g@microchip.com.com \
--cc=Ruksar.devadi@microchip.com \
--cc=Vasanthalakshmi.Tharmarajan@microchip.com \
--cc=Viswas.G@microchip.com \
--cc=akshatzen@google.com \
--cc=dpf@google.com \
--cc=linux-scsi@vger.kernel.org \
--cc=radha@google.com \
--cc=vishakhavc@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