From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
<linux-scsi@vger.kernel.org>,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>
Subject: Re: [PATCH v2] scsi: ufs: core: Fix a race condition related to device commands
Date: Mon, 07 Apr 2025 14:55:24 -0400 [thread overview]
Message-ID: <yq1a58rstcs.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <1c08cc57-60dc-4efc-870d-6b9688c85b2d@acm.org> (Bart Van Assche's message of "Mon, 7 Apr 2025 09:59:16 -0700")
Hi Bart!
> Has a pull request already been sent to Linus for the changes on the
> 6.15/scsi-staging branch?
scsi-staging is just for seeing what breaks. Patches aren't considered
submission material until they show up in either scsi-queue or
scsi-fixes.
However, commit 20b97acc4caf ("scsi: ufs: core: Fix a race condition
related to device commands") is in scsi-queue and thus technically ready
for submission.
Is there a problem with this patch?
If I were to drop it, I'd have to redo a few things in staging. I can do
that, but at this stage I'd prefer an incremental patch.
--
Martin K. Petersen
next prev parent reply other threads:[~2025-04-07 18:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 22:51 [PATCH v2] scsi: ufs: core: Fix a race condition related to device commands Bart Van Assche
2025-03-15 8:46 ` Avri Altman
2025-03-17 22:49 ` Bart Van Assche
2025-03-18 2:39 ` Peter Wang (王信友)
2025-03-21 0:48 ` Martin K. Petersen
2025-04-07 16:59 ` Bart Van Assche
2025-04-07 18:55 ` Martin K. Petersen [this message]
2025-04-07 19:18 ` Bart Van Assche
2025-04-07 19:44 ` 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=yq1a58rstcs.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=bvanassche@acm.org \
--cc=linux-scsi@vger.kernel.org \
/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.