From: Antonio Quartulli <antonio@meshcoding.com>
To: Sven Eckelmann <sven@narfation.org>, davem@davemloft.net
Cc: netdev@vger.kernel.org, b.a.t.m.a.n@lists.open-mesh.org,
Marek Lindner <mareklindner@neomailbox.ch>
Subject: Re: [PATCH] batman-adv: Fix out-of-order fragmentation support
Date: Tue, 05 Aug 2014 09:17:36 +0200 [thread overview]
Message-ID: <53E08510.4020308@meshcoding.com> (raw)
In-Reply-To: <5564567.83o54DtWyR@bentobox>
[-- Attachment #1: Type: text/plain, Size: 802 bytes --]
On 04/08/14 18:26, Sven Eckelmann wrote:
> On Monday 04 August 2014 17:47:01 Antonio Quartulli wrote:
>> This problem was introduced in 9b3eab61754d74a93c9840c296013fe3b4a1b606
>> ("batman-adv: Receive fragmented packets and merge").
>
> This is not a commit id from the kernel tree but the one from your out-of-tree
> repository at http://git.open-mesh.org/batman-adv.git .
> 610bfc6bc99bc83680d190ebc69359a05fc7f605 seems to be the one of Martin's
> commit when it was applied in the kernel repository.
Thanks Sven!
David, I "fixed" the commit message and pushed the tag
"batman-adv-fix-for-davem" again. If you pull now you will get the
correct text.
new head is:
batman-adv-for-davem = d9124268d84a836f14a6ead54ff9d8eee4c43be5)
Cheers,
--
Antonio Quartulli
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 884 bytes --]
next prev parent reply other threads:[~2014-08-05 7:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-04 15:47 pull request net: batman-adv 2014-08-04 Antonio Quartulli
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 [this message]
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=53E08510.4020308@meshcoding.com \
--to=antonio@meshcoding.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=davem@davemloft.net \
--cc=mareklindner@neomailbox.ch \
--cc=netdev@vger.kernel.org \
--cc=sven@narfation.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).