From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Alan Cox <alan@linux.intel.com>
Cc: 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>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc <linux-doc@vger.kernel.org>
Subject: Re: make mandocs build failure with next-20150210
Date: Wed, 11 Feb 2015 23:48:44 +0800 [thread overview]
Message-ID: <20150211154844.GA18637@kroah.com> (raw)
In-Reply-To: <1423664340.10724.40.camel@linux.intel.com>
On Wed, Feb 11, 2015 at 02:19:00PM +0000, Alan Cox wrote:
> On Wed, 2015-02-11 at 07:27 +1100, Stephen Rothwell wrote:
> > Hi Jim,
> >
> > On Tue, 10 Feb 2015 11:40:23 -0700 Jim Davis <jim.epost@gmail.com> wrote:
> > >
> > > DOCPROC Documentation/DocBook/device-drivers.xml
> > > docproc: .//include/linux/i2o.h: No such file or directory
> > > make[1]: *** [Documentation/DocBook/device-drivers.xml] Error 1
> >
> > Presumably caused by commit 2cbf7fe2d5d3 ("i2o: move to staging") from
> > the staging tree.
>
> Yep - I sent GregKH a fix.
You did? Did I apply it? I don't see it in my to-apply queue
anywhere...
Care to resend?
thanks,
greg k-h
next prev parent reply other threads:[~2015-02-11 15:48 UTC|newest]
Thread overview: 9+ 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 [this message]
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:46 ` Greg Kroah-Hartman
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=20150211154844.GA18637@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 \
/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