From: Marek Lindner <lindner_marek@yahoo.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: [B.A.T.M.A.N.] sysfs compat
Date: Mon, 3 May 2010 08:28:08 +0800 [thread overview]
Message-ID: <201005030828.08856.lindner_marek@yahoo.de> (raw)
Hi,
the current trunk contains some code which breaks our backward compatibility,
especially the sysfs API seem to be troublesome. I made 2 patches that address
the issue on my 2.6.21 test system. It would be nice if you could test them on
your system as well. I'd be particularly interested in kernels older than
2.6.25. Does someone have a 2.6.20 system ?
At some point we have to start thinking about how many versions we want to
support. Each new kernel brings more changes which need to be dealt with.
Right now, the required effort is still at a sustainable level but the gap is
growing. On one hand it is a nice playground to expand our knowledge about
macros and demonstrate what nasty things you can do (see the second patch as
an example). ;-)
On the other hand it always requires a serious amount of time and effort. It
only makes sense if at least some people are using it. Opinions ?
Regards,
Marek
next reply other threads:[~2010-05-03 0:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 0:28 Marek Lindner [this message]
2010-05-03 0:28 ` [B.A.T.M.A.N.] [PATCH 1/2] batman-adv: adding MAC_FMT compatibility Marek Lindner
2010-05-03 0:28 ` [B.A.T.M.A.N.] [PATCH 2/2] batman-adv: adding sysfs compat Marek Lindner
2010-05-03 8:03 ` [B.A.T.M.A.N.] " Andrew Lunn
2010-05-03 9:05 ` Franz Böhm
2010-05-03 10:30 ` Sven Eckelmann
2010-05-03 20:40 ` Simon Wunderlich
2010-05-04 2:21 ` Marek Lindner
2010-05-04 11:13 ` Franz Böhm
2010-05-04 11:40 ` elektra
2010-05-04 12:36 ` Franz Böhm
2010-05-04 13:05 ` elektra
2010-05-04 17:34 ` Franz Böhm
2010-05-04 23:59 ` RHS Linux User
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=201005030828.08856.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