linux-kernel - Re: [PATCH 04/17] kernel: futex.c: get rid of a docs build warning

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <87h7yj59m0.fsf@nanos.tec.linutronix.de>
Date:   Fri, 20 Mar 2020 16:28:23 +0100
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Mauro Carvalho Chehab <mchehab+huawei@...nel.org>,
        Linux Doc Mailing List <linux-doc@...r.kernel.org>
Cc:     Mauro Carvalho Chehab <mchehab+huawei@...nel.org>,
        linux-kernel@...r.kernel.org, Jonathan Corbet <corbet@....net>,
        Ingo Molnar <mingo@...hat.com>,
        Peter Zijlstra <peterz@...radead.org>,
        Darren Hart <dvhart@...radead.org>
Subject: Re: [PATCH 04/17] kernel: futex.c: get rid of a docs build warning

Mauro Carvalho Chehab <mchehab+huawei@...nel.org> writes:

The subject prefix for this is: 'futex:'

> Adjust whitespaces and blank lines in order to get rid of this:
>
> 	./kernel/futex.c:491: WARNING: Definition list ends without a blank line; unexpected unindent.
>
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
> ---
>  kernel/futex.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/kernel/futex.c b/kernel/futex.c
> index 67f004133061..dda6ddbc2e7d 100644
> --- a/kernel/futex.c
> +++ b/kernel/futex.c
> @@ -486,7 +486,8 @@ static u64 get_inode_sequence_number(struct inode *inode)
>   * The key words are stored in @key on success.
>   *
>   * For shared mappings (when @fshared), the key is:
> - *   ( inode->i_sequence, page->index, offset_within_page )
> + * ( inode->i_sequence, page->index, offset_within_page )

Sigh. Is there no better way to make this look sane both in the file and
in the docs?

Thanks,

        tglx