From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from layka.disroot.org (layka.disroot.org [178.21.23.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 3C9861B5EB5; Wed, 3 Sep 2025 15:51:07 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=178.21.23.139 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1756914670; cv=none; b=bqT1OTH0VRdQpj9pCWh89S1Z3tpIR6nC9eSB33y8KbWWAEMJwgYdRgGtgDAd/GbbmAkdegcI1g9SXHeHy+lSzg0m5wykz9rr3p4t47q2D48ihNZnGMgljxPYvZrVHt2Dsp8lFuky62Ps+1H/5XWxYcCBrGLeoITq0N1nOQmZEWM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1756914670; c=relaxed/simple; bh=1f0F6PtJuoEuyJyHHkBr1BSyx6JzviX2TSn720qBm+8=; h=MIME-Version:Date:From:To:Cc:Subject:In-Reply-To:References: Message-ID:Content-Type; b=HJ14efPjVYqTEbQKED+Wwo33smTO93DxqPYao8mppqFGf1oX4kk37XK91OMZd+U7S/VRaEsn+XDMUQuRrdZHIihr9me+brHeItHsNtudx0qP4bhhlUYrEi80T33ixJdHpTEGZCsGFjuLHe2X2O8fnacW4xty5DZqyqnYcSHOxDQ= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=disroot.org; spf=pass smtp.mailfrom=disroot.org; dkim=pass (2048-bit key) header.d=disroot.org header.i=@disroot.org header.b=I9T5mzee; arc=none smtp.client-ip=178.21.23.139 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=disroot.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=disroot.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=disroot.org header.i=@disroot.org header.b="I9T5mzee" Received: from mail01.disroot.lan (localhost [127.0.0.1]) by disroot.org (Postfix) with ESMTP id 4B16E25D4D; Wed, 3 Sep 2025 17:51:05 +0200 (CEST) X-Virus-Scanned: SPAM Filter at disroot.org Received: from layka.disroot.org ([127.0.0.1]) by localhost (disroot.org [127.0.0.1]) (amavis, port 10024) with ESMTP id rXn3TEdJtINv; Wed, 3 Sep 2025 17:51:03 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=disroot.org; s=mail; t=1756914663; bh=1f0F6PtJuoEuyJyHHkBr1BSyx6JzviX2TSn720qBm+8=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=I9T5mzee7pqgMbTCrBgVvdFhYDFyhqkiwm+l5pzZOUoLgYLld2tmQla6y9ML2ZF5y xXxTfAY0Spe3WSnaSpyX97SKULTdoPOTkkzvc3gxO7BJjkRrKfXW7Oq8Ik32e5Jlyj dCmp/mt4cxunfDM7+LiZzjlVe/7WFjxloGRlxWhrB4H6UkjDftjAgHZsg9pOvaMLXf pUCQ4JW32dFGWM7NwZjJLyBSOxpdngtFq5pmlPOJmCCpHJLcqG5DRpT/EI0OQeQo4J 0buouFggPM15y7Ib7mohlK4V2kQE4DvWtN8M6FfuD4ZswgaOe9tnP9op0wrosy9lPe xzPBBqOLOiKBA== Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Date: Wed, 03 Sep 2025 15:51:03 +0000 From: Kaustabh Chakraborty To: Stephen Rothwell Cc: Inki Dae , Inki Dae , Linux Kernel Mailing List , Linux Next Mailing List , Dave Airlie , DRI Subject: Re: linux-next: build failure after merge of the drm-exynos tree In-Reply-To: <20250902130304.1f80f4c6@canb.auug.org.au> References: <20250821112740.75a41814@canb.auug.org.au> <20250826121320.4931c6eb@canb.auug.org.au> <20250901122226.20a39858@canb.auug.org.au> <20250902130304.1f80f4c6@canb.auug.org.au> Message-ID: <54f68544fa192779e15b46257dd0bfb4@disroot.org> X-Sender: kauschluss@disroot.org Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit On 2025-09-02 03:03, Stephen Rothwell wrote: > Hi all, > > On Mon, 1 Sep 2025 12:22:26 +1000 Stephen Rothwell > wrote: >> >> On Tue, 26 Aug 2025 12:13:20 +1000 Stephen Rothwell >> wrote: >> > >> > On Thu, 21 Aug 2025 11:27:40 +1000 Stephen Rothwell wrote: >> > > >> > > After merging the drm-exynos tree, today's linux-next build (arm >> > > multi_v7_defconfig) failed like this: >> > > >> > > drivers/gpu/drm/exynos/exynos_drm_dsi.c:158:20: error: 'DSIM_TYPE_EXYNOS7870' undeclared here (not in a function); did you mean 'DSIM_TYPE_EXYNOS5410'? >> > > 158 | .hw_type = DSIM_TYPE_EXYNOS7870, >> > > | ^~~~~~~~~~~~~~~~~~~~ >> > > | DSIM_TYPE_EXYNOS5410 >> > > >> > > Caused by commit >> > > >> > > d07e4c00696f ("drm/exynos: dsi: add support for exynos7870") >> > > >> > > I have used the drm-exynos tree from next-20250820 for today. >> > >> > I am still seeing this failure. >> >> I am still seeing this failure. > > Today, I have just reverted that commit instead of the whole branch, Hi, sorry for the late reply. This commit is from commit [1] of branch [2]. However, the macro is defined in commit [3] of branch [4]. I had sent those patches in a single patchset, though. I guess the merge strategy would be exynos-drm-misc-next, followed by exynos-drm-next. Let me know if you need to know anything else. Thanks! [1] https://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git/commit/?h=exynos-drm-next&id=d07e4c00696f53510ec8a23dcba0c4ac87840874 [2] https://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git/log/?h=exynos-drm-next [3] https://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git/commit/?h=exynos-drm-misc-next&id=bcd0d93e902e54e6b404b574b3a6b23315bcea8d [4] https://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-exynos.git/log/?h=exynos-drm-misc-next > > -- > Cheers, > Stephen Rothwell