b.a.t.m.a.n.lists.open-mesh.org archive mirror
 help / color / mirror / Atom feed
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 15:12:01 +0200	[thread overview]
Message-ID: <3502293.18K6qFWs9T@sven-edge> (raw)
In-Reply-To: <4477321.n6vKnkidQF@sven-edge>

[-- Attachment #1: Type: text/plain, Size: 1101 bytes --]

On Freitag, 11. Mai 2018 08:13:09 CEST Sven Eckelmann wrote:
> 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"

Added as d65daee8617b [1] with the requested changes to the @flags 
documentation from Antonio

Thanks,
	Sven

[1] https://git.open-mesh.org/batman-adv.git/commit/d65daee8617b29c1ddcc949ce3a5ec24f7a1e1af

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2018-05-11 13:12 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
2018-05-11 13:12   ` Sven Eckelmann [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=3502293.18K6qFWs9T@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 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).