All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Karl Mehltretter" <kmehltretter@gmail.com>
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH v4 1/2] Documentation: Update after split of <linux/mod_devicetable.h>
Date: Thu, 29 Oct 2026 01:43:51 +0000	[thread overview]
Message-ID: <sashiko-outbox-188607@kernel.org> (raw)
In-Reply-To: <006464b404e9836e64c22689a8cdb4c34f43c87e.1793221199.git.kmehltretter@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Documentation: basics.rst omits kernel-doc for arm_smccc.h
--

commit 1e9cc1a9a128cf0749229f0053d8a9b4210d892b
Author: Uwe Kleine-König (The Capable Hub) <u.kleine-koenig@baylibre.com>

Documentation: Update after split of <linux/mod_devicetable.h>

This patch updates documentation references after struct definitions in
include/linux/mod_devicetable.h were split into bus-specific headers under
include/linux/device-id/.

> diff --git a/Documentation/driver-api/basics.rst b/Documentation/driver-api/basics.rst
> index 3b182cfdf1350..84f701b84e4fc 100644
> --- a/Documentation/driver-api/basics.rst
> +++ b/Documentation/driver-api/basics.rst
> @@ -10,9 +10,36 @@ Driver Entry and Exit points
>  Driver device table
>  -------------------
>  
> -.. kernel-doc:: include/linux/mod_devicetable.h
> +.. kernel-doc:: include/linux/device-id/amba.h
> +   :internal:
> +.. kernel-doc:: include/linux/device-id/cdx.h
> +   :internal:

[Severity: Low]
Should include/linux/device-id/arm_smccc.h also be included here in the
Driver device table section of Documentation/driver-api/basics.rst?

The commit message notes that basics.rst lists all headers that have
kernel-doc annotations and are not described elsewhere (with acpi.h left
out). However, include/linux/device-id/arm_smccc.h (which is included by
include/linux/mod_devicetable.h) defines struct arm_smccc_device_id with a
kernel-doc comment:

/**
 * struct arm_smccc_device_id - Arm SMCCC bus device identifier
 * @func_id: SMCCC function identifier
 */
struct arm_smccc_device_id {
	__u32 func_id;
};

Since arm_smccc.h is not referenced elsewhere under Documentation/ and is
skipped between amba.h and cdx.h, struct arm_smccc_device_id is omitted when
generating the documentation.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1793221199.git.kmehltretter@gmail.com?part=1

  reply	other threads:[~2026-10-29  1:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-29  1:37 [PATCH v4 0/2] Documentation: Restore device-ID documentation Karl Mehltretter
2026-10-29  1:37 ` [PATCH v4 1/2] Documentation: Update after split of <linux/mod_devicetable.h> Karl Mehltretter
2026-10-29  1:43   ` sashiko-bot [this message]
2026-10-29  1:37 ` [PATCH v4 2/2] docs/zh_CN: PCI: Update the pci_device_id header reference Karl Mehltretter
2026-10-29  1:41   ` sashiko-bot

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=sashiko-outbox-188607@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=kmehltretter@gmail.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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.