From: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
To: Jan Synacek <jsynacek@redhat.com>
Cc: netdev@vger.kernel.org, YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
Subject: Re: [PATCH 2/2] arping: Call usage() before limiting capabilities.
Date: Thu, 29 Nov 2012 03:18:18 +0900 [thread overview]
Message-ID: <50B6556A.6040700@linux-ipv6.org> (raw)
In-Reply-To: <1354018775-4966-2-git-send-email-jsynacek@redhat.com>
Jan Synacek wrote:
> Otherwise, running arping binary without the capabilities set results in printing
> warnings with the usage.
>
> Signed-off-by: Jan Synacek <jsynacek@redhat.com>
Fixed in different way. ping/ping6 has also been fixed.
Thank you.
--yoshfuji
next prev parent reply other threads:[~2012-11-28 18:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-27 12:19 [PATCH 1/2] arping: Fix finding of a default interface when no -I is specified Jan Synacek
2012-11-27 12:19 ` [PATCH 2/2] arping: Call usage() before limiting capabilities Jan Synacek
2012-11-28 18:18 ` YOSHIFUJI Hideaki [this message]
2012-11-28 18:38 ` [PATCH 1/2] arping: Fix finding of a default interface when no -I is specified YOSHIFUJI Hideaki
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=50B6556A.6040700@linux-ipv6.org \
--to=yoshfuji@linux-ipv6.org \
--cc=jsynacek@redhat.com \
--cc=netdev@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).