From: Jonathan Corbet <corbet@lwn.net>
To: Daniel Lundberg Pedersen <dlp@qtec.com>, linux-doc@vger.kernel.org
Subject: Re: Incorrect auto formatting of struct
Date: Thu, 23 Apr 2026 06:15:47 -0600 [thread overview]
Message-ID: <87eck5ub2k.fsf@trenco.lwn.net> (raw)
In-Reply-To: <35f1379c-41eb-422b-9441-393af5bddf31@qtec.com>
Daniel Lundberg Pedersen <dlp@qtec.com> writes:
> Hi
>
> I've just noticed that between v6.16 and v6.17 the documentation has started to
> highlight struct that are not structs, e.g `struct inside`:
>
> https://www.kernel.org/doc/html/v6.17/driver-api/media/v4l2-device.html
>
> Previously it did not highlight this as a struct:
>
> https://www.kernel.org/doc/html/v6.16/driver-api/media/v4l2-device.html
>
> I couldn't find anything about whether this is intentional and thus needs doc
> fixes, or if it was already reported, it's not that easy to search for.
Definitely not intentional. Thanks for the report, I'll look into it
when I get a chance.
jon
prev parent reply other threads:[~2026-04-23 12:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-22 13:37 Incorrect auto formatting of struct Daniel Lundberg Pedersen
2026-04-23 12:15 ` Jonathan Corbet [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=87eck5ub2k.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=dlp@qtec.com \
--cc=linux-doc@vger.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