The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Danilo Krummrich" <dakr@kernel.org>
To: "Francesco Valla" <francesco@valla.it>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	"Tim Bird" <tim.bird@sony.com>, <driver-core@lists.linux.dev>,
	<linux-kernel@vger.kernel.org>, <linux-embedded@vger.kernel.org>
Subject: Re: [PATCH v2] driver core: add driver name to probe debug print
Date: Fri, 03 Jul 2026 18:59:06 +0200	[thread overview]
Message-ID: <DJP3GW0F3BYU.2OY52DAYFCDS@kernel.org> (raw)
In-Reply-To: <20260703-probe_driver-v2-1-b6060559f33b@valla.it>

On Fri Jul 3, 2026 at 5:10 PM CEST, Francesco Valla wrote:
> The initcall_debug command line option is a useful tool while debugging
> and optimizing the initialization of a new system, mainly because it
> allows to see probe failures and deferrals without recompiling the
> kernel (e.g., with CONFIG_DEBUG_DRIVER). However, matching a device
> with the driver it is being probed with can become difficult, since
> some devices use names that are not explicit, at least at a first sight
> (e.g.: '1-0:1.0' or '1-0060').
>
> Add the driver name alongside the device name, to allow for an immediate
> match between the two.
>
> Suggested-by: Tim Bird <tim.bird@sony.com>
> Signed-off-by: Francesco Valla <francesco@valla.it>

Acked-by: Danilo Krummrich <dakr@kernel.org>

      reply	other threads:[~2026-07-03 16:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-03 15:10 [PATCH v2] driver core: add driver name to probe debug print Francesco Valla
2026-07-03 16:59 ` Danilo Krummrich [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=DJP3GW0F3BYU.2OY52DAYFCDS@kernel.org \
    --to=dakr@kernel.org \
    --cc=driver-core@lists.linux.dev \
    --cc=francesco@valla.it \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-embedded@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=tim.bird@sony.com \
    /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