linux-kernel - Re: linux-next: build failure after merge of the drm-exynos tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250904075923.537b45bd@canb.auug.org.au>
Date: Thu, 4 Sep 2025 07:59:23 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Kaustabh Chakraborty <kauschluss@...root.org>
Cc: Inki Dae <daeinki@...il.com>, Inki Dae <inki.dae@...sung.com>, Linux
 Kernel Mailing List <linux-kernel@...r.kernel.org>, Linux Next Mailing List
 <linux-next@...r.kernel.org>, Dave Airlie <airlied@...hat.com>, DRI
 <dri-devel@...ts.freedesktop.org>
Subject: Re: linux-next: build failure after merge of the drm-exynos tree

Hi Kaustabh,

On Wed, 03 Sep 2025 15:51:03 +0000 Kaustabh Chakraborty <kauschluss@...root.org> wrote:
>
> 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

The problem is that nobody has ever asked me to merge [4] into
linux-next ... I also presume that it will be merged into the drm-fixes
tree (or Linus' tree) at some point and that hasn't happened either.

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped