From: Alan Cox <alan@linux.intel.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-next@vger.kernel.org
Subject: Re: make mandocs build failure with next-20150210
Date: Mon, 16 Feb 2015 19:39:42 +0000 [thread overview]
Message-ID: <1424115582.10724.86.camel@linux.intel.com> (raw)
In-Reply-To: <20150216122504.36620b6f@lwn.net>
On Mon, 2015-02-16 at 12:25 -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.
I sent it again when he said that. Oh well. Guess his email is turning
something with lots of <> into spamfilter fodder.
My patch matches yours
Alan
next prev parent reply other threads:[~2015-02-16 19:39 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 [this message]
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=1424115582.10724.86.camel@linux.intel.com \
--to=alan@linux.intel.com \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-next@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).