[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210311135152.GT701493@dell>
Date: Thu, 11 Mar 2021 13:51:52 +0000
From: Lee Jones <lee.jones@...aro.org>
To: 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>,
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 Thu, 11 Mar 2021, Daniel Vetter wrote:
> 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.
Oh, I see. Well so long as they don't get dropped, I'll be happy.
Thanks for the explanation Daniel
--
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog
Powered by blists - more mailing lists