From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: "Lukas Bulwahn" <lukas.bulwahn@gmail.com>,
"Greg KH" <greg@kroah.com>, "Ozan Alpay" <ozyalpy@gmail.com>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
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
Subject: Re: clang warning: implicit conversion in intel_ddi.c:1481
Date: Fri, 2 Feb 2018 10:56:36 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1802021054500.13838@hsp> (raw)
In-Reply-To: <87372jkcu5.fsf@intel.com>
On Fri, 2 Feb 2018, Jani Nikula wrote:
> Being brutally honest, please write shorter reports and shorter emails
> to the lists.
>
> The static analysis reports are welcome, but only when 1) we didn't
> already fix it in linux-next, or 2) it reveals an actual bug, not just a
> warning, warranting a backport.
That will be our policy.
Lukas
next prev parent reply other threads:[~2018-02-02 9:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 17:33 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 [this message]
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.1802021054500.13838@hsp \
--to=lukas.bulwahn@gmail.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=greg@kroah.com \
--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=ozyalpy@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®