linux-kernel - linux-next: manual merge of the tegra tree with Linus' 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>] [day] [month] [year] [list]

Message-ID: <20251117092011.2993febb@canb.auug.org.au>
Date: Mon, 17 Nov 2025 09:20:11 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Colin Cross <ccross@...roid.com>, Thierry Reding <treding@...dia.com>
Cc: Jon Hunter <jonathanh@...dia.com>, Linux Kernel Mailing List
 <linux-kernel@...r.kernel.org>, Linux Next Mailing List
 <linux-next@...r.kernel.org>, Theodore Ts'o <tytso@....edu>
Subject: linux-next: manual merge of the tegra tree with Linus' tree

Hi all,

Today's linux-next merge of the tegra tree got a conflict in:

  arch/arm/configs/tegra_defconfig

between commit:

  c065b6046b34 ("Use CONFIG_EXT4_FS instead of CONFIG_EXT3_FS in all of the defconfigs")

from Linus' tree and commit:

  23a29a81b44e ("ARM: tegra: Enable EXT4 for Tegra")

from the tegra tree.

I fixed it up (the latter included the former change) and can carry the
fix as necessary. This is now fixed as far as linux-next is concerned,
but any non trivial conflicts should be mentioned to your upstream
maintainer when your tree is submitted for merging.  You may also want
to consider cooperating with the maintainer of the conflicting tree to
minimise any particularly complex conflicts.

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped