All of lore.kernel.org
 help / color / mirror / Atom feed
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 15:44:42 -0400	[thread overview]
Message-ID: <yq1mscrrcnf.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <2eb58df6-0985-4901-9494-9ecbe77a0b8e@acm.org> (Bart Van Assche's message of "Mon, 7 Apr 2025 12:18:58 -0700")


Bart,

> That patch is fine as far as I know. My question is about timing. Is
> my understanding correct that all these patches will be merged during
> the 6.16 merge window (three months from now)?

The patches currently merged will be pulled into 6.15/scsi-fixes once I
set up the new trees. There is almost always an outstanding delta at the
beginning of each cycle since I don't stop applying fixes during the
merge window.

-- 
Martin K. Petersen

      reply	other threads:[~2025-04-07 19:45 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
2025-04-07 19:18       ` Bart Van Assche
2025-04-07 19:44         ` Martin K. Petersen [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=yq1mscrrcnf.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.