Received: by 2002:a05:6358:9144:b0:117:f937:c515 with SMTP id r4csp3162278rwr; Fri, 21 Apr 2023 23:21:28 -0700 (PDT) X-Google-Smtp-Source: AKy350YdEEq3qqK5lHOX6Bn74rK2xHGMuvPmmNlSbaEoFIENloWy6q9oBSADvTKGqkNa2WK9dZBJ X-Received: by 2002:a17:90a:194b:b0:247:9c7d:523a with SMTP id 11-20020a17090a194b00b002479c7d523amr6579042pjh.4.1682144488196; Fri, 21 Apr 2023 23:21:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1682144488; cv=none; d=google.com; s=arc-20160816; b=mg9yEGMOImbHZ5ZHwMehtPTpwdiYawh2fI+Ampa2mwv6amcdH209sQ6tZ1hWpv1ui+ wu96RbMRss5D6rTLKiBczHShAvJbXn2oAD4Lwnt4eiiT5uXFCiRcjS4ob9P0y+rv1Wwt qbN3EBy+djhJb5xGBlCTU8lUYhJjbU2fx3cNbgKA/ktVDRKrbrCS+M4GlFcpDPbapfKS ALzolbTqjiWaU8mqgSMDRE9yp/z6i/KwL3I/8GTDu2vbi0DDHyAbGylwIG19cxIctF34 Go4hSQFVLFBB/vlFEoNT7P19SZguHv2R/tYgRHUx2FGGiBYLYEjWRgENzitwO4DwwCp+ xeow== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=4gxsQEarYV8Rjpyo59FAUH42E7BhJdSoFruOyw8300E=; b=y+938Nvd6U/Ue3h+LznHrUxHSjvGukj1buG4w53D3YZJ0paiRCE1SlpryIH+CT1Z+R 9KiaHiNkygH4tL2GZ279LTZ3HzlMY+Jw800Vm7NCJJD659LZyZxSCcu3hDhLMD79RluS kfZXJAb1nPCzgmifHYyIxx0liAgZtEJbMYcPrXn8GsdwpXsRxcW0w/FNjl2ZpPQBuBTr G9oZ2m6leKNiqTuq/fJaZ7++irJNg+aOZTaCsbWOyiIj6CT0S8Ewp4ooLXQYuekFUtpe Lfxz7fwfM38/Fg1wHjoHJnsS8e0QIpn/NJxbLebeUa8XKQdqda2CiIsmSqDi7pC1MAS/ 0PmQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=kXRZ2UUd; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id b2-20020a17090a10c200b0024b289164c4si6107760pje.52.2023.04.21.23.21.16; Fri, 21 Apr 2023 23:21:28 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=kXRZ2UUd; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229677AbjDVFqy (ORCPT + 99 others); Sat, 22 Apr 2023 01:46:54 -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 ); 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 To: Salvatore Bonaccorso Cc: stable , Sasha Levin , Peter Zijlstra , Thomas Gleixner , =?iso-8859-1?Q?Andr=E9?= Almeida , linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, Jonathan Corbet 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: References: <20230421221741.1827866-1-carnil@debian.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-7.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@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 > > --- > > 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(-) > > > > 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...