netdev - Re: [PATCHv8] net: Add batman-adv meshing protocol

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20101216.145228.27818669.davem@davemloft.net>
Date:	Thu, 16 Dec 2010 14:52:28 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	sven@...fation.org
Cc:	netdev@...r.kernel.org, b.a.t.m.a.n@...ts.open-mesh.org
Subject: Re: [PATCHv8] net: Add batman-adv meshing protocol

From: Sven Eckelmann <sven@...fation.org>
Date: Thu, 16 Dec 2010 23:21:09 +0100

> This brings me to another topic. How do you want to get patches for batman-
> adv? Do you prefer to pull changes from a git tree or do you want do have them 
> sent to netdev and you as real patches? Do you have special restrictions on 
> the time were you want to except feature patches for the next kernel version 
> (before Linus' merge window)?

Patches or GIT tree is fine.  Either way it should be based upon
net-next-2.6

If you use a GIT tree, you should still post the individual patches
for review on netdev.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html