From: Sven Eckelmann <sven.eckelmann@gmx.de>
To: Greg Kroah-Hartman <gregkh@suse.de>
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: [B.A.T.M.A.N.] batman-adv: Migration from staging to net
Date: Thu, 10 Jun 2010 13:03:36 +0200 [thread overview]
Message-ID: <201006101303.45771.sven.eckelmann@gmx.de> (raw)
[-- Attachment #1: Type: Text/Plain, Size: 2333 bytes --]
Hi,
the batman-adv developers had a smaller discussion what we wanted to achieve
in drivers/staging and if we have done everything we wanted to do. We think
that everything we wanted to do in staging is finished (the TODO file is
empty since a while), but that is just our opinion.
So we wanted to ask you first if you see any showstopper which make batman-adv
insufficient for net before we would ask the net maintainer. Our personal
favorite kernel for the move would be 2.6.37. Before that we would have 2.6.35
(which is not completely correct using the sysfs infrastructure) and at least
some RCs of 2.6.36 (which moves the remaining wrong stuff from sysfs to
debugfs).
Open patches for 2.6.36 are currently (may change)
* batman-adv: Mark locally used symbols as static (removed some dead code)
* batman-adv: 32bit sequence number and TTL for broadcasts
* batman-adv: Add bonding functionality
* batman-adv: bonding and interface alternating
* batman-adv: record route for ICMP messages
* ...
Nearly all of them are features and not really things which makes it more
suitable for the kernel. Open things are for example
* Re-Integration of some debugging infrastructure (currently not decided
which technology to use)
* virtualized meshing (I am not sure if that was the same fancy term the
actual developer used)
* forward error correction
* mesh optimized gateway support
* protocol optimizations
Again I wouldn't think that one of the mentioned points would make it better
suitable for the kernel (but of course makes batman-adv better in general
terms).
So is there anything you would want us to change before you would say that we
could try a review by the net maintainer?
To the merge process itself. We should prepare a patch which adds everything
in net/batman-adv/ (and Documentation/ABI/testing/, MAINTAINERS) and then send
it to netdev@vger.kernel.org/David S. Miller. After it was merged we just send
you a patch which removes drivers/staging/batman-adv. Is that correct (just
searched for an example and only found benet[1, 2])?
thanks,
Sven
[1] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=shortlog;h=6b7c5b947c671a96e39f9526a5fd70c178b8dfd1
[2] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=shortlog;h=d0573facf21d1e5cfbc1ddac272b7592722e6c01
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2010-06-10 11:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 11:03 Sven Eckelmann [this message]
2010-06-22 23:02 ` [B.A.T.M.A.N.] batman-adv: Migration from staging to net Greg KH
2010-06-23 7:47 ` Sven Eckelmann
2010-06-23 14:31 ` Greg KH
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=201006101303.45771.sven.eckelmann@gmx.de \
--to=sven.eckelmann@gmx.de \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=gregkh@suse.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