From: Marek Lindner <mareklindner@neomailbox.ch>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [PATCH maint] batctl tcpdump: Fix reported length of TCP payload
Date: Wed, 25 Sep 2013 22:49:54 +0800 [thread overview]
Message-ID: <6575869.FX9F3cA1N1@diderot> (raw)
In-Reply-To: <1379775907-19199-1-git-send-email-marco.dallato@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 497 bytes --]
On Saturday 21 September 2013 17:05:07 Marco Dalla Torre wrote:
> Fixes the erratic report of TCP payload length in 'batctl tcpdump'.
> Previously TCP header length size was considered fixed, while
> this is actually not the case given the variable length (or no
> presence at all) of the options field.
>
> Signed-off-by: Marco Dalla Torre <marco.dallato@gmail.com>
> ---
> tcpdump.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
Applied in revision e374a3f.
Thanks,
Marek
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
prev parent reply other threads:[~2013-09-25 14:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-21 15:05 [B.A.T.M.A.N.] [PATCH maint] batctl tcpdump: Fix reported length of TCP payload Marco Dalla Torre
2013-09-25 14:49 ` Marek Lindner [this message]
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=6575869.FX9F3cA1N1@diderot \
--to=mareklindner@neomailbox.ch \
--cc=b.a.t.m.a.n@lists.open-mesh.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