public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Danilo Krummrich" <dakr@kernel.org>
To: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	"Arnd Bergmann" <arnd@kernel.org>,
	"Bartosz Golaszewski" <brgl@kernel.org>,
	"Hans de Goede" <hansg@kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/3] Allow attaching software node when registering platform devices
Date: Sat, 14 Feb 2026 11:55:57 +0100	[thread overview]
Message-ID: <DGEMP4EE87BE.4B8FH5897EG8@kernel.org> (raw)
In-Reply-To: <20260214025246.2095239-1-dmitry.torokhov@gmail.com>

On Sat Feb 14, 2026 at 3:52 AM CET, Dmitry Torokhov wrote:
> v2:
> - add kerneldoc for platform_device_info

Thanks for documenting the whole struct!

> - split out formatting changes into a separate patch

There is still the mixup in the documentation patch, but I can see why you did
it and I think it's fine.

>   driver core: platform: add kerneldoc to struct platform_device_info
>   driver core: platform: allow attaching software nodes when creating
>     devices

Unless there there is any contrary feedback from Greg or Rafael, I can pick up
the series after -rc1 is out and hand out a signed tag for the two of those.

>   driver core: platform: fix various formatting issues

Thanks,
Danilo

  parent reply	other threads:[~2026-02-14 10:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-14  2:52 [PATCH v2 0/3] Allow attaching software node when registering platform devices Dmitry Torokhov
2026-02-14  2:52 ` [PATCH v2 1/3] driver core: platform: add kerneldoc to struct platform_device_info Dmitry Torokhov
2026-02-16 13:31   ` Bartosz Golaszewski
2026-02-14  2:52 ` [PATCH v2 2/3] driver core: platform: allow attaching software nodes when creating devices Dmitry Torokhov
2026-02-16 13:31   ` Bartosz Golaszewski
2026-02-14  2:52 ` [PATCH v2 3/3] driver core: platform: fix various formatting issues Dmitry Torokhov
2026-02-16 13:31   ` Bartosz Golaszewski
2026-02-14 10:55 ` Danilo Krummrich [this message]
2026-03-01  5:02   ` [PATCH v2 0/3] Allow attaching software node when registering platform devices Dmitry Torokhov
2026-03-02  0:42     ` Danilo Krummrich
2026-03-02 14:39       ` Danilo Krummrich
2026-03-03 15:55         ` Dmitry Torokhov
2026-03-03 16:45         ` Danilo Krummrich

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=DGEMP4EE87BE.4B8FH5897EG8@kernel.org \
    --to=dakr@kernel.org \
    --cc=arnd@kernel.org \
    --cc=brgl@kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hansg@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@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