From: Anna-Maria Behnsen <anna-maria@linutronix.de>
To: Jani Nikula <jani.nikula@linux.intel.com>, linux-doc@vger.kernel.org
Cc: Matthew Wilcox <willy@infradead.org>,
Jonathan Corbet <corbet@lwn.net>,
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>
Subject: Re: [RFC PATCH 1/2] drm/vram-helper: Fix 'multi-line' kernel-doc comments
Date: Mon, 22 Jan 2024 10:13:43 +0100 [thread overview]
Message-ID: <875xzlzq60.fsf@somnus> (raw)
In-Reply-To: <87frywqrbc.fsf@intel.com>
Jani Nikula <jani.nikula@linux.intel.com> writes:
> On Tue, 16 Jan 2024, Anna-Maria Behnsen <anna-maria@linutronix.de> wrote:
>> Reformat lines in kernel-doc comments, which make use of the backslash at
>> the end to suggest it is a multi-line comment. kernel-doc is able to
>> process e.g. the short description of a function properly, even if it is
>> across two lines.
>>
>> No functional change.
>>
>> Signed-off-by: Anna-Maria Behnsen <anna-maria@linutronix.de>
>
> Should be sent to dri-devel.
>
> Reviewed-by: Jani Nikula <jani.nikula@intel.com>
Thanks for the review. As it was a RFC and would only work if the doc
people are fine with the change, I decided not to bother all people in
advance. I'll resend it without RFC also to dri-devel.
Thanks,
Anna-Maria
next prev parent reply other threads:[~2024-01-22 9: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 [this message]
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
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=875xzlzq60.fsf@somnus \
--to=anna-maria@linutronix.de \
--cc=airlied@gmail.com \
--cc=corbet@lwn.net \
--cc=daniel@ffwll.ch \
--cc=jani.nikula@linux.intel.com \
--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.