public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: info@wifi-frankfurt.de, thomas@t-8ch.de
Subject: Re: [B.A.T.M.A.N.] Batman-advanced-dkms + debian + kernel >4.1
Date: Sun, 04 Oct 2015 18:41:40 +0200	[thread overview]
Message-ID: <3035214.3FFCJO0HV9@sven-edge> (raw)
In-Reply-To: <37028290.5tXI0TbgDB@lappi>

[-- Attachment #1: Type: text/plain, Size: 1913 bytes --]

On Sunday 04 October 2015 16:24:11 Christof Schulze wrote:
> Hello Simon,
> 
> when trying to run batman v14 on a current kernel (I noticed it for Version
> 4.1) I realized that batman will not build beause the netdev-structs
>   have changed.

v14 is not maintained anymore in the official batman-adv repositories. You may 
instead try to contact the developers of the batman-adv-legacy [1] gluon fork.

> The solution is fairly simple because the fix has already been
> implemented in newer batman versions. The function
> batadv_is_on_batman_iface can be copied from there and is working fine.
> 
[...]
> 
> Now: Where is the correct place to implement the patch: in
> batman-adv-dkms or in batman itself?

Which batman-adv-dkms? I was maintaining a Debian package with that name but 
this was dropped a long time ago... I think 2011 or so. But I would guess that 
you want to add a patch to your "batman-adv-dkms" that patches batman-adv so 
dkms is able to build it against your current kernel. Or get the patch 
directly into your batman-adv v14 fork... But this is nothing Simon or I can 
help you with because we stopped working on v14 and batman-adv-dkms years ago.

Most likely you are talking about gluon based batman-adv-dkms [2] package 
which is also made by the batman-adv-legacy people. But these packages clearly 
states that Matthias Schiffer <mschiffer@universe-factory.net> is responsible 
for them (ok, he forgot to change it maintainer name in 
debian/control.modules.in and didn't update the upstream addresses). So you 
better contact him when you are using his forks. He most likely has complete 
different ideas how this patch has to look like because he isn't interested in 
getting it merged into the official Linux repository.

Kind regards,
	Sven

[1] https://github.com/freifunk-gluon/batman-adv-legacy
[2] http://repo.universe-factory.net/debian/pool/main/b/batman-adv-kernelland/

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2015-10-04 16:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-04 14:24 [B.A.T.M.A.N.] Batman-advanced-dkms + debian + kernel >4.1 Christof Schulze
2015-10-04 16:41 ` 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=3035214.3FFCJO0HV9@sven-edge \
    --to=sven@narfation.org \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=info@wifi-frankfurt.de \
    --cc=thomas@t-8ch.de \
    /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