From: Lee Jones <lee@kernel.org>
To: Kit Dallege <xaum.io@gmail.com>
Cc: Daniel Thompson <danielt@kernel.org>,
Jingoo Han <jingoohan1@gmail.com>,
dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/5] backlight: cgbc_bl: fix kernel-doc comment for struct cgbc_bl_data
Date: Mon, 16 Mar 2026 14:12:05 +0000 [thread overview]
Message-ID: <20260316141205.GA554736@google.com> (raw)
In-Reply-To: <20260315145802.24224-1-xaum.io@gmail.com>
On Sun, 15 Mar 2026, Kit Dallege wrote:
> Add the required 'struct cgbc_bl_data -' prefix to the kernel-doc
> comment so it is properly recognized as struct documentation.
>
> This fixes the following warning:
>
> drivers/video/backlight/cgbc_bl.c:29: This comment starts with '/**', but isn't a kernel-doc comment
>
> Signed-off-by: Kit Dallege <xaum.io@gmail.com>
> Signed-off-by: kovan <xaum.io@gmail.com>
Real names please.
--
Lee Jones [李琼斯]
prev parent reply other threads:[~2026-03-16 14:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-15 14:58 [PATCH 4/5] backlight: cgbc_bl: fix kernel-doc comment for struct cgbc_bl_data Kit Dallege
2026-03-16 14:12 ` Lee Jones [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=20260316141205.GA554736@google.com \
--to=lee@kernel.org \
--cc=danielt@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jingoohan1@gmail.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xaum.io@gmail.com \
/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