From: Steven Rostedt <rostedt@goodmis.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
linux-doc@vger.kernel.org,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arch/Kconfig: update a broken file reference
Date: Thu, 21 Jan 2021 14:44:15 -0500 [thread overview]
Message-ID: <20210121144415.7b2ddf3c@gandalf.local.home> (raw)
In-Reply-To: <20210121114458.614ee8da@lwn.net>
On Thu, 21 Jan 2021 11:44:58 -0700
Jonathan Corbet <corbet@lwn.net> wrote:
> On Tue, 19 Jan 2021 10:53:26 +0100
> Lukas Bulwahn <lukas.bulwahn@gmail.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@gmail.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
prev parent reply other threads:[~2021-01-21 19:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 9:53 [PATCH] arch/Kconfig: update a broken file reference Lukas Bulwahn
2021-01-21 18:44 ` Jonathan Corbet
2021-01-21 19:44 ` Steven Rostedt [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=20210121144415.7b2ddf3c@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=corbet@lwn.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=mchehab+huawei@kernel.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