From: Sven Eckelmann <sven@narfation.org>
To: "Berg, Johannes" <johannes.berg@intel.com>
Cc: "b.a.t.m.a.n@lists.open-mesh.org"
<b.a.t.m.a.n@lists.open-mesh.org>, Felix Fietkau <nbd@nbd.name>,
Arend van Spriel <aspriel@gmail.com>
Subject: Re: [B.A.T.M.A.N.] [PATCH maint] batman-adv: release station info tidstats
Date: Fri, 25 Jan 2019 09:23:42 +0100 [thread overview]
Message-ID: <2843714.oyMTxGbNKy@bentobox> (raw)
In-Reply-To: <1DC40B07CD6EC041A66726C271A73AE68CFA842A@IRSMSX108.ger.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1031 bytes --]
On Friday, 25 January 2019 08.16.46 CET Berg, Johannes wrote:
> Huh, sorry about that.
>
> > From: Felix Fietkau <nbd@nbd.name>
>
> If Felix had nothing to do with the patch, why would you pretend otherwise?
This is what he has dropped and Martin Weinelt forwarded to us:
http://nbd.name/batman-adv-memleak.patch
So just the net/batman-adv/bat_v_elp.c part without anything else.
> You need two patches - one for backports, this part:
>
> > compat-include/net/cfg80211.h | 7 +++++++
This is not for backports [0] - this is for batman-adv.git [1]
> And for mainline, this part:
>
> > net/batman-adv/bat_v_elp.c | 3 +++
>
> So send the two separate patches to the two separate projects, and that's it?
The upstream patch (for David) is just stripped from the compat-include part.
Kind regards,
Sven
[0] https://git.kernel.org/pub/scm/linux/kernel/git/backports/backports.git/
[1] https://git.open-mesh.org/batman-adv.git
[2] https://git.open-mesh.org/linux-merge.git/commit/7d652669b61d702c6e62a39579d17f6881670ab6
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-01-25 8:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 8:02 [B.A.T.M.A.N.] [PATCH maint] batman-adv: release station info tidstats Sven Eckelmann
2019-01-25 8:16 ` Berg, Johannes
2019-01-25 8:23 ` Sven Eckelmann [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=2843714.oyMTxGbNKy@bentobox \
--to=sven@narfation.org \
--cc=aspriel@gmail.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=johannes.berg@intel.com \
--cc=nbd@nbd.name \
/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