From: Andrew Lunn <andrew@lunn.ch>
To: "B.A.T.M.A.N" <b.a.t.m.a.n@lists.open-mesh.net>
Subject: [B.A.T.M.A.N.] FWD: patch staging-batman-adv-meshing-protocol.patch added to gregkh-2.6 tree
Date: Fri, 20 Nov 2009 09:22:53 +0100 [thread overview]
Message-ID: <20091120082253.GA12827@lunn.ch> (raw)
FYI:
We just made a big towards getting batman-adv in mainline. We are now
in GregKH patch tree.
What i don't know is if this will be merged for the next 2.6.32-rc or
if we need to wait for the opening of the 2.6.33 window.
Andrew
----- Forwarded message from gregkh@suse.de -----
Date: Thu, 19 Nov 2009 15:01:09 -0800
From: gregkh@suse.de
To: andrew@lunn.ch, gregkh@suse.de, lindner_marek@yahoo.de,
siwu@hrz.tu-chemnitz.de
Subject: patch staging-batman-adv-meshing-protocol.patch added to gregkh-2.6
tree
X-Spam-Status: No, score=-2.6 required=4.0 tests=BAYES_00 autolearn=ham
version=3.2.5
This is a note to let you know that I've just added the patch titled
Subject: staging: batman-adv meshing protocol
to my gregkh-2.6 tree. Its filename is
staging-batman-adv-meshing-protocol.patch
This tree can be found at
http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/patches/
----- End forwarded message -----
reply other threads:[~2009-11-20 8:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20091120082253.GA12827@lunn.ch \
--to=andrew@lunn.ch \
--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