public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] Are older kernels abandoned?
Date: Mon, 11 Jan 2010 09:06:43 +0100	[thread overview]
Message-ID: <20100111080643.GA7844@lunn.ch> (raw)
In-Reply-To: <4B4AD36A.60209@gmail.com>

On Sun, Jan 10, 2010 at 11:29:46PM -0800, Gus Wirth wrote:
> Now that work is under way to incorporate B.A.T.M.A.N (batman-adv) into
> the mainline Linux kernel, hopefully 2.6.33, will older kernels be
> abandoned?
> 
> I have some embedded systems that are on 2.6.30.10 and running fine, and
> I really don't want to have to put in a new kernel and recertify the
> software just to get some improvements to B.A.T.M.A.N.
> 
> Is there any consideration to doing something similar to compat-wireless
> but for B.A.T.M.A.N  (batman-adv) instead?

Older kernels are still supported. The development work is being
performed in subversion. This tree has all the backwards compatibility
code which allows it be compiled on some older kernels, currently
2.6.20 - 2.6.32.

I then take the code out of subversion and put it into git. The git
repository has all this backwards compatibility removed in order that
i can make clean patches for this development work for submission to
mainline in 2.6.34.

  Andrew

      reply	other threads:[~2010-01-11  8:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-11  7:29 [B.A.T.M.A.N.] Are older kernels abandoned? Gus Wirth
2010-01-11  8:06 ` Andrew Lunn [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=20100111080643.GA7844@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    /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