From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Fernando Luis Vazquez Cao <fernando_b1@lab.ntt.co.jp>
Cc: Michael Kerrisk <mtk.manpages@gmail.com>,
linux-man@vger.kernel.org, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org,
Patrick McHardy <kaber@trash.net>,
Hirotaka Sasaki <sasaki.hirotaka@lab.ntt.co.jp>
Subject: Re: [PATCH 1/2] man/send(2): add EPERM to the list of possible errors
Date: Tue, 26 Mar 2013 11:48:33 +0100 [thread overview]
Message-ID: <20130326104833.GA5331@localhost> (raw)
In-Reply-To: <51515E5E.7020309@lab.ntt.co.jp>
On Tue, Mar 26, 2013 at 05:37:50PM +0900, Fernando Luis Vazquez Cao wrote:
> Hi Michael,
>
> Do you see any problem with these two patches?
Please, hold on with the second patch.
I'd like to find a possible solution for the EPERM problem that we've
been discussing. It requires some rework and performance evaluation.
next prev parent reply other threads:[~2013-03-26 10:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 6:45 [PATCH 1/2] man/send(2): add EPERM to the list of possible errors Fernando Luis Vázquez Cao
2013-03-19 6:52 ` [PATCH 2/2] man/send(2): document a long standing bug that can cause spurious EPERM errors Fernando Luis Vázquez Cao
2013-03-19 10:12 ` Pablo Neira Ayuso
2013-03-21 5:07 ` Fernando Luis Vazquez Cao
2013-03-26 8:37 ` [PATCH 1/2] man/send(2): add EPERM to the list of possible errors Fernando Luis Vazquez Cao
2013-03-26 10:48 ` Pablo Neira Ayuso [this message]
2013-03-27 4:14 ` Fernando Luis Vazquez Cao
2013-03-27 17:51 ` Pablo Neira Ayuso
2013-03-28 5:37 ` Fernando Luis Vazquez Cao
2013-03-27 17:42 ` Pablo Neira Ayuso
2013-03-28 2:46 ` Fernando Luis Vazquez Cao
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=20130326104833.GA5331@localhost \
--to=pablo@netfilter.org \
--cc=fernando_b1@lab.ntt.co.jp \
--cc=kaber@trash.net \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=sasaki.hirotaka@lab.ntt.co.jp \
/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).