From: Joe Perches <joe@perches.com>
To: Tom Rix <trix@redhat.com>,
Nick Desaulniers <ndesaulniers@google.com>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: LKML <linux-kernel@vger.kernel.org>,
clang-built-linux <clang-built-linux@googlegroups.com>,
linux-toolchains@vger.kernel.org, Julia.Lawall@lip6.fr,
Linus Torvalds <torvalds@linux-foundation.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Nathan Huckleberry <nhuck15@gmail.com>
Subject: Re: Subject: [RFC] clang tooling cleanups
Date: Tue, 27 Oct 2020 14:34:51 -0700 [thread overview]
Message-ID: <df5ec26c2d219d204eaac445571bc92de3f18e21.camel@perches.com> (raw)
In-Reply-To: <cfad533d-1a9e-cf01-cefe-47c23de27a33@redhat.com>
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.
next prev parent reply other threads:[~2020-10-27 21:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201027164255.1573301-1-trix@redhat.com>
2020-10-27 18:42 ` Subject: [RFC] clang tooling cleanups Nick Desaulniers
2020-10-27 19:33 ` Tom Rix
2020-10-27 19:51 ` Joe Perches
2020-10-27 20:50 ` Nick Desaulniers
2020-10-27 21:21 ` Tom Rix
2020-10-27 21:09 ` Tom Rix
2020-10-27 21:34 ` Joe Perches [this message]
2020-10-27 19:39 ` Linus Torvalds
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=df5ec26c2d219d204eaac445571bc92de3f18e21.camel@perches.com \
--to=joe@perches.com \
--cc=Julia.Lawall@lip6.fr \
--cc=clang-built-linux@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-toolchains@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nhuck15@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
--cc=trix@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).