Linux Documentation
 help / color / mirror / Atom feed
From: "Danilo Krummrich" <dakr@kernel.org>
To: "Randy Dunlap" <rdunlap@infradead.org>
Cc: <linux-kernel@vger.kernel.org>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	<driver-core@lists.linux.dev>, "Jonathan Corbet" <corbet@lwn.net>,
	"Shuah Khan" <skhan@linuxfoundation.org>,
	<linux-doc@vger.kernel.org>
Subject: Re: [PATCH] docs/driver-api: infrastructure: add property.h and fwnode.h
Date: Mon, 27 Jul 2026 22:29:05 +0200	[thread overview]
Message-ID: <DK9MYQPGPXPS.1M53LWK3OZUYT@kernel.org> (raw)
In-Reply-To: <20260726211200.2643484-1-rdunlap@infradead.org>

On Sun Jul 26, 2026 at 11:12 PM CEST, Randy Dunlap wrote:
> @@ -17,6 +17,10 @@ The Basic Device Driver-Model Structures
>  .. kernel-doc:: include/linux/device/driver.h
>     :identifiers: probe_type device_driver
>  
> +.. kernel-doc:: include/linux/property.h
> +
> +.. kernel-doc:: include/linux/fwnode.h

This introduces new warnings, since some fields of  are not documented:

	WARNING: ./include/linux/fwnode.h:185 struct member 'device_dma_supported' not described in 'fwnode_operations'
	WARNING: ./include/linux/fwnode.h:185 struct member 'device_get_dma_attr' not described in 'fwnode_operations'
	WARNING: ./include/linux/fwnode.h:185 struct member 'iomap' not described in 'fwnode_operations'
	WARNING: ./include/linux/fwnode.h:185 struct member 'irq_get' not described in 'fwnode_operations'

I send a patch [1] to fix those; I will pick this one up once it landed.

Thanks,
Danilo

[1] https://lore.kernel.org/driver-core/20260727202748.2232253-1-dakr@kernel.org/

  reply	other threads:[~2026-07-27 20:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-26 21:12 [PATCH] docs/driver-api: infrastructure: add property.h and fwnode.h Randy Dunlap
2026-07-27 20:29 ` Danilo Krummrich [this message]
2026-07-30 14:24 ` 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=DK9MYQPGPXPS.1M53LWK3OZUYT@kernel.org \
    --to=dakr@kernel.org \
    --cc=corbet@lwn.net \
    --cc=driver-core@lists.linux.dev \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=skhan@linuxfoundation.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