From: Ozan Alpay <ozyalpy@gmail.com>
To: "Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: sil2review@lists.osadl.org, kernelnewbies@kernelnewbies.org,
David Airlie <airlied@linux.ie>,
intel-gfx@lists.freedesktop.org,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
llvmlinux@lists.linuxfoundation.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Jani Nikula <jani.nikula@linux.intel.com>,
lukas.bulwahn@gmail.com
Subject: clang warning: implicit conversion in intel_ddi.c:1481
Date: Thu, 1 Feb 2018 18:33:30 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1802011823340.4316@alpaca> (raw)
[-- Attachment #1: Type: text/plain, Size: 2045 bytes --]
Dear Rodrigo Vivi, Ville Syrjälä,
My name is Ozan Alpay, and I am a student mentored by Lukas Bulwahn. We
intend to use static analysis tools on the kernel source to identify,
analyze and report issues. As a very first step, we are looking into
clang compiler warnings and will then move to more sophisticated tools.
When compiling Linux 4.15 with clang, we have discovered that your commit
2952cd6fb4cc ("drm/i915: Let's use more enum intel_dpll_id pll_id.")
introduced the following warning:
drivers/gpu/drm/i915/intel_ddi.c:1481:30: warning: implicit conversion from enumeration type 'enum port' to different enumeration type 'enum intel_dpll_id' [-Wenum-conversion]
enum intel_dpll_id pll_id = port;
To reproduce it, you can compile Linux 4.15 with clang with this command:
make HOSTCC=clang-5.0 defconfig && make -j32 HOSTCC=clang-5.0 CC=clang-5.0
If you don't have clang installed in your system, you can use this simple
docker setup to compile the kernel with clang:
wget https://raw.githubusercontent.com/bulwahn/linux-kernel-analysis/master/docker/kernel-clang/Dockerfile && \
docker build -t kernel-clang . && \
docker run -v <your kernel source directory>:/linux/ kernel-clang /bin/sh -c "cd linux && make CC=clang-5.0 clean && make HOSTCC=clang-5.0 defconfig && make -j32 HOSTCC=clang-5.0 CC=clang-5.0"
While we were doing our analysis on 4.15, we noticed that you already
resolved this warning on linux-next with your work in commit bb911536f07e
("drm/i915: Eliminate pll->state usage from bxt_calc_pll_link()"). So,
since it is resolved on linux-next and we expect that this commit will be
merged in the merge window for 4.16, there is probably nothing further to
do.
Linux 4.15 is shipped with this clang warning, but we don't see the
crucial need to provide a backport commit to the stable branch for 4.15.
We just wanted to inform you about our analysis of this clang warning.
Ultimately the final call if you would like to address this clang warning
in 4.15 is yours.
Best regards,
Ozan & Lukas
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next reply other threads:[~2018-02-01 17:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 17:33 Ozan Alpay [this message]
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
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=alpine.DEB.2.20.1802011823340.4316@alpaca \
--to=ozyalpy@gmail.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvmlinux@lists.linuxfoundation.org \
--cc=lukas.bulwahn@gmail.com \
--cc=rodrigo.vivi@intel.com \
--cc=sil2review@lists.osadl.org \
--cc=ville.syrjala@linux.intel.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
all inboxes | Powered by JetHome®