From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-doc-owner@vger.kernel.org>
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on
	aws-us-west-2-korg-lkml-1.web.codeaurora.org
Received: from vger.kernel.org (vger.kernel.org [23.128.96.18])
	by smtp.lore.kernel.org (Postfix) with ESMTP id 79C13C7618E
	for <linux-doc@archiver.kernel.org>; Sat, 22 Apr 2023 05:46:54 +0000 (UTC)
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S229669AbjDVFqx (ORCPT <rfc822;linux-doc@archiver.kernel.org>);
        Sat, 22 Apr 2023 01:46:53 -0400
Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56228 "EHLO
        lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S229504AbjDVFqw (ORCPT
        <rfc822;linux-doc@vger.kernel.org>); Sat, 22 Apr 2023 01:46:52 -0400
Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217])
        by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8B69D1BC6;
        Fri, 21 Apr 2023 22:46:51 -0700 (PDT)
Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140])
        (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
        (No client certificate requested)
        by dfw.source.kernel.org (Postfix) with ESMTPS id 248B6601BD;
        Sat, 22 Apr 2023 05:46:51 +0000 (UTC)
Received: by smtp.kernel.org (Postfix) with ESMTPSA id EEAD2C433D2;
        Sat, 22 Apr 2023 05:46:49 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org;
        s=korg; t=1682142410;
        bh=oXrfF0+q+OjmweaqDYxmuwSbcE5OLmEHWrKpfu2ytJg=;
        h=Date:From:To:Cc:Subject:References:In-Reply-To:From;
        b=kXRZ2UUdvtwzPVs+F0IUc48X2UkkWE32EzYqwwjX21BC1LywmY1B1bpc9x/mWM7Op
         TLXec2rcTmu2tBmjiY61XUpa/bSdvfYRzeg96zMmobr8SvmSbQ/GXYdcKGJ3cn26BE
         wDYS6BOmiwIlqaj0E+fhkk4fjH5LeUhkgj8ckeBU=
Date:   Sat, 22 Apr 2023 07:46:47 +0200
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>,
        =?iso-8859-1?Q?Andr=E9?= 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
Message-ID: <ZEN0x2Opg2dryAND@kroah.com>
References: <20230421221741.1827866-1-carnil@debian.org>
 <ZEN0MsKMQXTqGwk-@kroah.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <ZEN0MsKMQXTqGwk-@kroah.com>
Precedence: bulk
List-ID: <linux-doc.vger.kernel.org>
X-Mailing-List: linux-doc@vger.kernel.org

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...