From: Mikulas Patocka <mpatocka@redhat.com>
To: Peter Korsgaard <peter@korsgaard.com>
Cc: Guillaume Gonnet <ggonnet.linux@gmail.com>,
Alasdair Kergon <agk@redhat.com>,
Mike Snitzer <snitzer@kernel.org>,
Benjamin Marzinski <bmarzins@redhat.com>,
dm-devel@schwermer.no, chanho.min@lge.com, jaeyuel.im@lge.com,
dm-devel@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dm init: ensure device probing has finished in dm-mod.waitfor=
Date: Wed, 18 Mar 2026 22:13:27 +0100 (CET) [thread overview]
Message-ID: <0964cb66-6273-9e42-c393-31ff799a2d01@redhat.com> (raw)
In-Reply-To: <87y0jpf2ar.fsf@dell.be.48ers.dk>
On Wed, 18 Mar 2026, Peter Korsgaard wrote:
> >>>>> "Mikulas" == Mikulas Patocka <mpatocka@redhat.com> writes:
>
> > Hi
> > I staged the patch, thanks.
>
> But how does it work? Do we still need the other wait_for_device_probe()
> call? This looks nontrivial, a comment would be helpful.
>
> --
> Bye, Peter Korsgaard
So, if you want to add some comment to the code or to the patch header,
let me know, and I will add it.
Mikulas
next prev parent reply other threads:[~2026-03-18 21:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 21:32 [PATCH] dm init: ensure device probing has finished in dm-mod.waitfor= Guillaume Gonnet
2026-03-18 8:22 ` Peter Korsgaard
2026-03-18 9:25 ` Guillaume GONNET
2026-03-18 16:36 ` Mikulas Patocka
2026-03-18 17:57 ` Peter Korsgaard
2026-03-18 21:13 ` Mikulas Patocka [this message]
2026-03-19 8:47 ` Guillaume Gonnet
2026-03-19 10:53 ` Peter Korsgaard
2026-03-26 21:40 ` Francesco Valla
[not found] ` <abtakh4sU3HldDBB@BRUNHILD>
[not found] ` <DH6N0QM6764O.2CZNT5C8VH6Y1@gmail.com>
2026-03-27 4:33 ` Chanho Min
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=0964cb66-6273-9e42-c393-31ff799a2d01@redhat.com \
--to=mpatocka@redhat.com \
--cc=agk@redhat.com \
--cc=bmarzins@redhat.com \
--cc=chanho.min@lge.com \
--cc=dm-devel@lists.linux.dev \
--cc=dm-devel@schwermer.no \
--cc=ggonnet.linux@gmail.com \
--cc=jaeyuel.im@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@korsgaard.com \
--cc=snitzer@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.