From: Antonio Quartulli <antonio@meshcoding.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, b.a.t.m.a.n@lists.open-mesh.org
Subject: pull request net: batman-adv 2014-08-04
Date: Mon, 4 Aug 2014 17:47:00 +0200 [thread overview]
Message-ID: <1407167221-10575-1-git-send-email-antonio@meshcoding.com> (raw)
Hello David,
this is a pull request intended for net.
It just contains a patch by Sven Eckelmann that fixes the
reception of out-of-order fragments. As explained in the
commit message, the issue was due to a wrong assumption
about hlist_for_each_entry() in batadv_frag_insert_packet().
Please pull or let me know of any problem.
*If possible, this patch should also be enqueued for stable*
Thanks a lot,
Antonio
The following changes since commit 4f933f414bf629852f361edf0fc5e765e3e78388:
r8152: add missing Makefile rule (2014-08-02 20:53:55 -0700)
are available in the git repository at:
git://git.open-mesh.org/linux-merge.git tags/batman-adv-fix-for-davem
for you to fetch changes up to 9d2155fb59e21f4a38838035d2a26a8a02fec16c:
batman-adv: Fix out-of-order fragmentation support (2014-08-04 16:05:43 +0200)
----------------------------------------------------------------
Fix out-of-order fragments reception.
----------------------------------------------------------------
Sven Eckelmann (1):
batman-adv: Fix out-of-order fragmentation support
net/batman-adv/fragmentation.c | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
next reply other threads:[~2014-08-04 15:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-04 15:47 Antonio Quartulli [this message]
2014-08-04 15:47 ` [PATCH] batman-adv: Fix out-of-order fragmentation support Antonio Quartulli
2014-08-04 16:26 ` Sven Eckelmann
2014-08-05 7:17 ` Antonio Quartulli
2014-08-05 23:22 ` pull request net: batman-adv 2014-08-04 David Miller
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=1407167221-10575-1-git-send-email-antonio@meshcoding.com \
--to=antonio@meshcoding.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.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).