linux-kernel - Re: [PATCH 0/5] Convert more books to ReST

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]

Message-ID: <20170515111519.7bbb449b@lwn.net>
Date:   Mon, 15 May 2017 11:15:19 -0600
From:   Jonathan Corbet <corbet@....net>
To:     Boris Brezillon <boris.brezillon@...e-electrons.com>
Cc:     Mauro Carvalho Chehab <mchehab@...pensource.com>,
        Linux Doc Mailing List <linux-doc@...r.kernel.org>,
        Rich Felker <dalias@...c.org>, linux-sh@...r.kernel.org,
        Takashi Iwai <tiwai@...e.de>,
        Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
        "Herton R. Krzesinski" <herton@...hat.com>,
        linux-mtd@...ts.infradead.org,
        Cyrille Pitchen <cyrille.pitchen@...el.com>,
        Markus Heiser <markus.heiser@...marit.de>,
        Yoshinori Sato <ysato@...rs.sourceforge.jp>,
        Richard Weinberger <richard@....at>,
        Marek Vasut <marek.vasut@...il.com>,
        sayli karnik <karniksayli1995@...il.com>,
        Jani Nikula <jani.nikula@...el.com>,
        Mauro Carvalho Chehab <mchehab@...radead.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        linux-kernel@...r.kernel.org,
        linux-security-module@...r.kernel.org,
        Silvio Fricke <silvio.fricke@...il.com>,
        Brian Norris <computersforpeace@...il.com>,
        David Woodhouse <dwmw2@...radead.org>
Subject: Re: [PATCH 0/5] Convert more books to ReST

On Mon, 15 May 2017 14:09:12 +0200
Boris Brezillon <boris.brezillon@...e-electrons.com> wrote:

> >   mtd: adjust kernel-docs to avoid Sphinx/kerneldoc warnings  
> 
> Not sure how you plan to merge these changes, but if it goes through
> a single tree I'll probably need an immutable topic branch, because I
> plan to change a few things in nand_base.c nand.h for the next release.

docs-next doesn't rebase, so there shouldn't be trouble there.  But we
could also just separate this patch into two pieces.  I suspect we could
live with a couple of warnings for a period during the 4.13 merge window
without too much pain...

jon