All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Anna-Maria Behnsen <anna-maria@linutronix.de>, linux-doc@vger.kernel.org
Cc: Matthew Wilcox <willy@infradead.org>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
	Anna-Maria Behnsen <anna-maria@linutronix.de>
Subject: Re: [RFC PATCH 0/2] kernel-doc: Do not pre-process comments
Date: Tue, 16 Jan 2024 14:13:21 -0700	[thread overview]
Message-ID: <87le8p9e32.fsf@meer.lwn.net> (raw)
In-Reply-To: <87ttnd9ggx.fsf@meer.lwn.net>

Jonathan Corbet <corbet@lwn.net> writes:

> Anna-Maria Behnsen <anna-maria@linutronix.de> writes:
>
>> this is a RFC as I'm not quite sure if this change has some subtle side
>> effect.
>
> Turns out it does, unfortunately.  Consider a hunk like this:

Actually, I respectfully suggest that you ignore me completely...I'm
having kind of a scattered day.  In truth, this all seems good.

There is, however, one subtle little change.  Consider this from the
comment-cleanup patch:

> /**
> - * drm_gem_vram_plane_helper_prepare_fb() - \
> - *	Implements &struct drm_plane_helper_funcs.prepare_fb
> + * drm_gem_vram_plane_helper_prepare_fb() - Implements &struct
> + *					    drm_plane_helper_funcs.prepare_fb

Current kernel-doc preserves the "*" on the continuation line, with the
result that the description is rendered as an itemized list.  You can
see it at:

  https://docs.kernel.org/gpu/drm-mm.html?highlight=drm_gem_vram_plane_helper_prepare_fb#c.drm_gem_vram_plane_helper_prepare_fb

It's a subtle thing that doesn't really affect the readability, but even
so, somebody clearly ran into it at some point:

> /**
> - * drm_gem_vram_driver_dumb_create() - \
> -	Implements &struct drm_driver.dumb_create
> + * drm_gem_vram_driver_dumb_create() - Implements &struct drm_driver.dumb_create

A number of the existing comments leave out the leading "*" on the
continuation lines, presumably to work around this weirdness.  With your
patch, this little problem goes away - a little unadvertised extra
benefit! :)

The kernel-doc change should really go together with the DRM change.
I'm happy to carry both with an ack from DRMland or have the kernel-doc
patch go through the DRM tree, whichever is easiest.

Thanks,

jon

      reply	other threads:[~2024-01-16 21:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-16 15:14 [RFC PATCH 0/2] kernel-doc: Do not pre-process comments Anna-Maria Behnsen
2024-01-16 15:14 ` [RFC PATCH 1/2] drm/vram-helper: Fix 'multi-line' kernel-doc comments Anna-Maria Behnsen
2024-01-17  8:47   ` Jani Nikula
2024-01-22  9:13     ` Anna-Maria Behnsen
2024-01-16 15:14 ` [RFC PATCH 2/2] scripts/kernel-doc: Do not process backslash lines in comments Anna-Maria Behnsen
2024-01-16 20:21 ` [RFC PATCH 0/2] kernel-doc: Do not pre-process comments Jonathan Corbet
2024-01-16 21:13   ` 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=87le8p9e32.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=airlied@gmail.com \
    --cc=anna-maria@linutronix.de \
    --cc=daniel@ffwll.ch \
    --cc=linux-doc@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=tzimmermann@suse.de \
    --cc=willy@infradead.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 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.