From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-scsi@vger.kernel.org,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
GR-QLogic-Storage-Upstream@marvell.com,
Hannes Reinecke <hare@suse.de>, Javed Hasan <jhasan@marvell.com>,
Saurav Kashyap <skashyap@marvell.com>,
Thomas Gleixner <tglx@linutronix.de>,
Davidlohr Bueso <dbueso@suse.de>
Subject: Re: [PATCH 0/4] scsi: PREEMPT_RT related fixes.
Date: Mon, 16 May 2022 21:28:51 -0400 [thread overview]
Message-ID: <yq1mtfhrlrr.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20220506105758.283887-1-bigeasy@linutronix.de> (Sebastian Andrzej Siewior's message of "Fri, 6 May 2022 12:57:54 +0200")
Sebastian,
> this is what I have in PREEMPT_RT queue for the SCSI stack. Two of
> these patches have been posted earlier by Davidlohr in another
> series. I then added the statistics change and then I stumbled upon
> another get_cpu() usage in bnx2fc so there are four patches now. Due
> lack of hardware, the series has been compile tested only.
Applied to 5.19/scsi-staging, thanks!
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2022-05-17 1:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 10:57 [PATCH 0/4] scsi: PREEMPT_RT related fixes Sebastian Andrzej Siewior
2022-05-06 10:57 ` [PATCH 1/4] scsi: fcoe: Add a local_lock to fcoe_percpu Sebastian Andrzej Siewior
2022-05-06 10:57 ` [PATCH 2/4] scsi: fcoe: Use per-CPU API to update per-CPU statistics Sebastian Andrzej Siewior
2022-05-10 0:48 ` Davidlohr Bueso
2022-05-06 10:57 ` [PATCH 3/4] scsi: libfc: Remove get_cpu() semantics in fc_exch_em_alloc() Sebastian Andrzej Siewior
2022-05-06 10:57 ` [PATCH 4/4] scsi: bnx2fc: Avoid using get_cpu() in bnx2fc_cmd_alloc() Sebastian Andrzej Siewior
2022-05-07 4:46 ` Davidlohr Bueso
2022-05-17 1:28 ` Martin K. Petersen [this message]
2022-05-17 6:11 ` [PATCH 0/4] scsi: PREEMPT_RT related fixes Sebastian Andrzej Siewior
2022-05-20 1:09 ` 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=yq1mtfhrlrr.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=GR-QLogic-Storage-Upstream@marvell.com \
--cc=bigeasy@linutronix.de \
--cc=dbueso@suse.de \
--cc=hare@suse.de \
--cc=jejb@linux.ibm.com \
--cc=jhasan@marvell.com \
--cc=linux-scsi@vger.kernel.org \
--cc=skashyap@marvell.com \
--cc=tglx@linutronix.de \
/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