linux-kernel - RE: linux-next: manual merge of the arm-soc 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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 27 May 2022 15:38:56 +0000
From:   "Hawkins, Nick" <nick.hawkins@....com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Olof Johansson <olof@...om.net>, Arnd Bergmann <arnd@...db.de>,
        ARM <linux-arm-kernel@...ts.infradead.org>
CC:     Geert Uytterhoeven <geert@...ux-m68k.org>,
        Laurent Vivier <laurent@...ier.eu>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: RE: linux-next: manual merge of the arm-soc tree with Linus' tree




> Today's linux-next merge of the arm-soc tree got a conflict in:

>   drivers/clocksource/Makefile

> between commit:

>   c92e7ef16400 ("clocksource/drivers: Add a goldfish-timer clocksource")

> from Linus' tree and commit:

>   5184f4bf151b ("clocksource/drivers/timer-gxp: Add HPE GXP Timer")

> from the arm-soc tree.

> I fixed it up (see below) 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.

Hi Stephen,

Thank you for resolving the merge issue. I am relatively new to this process.. Can you provide a link to where you were notified of the merge conflict?

-Nick Hawkins