From: Bart Van Assche <bvanassche@acm.org>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH v2 0/4] UFS driver bug fixes
Date: Fri, 15 Aug 2025 08:56:56 -0700 [thread overview]
Message-ID: <e18b474f-04db-4b4c-823d-7c6003ca85a8@acm.org> (raw)
In-Reply-To: <yq1bjohqn97.fsf@ca-mkp.ca.oracle.com>
On 8/14/25 8:27 PM, Martin K. Petersen wrote:
> Only the first two patches made it to the list when you sent v2.
Thanks Martin for having reported this. I will repost this series.
Bart.
prev parent reply other threads:[~2025-08-15 15:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 16:22 [PATCH v2 0/4] UFS driver bug fixes Bart Van Assche
2025-08-13 16:22 ` [PATCH v2 1/4] ufs: core: Fix IRQ lock inversion for the SCSI host lock Bart Van Assche
2025-08-13 16:22 ` [PATCH v2 2/4] ufs: core: Remove WARN_ON_ONCE() call from ufshcd_uic_cmd_compl() Bart Van Assche
2025-08-15 3:27 ` [PATCH v2 0/4] UFS driver bug fixes Martin K. Petersen
2025-08-15 15:56 ` Bart Van Assche [this message]
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=e18b474f-04db-4b4c-823d-7c6003ca85a8@acm.org \
--to=bvanassche@acm.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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).