From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Don Brace <don.brace@microchip.com>
Cc: <scott.teel@microchip.com>, <scott.benesh@microchip.com>,
<gerry.morong@microchip.com>, <mahesh.rajashekhara@microchip.com>,
<mike.mcgowen@microchip.com>, <murthy.bhat@microchip.com>,
<kumar.meiyappan@microchip.com>, <jeremy.reeves@microchip.com>,
<david.strahan@microchip.com>, <hch@infradead.org>,
<James.Bottomley@HansenPartnership.com>,
<martin.petersen@oracle.com>, <joseph.szczypek@hpe.com>,
<POSWALD@suse.com>, <cameron.cumberland@suse.com>,
Yi Zhang <yi.zhang@redhat.com>, <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 0/4] smartpqi updates
Date: Sat, 08 Nov 2025 13:09:29 -0500 [thread overview]
Message-ID: <yq1wm40gzwp.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20251106163823.786828-1-don.brace@microchip.com> (Don Brace's message of "Thu, 6 Nov 2025 10:38:18 -0600")
Don,
> David Strahan (1):
> smartpqi: add support for Hurray Data new controller PCI device
>
> Don Brace (1):
> smartpqi: update version to 2.1.36-026
>
> Mike McGowen (2):
> smartpqi: Add timeout value to RAID path requests to physical devices
> smartpqi: Fix device resources accessed after device removal
Applied to 6.19/scsi-staging, thanks!
--
Martin K. Petersen
next prev parent reply other threads:[~2025-11-08 18:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 16:38 [PATCH 0/4] smartpqi updates Don Brace
2025-11-06 16:38 ` [PATCH 1/4] smartpqi: Add timeout value to RAID path requests to physical devices Don Brace
2025-11-06 16:38 ` [PATCH 2/4] smartpqi: Fix device resources accessed after device removal Don Brace
2025-11-06 16:38 ` [PATCH 3/4] smartpqi: add support for Hurray Data new controller PCI device Don Brace
2025-11-06 16:38 ` [PATCH 4/4] smartpqi: update version to 2.1.36-026 Don Brace
2025-11-08 18:09 ` Martin K. Petersen [this message]
2025-11-13 2:46 ` [PATCH 0/4] smartpqi updates 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=yq1wm40gzwp.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=POSWALD@suse.com \
--cc=cameron.cumberland@suse.com \
--cc=david.strahan@microchip.com \
--cc=don.brace@microchip.com \
--cc=gerry.morong@microchip.com \
--cc=hch@infradead.org \
--cc=jeremy.reeves@microchip.com \
--cc=joseph.szczypek@hpe.com \
--cc=kumar.meiyappan@microchip.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mahesh.rajashekhara@microchip.com \
--cc=mike.mcgowen@microchip.com \
--cc=murthy.bhat@microchip.com \
--cc=scott.benesh@microchip.com \
--cc=scott.teel@microchip.com \
--cc=yi.zhang@redhat.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