From: Don Brace <don.brace@microsemi.com>
To: <Kevin.Barnett@microchip.com>, <scott.teel@microchip.com>,
<Justin.Lindley@microchip.com>, <scott.benesh@microchip.com>,
<bader.alisaleh@microchip.com>, <gerry.morong@microchip.com>,
<mahesh.rajashekhara@microchip.com>, <hch@infradead.org>,
<jejb@linux.vnet.ibm.com>, <joseph.szczypek@hpe.com>,
<POSWALD@suse.com>
Cc: <linux-scsi@vger.kernel.org>
Subject: [PATCH 0/7] smartpqi updates
Date: Fri, 31 Jul 2020 16:01:05 -0500 [thread overview]
Message-ID: <159622890296.30579.6820363566594432069.stgit@brunhilda> (raw)
These patches are based on Linus's tree
The changes are:
smartpqi-identify-physical-devices-without-issuing-INQUIRY
- eliminate sending INQUIRYs to physical devices
smartpqi-add-id-support-for-smartRAID-3152-8i
- add support for a new controller
smartpqi-update-logical-volume-size-after-expansion
- update volume size in OS after expansion.
smartpqi-avoid-crashing-kernel-for-controller-issues
- remove BUG calls for rare cases when controller returns
bad responses.
smartpqi-support-device-deletion-via-sysfs
- handle device removal using sysfs file
/sys/block/sd<X>/device/delete where X is device name is a, b, ...
smartpqi-add-RAID-bypass-counter
- aid to identify when RAID bypass is in use.
smartpqi-bump-version-to-1.2.16-010
---
Don Brace (1):
smartpqi: bump version to 1.2.16-010
Kevin Barnett (4):
smartpqi identify physical devices without issuing INQUIRY
smartpqi: avoid crashing kernel for controller issues
smartpqi: support device deletion via sysfs
smartpqi: add RAID bypass counter
Mahesh Rajashekhara (2):
smartpqi: add id support for SmartRAID 3152-8i
smartpqi: update logical volume size after expansion
drivers/scsi/smartpqi/smartpqi.h | 4 +-
drivers/scsi/smartpqi/smartpqi_init.c | 301 ++++++++++++++++----------
2 files changed, 189 insertions(+), 116 deletions(-)
--
Signature
next reply other threads:[~2020-07-31 21:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-31 21:01 Don Brace [this message]
2020-07-31 21:01 ` [PATCH 1/7] smartpqi identify physical devices without issuing INQUIRY Don Brace
2020-07-31 21:01 ` [PATCH 2/7] smartpqi: add id support for SmartRAID 3152-8i Don Brace
2020-07-31 21:01 ` [PATCH 3/7] smartpqi: update logical volume size after expansion Don Brace
2020-07-31 21:01 ` [PATCH 4/7] smartpqi: avoid crashing kernel for controller issues Don Brace
2020-07-31 21:01 ` [PATCH 5/7] smartpqi: support device deletion via sysfs Don Brace
2020-07-31 21:01 ` [PATCH 6/7] smartpqi: add RAID bypass counter Don Brace
2020-07-31 21:01 ` [PATCH 7/7] smartpqi: bump version to 1.2.16-010 Don Brace
2020-08-12 20:03 ` [PATCH 0/7] smartpqi updates Martin Wilck
2020-08-13 2:50 ` Martin K. Petersen
2020-08-18 3:11 ` Martin K. Petersen
-- strict thread matches above, loose matches on Subject: below --
2017-08-10 18:46 Don Brace
2017-08-11 0:00 ` 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=159622890296.30579.6820363566594432069.stgit@brunhilda \
--to=don.brace@microsemi.com \
--cc=Justin.Lindley@microchip.com \
--cc=Kevin.Barnett@microchip.com \
--cc=POSWALD@suse.com \
--cc=bader.alisaleh@microchip.com \
--cc=gerry.morong@microchip.com \
--cc=hch@infradead.org \
--cc=jejb@linux.vnet.ibm.com \
--cc=joseph.szczypek@hpe.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mahesh.rajashekhara@microchip.com \
--cc=scott.benesh@microchip.com \
--cc=scott.teel@microchip.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).