From: Nick Desaulniers <ndesaulniers@google.com>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: Nathan Chancellor <nathan@kernel.org>,
llvm@lists.linux.dev, Lukas Bulwahn <lukas.bulwahn@gmail.com>
Subject: Re: linux-next: Tree for Jul 14
Date: Thu, 14 Jul 2022 11:51:51 -0700 [thread overview]
Message-ID: <CAKwvOdmS2SugAzRSmQzWAmRgz642KEgTtOw5O3TvZwFSHU-fPQ@mail.gmail.com> (raw)
In-Reply-To: <CADVatmOTNA8uVqDEx6kp=+_O=wEhV2jbS9-frct-c4ZqBxcspg@mail.gmail.com>
(Moving Stephen, linux-next, and lkml to bcc)
On Thu, Jul 14, 2022 at 9:22 AM Sudip Mukherjee
<sudipm.mukherjee@gmail.com> wrote:
>
> Hi Nathan,
>
> On Thu, Jul 14, 2022 at 5:05 PM Nathan Chancellor <nathan@kernel.org> wrote:
> >
> > Hi Sudip,
> >
> >
> > In the future, consider CC'ing our mailing list (llvm@lists.linux.dev)
> > for any clang related issues so that we can get them taken care of ASAP,
> > we have a MAINTAINERS entry for a reason :) thank you for testing with
> > clang; the more people that use it, hopefully the easier it will be to
> > get things unbroken.
>
> Sure. I run arm, arm64, powerpc and x86_64 allmodconfigs with clang
> (along with gcc) every night for mainline, started with linux-next
> from today. Trying to setup the mips build also, I will mail llvm list
> asking for help with the mips build.
> Currently I only monitor the clang output from x86_64 as thats the one
> which builds. If you want I can send the other reports also.
Hi Sudip!
Right on, nice to hear from you. Consider filing bugs in our issue tracker
https://github.com/ClangBuiltLinux/linux/issues (consider taking a
peak to see which are already known issues and commenting on those
rather than filing new ones, time permitting), and joining our meeting
(next one in two weeks) see https://clangbuiltlinux.github.io/ for
calendar invite and meeting link.
> I have added Lukas if you both think
> it will be good to collaborate.
Ah, yeah, Lukas is an old friend. Hi Lukas!
--
Thanks,
~Nick Desaulniers
next prev parent reply other threads:[~2022-07-14 18:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 8:55 linux-next: Tree for Jul 14 Stephen Rothwell
2022-07-14 11:07 ` Sudip Mukherjee (Codethink)
2022-07-14 16:05 ` Nathan Chancellor
2022-07-14 16:21 ` Sudip Mukherjee
2022-07-14 16:29 ` Nathan Chancellor
2022-07-14 16:55 ` Sudip Mukherjee
2022-07-14 18:26 ` Sudip Mukherjee
2022-07-14 21:24 ` Nathan Chancellor
2022-07-15 22:06 ` Sudip Mukherjee
2022-07-17 22:05 ` Sudip Mukherjee
2022-07-14 18:51 ` Nick Desaulniers [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-14 4:15 Stephen Rothwell
2021-07-14 3:25 Stephen Rothwell
2020-07-14 10:03 Stephen Rothwell
2017-07-14 3:58 Stephen Rothwell
2016-07-14 6:18 Stephen Rothwell
2015-07-14 5:41 Stephen Rothwell
2014-07-14 7:17 Stephen Rothwell
2014-07-14 17:50 ` Nick Krause
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=CAKwvOdmS2SugAzRSmQzWAmRgz642KEgTtOw5O3TvZwFSHU-fPQ@mail.gmail.com \
--to=ndesaulniers@google.com \
--cc=llvm@lists.linux.dev \
--cc=lukas.bulwahn@gmail.com \
--cc=nathan@kernel.org \
--cc=sudipm.mukherjee@gmail.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 NNTP newsgroup(s).