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: 5+ 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-15 12:09 ` Boris Brezillon
2017-05-15 17:15 ` Jonathan Corbet [this message]
2017-05-16 7:01 ` Boris Brezillon
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=linux-security-module@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).