From: Jason Gunthorpe <jgg@ziepe.ca>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: Nathan Chancellor <natechancellor@gmail.com>,
Bernard Metzler <BMT@zurich.ibm.com>,
Doug Ledford <dledford@redhat.com>,
linux-rdma@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
clang-built-linux <clang-built-linux@googlegroups.com>
Subject: Re: [PATCH] rdma/siw: Use proper enumerated type in map_cqe_status
Date: Thu, 11 Jul 2019 14:18:08 -0300 [thread overview]
Message-ID: <20190711171808.GF25807@ziepe.ca> (raw)
In-Reply-To: <CAKwvOdnHz3uH4ZM20LGQJ3FYhLQQUYn4Lg0B-YMr7Y1L66TAsA@mail.gmail.com>
On Thu, Jul 11, 2019 at 10:16:44AM -0700, Nick Desaulniers wrote:
> On Thu, Jul 11, 2019 at 6:39 AM Jason Gunthorpe <jgg@ziepe.ca> wrote:
> >
> > On Thu, Jul 11, 2019 at 01:14:34AM -0700, Nathan Chancellor wrote:
> > > Maybe time to start plumbing Clang into your test flow until it can get
> > > intergrated with more CI setups? :) It can catch some pretty dodgy
> > > behavior that GCC doesn't:
> >
> > I keep asking how to use clang to build the kernel and last I was told
> > it still wasn't ready..
> >
> > Is it ready now? Is there some flow that will compile with clang
> > warning free, on any arch? (at least the portion of the kernel I check)
>
> $ make CC=clang ...
>
> Let us know if you find something we haven't already.
> https://clangbuiltlinux.github.io/
> https://github.com/ClangBuiltLinux/linux/issues
What clang version?
Jason
next prev parent reply other threads:[~2019-07-11 17:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-10 17:48 [PATCH] rdma/siw: Use proper enumerated type in map_cqe_status Nathan Chancellor
2019-07-10 18:26 ` Jason Gunthorpe
2019-07-10 23:53 ` Nick Desaulniers
2019-07-11 3:02 ` Nathan Chancellor
2019-07-11 7:44 ` Bernard Metzler
2019-07-11 8:14 ` Nathan Chancellor
2019-07-11 13:39 ` Jason Gunthorpe
2019-07-11 17:16 ` Nick Desaulniers
2019-07-11 17:18 ` Jason Gunthorpe [this message]
2019-07-11 17:30 ` Nathan Chancellor
2019-08-23 14:24 ` Jason Gunthorpe
2019-08-26 15:38 ` Nathan Chancellor
2019-08-26 15:42 ` Jason Gunthorpe
2019-08-26 23:38 ` Nathan Chancellor
2019-08-27 15:08 ` Josh Poimboeuf
2019-08-27 17:00 ` Leon Romanovsky
2019-08-27 19:23 ` Josh Poimboeuf
2019-08-27 21:27 ` Nick Desaulniers
2019-08-27 22:50 ` 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=20190711171808.GF25807@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=BMT@zurich.ibm.com \
--cc=clang-built-linux@googlegroups.com \
--cc=dledford@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.