From: jani.nikula@linux.intel.com (Jani Nikula)
To: kernelnewbies@lists.kernelnewbies.org
Subject: clang warning: implicit conversion in intel_ddi.c:1481
Date: Fri, 02 Feb 2018 12:44:38 +0200 [thread overview]
Message-ID: <87h8qzisbt.fsf@intel.com> (raw)
In-Reply-To: <20180202100613.GA21492@kroah.com>
+Knut, Fengguang
On Fri, 02 Feb 2018, Greg KH <gregkh@linuxfoundation.org> wrote:
> - If clang now builds the kernel "cleanly", yes, I want to take
> warning fixes in the stable tree. And even better yet, if you
> keep working to ensure the tree is "clean", that would be
> wonderful.
So we can run sparse using 'make C=1' and friends, or other static
analysis tools using 'make CHECK=foo C=1', as long as the passed command
line params work. There was work by Knut to extend this make checker
stuff [1]. Since mixing different HOSTCC's in a single workdir seems
like a bad idea, I wonder how hard it would be to make clang work like
this:
$ make CHECK=clang C=1
Or using Knut's wrapper. Feels like that could increase the use of clang
for static analysis of patches.
BR,
Jani.
[1] http://mid.mail-archive.com/cover.5b56d020b8e826a7da33b1823c059acd0c123f8b.1515072782.git-series.knut.omang at oracle.com
--
Jani Nikula, Intel Open Source Technology Center
next prev parent reply other threads:[~2018-02-02 10:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 17:33 clang warning: implicit conversion in intel_ddi.c:1481 Ozan Alpay
2018-02-01 18:02 ` Greg KH
2018-02-01 19:27 ` Ozgur
2018-02-01 22:13 ` Lukas Bulwahn
2018-02-02 8:36 ` Jani Nikula
2018-02-02 9:56 ` Lukas Bulwahn
2018-02-02 10:06 ` Greg KH
2018-02-02 10:44 ` Jani Nikula [this message]
2018-02-02 11:04 ` Knut Omang
2018-02-02 13:13 ` Greg KH
2018-02-02 14:37 ` Jani Nikula
2018-02-02 15:50 ` Greg KH
2018-02-03 7:04 ` Knut Omang
2018-02-05 18:46 ` Ruben Safir
2018-02-02 14:33 ` Ruben Safir
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=87h8qzisbt.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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).