From: "Richard Weinberger (sigma star gmbh)" <rw@kernel.org>
To: linux-kernel@vger.kernel.org, Randy Dunlap <rdunlap@infradead.org>
Cc: Richard Weinberger <richard@nod.at>,
Zhihao Cheng <chengzhihao1@huawei.com>,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH] ubifs: headers: clean up some kernel-doc comments
Date: Tue, 11 Aug 2026 23:05:53 +0200 [thread overview]
Message-ID: <178648234018.3948622.4036568993369014811.b4-ty@b4> (raw)
In-Reply-To: <20260729172044.1793865-1-rdunlap@infradead.org>
From: Richard Weinberger <richard@nod.at>
On Wed, 29 Jul 2026 10:20:41 -0700, Randy Dunlap wrote:
> Clean up kernel-doc comments in 3 ubifs header files:
>
> [PATCH 1/3] ubifs: debug.h: fix kernel-doc struct prototypes
> [PATCH 2/3] ubifs: key.h: use correct function parameter name
> [PATCH 3/3] ubifs: ubifs.h: clean up kernel-doc comments
>
> fs/ubifs/debug.h | 4 ++--
> fs/ubifs/key.h | 2 +-
> fs/ubifs/ubifs.h | 20 ++++++++++++--------
> 3 files changed, 15 insertions(+), 11 deletions(-)
>
> [...]
Applied, thanks!
[1/3] ubifs: debug.h: fix kernel-doc struct prototypes
commit: f06711486c12c1fbb3ea9c0c595ca244b111891f
[2/3] ubifs: key.h: use correct function parameter name
commit: abd6591fb5cc1490ab2cf5d9ff513a6677fa57b2
[3/3] ubifs: ubifs.h: clean up kernel-doc comments
commit: 4e5e02340a18183b0f8ad633da1516cad92ee43e
Best regards,
--
Richard Weinberger <richard@nod.at>
prev parent reply other threads:[~2026-08-11 21:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 17:20 Randy Dunlap
2026-07-29 17:20 ` [PATCH 1/3] ubifs: debug.h: fix kernel-doc struct prototypes Randy Dunlap
2026-07-29 17:20 ` [PATCH 2/3] ubifs: key.h: use correct function parameter name Randy Dunlap
2026-07-30 1:20 ` Zhihao Cheng
2026-07-29 17:20 ` [PATCH 3/3] ubifs: ubifs.h: clean up kernel-doc comments Randy Dunlap
2026-07-30 1:25 ` Zhihao Cheng
2026-08-11 21:05 ` Richard Weinberger (sigma star gmbh) [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=178648234018.3948622.4036568993369014811.b4-ty@b4 \
--to=rw@kernel.org \
--cc=chengzhihao1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=rdunlap@infradead.org \
--cc=richard@nod.at \
/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
all inboxes | Powered by JetHome®