From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org
Subject: Re: [PATCH] i2c: i2c.h: fix a bad kernel-doc line
Date: Sat, 29 Nov 2025 21:40:07 +0900 [thread overview]
Message-ID: <aSrpp1l2BQkakfF2@shikoro> (raw)
In-Reply-To: <20251125022808.3168059-1-rdunlap@infradead.org>
On Mon, Nov 24, 2025 at 06:28:08PM -0800, Randy Dunlap wrote:
> Change an empty line into a blank kernel-doc line to prevent
> a kernel-doc warning:
>
> Warning: ../include/uapi/linux/i2c.h:38 bad line:
>
> Fixes: bfb3939c51d5 ("i2c: refactor documentation of struct i2c_msg")
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Applied to for-next, thanks!
prev parent reply other threads:[~2025-11-29 12:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 2:28 [PATCH] i2c: i2c.h: fix a bad kernel-doc line Randy Dunlap
2025-11-29 12:40 ` Wolfram Sang [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=aSrpp1l2BQkakfF2@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox