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 v3 maint] batman-adv: Fix TT sync flags for intermediate TT responses
Date: Fri, 11 May 2018 08:13:09 +0200 [thread overview]
Message-ID: <4477321.n6vKnkidQF@sven-edge> (raw)
In-Reply-To: <20180510174428.8646-1-linus.luessing@c0d3.blue>
[-- Attachment #1: Type: text/plain, Size: 818 bytes --]
On Donnerstag, 10. Mai 2018 19:44:28 CEST Linus Lüssing wrote:
[...]
> + * @flags: a pointer to store TT flags for the given @orig_node and @entry to
[...]
> + * @flags: a pointer to store TT flags for this client to
[...]
> + * @flags: a pointer to store TT flags to
Antonio wanted to have some changes here. From IRC:
<ecsv> ordex: any objections to T_X's last patch version? https://patchwork.open-mesh.org/patch/17355/
<ordex> hm is this correct: "@flags: a pointer to store TT flags for the given @orig_node and @entry to" ?
<ordex> entry to ?
<ordex> the rest looks ok
<ecsv> maybe "@flags: a pointer to store TT flags of the given @orig_node and @entry" is better ?
<ordex> ecsv: maybe ""@flags: a pointer to store TT flags for the given @entry received from @orig_node"
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-05-11 6:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 17:44 [B.A.T.M.A.N.] [PATCH v3 maint] batman-adv: Fix TT sync flags for intermediate TT responses Linus Lüssing
2018-05-11 6:13 ` Sven Eckelmann [this message]
2018-05-11 13:12 ` Sven Eckelmann
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=4477321.n6vKnkidQF@sven-edge \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.