public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	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: Wed, 18 Oct 2017 09:27:01 -0700	[thread overview]
Message-ID: <20171018162700.GI3521@linux.vnet.ibm.com> (raw)
In-Reply-To: <20171018100340.7f34aace@lwn.net>

On Wed, Oct 18, 2017 at 10:03:40AM -0600, Jonathan Corbet wrote:
> On Mon, 16 Oct 2017 13:26:19 -0700
> "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> wrote:
> 
> > OK, how about if I submit them to the 4.15 merge window, but add the
> > appropriate -stable tags to get them backported?  Yes, these are bugs,
> > but I cannot in good conscience claim that they are v4.14 regressions.
> > 
> > But if Jon agrees with you, I will of course create a patch series,
> > pull request, or whatever and send it along to him.
> 
> [Sorry for being slow ... $EXCUSES ... ]
> 
> One could argue that they are indeed a regression; they introduced a bunch
> of build errors into 4.14.  I think it would be better to see it fixed if
> possible.  I don't care that much about how it gets there; Paul, I can
> send it Linusward if you don't want to.

I never have pushed directly to Linus, so I might as well get started
doing so.

On a related topic...  Is there anything that test-builds docbook prior
to patches hitting mainline?  My experience indicates that the answer is
"no".

							Thanx, Paul

  reply	other threads:[~2017-10-18 16:27 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-17  1:26 rcu kernel-doc issues (4.14-rc1) 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 [this message]
2017-10-18 16:36                     ` Jonathan Corbet
2017-10-20 16:42                       ` Paul E. McKenney
2017-10-20 16:53                         ` Randy Dunlap
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=20171018162700.GI3521@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.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