[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <df5ec26c2d219d204eaac445571bc92de3f18e21.camel@perches.com>
Date: Tue, 27 Oct 2020 14:34:51 -0700
From: Joe Perches <joe@...ches.com>
To: Tom Rix <trix@...hat.com>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Stephen Rothwell <sfr@...b.auug.org.au>
Cc: LKML <linux-kernel@...r.kernel.org>,
clang-built-linux <clang-built-linux@...glegroups.com>,
linux-toolchains@...r.kernel.org, Julia.Lawall@...6.fr,
Linus Torvalds <torvalds@...ux-foundation.org>,
Masahiro Yamada <masahiroy@...nel.org>,
Nathan Huckleberry <nhuck15@...il.com>
Subject: Re: Subject: [RFC] clang tooling cleanups
On Tue, 2020-10-27 at 14:09 -0700, Tom Rix wrote:
> On 10/27/20 12:51 PM, Joe Perches wrote:
[]
> > I hope a scripted patches mechanism will be established.
>
> I would be interested in this as well.
> I already have a repo tracking next.
> I can code up a script to do the commits.
> Then we can poke at it with sticks and see if hooking it into next is worthwhile.
I presume it will be worthwhile.
I hope the robot will run compilation and integration tests against
this -next plus additional scripted patches repo.
I also hope the time required before integration it into -next itself
is short as running the robot for all arches seems relatively expensive.
Powered by blists - more mailing lists