From mboxrd@z Thu Jan 1 00:00:00 1970 From: Boris Brezillon Date: Tue, 16 May 2017 07:01:56 +0000 Subject: Re: [PATCH 0/5] Convert more books to ReST Message-Id: <20170516090156.47d55338@bbrezillon> List-Id: References: <20170515140912.100c9cac@bbrezillon> <20170515111519.7bbb449b@lwn.net> In-Reply-To: <20170515111519.7bbb449b@lwn.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Jonathan Corbet Cc: Rich Felker , linux-sh@vger.kernel.org, Takashi Iwai , Sebastian Andrzej Siewior , "Herton R. Krzesinski" , linux-mtd@lists.infradead.org, Cyrille Pitchen , Markus Heiser , Yoshinori Sato , Richard Weinberger , Linux Doc Mailing List , Mauro Carvalho Chehab , Marek Vasut , sayli karnik , Jani Nikula , Mauro Carvalho Chehab , Greg Kroah-Hartman , linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org, Silvio Fricke , Brian Norris , David Woodhouse Hi Jonathan, On Mon, 15 May 2017 11:15:19 -0600 Jonathan Corbet wrote: > On Mon, 15 May 2017 14:09:12 +0200 > Boris Brezillon 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... I like this idea. This way I can take the nand_base.c/nand.h changes through my tree and let you pick the Doc migration bits. Thanks, Boris