From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Salvatore Bonaccorso <carnil@debian.org>
Cc: stable <stable@vger.kernel.org>,
"Sasha Levin" <sashal@kernel.org>,
"Peter Zijlstra" <peterz@infradead.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"André Almeida" <andrealmeid@collabora.com>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
"Jonathan Corbet" <corbet@lwn.net>
Subject: Re: [PATCH v2 stable-5.10.y stable-5.15.y] docs: futex: Fix kernel-doc references after code split-up preparation
Date: Sat, 22 Apr 2023 07:46:47 +0200 [thread overview]
Message-ID: <ZEN0x2Opg2dryAND@kroah.com> (raw)
In-Reply-To: <ZEN0MsKMQXTqGwk-@kroah.com>
On Sat, Apr 22, 2023 at 07:44:18AM +0200, Greg Kroah-Hartman wrote:
> On Sat, Apr 22, 2023 at 12:17:42AM +0200, Salvatore Bonaccorso wrote:
> > In upstream commit 77e52ae35463 ("futex: Move to kernel/futex/") the
> > futex code from kernel/futex.c was moved into kernel/futex/core.c in
> > preparation of the split-up of the implementation in various files.
> >
> > Point kernel-doc references to the new files as otherwise the
> > documentation shows errors on build:
> >
> > [...]
> > Error: Cannot open file ./kernel/futex.c
> > Error: Cannot open file ./kernel/futex.c
> > [...]
> > WARNING: kernel-doc './scripts/kernel-doc -rst -enable-lineno -sphinx-version 3.4.3 -internal ./kernel/futex.c' failed with return code 2
> >
> > There is no direct upstream commit for this change. It is made in
> > analogy to commit bc67f1c454fb ("docs: futex: Fix kernel-doc
> > references") applied as consequence of the restructuring of the futex
> > code.
> >
> > Fixes: 77e52ae35463 ("futex: Move to kernel/futex/")
> > Signed-off-by: Salvatore Bonaccorso <carnil@debian.org>
> > ---
> > v1->v2:
> > - Fix typo in description about new target file for futex.c code
> > - Indent block with build log output
> >
> > Documentation/kernel-hacking/locking.rst | 2 +-
> > Documentation/translations/it_IT/kernel-hacking/locking.rst | 2 +-
> > 2 files changed, 2 insertions(+), 2 deletions(-)
>
> <formletter>
>
> This is not the correct way to submit patches for inclusion in the
> stable kernel tree. Please read:
> https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
> for how to do this properly.
Oops, nope, this was sent just fine, my bot got it wrong, sorry for the
noise...
prev parent reply other threads:[~2023-04-22 5:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 22:17 [PATCH v2 stable-5.10.y stable-5.15.y] docs: futex: Fix kernel-doc references after code split-up preparation Salvatore Bonaccorso
2023-04-22 0:03 ` Randy Dunlap
2023-04-22 7:02 ` Salvatore Bonaccorso
2023-04-22 5:44 ` Greg Kroah-Hartman
2023-04-22 5:46 ` Greg Kroah-Hartman [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=ZEN0x2Opg2dryAND@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andrealmeid@collabora.com \
--cc=carnil@debian.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).