public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Marek Lindner <lindner_marek@yahoo.de>
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.] [RFC] batman-adv: Remove compat code for kernel versions < 2.6.29
Date: Sun, 17 Jul 2011 21:11:31 +0200	[thread overview]
Message-ID: <201107172111.32232.lindner_marek@yahoo.de> (raw)
In-Reply-To: <1310899392-1941-1-git-send-email-sven@narfation.org>

On Sunday, July 17, 2011 12:43:12 Sven Eckelmann wrote:
> The removal of the HAVE_NET_DEVICE_OPS in the kernel sources by David S.
> Miller makes it hard to implement compatibility code using compat.(c|h).
> Either the sources of the kernel and the external module have to diverge
> again or more complex workarounds have to be found.
> 
> Dropping support for kernels older than 2.6.29 will remove the dead ballast
> of stuff older than two years. People which need it can revert
> 7f1b7b837c205e413a7aa078a47ec96f0c11afa7 and this patch.

Although it might not please everyone I believe this is the way to go. In case 
somebody does not agree he can propose an alternative in the following days.

Cheers,
Marek

  parent reply	other threads:[~2011-07-17 19:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-17 10:43 [B.A.T.M.A.N.] [RFC] batman-adv: Remove compat code for kernel versions < 2.6.29 Sven Eckelmann
2011-07-17 11:11 ` [B.A.T.M.A.N.] [RFC] batman-adv: Start to fiddle with compat stuff Sven Eckelmann
2011-07-17 11:15   ` Sven Eckelmann
2011-07-17 19:14     ` Simon Wunderlich
2011-07-18  8:35       ` Sven Eckelmann
2011-07-17 19:11 ` Marek Lindner [this message]
2011-07-23  9:51 ` [B.A.T.M.A.N.] [RFC] batman-adv: Remove compat code for kernel versions < 2.6.29 Marek Lindner

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=201107172111.32232.lindner_marek@yahoo.de \
    --to=lindner_marek@yahoo.de \
    --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