From: Sven Eckelmann <sven@narfation.org>
To: Xuebing Wang <xbing6@gmail.com>
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [batman-adv] Does batman-adv works perfectly?
Date: Thu, 06 Apr 2017 11:27:10 +0200 [thread overview]
Message-ID: <2195040.ykU6RrkfU7@bentobox> (raw)
In-Reply-To: <56f44583-9cbc-d3eb-20c2-b8243a7889a1@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 794 bytes --]
On Donnerstag, 6. April 2017 16:05:26 CEST Xuebing Wang wrote:
> Hi Sven, Simon,
>
> Thank you very much for your help. These 2 patches are not merged
> upstream? I did see a similar patch merged (as you 2 are the authors,
> you know it very well):
> > [1] https://patchwork.kernel.org/patch/9433619/
> > [2] https://patchwork.kernel.org/patch/9433621/
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a34d0a0da1abae46a5f6ebd06fb0ec484ca099d9
>
The deaf patch is not applied upstream. But yes, the deadbeef patch was
modified by Felix and then applied upstream (the commit you've listed here).
And these patches (in patchwork) are much newer than Chaos Calmer. So I would
not expect to see them in the Chaos Calmer mac80211 package.
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-04-06 9:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 2:32 [B.A.T.M.A.N.] [batman-adv] Does batman-adv works perfectly? Xuebing Wang
2017-04-06 7:04 ` Simon Wunderlich
2017-04-06 7:13 ` Sven Eckelmann
2017-04-06 8:05 ` Xuebing Wang
2017-04-06 9:27 ` Sven Eckelmann [this message]
[not found] ` <CAG5qQ7hQACaP=vz6jmvWDXoK=Sn0wpE3DrDhJv8Qajnhjbp+Og@mail.gmail.com>
2017-04-18 10:40 ` Simon Wunderlich
2017-04-18 10:40 ` Simon Wunderlich
2017-04-22 7:12 ` Xuebing Wang
2017-04-22 8:35 ` Simon Wunderlich
2017-04-22 12:49 ` Xuebing Wang
2017-04-26 2:49 ` Xuebing Wang
2017-04-26 7:46 ` Simon Wunderlich
2017-04-06 7:10 ` Sven Eckelmann
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=2195040.ykU6RrkfU7@bentobox \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=xbing6@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.