From: Marek Lindner <lindner_marek@yahoo.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: "Martin Hundebøll" <martin@hundeboll.net>
Subject: Re: [B.A.T.M.A.N.] [PATCHv5] batman-adv: Move call to batadv_nc_skb_forward() from routing.c to send.c
Date: Sat, 20 Apr 2013 22:16:24 +0800 [thread overview]
Message-ID: <201304202216.25126.lindner_marek@yahoo.de> (raw)
In-Reply-To: <1366458879-31677-1-git-send-email-martin@hundeboll.net>
On Saturday, April 20, 2013 19:54:39 Martin Hundebøll wrote:
> The call to batadv_nc_skb_forward() fits better in
> batadv_send_skb_to_orig(), as this is where the actual next hop is
> looked up.
>
> To let the caller of batadv_send_skb_to_orig() know wether the skb is
> transmitted, buffered or failed, the return value is changed from
> boolean to int.
>
> Signed-off-by: Martin Hundebøll <martin@hundeboll.net>
> ---
>
> v2: I should make random defines lowercase
> v3: Do git add before committing and sending patches :|
> v4: Don't count non-coded packets twice
> v5: Change return value to do correct counting
>
> network-coding.c | 5 ++---
> network-coding.h | 6 ++----
> routing.c | 23 +++++++++++++----------
> send.c | 27 +++++++++++++++++++--------
> send.h | 6 +++---
> translation-table.c | 12 +++++++-----
> unicast.c | 2 +-
> vis.c | 7 ++++---
> 8 files changed, 51 insertions(+), 37 deletions(-)
Applied in revision ae72fda.
Thanks,
Marek
next prev parent reply other threads:[~2013-04-20 14:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-18 8:11 [B.A.T.M.A.N.] [PATCH] batman-adv: Move call to batadv_nc_skb_forward() from routing.c to send.c Martin Hundebøll
2013-04-18 10:11 ` [B.A.T.M.A.N.] [PATCHv2] " Martin Hundebøll
2013-04-18 10:14 ` [B.A.T.M.A.N.] [PATCHv3] " Martin Hundebøll
2013-04-19 12:16 ` [B.A.T.M.A.N.] [PATCHv4] " Martin Hundebøll
2013-04-20 11:54 ` [B.A.T.M.A.N.] [PATCHv5] " Martin Hundebøll
2013-04-20 14:16 ` Marek Lindner [this message]
2013-04-20 14:01 ` [B.A.T.M.A.N.] [PATCHv4] " Martin Hundebøll
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=201304202216.25126.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.de \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=martin@hundeboll.net \
/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