[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20171018162700.GI3521@linux.vnet.ibm.com>
Date: Wed, 18 Oct 2017 09:27:01 -0700
From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To: Jonathan Corbet <corbet@....net>
Cc: Randy Dunlap <rdunlap@...radead.org>,
LKML <linux-kernel@...r.kernel.org>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>
Subject: Re: rcu kernel-doc issues (4.14-rc1)
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@...ux.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
Powered by blists - more mailing lists