Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp3310962ybl; Mon, 19 Aug 2019 16:26:22 -0700 (PDT) X-Google-Smtp-Source: APXvYqzfcd6jUuRB/PaJMifJGCGVuviGtutn25h626HhWGChriNR1nhf0CjgHTZuf+Z425vUgGrn X-Received: by 2002:a65:6815:: with SMTP id l21mr22536066pgt.146.1566257182080; Mon, 19 Aug 2019 16:26:22 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566257182; cv=none; d=google.com; s=arc-20160816; b=hyarYHzCN2sgzRD25yqvr/FsrOrzKpUfPWI/wEU3/QrvyX66zcCKAaiOBeDFqcFaVA R61K1G0vLw32v3ZWeZwBumB8FSCzRs3rL0PLihgHLdlcIQY/6o4cfe0XoTw5ivcBn0nh I1J/p67XBnZ1lNyrio2aiB9yuEyVu9HvcUQtGpaewhdL1Fiy8dhlBN9U0gGyx9AxWm+I 2uQdGdS9xI5D3bu4e393z4YnjSiUqhv7TC/dbbYwAxpSU7SducL286Brj29yxpO8eQqP csAn12A3TQ/TDay93TrlnGYJKNnL4mzNNlEkDfsrbBm8P8LFV/18Oaff5pLQ9JrTG4gM fe5Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:dkim-signature; bh=YJKtCk0kK5H2o7lvu23PoP1AFRf2kOuKe6FaNLpsT6k=; b=edD1yQAVLfZD6tpnE0GF8JJAR/s65fAhvFZrjc6Din7Z3449KtnF9XbqmjChcsDdSU nn/U6MGUt47qPtsFkBBrD0aERUwLTk6MAS5LI+U1mh39o+gIPN8lq4QmONKsYA21FFtU UPLDJQ1ZMQqvPQjEKmnUzE7fofIk8P2nlV6A3prA9EIKnuMP2O4ob9TbIJHmdLOha47g /AJDP5UTGiRkPko7Y/B3a9G46BSARQXhWHgX9ZuhN5xSE2v++SbHrjSvd0wCIgA0gASG CEKekEk4m/nz8AOT5AcCr2RTGJ8iEDH2exWzzO16mXxa68xKLni7fsl4eKZA/uh+L/Gg ipcQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@canb.auug.org.au header.s=201702 header.b=IzEbJi90; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b17si10607695pgw.519.2019.08.19.16.26.06; Mon, 19 Aug 2019 16:26:22 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@canb.auug.org.au header.s=201702 header.b=IzEbJi90; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728704AbfHSXZN (ORCPT + 99 others); Mon, 19 Aug 2019 19:25:13 -0400 Received: from bilbo.ozlabs.org ([203.11.71.1]:53375 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728469AbfHSXZN (ORCPT ); Mon, 19 Aug 2019 19:25:13 -0400 Received: from authenticated.ozlabs.org (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.ozlabs.org (Postfix) with ESMTPSA id 46C9515zkbz9s4Y; Tue, 20 Aug 2019 09:25:09 +1000 (AEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=canb.auug.org.au; s=201702; t=1566257110; bh=2Pj2jJiylfrbuLd4zpWI6NoNJ2SLOCH8y4D4yzyDP3k=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=IzEbJi90pYjw2vtblMHENm1cT4y3ae+y9hEpObKiTVS34tzl1C0BDXd27FHF4LWiZ UiMKrqcCD1s9WO93eEbbMGhXjZRmsyh63v81sGwrng24mizO2rtyILs5YY3pRp+ndU +X3+LmqQzLNzYV/9KpzRlq8FIRzH+lePNRfy2GJm4GM5qU2gEc2WnuCQcXU3Q6Dy3A /mM3PceTvqNDioL7mkZ1PZXfKo6tFbtxbdq27aH47bfWza1lPOlyd9VPFvTzHHcPmY TfMAWsRFS+5gzkYQn/LyNwFJKszSbColwa6x2xcjiVPYP9g9xzpT8HoxDnCJG0b6k2 /hwD92Y7EhvUg== Date: Tue, 20 Aug 2019 09:24:51 +1000 From: Stephen Rothwell To: Joe Perches Cc: Linus Torvalds , Julia Lawall , "Gustavo A. R. Silva" , LKML , clang-built-linux@googlegroups.com, Linux Next Mailing List Subject: Re: rfc: treewide scripted patch mechanism? (was: Re: [PATCH] Makefile: Convert -Wimplicit-fallthrough=3 to just -Wimplicit-fallthrough for clang)QUILT Message-ID: <20190820092451.791c85e5@canb.auug.org.au> In-Reply-To: References: <9c7a79b4d21aea52464d00c8fa4e4b92638560b6.camel@perches.com> <6a5f470c1375289908c37632572c4aa60d6486fa.camel@perches.com> <4398924f28a58fca296d101dae11e7accce80656.camel@perches.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/6d1c0JM9/Va=lL_uvs+h.TO"; protocol="application/pgp-signature"; micalg=pgp-sha256 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --Sig_/6d1c0JM9/Va=lL_uvs+h.TO Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hi Joe, Sorry for the slow response. On Fri, 16 Aug 2019 12:58:27 -0700 Joe Perches wrote: > > On Sat, 2019-08-10 at 13:33 -0700, Joe Perches wrote: > > On Sat, 2019-08-10 at 13:18 -0700, Joe Perches wrote: =20 > [] > > > There are classes of patches generated by scripts that have > > > no real mechanism to be applied today. > > >=20 > > > For instance: global coccinelle scripted changes to use stracpy > > > https://lore.kernel.org/lkml/alpine.DEB.2.21.1907251747560.2494@hadri= en/ > > >=20 > > > and trivial scripted changes to MAINTAINERS > > > https://lore.kernel.org/lkml/6482e6546dc328ec47b07dba9a78a9573ebb3e56= .camel@perches.com/ > > >=20 > > > that are basically impossible to be applied by anyone but you. > > >=20 > > > Otherwise there are hundreds of little micro patches most of > > > which would not otherwise be applied. > > >=20 > > > There should be some process available to get these treewide > > > or difficult to keep up-to-date and apply patches handled. > > >=20 > > > I believe these sorts of scripted patches should ideally > > > be handled immediately before an RC1 so other trees can be=20 > > > synchronized in the simplest way possible. =20 > >=20 > > Hey Stephen > >=20 > > Question for you about a possible -next process change. > >=20 > > Would it be reasonable to have some mechanism to script > > treewide patches to generate and apply after Andrew Morton's > > mmotm patches are applied to -next? I don't see why not (its all just software, right? :-)). I would have to refresh my understanding of how Andrew constructs his mmot{s,m} quilt series, but I should be able to sort that out. The only other issue is the time it takes to apply these changes and test them. The total time it takes to construct linux-next each day increases towards the opening of the merge window (we are currently at -rc5 and I am already taking about 12 hours each day). > > This could allow treewide scripted patches to have > > compilation and test coverage before possibly being > > applied to Linus' tree. Always a good thing :-) So, do we have a pending example, or can you give my some idea of what they would look like? --=20 Cheers, Stephen Rothwell --Sig_/6d1c0JM9/Va=lL_uvs+h.TO Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEENIC96giZ81tWdLgKAVBC80lX0GwFAl1bL8MACgkQAVBC80lX 0GzJ6Qf+Ioda512r7v+ci6QP5Le/DVEAd4qcYSCE3ikVUruvXUyYdEps3FTuo/9y 50D9wjZjRTTLtjiCBdxLlymA4HyQj/NMBvshKn6g+fPBxH2yAc0IUHwz8UX2gAo4 DP7HtiYKvPB4pBG/yI+ppdwtWyzzVAKT6qXc6bu4+baCXt2h/I5xhJndFYp+QoFN SQagyZ8AbKDBC7fENxxZe6ysgBqYM+1JFcoBP7/hgP5vI+6FF/ofFReT5LgPKzRX YWSB7NIeeEFoxGraRUYGLeJZQz1uo3ur3jpU5qGOhVasLgkc8y2ZhIJrvlzjKoxZ VhBBvqbUHNKF6gyI9Li+gwFmYsMQGQ== =14Og -----END PGP SIGNATURE----- --Sig_/6d1c0JM9/Va=lL_uvs+h.TO--