linux-kernel - linux-next: manual merge of the amlogic tree with the pinctrl 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: <20160915101908.08f24fe1@canb.auug.org.au>
Date:   Thu, 15 Sep 2016 10:19:08 +1000
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Kevin Hilman <khilman@...libre.com>,
        Carlo Caione <carlo@...one.org>,
        Linus Walleij <linus.walleij@...aro.org>
Cc:     linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
        Deepak <deepak_das@...tor.com>
Subject: linux-next: manual merge of the amlogic tree with the pinctrl tree

Hi all,

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

  drivers/base/pinctrl.c

between commit:

  23b4ed268076 ("driver: base: pinctrl: return error from pinctrl_bind_pins()")

from the pinctrl tree and commit:

  eb4ec68acf5e ("driver: base: pinctrl: return error from pinctrl_bind_pins()")

from the amlogic tree.

I fixed it up (I used the version from the pinctrl tree) 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