From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [PATCH v6] batman-adv: Snoop DHCPACKs for DAT
Date: Wed, 29 Aug 2018 09:03:19 +0200 [thread overview]
Message-ID: <7877406.oIGdHSL0FI@bentobox> (raw)
In-Reply-To: <20180621162745.3408-1-linus.luessing@c0d3.blue>
[-- Attachment #1: Type: text/plain, Size: 395 bytes --]
On Donnerstag, 21. Juni 2018 18:27:45 CEST Linus Lüssing wrote:
[...]
> Changes in v6:
> * moved dhcp packet definition from batadv_packet.h to
> distributed-arp-table.c
It looks in patchwork like the new revision was completely ignored. But I am
waiting here for some statements from Antonio. This is also the reason why it
was assigned to him a while ago.
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-08-29 7:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 16:27 [B.A.T.M.A.N.] [PATCH v6] batman-adv: Snoop DHCPACKs for DAT Linus Lüssing
2018-08-29 7:03 ` Sven Eckelmann [this message]
2018-09-06 14:34 ` Antonio Quartulli
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=7877406.oIGdHSL0FI@bentobox \
--to=sven@narfation.org \
--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