public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: "Martin Hundebøll" <martin@hundeboll.net>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [PATCHv4] batman-adv: Move call to batadv_nc_skb_forward() from routing.c to send.c
Date: Sat, 20 Apr 2013 16:01:41 +0200	[thread overview]
Message-ID: <51729FC5.2080608@hundeboll.net> (raw)
In-Reply-To: <1366373804-26785-1-git-send-email-martin@hundeboll.net>

On 2013-04-19 14:16, 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.
>
> 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
>
> network-coding.c | 8 ++------
>   network-coding.h | 6 ++----
>   routing.c        | 9 +++------
>   send.c           | 9 +++++++--
>   4 files changed, 14 insertions(+), 18 deletions(-)


Okay, I include this patch as a part of the fragmentation series, as 
this is why it is needed.


-- 
Kind Regards
Martin Hundebøll
Frederiks Allé 99, 1.th
8000 Aarhus C
Denmark

+45 61 65 54 61
martin@hundeboll.net

      parent reply	other threads:[~2013-04-20 14:01 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
2013-04-20 14:01       ` Martin Hundebøll [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=51729FC5.2080608@hundeboll.net \
    --to=martin@hundeboll.net \
    --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