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.] sysfs abi documentation
Date: Mon, 10 May 2010 01:44:25 +0800	[thread overview]
Message-ID: <201005100144.26046.lindner_marek@yahoo.de> (raw)
In-Reply-To: <201005091658.45998.sven.eckelmann@gmx.de>

On Sunday 09 May 2010 22:58:39 Sven Eckelmann wrote:
> I've read a little bit through the different descriptions and it sound
> good... for the reading situation. The problem is that it is nearly never
> clear that you control the behavior of batman-adv through that specific
> file. For example /sys/class/net/<iface>/batman-adv/mesh_iface - I think
> it is especially important for GregKH to see that it needed is now
> associated to the iface and we attach it to the mesh_iface through that
> file when he should give us some advice what virtual fs should be used for
> what kind of information.

Thanks for the review. 
Before writing these descriptions I looked up various examples that are 
available in the kernel tree. I had the feeling that our ABI docs are not too 
far off. But I know that this will not be enough to understand the meaning 
behind those settings which is why I created a wikipage explaining the 
connections between the various sysfs files. I intended to send this along with 
the sysfs ABI files:
http://www.open-mesh.org/wiki/tweaking-batman-adv


Regards,
Marek

      reply	other threads:[~2010-05-09 17:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-09  3:17 [B.A.T.M.A.N.] sysfs abi documentation Marek Lindner
2010-05-09  7:08 ` Andrew Lunn
2010-05-09  7:20   ` Marek Lindner
2010-05-09 14:58 ` Sven Eckelmann
2010-05-09 17:44   ` Marek Lindner [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=201005100144.26046.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