mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: "Guillaume Gonnet" <ggonnet.linux@gmail.com>
Cc: "Mikulas Patocka" <mpatocka@redhat.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: Thu, 19 Mar 2026 11:53:37 +0100	[thread overview]
Message-ID: <87cy10dr9q.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <DH6MMYX3TX5Y.R3N3IX6370ED@gmail.com> (Guillaume Gonnet's message of "Thu, 19 Mar 2026 09:47:47 +0100")

>>>>> "Guillaume" == Guillaume Gonnet <ggonnet.linux@gmail.com> writes:

 > Hello Peter,
 > Here are my answers to your questions.

Thanks for the details.

 >> This looks nontrivial, a comment would be helpful.

 > I think the commit message contains enough information to understand why
 > the second wait_for_device_probe() call is required, a comment would
 > contain less information so I prefer letting the code like that.

OK. Ideally the above description would have made it into the commit
message, but fine.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2026-03-19 10:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-17 21:32 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
2026-03-19  8:47     ` Guillaume Gonnet
2026-03-19 10:53       ` Peter Korsgaard [this message]
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=87cy10dr9q.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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=mpatocka@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®