linux-kernel - Re: linux-next: manual merge of the nand tree with the jc

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] [day] [month] [year] [list]

Date:   Tue, 30 May 2017 09:21:37 +0200
From:   Boris Brezillon <boris.brezillon@...e-electrons.com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Jonathan Corbet <corbet@....net>,
        Linux-Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Mauro Carvalho Chehab <mchehab@...pensource.com>
Subject: Re: linux-next: manual merge of the nand tree with the jc_docs tree

Hi Stephen,

On Tue, 30 May 2017 11:37:23 +1000
Stephen Rothwell <sfr@...b.auug.org.au> wrote:

> Hi Boris,
> 
> Today's linux-next merge of the nand tree got a conflict in:
> 
>   drivers/mtd/nand/nand_base.c
> 
> between commit:
> 
>   b6f6c29454d2 ("mtd: adjust kernel-docs to avoid Sphinx/kerneldoc warnings")
> 
> from the jc_docs tree and commit:
> 
>   c79d63fd272c ("mtd: nand: Remove support for block locking/unlocking")
> 
> from the nand tree.
> 
> I fixed it up (the latter just removed the code modified by the former,
> so I did that) 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.

I just dropped commit c79d63fd272c from my nand/next branch. I'll queue
it for the next release.

Thanks,

Boris