From: Sven Eckelmann <sven.eckelmann@gmx.de>
To: b.a.t.m.a.n@lists.open-mesh.net
Subject: Re: [B.A.T.M.A.N.] Fwd: Re: Debian extra modules
Date: Tue, 6 Oct 2009 13:55:46 +0200 [thread overview]
Message-ID: <200910061355.49409.sven.eckelmann@gmx.de> (raw)
In-Reply-To: <200910061328.04894.holger@layer-acht.org>
[-- Attachment #1: Type: Text/Plain, Size: 2418 bytes --]
Holger Levsen wrote:
> I've shortened Gregs mail to only have the relevant info for this list :-)
> Full mail is at http://lists.debian.org/debian-kernel/2009/10/msg00236.html
> > batman
> > ------
> >
> > A mesh routing system. Maybe a candidate for staging; try asking
> > upstream.
> >
> > Debian: http://packages.debian.org/source/sid/batmand
> > Upstream: http://www.open-mesh.net/browser/trunk/batman/linux/modules
As far as I know it isn't a part which is currently not targeted for linux-2.6
(staging or netdev) as this isn't self contained, but just a "hack" to improve
gateway speed with batmand. Marek has to decide what to do with it further.
> > batman-adv
> > ----------
> >
> > A mesh bridging system. As for batman.
> >
> > Debian: http://packages.debian.org/source/sid/batman-adv-kernelland
> > Upstream: http://www.open-mesh.net/browser/trunk/batman-adv-kernelland
>
> Please post this code, if it's a module, and the developers want it
> upstream, I'll be glad to take it in staging.
This one should go staging sometime in the near future. We are in contact with
Greg KH and some preparations are currently done to make it fit into staging
and get it to a review for linux netdev soon.
Parts which are important:
* TODO list for staging inside batman-adv folder
* removed compat.h and remaining LINUX_VERSION_CODE (net_device_ops,
unregister_chrdev)
* clean Makefile and Kconfig
* anyone who says how the further development should be done
* anyone who sends the patch to Greg (probably Marek)
Also a open question is how the "issue" of the closed mailing list should be
fixed. Vger doesn't seem to want us before we are successfully reviewed by the
netdev maintainer. Moving the mailinglist every month doesn't seem to be a
good idea. Opening this mailinglist could according to Marek create this ml
useless as there is a big amount of spam send to it. There is a third option
of having the ml semi-open with moderators for mails send by non-subscribers.
But we have to decide who does the moderation.
@Marek: Is the postfix server configured to do greylisting? If yes, do you
have a some statistics about how many spam mails come through and will be
kicked out by the mailinglist system? If it isn't that much I would do some
moderation for some months before we maybe move to a better option.
Best regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2009-10-06 11:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 11:28 [B.A.T.M.A.N.] Fwd: Re: Debian extra modules Holger Levsen
2009-10-06 11:55 ` Sven Eckelmann [this message]
2009-10-06 13:27 ` Marek Lindner
2009-10-06 13:52 ` Andrew Lunn
2009-10-06 14:02 ` Andrew Lunn
2009-10-06 15:11 ` Marek Lindner
2009-10-06 17:12 ` Jacob Marble
2009-10-06 17:37 ` Sven Eckelmann
2009-10-06 18:10 ` Andrew Lunn
2009-10-07 14:56 ` Marek Lindner
2009-10-06 11:59 ` Andrew Lunn
2009-10-20 10:04 ` [B.A.T.M.A.N.] " Sven Eckelmann
2009-10-20 10:35 ` Holger Levsen
2009-10-29 13:15 ` 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=200910061355.49409.sven.eckelmann@gmx.de \
--to=sven.eckelmann@gmx.de \
--cc=b.a.t.m.a.n@lists.open-mesh.net \
/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