From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Matt Coster <matt.coster@imgtec•com>
Cc: Frank Binns <frank.binns@imgtec•com>,
Alessio Belle <alessio.belle@imgtec•com>,
Alexandru Dadu <alexandru.dadu@imgtec•com>,
Maarten Lankhorst <maarten.lankhorst@linux•intel.com>,
Maxime Ripard <mripard@kernel•org>,
Thomas Zimmermann <tzimmermann@suse•de>,
David Airlie <airlied@gmail•com>, Simona Vetter <simona@ffwll•ch>,
<dri-devel@lists•freedesktop.org>, <linux-kernel@vger•kernel.org>,
<linux-next@vger•kernel.org>
Subject: Re: [PATCH v2] drm/imagination: Document pvr_device.power member
Date: Sat, 22 Nov 2025 14:46:19 +1100 [thread overview]
Message-ID: <20251122144619.73fa991d@canb.auug.org.au> (raw)
In-Reply-To: <20251121-device-power-doc-fix-v2-1-3417779f36c7@imgtec.com>
[-- Attachment #1: Type: text/plain, Size: 836 bytes --]
Hi Matt,
On Fri, 21 Nov 2025 15:20:31 +0000 Matt Coster <matt.coster@imgtec•com> wrote:
>
> Based on the build target indicated in the report, I tried (and failed)
> to reproduce the reported warning using:
>
> make W=1 htmldocs
>
> I was, however, able to get the reported warning (and verify that this
> patch clears it) using:
>
> scripts/kernel-doc -none drivers/gpu/drm/imagination/pvr_device.h
>
> Does anyone have any ideas why my invocation of htmldocs didn't seem to
> have the same effect? Is it just simply that the relevant doc comment
> isn't pulled into any of the rst docs; in which case how did the
> linux-next build catch this warning?
I just do "make htmldocs" on the final linux-next tree each day, so I
have no idea what makes a difference, sorry.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 484 bytes --]
prev parent reply other threads:[~2025-11-22 3:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-21 15:20 [PATCH v2] drm/imagination: Document pvr_device.power member Matt Coster
2025-11-21 16:43 ` Alessio Belle
2025-11-21 17:12 ` Matt Coster
2025-11-22 0:29 ` Randy Dunlap
2025-11-22 3:46 ` Stephen Rothwell [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=20251122144619.73fa991d@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=airlied@gmail$(echo .)com \
--cc=alessio.belle@imgtec$(echo .)com \
--cc=alexandru.dadu@imgtec$(echo .)com \
--cc=dri-devel@lists$(echo .)freedesktop.org \
--cc=frank.binns@imgtec$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=maarten.lankhorst@linux$(echo .)intel.com \
--cc=matt.coster@imgtec$(echo .)com \
--cc=mripard@kernel$(echo .)org \
--cc=simona@ffwll$(echo .)ch \
--cc=tzimmermann@suse$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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