Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <mkp@kernel.org>
To: Bart Van Assche <bvanassche@acm.org>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH v3 0/7] scsi_debug: Enable lock context analysis
Date: Mon, 05 Oct 2026 21:39:12 -0400	[thread overview]
Message-ID: <yq1fqyjk3tm.fsf@mail.kernel.org> (raw)
In-Reply-To: <2fe7fd58-fda8-45db-830f-3197999a2538@acm.org>


Bart,

>> There are several conflicts wrt. Niklas' zoned write series. Please
>> rebase, thanks!
>
> Is Niklas' series already available on kernel.org? This is what I see:

Ah, a recent infrastructure change meant my trees did not get pushed.

Thanks for spotting! I'll get this resolved shortly.

-- 
Martin K. Petersen

      reply	other threads:[~2026-10-06  1:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-29 23:22 [PATCH v3 0/7] scsi_debug: Enable lock context analysis Bart Van Assche
2026-09-29 23:22 ` [PATCH v3 1/7] scsi: scsi_debug: Fix a locking bug in resp_write_same() Bart Van Assche
2026-09-29 23:22 ` [PATCH v3 2/7] scsi: scsi_debug: Split resp_write_same() Bart Van Assche
2026-09-29 23:22 ` [PATCH v3 3/7] scsi: scsi_debug: Split corrupt_lbas() Bart Van Assche
2026-09-29 23:23 ` [PATCH v3 4/7] scsi: scsi_debug: Split resp_read_dt0() Bart Van Assche
2026-09-29 23:23 ` [PATCH v3 5/7] scsi: scsi_debug: Split resp_write_dt0() Bart Van Assche
2026-09-29 23:23 ` [PATCH v3 6/7] scsi: scsi_debug: Improve lock context annotations Bart Van Assche
2026-09-29 23:35   ` sashiko-bot
2026-09-30 13:16     ` Bart Van Assche
2026-09-29 23:23 ` [PATCH v3 7/7] scsi: core: Enable lock context analysis for the scsi_debug driver Bart Van Assche
2026-10-03 14:24 ` [PATCH v3 0/7] scsi_debug: Enable lock context analysis Martin K. Petersen (Oracle)
2026-10-04 22:39   ` Bart Van Assche
2026-10-06  1:39     ` 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=yq1fqyjk3tm.fsf@mail.kernel.org \
    --to=mkp@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox