public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Daan De Meyer <daan.j.demeyer@gmail.com>
Cc: linux-block@vger.kernel.org, axboe@kernel.dk, brauner@kernel.org,
	hch@infradead.org, Daan De Meyer <daan@amutable.com>
Subject: Re: [PATCH v3 1/3] loop: fix partition scan race between udev and loop_reread_partitions()
Date: Tue, 31 Mar 2026 07:59:57 -0700	[thread overview]
Message-ID: <acvhbcRbR2cvMGRg@infradead.org> (raw)
In-Reply-To: <20260331105130.1077599-1-daan@amutable.com>

The subject looks odd - for one this is now a block patch and not
loop, so the prefix is wrong.  It also claims to be patch 1 of a
3 patch series, but so far I've not seen more than this or a cover
letter.

Otherwise this looks good to me.

      parent reply	other threads:[~2026-03-31 14:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-31 10:51 [PATCH v3 1/3] loop: fix partition scan race between udev and loop_reread_partitions() Daan De Meyer
2026-03-31 11:45 ` Christian Brauner
2026-03-31 13:07 ` Jens Axboe
2026-03-31 14:59 ` Christoph Hellwig [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=acvhbcRbR2cvMGRg@infradead.org \
    --to=hch@infradead.org \
    --cc=axboe@kernel.dk \
    --cc=brauner@kernel.org \
    --cc=daan.j.demeyer@gmail.com \
    --cc=daan@amutable.com \
    --cc=linux-block@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