linux-kernel - linux-next: manual merge of the staging tree with the v4l-dvb 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: <20170206153151.3e999469@canb.auug.org.au>
Date:   Mon, 6 Feb 2017 15:31:51 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Greg KH <greg@...ah.com>,
        Mauro Carvalho Chehab <mchehab@....samsung.com>
Cc:     linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
        Sean Young <sean@...s.org>,
        Sudip Mukherjee <sudip.mukherjee@...ethink.co.uk>
Subject: linux-next: manual merge of the staging tree with the v4l-dvb tree

Hi Greg,

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

  drivers/staging/media/lirc/lirc_parallel.c

between commit:

  2933974cbb03 ("[media] staging: lirc_parallel: remove")

from the v4l-dvb tree and commit:

  1c5fa1c7dbff ("staging: media: lirc: use new parport device model")

from the staging tree.

Unfortunate ...

I fixed it up (I removed the file) 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