From: Daniel Vetter <daniel@ffwll.ch>
To: Zack Rusin <zackr@vmware.com>
Cc: "David Airlie" <airlied@linux.ie>,
"nouveau@lists.freedesktop.org" <nouveau@lists.freedesktop.org>,
"DRI Development" <dri-devel@lists.freedesktop.org>,
"Eric Anholt" <eric@anholt.net>,
"Jesse Barnes" <jesse.barnes@intel.com>,
"Jan Safrata" <jan.nikitenko@gmail.com>,
"Lee Jones" <lee.jones@linaro.org>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Gareth Hughes" <gareth@valinux.com>,
"Pei Zhang" <pei.zhang@intel.com>,
"Rob Clark" <rob.clark@linaro.org>, "Min He" <min.he@intel.com>,
Linux-graphics-maintainer <Linux-graphics-maintainer@vmware.com>,
"Ben Skeggs" <bskeggs@redhat.com>,
"Dave Airlie" <airlied@redhat.com>,
"Niu Bing" <bing.niu@intel.com>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"jim liu" <jim.liu@intel.com>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Roland Scheidegger" <sroland@vmware.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"linaro-mm-sig@lists.linaro.org" <linaro-mm-sig@lists.linaro.org>,
"Maxime Ripard" <mripard@kernel.org>,
"intel-gvt-dev@lists.freedesktop.org"
<intel-gvt-dev@lists.freedesktop.org>,
"Eddie Dong" <eddie.dong@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Faith <faith@valinux.com>, "Ping Gao" <ping.a.gao@intel.com>,
"Christian König" <christian.koenig@amd.com>,
"Zhiyuan Lv" <zhiyuan.lv@intel.com>
Subject: Re: [Intel-gfx] [PATCH 00/29] [Set 15] Finally rid W=1 warnings from GPU!
Date: Mon, 18 Jan 2021 15:54:05 +0100 [thread overview]
Message-ID: <YAWhDRkSOHbJ+2Le@phenom.ffwll.local> (raw)
In-Reply-To: <F914D9B9-6DD4-4383-9F7C-8D09FBFE96CE@vmware.com>
On Fri, Jan 15, 2021 at 06:27:15PM +0000, Zack Rusin wrote:
>
> > On Jan 15, 2021, at 13:15, Lee Jones <lee.jones@linaro.org> wrote:
> >
> > This set is part of a larger effort attempting to clean-up W=1
> > kernel builds, which are currently overwhelmingly riddled with
> > niggly little warnings.
> >
> > Last set! All clean after this for; Arm, Arm64, PPC, MIPS and x86.
>
> Thanks! For all the vmwgfx bits:
> Reviewed-by: Zack Rusin <zackr@vmware.com>
Ok I merged everything except vmwgfx (that's for Zack) and i915/nouveau
(those generally go through other trees, pls holler if they're stuck).
Note that we have some build issue on some of the configs sfr uses, so drm
trees are still stuck on old versions in linux-next. Hopefully should get
resolved soon, the bugfix is in some subtree I've heard.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2021-01-18 14:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 18:15 [Intel-gfx] [PATCH 00/29] [Set 15] Finally rid W=1 warnings from GPU! Lee Jones
2021-01-15 18:15 ` [Intel-gfx] [PATCH 24/29] drm/i915/gvt/handlers: Remove kernel-doc formatting from non-kernel-doc header Lee Jones
2021-01-15 18:27 ` [Intel-gfx] [PATCH 00/29] [Set 15] Finally rid W=1 warnings from GPU! Zack Rusin
2021-01-18 9:49 ` Daniel Vetter
2021-01-18 14:54 ` Daniel Vetter [this message]
2021-01-18 15:09 ` Lee Jones
2021-01-18 17:21 ` Daniel Vetter
2021-01-19 8:29 ` Lee Jones
2021-01-19 19:27 ` Zack Rusin
2021-01-20 8:05 ` Lee Jones
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=YAWhDRkSOHbJ+2Le@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=Linux-graphics-maintainer@vmware.com \
--cc=airlied@linux.ie \
--cc=airlied@redhat.com \
--cc=bing.niu@intel.com \
--cc=bskeggs@redhat.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=eddie.dong@intel.com \
--cc=eric@anholt.net \
--cc=faith@valinux.com \
--cc=gareth@valinux.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=jan.nikitenko@gmail.com \
--cc=jesse.barnes@intel.com \
--cc=jim.liu@intel.com \
--cc=lee.jones@linaro.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=min.he@intel.com \
--cc=mripard@kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=pei.zhang@intel.com \
--cc=ping.a.gao@intel.com \
--cc=rob.clark@linaro.org \
--cc=sroland@vmware.com \
--cc=sumit.semwal@linaro.org \
--cc=tzimmermann@suse.de \
--cc=zackr@vmware.com \
--cc=zhiyuan.lv@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