From: Alan Cox <alan@linux.intel.com>
To: Masanari Iida <standby24x7@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
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: Mon, 16 Feb 2015 16:21:30 +0000 [thread overview]
Message-ID: <1424103690.10724.62.camel@linux.intel.com> (raw)
In-Reply-To: <CALLJCT11o3CkhmsDF7nJxg-r0zoEaee4eScy9Xc5LVEg7Vg4Yg@mail.gmail.com>
On Mon, 2015-02-16 at 11:29 +0900, Masanari Iida wrote:
> On Thu, Feb 12, 2015 at 12:48 AM, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> > 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?
> >
>
> 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
next prev parent reply other threads:[~2015-02-16 16:21 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
2015-02-16 2:29 ` Masanari Iida
2015-02-16 16:21 ` Alan Cox [this message]
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=1424103690.10724.62.camel@linux.intel.com \
--to=alan@linux.intel.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--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