linux-kernel - Re: [PATCH] arch/Kconfig: update a broken file reference

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: <20210121144415.7b2ddf3c@gandalf.local.home>
Date:   Thu, 21 Jan 2021 14:44:15 -0500
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Jonathan Corbet <corbet@....net>
Cc:     Lukas Bulwahn <lukas.bulwahn@...il.com>, linux-doc@...r.kernel.org,
        Mauro Carvalho Chehab <mchehab+huawei@...nel.org>,
        kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] arch/Kconfig: update a broken file reference

On Thu, 21 Jan 2021 11:44:58 -0700
Jonathan Corbet <corbet@....net> wrote:

> On Tue, 19 Jan 2021 10:53:26 +0100
> Lukas Bulwahn <lukas.bulwahn@...il.com> wrote:
> 
> > Commit adab66b71abf ("Revert: "ring-buffer: Remove HAVE_64BIT_ALIGNED_ACCESS"")
> > added the config HAVE_64BIT_ALIGNED_ACCESS back into arch/Kconfig with this
> > revert. In the meantime, commit c9b54d6f362c ("docs: move other kAPI
> > documents to core-api") changed ./Documentation/unaligned-memory-access.txt
> > to ./Documentation/core-api/unaligned-memory-access.rst.
> > 
> > Fortunately, ./scripts/documentation-file-ref-check detects this and warns
> > about this broken reference.
> > 
> > Update the file reference in arch/Kconfig.
> > 
> > Fixes: adab66b71abf ("Revert: "ring-buffer: Remove HAVE_64BIT_ALIGNED_ACCESS"")
> > Signed-off-by: Lukas Bulwahn <lukas.bulwahn@...il.com>
> > ---
> > applies cleanly on current master and next-20210118
> > 
> > Steven, could you pick this fix to your commit or, at least, ack it so that
> > Jonathan can pick it?  
> 
> I've gone ahead and applied it, thanks.


Thanks Jon!

-- Steve