From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 7D50CC04FFE for ; Fri, 17 May 2024 20:12:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:References:In-Reply-To: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=gNMKOFo9YSPJdiKSWeBX8midBrkIWTSlS9lAH2mi4HU=; b=cqgI/kXPJdB1zE qlhn7y/XqUwrQjwFeqXEne5l6WMQvQSNFyJaaz72m/UAjaKPqqLlmwAQSLUh6+5xQbCeBAwgiygXI FOUr+qjKkvjsXtyOFkZ4XfoavsjGlK5BaBQ+UcesYyG9nMHyq+vN6SsQPVf6m76hsWBTzF8gzCvlO qtqd3SBD5vPKpns+AWZPTWKGFc3X63k8wG9nmDPZ2y1xeQwMV4tZjWqEyLTL1iQs7CGrCsDvPm4EN iH4zSZcgNGQ8H2TBI3j8P+wL+zeyGPWGlSyT5qJGSSglfKDk8IijLrbDRg1nn4PjRsGsWnbIFaL8+ 0xodf6g7u/BjrZ7uCdsw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1s83wL-00000008us4-0fY9; Fri, 17 May 2024 20:12:29 +0000 Received: from dfw.source.kernel.org ([139.178.84.217]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1s83wH-00000008ure-3ITC for linux-arm-kernel@lists.infradead.org; Fri, 17 May 2024 20:12:27 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by dfw.source.kernel.org (Postfix) with ESMTP id 7209161E2A; Fri, 17 May 2024 20:12:24 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 81D93C32782; Fri, 17 May 2024 20:12:23 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1715976744; bh=S8uwpeLZ+ub2Pr8pjfgM4+SSbXbFNBtJ2z2gFUGvxh8=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=Ur9I/fdOwlQftj39+BLRaZvYz/EKKieyZqNSdOFkj1wv6eHn3qYhFQwVO8VNg0fy1 K7nLW4pt6Upyaz9lVmzGI0pELPdiicDSf8kcjqWvvJFX22MqEEtIUmSSj+VuLAXdb5 /h3dY/0lQlMb8FQOd9fYA2Dd73Q+sCLsyTTyNxUXSm4PhzG6/jG49d9OMVsI60dQsz 5/8/mexdS6A2hqg0GrR5lQojsRfpYbnssOcP6//KL2G9fk+BvQsODdxddqjaHzGmbM NFKhiUmkAwDb3rjvZaitpuhY9ST5/AuU47sYn+Eoft18j+q2SqMMJEMzOxZQmd6rXO xchTC4RlyUytQ== Date: Fri, 17 May 2024 13:12:22 -0700 From: Jakub Kicinski To: Tomi Valkeinen , David Airlie Cc: Nathan Chancellor , Thomas Zimmermann , Maarten Lankhorst , Maxime Ripard , Anatoliy Klymenko , dri-devel@lists.freedesktop.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, kernel test robot , Laurent Pinchart , Daniel Vetter , Michal Simek Subject: Re: [PATCH v3 0/2] Fix Kernel CI issues Message-ID: <20240517131222.2f147cf9@kernel.org> In-Reply-To: <2002d2b4-ab0c-4c35-9693-c2b82054262c@ideasonboard.com> References: <20240426-dp-live-fmt-fix-v3-0-e904b5ae51d7@amd.com> <2a14d8ff-a8f5-4ebe-9f0e-a5554b417f0c@ideasonboard.com> <20240503162733.GA4136865@thelio-3990X> <2002d2b4-ab0c-4c35-9693-c2b82054262c@ideasonboard.com> MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240517_131225_908809_125261F5 X-CRM114-Status: GOOD ( 14.81 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org 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