From: Jonathan Corbet <corbet@lwn.net>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: linux-kernel@vger.kernel.org,
Greg KH <gregkh@linuxfoundation.org>,
Alan Cox <alan@linux.intel.com>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] Documentation: i2o: remove duplicate documentation
Date: Wed, 18 Mar 2015 15:26:34 -0600 [thread overview]
Message-ID: <20150318152634.7678124f@lwn.net> (raw)
In-Reply-To: <20150318212147.GA13170@katana>
On Wed, 18 Mar 2015 22:21:47 +0100
Wolfram Sang <wsa@the-dreams.de> wrote:
> Ping. For consistency, I'd think this would be nice in 4.0.
I have it in my pile of docs patches, should get to that before too long.
LSFMM kind of slowed everything down.
jon
next prev parent reply other threads:[~2015-03-18 21:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 10:07 [PATCH] Documentation: i2o: remove duplicate documentation Wolfram Sang
2015-03-18 21:21 ` Wolfram Sang
2015-03-18 21:26 ` Jonathan Corbet [this message]
2015-03-19 20:49 ` Jonathan Corbet
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=20150318152634.7678124f@lwn.net \
--to=corbet@lwn.net \
--cc=alan@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wsa@the-dreams.de \
/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).