[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20240517131222.2f147cf9@kernel.org>
Date: Fri, 17 May 2024 13:12:22 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Tomi Valkeinen <tomi.valkeinen@...asonboard.com>, David Airlie
<airlied@...il.com>
Cc: Nathan Chancellor <nathan@...nel.org>, Thomas Zimmermann
<tzimmermann@...e.de>, Maarten Lankhorst
<maarten.lankhorst@...ux.intel.com>, Maxime Ripard <mripard@...nel.org>,
Anatoliy Klymenko <anatoliy.klymenko@....com>,
dri-devel@...ts.freedesktop.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, kernel test robot <lkp@...el.com>, Laurent
Pinchart <laurent.pinchart@...asonboard.com>, Daniel Vetter
<daniel@...ll.ch>, Michal Simek <michal.simek@....com>
Subject: Re: [PATCH v3 0/2] Fix Kernel CI issues
On Fri, 3 May 2024 20:25:49 +0300 Tomi Valkeinen wrote:
> > I think the second patch also needs to go to drm-misc-next-fixes? The
> > clang warning fixed by it has returned in next-20240503 because it
> > appears that for-linux-next was switch from drm-misc-next to
> > drm-misc-next-fixes, as I see for-linux-next was pointing to commit
> > 235e60653f8d ("drm/debugfs: Drop conditionals around of_node pointers")
> > on drm-misc-next in next-20240502 but it is now pointing to commit
> > be3f3042391d ("drm: zynqmp_dpsub: Always register bridge") on
> > drm-misc-next-fixes in next-20240503.
>
> Oh. Hmm, did I just hit the feature-freeze point with the fixes...
>
> Now I'm unsure where I should push these (if anywhere), as they already
> are in drm-misc-next.
>
> DRM Misc maintainers, can you give me a hint? =)
This is now breaking allmodconfig build of Linus's tree.
Could you please get it fixed ASAP?
Powered by blists - more mailing lists