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

Message-ID: <20180315185917.3316d781@canb.auug.org.au>
Date:   Thu, 15 Mar 2018 18:59:17 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Alexandre Belloni <alexandre.belloni@...tlin.com>,
        Arnd Bergmann <arnd@...db.de>
Cc:     Linux-Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: linux-next: manual merge of the rtc tree with the asm-generic tree

Hi Alexandre,

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

  drivers/rtc/rtc-tile.c

between commit:

  909ce75a0665 ("rtc: remove tile driver")

from the asm-generic tree and commit:

  1fbcb2aa1d64 ("rtc: tile: remove useless message")

from the rtc 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.

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped