From: Jonathan Corbet <corbet@lwn.net>
To: Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: Mauro Carvalho Chehab <mchehab@s-opensource.com>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Rich Felker <dalias@libc.org>,
linux-sh@vger.kernel.org, Takashi Iwai <tiwai@suse.de>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
"Herton R. Krzesinski" <herton@redhat.com>,
linux-mtd@lists.infradead.org,
Cyrille Pitchen <cyrille.pitchen@atmel.com>,
Markus Heiser <markus.heiser@darmarit.de>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Richard Weinberger <richard@nod.at>,
Marek Vasut <marek.vasut@gmail.com>,
sayli karnik <karniksayli1995@gmail.com>,
Jani Nikula <jani.nikula@intel.com>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
Silvio Fricke <silvio.fricke@gmail.com>,
Brian Norris <computersforpeace@gmail.com>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH 0/5] Convert more books to ReST
Date: Mon, 15 May 2017 11:15:19 -0600 [thread overview]
Message-ID: <20170515111519.7bbb449b@lwn.net> (raw)
In-Reply-To: <20170515140912.100c9cac@bbrezillon>
On Mon, 15 May 2017 14:09:12 +0200
Boris Brezillon <boris.brezillon@free-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
WARNING: multiple messages have this Message-ID (diff)
From: Jonathan Corbet <corbet@lwn.net>
To: Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: Mauro Carvalho Chehab <mchehab@s-opensource.com>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Rich Felker <dalias@libc.org>,
linux-sh@vger.kernel.org, Takashi Iwai <tiwai@suse.de>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
"Herton R. Krzesinski" <herton@redhat.com>,
linux-mtd@lists.infradead.org,
Cyrille Pitchen <cyrille.pitchen@atmel.com>,
Markus Heiser <markus.heiser@darmarit.de>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Richard Weinberger <richard@nod.at>,
Marek Vasut <marek.vasut@gmail.com>,
sayli karnik <karniksayli1995@gmail.com>,
Jani Nikula <jani.nikula@intel.com>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
Silvio Fricke <silvio.fricke@gmail.com>,
Brian Norris <computersforpeace@gmail.com>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH 0/5] Convert more books to ReST
Date: Mon, 15 May 2017 17:15:19 +0000 [thread overview]
Message-ID: <20170515111519.7bbb449b@lwn.net> (raw)
In-Reply-To: <20170515140912.100c9cac@bbrezillon>
On Mon, 15 May 2017 14:09:12 +0200
Boris Brezillon <boris.brezillon@free-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
WARNING: multiple messages have this Message-ID (diff)
From: corbet@lwn.net (Jonathan Corbet)
To: linux-security-module@vger.kernel.org
Subject: [PATCH 0/5] Convert more books to ReST
Date: Mon, 15 May 2017 11:15:19 -0600 [thread overview]
Message-ID: <20170515111519.7bbb449b@lwn.net> (raw)
In-Reply-To: <20170515140912.100c9cac@bbrezillon>
On Mon, 15 May 2017 14:09:12 +0200
Boris Brezillon <boris.brezillon@free-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
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-05-15 17:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-13 11:10 [PATCH 0/5] Convert more books to ReST Mauro Carvalho Chehab
2017-05-13 11:10 ` Mauro Carvalho Chehab
2017-05-13 11:10 ` Mauro Carvalho Chehab
2017-05-13 11:10 ` [PATCH 1/5] docs-rst: convert librs book " Mauro Carvalho Chehab
2017-05-13 11:10 ` [PATCH 2/5] docs-rst: convert mtdnand " Mauro Carvalho Chehab
2017-05-13 11:10 ` [PATCH 3/5] mtdnand.rst: Fix some typos and group the "::" with previous line Mauro Carvalho Chehab
2017-05-13 11:10 ` [PATCH 4/5] mtd: adjust kernel-docs to avoid Sphinx/kerneldoc warnings Mauro Carvalho Chehab
2017-05-13 11:10 ` [PATCH 5/5] docs-rst: convert sh book to ReST Mauro Carvalho Chehab
2017-05-13 11:10 ` Mauro Carvalho Chehab
2017-05-15 12:09 ` [PATCH 0/5] Convert more books " Boris Brezillon
2017-05-15 12:09 ` Boris Brezillon
2017-05-15 12:09 ` Boris Brezillon
2017-05-15 17:15 ` Jonathan Corbet [this message]
2017-05-15 17:15 ` Jonathan Corbet
2017-05-15 17:15 ` Jonathan Corbet
2017-05-16 7:01 ` Boris Brezillon
2017-05-16 7:01 ` Boris Brezillon
2017-05-16 7:01 ` Boris Brezillon
2017-05-16 10:38 ` Mauro Carvalho Chehab
2017-05-16 10:38 ` Mauro Carvalho Chehab
2017-05-16 10:38 ` Mauro Carvalho Chehab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170515111519.7bbb449b@lwn.net \
--to=corbet@lwn.net \
--cc=bigeasy@linutronix.de \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@atmel.com \
--cc=dalias@libc.org \
--cc=dwmw2@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=herton@redhat.com \
--cc=jani.nikula@intel.com \
--cc=karniksayli1995@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-security-module@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=marek.vasut@gmail.com \
--cc=markus.heiser@darmarit.de \
--cc=mchehab@infradead.org \
--cc=mchehab@s-opensource.com \
--cc=richard@nod.at \
--cc=silvio.fricke@gmail.com \
--cc=tiwai@suse.de \
--cc=ysato@users.sourceforge.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.