linux-kernel - linux-next: manual merge of the mfd tree with the mfd-fixes 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: <20250620160345.48fd2d50@canb.auug.org.au>
Date: Fri, 20 Jun 2025 16:03:45 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Lee Jones <lee@...nel.org>
Cc: Abinash Singh <abinashlalotra@...il.com>, Abinash Singh
 <abinashsinghlalotra@...il.com>, Arnd Bergmann <arnd@...db.de>, Linux
 Kernel Mailing List <linux-kernel@...r.kernel.org>, Linux Next Mailing List
 <linux-next@...r.kernel.org>
Subject: linux-next: manual merge of the mfd tree with the mfd-fixes tree

Hi all,

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

  drivers/mfd/twl4030-irq.c

between commit:

  d9d79e4f7dc9 ("mfd: Fix building without CONFIG_OF")

from the mfd-fixes tree and commit:

  3d77b3cc7cc8 ("mfd: twl4030-irq: Remove redundant 'node' variable")

from the mfd tree.

I fixed it up (I just used the former) 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