From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 80B4BC433F5 for ; Thu, 24 Feb 2022 04:07:52 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 9612B8D0002; Wed, 23 Feb 2022 23:07:51 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 8E7C68D0001; Wed, 23 Feb 2022 23:07:51 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 789908D0002; Wed, 23 Feb 2022 23:07:51 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0099.hostedemail.com [216.40.44.99]) by kanga.kvack.org (Postfix) with ESMTP id 51B388D0001 for ; Wed, 23 Feb 2022 23:07:51 -0500 (EST) Received: from smtpin27.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay05.hostedemail.com (Postfix) with ESMTP id D4810181CCCA0 for ; Thu, 24 Feb 2022 04:07:50 +0000 (UTC) X-FDA: 79176339900.27.22BF121 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by imf27.hostedemail.com (Postfix) with ESMTP id 405DB40002 for ; Thu, 24 Feb 2022 04:07:50 +0000 (UTC) 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 1655061745; Thu, 24 Feb 2022 04:07:49 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 2FA19C340E9; Thu, 24 Feb 2022 04:07:48 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linux-foundation.org; s=korg; t=1645675668; bh=RXbuaGAWoYDu4/DJaRsCxnBFQVeV8135g45SZLFpu9E=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=Dqb2UagG8Z+ewkVnFDULM4ZF/u/BR6Jk76eBkwIgqbtRuFBmDSp8eTqTWu/bvduWv TfqIviA3mvIqX1Vt+DzQFLb450Kf1j5rXtZIYA61SeZDDffe6ez90vYY8Bx1v/BNQS LsR+4hFw3W7be3GHfOYn8BrBYd7LZb4Neppx/FVo= Date: Wed, 23 Feb 2022 20:07:47 -0800 From: Andrew Morton To: Marco Elver Cc: Peter Collingbourne , Miaohe Lin , Linux Memory Management List , Andrey Konovalov , kasan-dev , LKML , Sasha Levin Subject: Re: [PATCH] kasan: update function name in comments Message-Id: <20220223200747.2487235367d74255d8e13ba9@linux-foundation.org> In-Reply-To: References: <20220219012433.890941-1-pcc@google.com> <7a6afd53-a5c8-1be3-83cc-832596702401@huawei.com> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Authentication-Results: imf27.hostedemail.com; dkim=pass header.d=linux-foundation.org header.s=korg header.b=Dqb2UagG; dmarc=none; spf=pass (imf27.hostedemail.com: domain of akpm@linux-foundation.org designates 139.178.84.217 as permitted sender) smtp.mailfrom=akpm@linux-foundation.org X-Rspam-User: X-Rspamd-Server: rspam07 X-Rspamd-Queue-Id: 405DB40002 X-Stat-Signature: cazcke79r7cpp441w9cr8oem7j7iuj3w X-HE-Tag: 1645675670-638425 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Thu, 24 Feb 2022 00:35:32 +0100 Marco Elver wrote: > > I thought that Cc: stable@vger.kernel.org controlled whether the patch > > is to be taken to the stable kernel and Fixes: was more of an > > informational tag. At least that's what this seems to say: > > https://www.kernel.org/doc/html/latest/process/submitting-patches.html#reviewer-s-statement-of-oversight > > These days patches that just have a Fixes tag (and no Cc: stable) will > be auto-picked in many (most?) cases (by empirical observation). > > I think there were also tree-specific variances of this policy, but am > not sure anymore. What is the latest policy? The -stable maintainers have been asked not to do that for MM patches - to only take those which the developers (usually I) have explicitly tagged for backporting. I don't know how rigorously this is being followed. Probably OK for patches to mm/* but if it's drivers/base/node.c then heaven knows.