From: Randy Dunlap <rdunlap@infradead.org>
To: paulmck@linux.vnet.ibm.com, Jonathan Corbet <corbet@lwn.net>
Cc: LKML <linux-kernel@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Subject: Re: rcu kernel-doc issues (4.14-rc1)
Date: Fri, 20 Oct 2017 09:53:30 -0700 [thread overview]
Message-ID: <f8a88d0b-47f7-24ff-cdae-4828df8e1d7c@infradead.org> (raw)
In-Reply-To: <20171020164254.GJ3521@linux.vnet.ibm.com>
On 10/20/17 09:42, Paul E. McKenney wrote:
> On Wed, Oct 18, 2017 at 10:36:47AM -0600, Jonathan Corbet wrote:
>> On Wed, 18 Oct 2017 09:27:01 -0700
>> "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> wrote:
>>
>>> On a related topic... Is there anything that test-builds docbook prior
>>> to patches hitting mainline? My experience indicates that the answer is
>>> "no".
>>
>> The zero-day robot is said to be testing for new doc-build errors, but I
>> haven't actually seen much of that.
>
> Well, on the good side, Linus did take the fixes. I will leave it
> to you guys to sort things as needed with Fengguang. ;-)
Thanks.
--
~Randy
next prev parent reply other threads:[~2017-10-20 16:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-17 1:26 Randy Dunlap
2017-09-17 4:41 ` Paul E. McKenney
2017-09-17 17:47 ` Paul E. McKenney
2017-09-17 17:57 ` Randy Dunlap
2017-09-17 19:49 ` Paul E. McKenney
2017-09-18 2:40 ` Paul E. McKenney
2017-09-18 7:30 ` Markus Heiser
2017-09-18 14:21 ` Paul E. McKenney
2017-10-16 19:58 ` Randy Dunlap
2017-10-16 20:07 ` Paul E. McKenney
2017-10-16 20:18 ` Randy Dunlap
2017-10-16 20:26 ` Paul E. McKenney
2017-10-16 21:46 ` Randy Dunlap
2017-10-16 23:35 ` Paul E. McKenney
2017-10-18 16:03 ` Jonathan Corbet
2017-10-18 16:27 ` Paul E. McKenney
2017-10-18 16:36 ` Jonathan Corbet
2017-10-20 16:42 ` Paul E. McKenney
2017-10-20 16:53 ` Randy Dunlap [this message]
2017-09-18 6:43 ` Markus Heiser
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=f8a88d0b-47f7-24ff-cdae-4828df8e1d7c@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
/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
all inboxes | Powered by JetHome®