linux-kernel - linux-next: manual merge of the drivers-x86 tree with the drivers-x86-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 for Android: free password hash cracker in your pocket

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

Date:   Wed, 29 Jun 2022 13:34:23 +1000
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Hans de Goede <hdegoede@...hat.com>,
        Mark Gross <markgross@...nel.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Mario Limonciello <mario.limonciello@....com>,
        Mark Pearson <markpearson@...ovo.com>
Subject: linux-next: manual merge of the drivers-x86 tree with the
 drivers-x86-fixes tree

Hi all,

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

  drivers/platform/x86/thinkpad_acpi.c

between commits:

  42504af77536 ("platform/x86: thinkpad-acpi: profile capabilities as integer")
  bce6243f767f ("platform/x86: thinkpad_acpi: do not use PSC mode on Intel platforms")

from the drivers-x86-fixes tree and commit:

  6fe391dd5d87 ("platform/x86: thinkpad-acpi: profile capabilities as integer")

from the drivers-x86 tree.

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