From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Alan Cox <alan@linux.intel.com>,
Masanari Iida <standby24x7@gmail.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Jim Davis <jim.epost@gmail.com>,
linux-next <linux-next@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-doc <linux-doc@vger.kernel.org>
Subject: Re: make mandocs build failure with next-20150210
Date: Mon, 16 Feb 2015 11:46:15 -0800 [thread overview]
Message-ID: <20150216194615.GA9933@kroah.com> (raw)
In-Reply-To: <20150216122504.36620b6f@lwn.net>
On Mon, Feb 16, 2015 at 12:25:04PM -0700, Jonathan Corbet wrote:
> On Mon, 16 Feb 2015 16:21:30 +0000
> Alan Cox <alan@linux.intel.com> wrote:
>
> > > This warning started to appear on Linus's tree, after staging pull
> > > request was merged.
> >
> > I sent GregKH a fix for it a while ago
>
> He seemed to indicate that he doesn't have it. The following would seem
> to fit the bill; unless somebody objects I'll send it upward so that docs
> builds start working again.
I got the second patch, but it was too late for my first round of
patches to send to Linus. Feel free to send this on yourself as I'm
going to be at a conference all this week and have limited time to do
this.
thanks,
greg k-h
next prev parent reply other threads:[~2015-02-16 19:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 18:40 make mandocs build failure with next-20150210 Jim Davis
2015-02-10 20:27 ` Stephen Rothwell
2015-02-11 14:19 ` Alan Cox
2015-02-11 15:48 ` Greg Kroah-Hartman
2015-02-16 2:29 ` Masanari Iida
2015-02-16 16:21 ` Alan Cox
2015-02-16 19:25 ` Jonathan Corbet
2015-02-16 19:39 ` Alan Cox
2015-02-16 19:46 ` Greg Kroah-Hartman [this message]
2015-02-16 19:46 ` Greg Kroah-Hartman
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=20150216194615.GA9933@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alan@linux.intel.com \
--cc=corbet@lwn.net \
--cc=jim.epost@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=standby24x7@gmail.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;
as well as URLs for NNTP newsgroup(s).