LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: eliezer.tamir@linux.intel.com,
linux-man <linux-man@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
eliezer@tamir.org.il
Subject: Re: [PATCH v2] socket.7: add description for SO_BUSY_POLL
Date: Wed, 10 Jul 2013 20:57:16 +0200 [thread overview]
Message-ID: <CAKgNAkhk+K=t0fu12Q03wcp18JrNsudTpEYs4=XP8KF81918ZQ@mail.gmail.com> (raw)
In-Reply-To: <20130710.115215.1793423861402826221.davem@davemloft.net>
On Wed, Jul 10, 2013 at 8:52 PM, David Miller <davem@davemloft.net> wrote:
> From: Michael Kerrisk <mtk.manpages@gmail.com>
> Date: Wed, 10 Jul 2013 20:03:08 +0200
>
>> On 07/10/13 16:18, Eliezer Tamir wrote:
>>> Add description for the SO_BUSY_POLL socket option to the socket(7) manpage.
>>>
>>> v2
>>> fixed typos reported by Rasmus Villemoes
>>
>> Eliezer,
>>
>> What's the status of this feature. A quick grep seems to show
>> that the feature is not yet in mainline. What is the plan?
>
> It's in Linus's tree.
That doesn't appear to be the case. grepping current Linus Git for
SO_BUSY_POLL yields nada. What am I missing?
next prev parent reply other threads:[~2013-07-10 18:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-10 14:18 Eliezer Tamir
2013-07-10 18:03 ` Michael Kerrisk
2013-07-10 18:52 ` David Miller
2013-07-10 18:57 ` Michael Kerrisk (man-pages) [this message]
2013-07-10 19:01 ` David Miller
2013-07-10 18:56 ` Eliezer Tamir
2014-01-20 16:28 ` Michael Kerrisk (man-pages)
2014-01-20 17:28 ` Eliezer Tamir
2015-02-05 13:17 ` Michael Kerrisk (man-pages)
2015-02-05 17:48 ` Eliezer Tamir
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='CAKgNAkhk+K=t0fu12Q03wcp18JrNsudTpEYs4=XP8KF81918ZQ@mail.gmail.com' \
--to=mtk.manpages@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=eliezer.tamir@linux.intel.com \
--cc=eliezer@tamir.org.il \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--subject='Re: [PATCH v2] socket.7: add description for SO_BUSY_POLL' \
/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
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).