From: Nathan Chancellor <natechancellor@gmail.com>
To: Nick Desaulniers <ndesaulniers@google.com>, g@archlinux-ryzen
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
Jon Flatley <jflat@chromium.org>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Michal Marek <michal.lkml@markovi.net>
Subject: Re: [PATCH] kbuild, LLVMLinux: Don't suppress format warnings
Date: Wed, 6 Feb 2019 17:37:12 -0700 [thread overview]
Message-ID: <20190207003712.GA10692@archlinux-ryzen> (raw)
In-Reply-To: <CAKwvOdk4cT=Ay2Xk4hYo4-x8=4ng9gF5rF=5RsV-Rp=q5UFNtg@mail.gmail.com>
On Wed, Feb 06, 2019 at 04:30:21PM -0800, Nick Desaulniers wrote:
> On Wed, Feb 6, 2019 at 4:28 PM Masahiro Yamada
> <yamada.masahiro@socionext.com> wrote:
> > BTW, it would be nice if kbuild test robot
> > could test building with clang ...
>
> Is "kbuild test robot" different than 0day, kernelCI, or ClangBuiltLinux's CI?
> --
> Thanks,
> ~Nick Desaulniers
kbuild test robot is 0day (that's the name the emails come under when
reporting issues).
Nathan
next prev parent reply other threads:[~2019-02-07 0:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-01 21:08 [PATCH] kbuild, LLVMLinux: Don't suppress format warnings jflat
2019-02-05 8:26 ` Masahiro Yamada
2019-02-06 16:45 ` Nathan Chancellor
2019-02-06 17:32 ` Jon Flatley
2019-02-06 17:36 ` Nick Desaulniers
2019-02-06 17:43 ` Nathan Chancellor
2019-02-07 0:24 ` Masahiro Yamada
2019-02-07 0:27 ` Masahiro Yamada
2019-02-07 0:30 ` Nick Desaulniers
2019-02-07 0:37 ` Nathan Chancellor [this message]
2019-02-07 0:40 ` Nick Desaulniers
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=20190207003712.GA10692@archlinux-ryzen \
--to=natechancellor@gmail.com \
--cc=g@archlinux-ryzen \
--cc=jflat@chromium.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=ndesaulniers@google.com \
--cc=yamada.masahiro@socionext.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