[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YEobySvG0zPs9xhc@phenom.ffwll.local>
Date: Thu, 11 Mar 2021 14:31:53 +0100
From: Daniel Vetter <daniel@...ll.ch>
To: Lee Jones <lee.jones@...aro.org>
Cc: Roland Scheidegger <sroland@...are.com>,
linux-kernel@...r.kernel.org,
Alex Deucher <alexander.deucher@....com>,
amd-gfx@...ts.freedesktop.org, Anthony Koo <Anthony.Koo@....com>,
Ben Skeggs <bskeggs@...hat.com>,
Christian König <christian.koenig@....com>,
Colin Ian King <colin.king@...onical.com>,
Daniel Vetter <daniel@...ll.ch>,
Dave Airlie <airlied@...hat.com>,
David Airlie <airlied@...ux.ie>,
dri-devel@...ts.freedesktop.org, freedreno@...ts.freedesktop.org,
Harry Wentland <harry.wentland@....com>,
Jeremy Kolb <jkolb@...ndeis.edu>,
Kuogee Hsieh <khsieh@...eaurora.org>,
Leo Li <sunpeng.li@....com>, linaro-mm-sig@...ts.linaro.org,
linux-arm-msm@...r.kernel.org, linux-media@...r.kernel.org,
Lyude Paul <lyude@...hat.com>,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>,
nouveau@...ts.freedesktop.org,
Qinglang Miao <miaoqinglang@...wei.com>,
Rob Clark <rob.clark@...aro.org>,
Rob Clark <robdclark@...il.com>, Sean Paul <sean@...rly.run>,
Sumit Semwal <sumit.semwal@...aro.org>,
Thomas Zimmermann <tzimmermann@...e.de>,
VMware Graphics <linux-graphics-maintainer@...are.com>,
Zack Rusin <zackr@...are.com>
Subject: Re: [RESEND 00/53] Rid GPU from W=1 warnings
On Mon, Mar 08, 2021 at 09:19:32AM +0000, Lee Jones wrote:
> On Fri, 05 Mar 2021, Roland Scheidegger wrote:
>
> > The vmwgfx ones look all good to me, so for
> > 23-53: Reviewed-by: Roland Scheidegger <sroland@...are.com>
> > That said, they were already signed off by Zack, so not sure what
> > happened here.
>
> Yes, they were accepted at one point, then dropped without a reason.
>
> Since I rebased onto the latest -next, I had to pluck them back out of
> a previous one.
They should show up in linux-next again. We merge patches for next merge
window even during the current merge window, but need to make sure they
don't pollute linux-next. Occasionally the cut off is wrong so patches
show up, and then get pulled again.
Unfortunately especially the 5.12 merge cycle was very wobbly due to some
confusion here. But your patches should all be in linux-next again (they
are queued up for 5.13 in drm-misc-next, I checked that).
Sorry for the confusion here.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
Powered by blists - more mailing lists