linux-kernel - Re: [PATCH v1] jffs2: fix comment typo and adjust formatting

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1d247663-9b37-1bff-d18c-7f6866e5f041@huawei.com>
Date: Wed, 4 Jun 2025 12:20:17 +0800
From: Zhihao Cheng <chengzhihao1@...wei.com>
To: Baolin Liu <liubaolin12138@....com>, <dwmw2@...radead.org>,
	<richard@....at>
CC: <liubaolin@...inos.cn>, <linux-mtd@...ts.infradead.org>,
	<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v1] jffs2: fix comment typo and adjust formatting

在 2025/6/4 10:20, Baolin Liu 写道:
> From: Baolin Liu <liubaolin@...inos.cn>
> 
> This commit makes two documentation improvements:
> 1. Fixes spelling of "coresponding" to "corresponding"
> 2. Adjusts comment formatting to meet kernel style guidelines by:
>     - Breaking long lines to fit 80-column limit
>     - Aligning asterisks in multi-line comments
>     - Improving readability while preserving original meaning
> 
> No functional changes.
> 
> Signed-off-by: Baolin Liu <liubaolin@...inos.cn>
> ---
>   fs/jffs2/build.c | 6 ++++--
>   1 file changed, 4 insertions(+), 2 deletions(-)
> 

Reviewed-by: Zhihao Cheng <chengzhihao1@...wei.com>
> diff --git a/fs/jffs2/build.c b/fs/jffs2/build.c
> index 6ae9d6fefb86..1e651d3dcef3 100644
> --- a/fs/jffs2/build.c
> +++ b/fs/jffs2/build.c
> @@ -185,8 +185,10 @@ static int jffs2_build_filesystem(struct jffs2_sb_info *c)
>   			 * one. */
>   			if (fd->type == DT_DIR) {
>   				if (!fd->ic) {
> -					/* We'll have complained about it and marked the coresponding
> -					   raw node obsolete already. Just skip it. */
> +					/* We'll have complained about it
> +					 * and marked the corresponding raw node obsolete already.
> +					 * Just skip it.
> +					 */
>   					continue;
>   				}
>   
>