From: Jakub Kicinski <kuba@kernel.org>
To: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>,
David Airlie <airlied@gmail.com>
Cc: Nathan Chancellor <nathan@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Anatoliy Klymenko <anatoliy.klymenko@amd.com>,
dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel test robot <lkp@intel.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Daniel Vetter <daniel@ffwll.ch>,
Michal Simek <michal.simek@amd.com>
Subject: Re: [PATCH v3 0/2] Fix Kernel CI issues
Date: Fri, 17 May 2024 13:12:22 -0700 [thread overview]
Message-ID: <20240517131222.2f147cf9@kernel.org> (raw)
In-Reply-To: <2002d2b4-ab0c-4c35-9693-c2b82054262c@ideasonboard.com>
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?
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2024-05-17 20:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 19:27 [PATCH v3 0/2] Fix Kernel CI issues Anatoliy Klymenko
2024-04-26 19:27 ` [PATCH v3 1/2] drm: xlnx: zynqmp_dpsub: Fix few function comments Anatoliy Klymenko
2024-04-26 19:27 ` [PATCH v3 2/2] drm: xlnx: zynqmp_dpsub: Fix compilation error Anatoliy Klymenko
2024-04-27 7:48 ` [PATCH v3 0/2] Fix Kernel CI issues Tomi Valkeinen
2024-05-03 16:27 ` Nathan Chancellor
2024-05-03 17:25 ` Tomi Valkeinen
2024-05-17 20:12 ` Jakub Kicinski [this message]
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=20240517131222.2f147cf9@kernel.org \
--to=kuba@kernel.org \
--cc=airlied@gmail.com \
--cc=anatoliy.klymenko@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=michal.simek@amd.com \
--cc=mripard@kernel.org \
--cc=nathan@kernel.org \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=tzimmermann@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).