From: Phil Sutter <phil@nwl.cc>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: Stephen Hemminger <shemming@brocade.com>, netdev@vger.kernel.org
Subject: Re: [iproute PATCH v2] ip{,6}tunnel: have a shared stats parser/printer
Date: Mon, 21 Dec 2015 20:36:58 +0100 [thread overview]
Message-ID: <20151221193533.9F13761201@mail.nwl.cc> (raw)
In-Reply-To: <5677DBB6.3070008@iogearbox.net>
On Mon, Dec 21, 2015 at 12:00:06PM +0100, Daniel Borkmann wrote:
> On 12/18/2015 11:58 AM, Phil Sutter wrote:
> > This has a slight side-effect of not aborting when /proc/net/dev is
> > malformed, but OTOH stats are not parsed for uninteresting interfaces.
> >
> > Signed-off-by: Phil Sutter <phil@nwl.cc>
> > ---
> > Changes since v1:
> > - Fix conflict resolution (sscan from 'buf' instead of 'ptr').
> [...]
>
> Hmm, did you actually compile that?
>
> The code is still the same as in v1 ... the only thing added is the "Changes since v1"
> description. ;)
Oh man. I certainly double-checked it, especially since I messed it up
the first time already. Quick forensics in my local clone revealed what
had happened:
1) Exported the V2 patch into a dedicated patch subdir.
2) ???
3) Edited the V1 patch in $TOPDIR and sent that out.
Face -> Desk.
Fix follows. :(
Thanks for reporting,
Phil
next prev parent reply other threads:[~2015-12-21 19:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 12:23 [iproute PATCH] ip{,6}tunnel: have a shared stats parser/printer Phil Sutter
2015-12-18 1:14 ` Stephen Hemminger
2015-12-18 10:52 ` Phil Sutter
2015-12-18 10:58 ` [iproute PATCH v2] " Phil Sutter
2015-12-18 19:47 ` Stephen Hemminger
2015-12-21 11:00 ` Daniel Borkmann
2015-12-21 19:36 ` Phil Sutter [this message]
2015-12-21 19:42 ` [iproute PATCH] iptunnel: Fix compile error in ip/tunnel.c Phil Sutter
2015-12-22 5:34 ` Stephen Hemminger
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=20151221193533.9F13761201@mail.nwl.cc \
--to=phil@nwl.cc \
--cc=daniel@iogearbox.net \
--cc=netdev@vger.kernel.org \
--cc=shemming@brocade.com \
/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).