From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Don Brace <don.brace@microchip.com>
Cc: <Kevin.Barnett@microchip.com>, <scott.teel@microchip.com>,
<Justin.Lindley@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>,
<jejb@linux.vnet.ibm.com>, <joseph.szczypek@hpe.com>,
<POSWALD@suse.com>, <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 0/3] smartpqi updates
Date: Wed, 03 Jan 2024 23:11:04 -0500 [thread overview]
Message-ID: <yq18r55agcb.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20231219193653.277553-1-don.brace@microchip.com> (Don Brace's message of "Tue, 19 Dec 2023 13:36:49 -0600")
Don,
> The only functional change to smartpqi is correction of a race
> condition during a scan/rescan operation. The device->rescan flag can
> be updated by multiple threads causing issues.
Applied to 6.8/scsi-staging, thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2024-01-04 4:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 19:36 [PATCH 0/3] smartpqi updates Don Brace
2023-12-19 19:36 ` [PATCH 1/3] smartpqi: Add new controller PCI IDs Don Brace
2023-12-19 19:36 ` [PATCH 2/3] smartpqi: fix logical volume rescan race condition Don Brace
2023-12-19 19:36 ` [PATCH 3/3] smartpqi: bump driver version to 2.1.26-030 Don Brace
2024-01-04 4:11 ` Martin K. Petersen [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-11-11 20:24 [PATCH 0/3] smartpqi updates Don Brace
2020-11-17 4:03 ` Martin K. Petersen
2020-11-20 3:29 ` Martin K. Petersen
2017-09-27 21:29 Don Brace
2017-10-03 2:26 ` 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=yq18r55agcb.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=Justin.Lindley@microchip.com \
--cc=Kevin.Barnett@microchip.com \
--cc=POSWALD@suse.com \
--cc=david.strahan@microchip.com \
--cc=don.brace@microchip.com \
--cc=gerry.morong@microchip.com \
--cc=hch@infradead.org \
--cc=jejb@linux.vnet.ibm.com \
--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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.