public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven.eckelmann@gmx.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: Marek Lindner <lindner_marek@yahoo.de>
Subject: Re: [B.A.T.M.A.N.] sysfs abi documentation
Date: Sun, 9 May 2010 16:58:39 +0200	[thread overview]
Message-ID: <201005091658.45998.sven.eckelmann@gmx.de> (raw)
In-Reply-To: <201005091117.05627.lindner_marek@yahoo.de>

[-- Attachment #1: Type: Text/Plain, Size: 874 bytes --]

Marek Lindner wrote:
> Hi,
> 
> Greg asked us to provide an ABI documentation for the files creates in the
> sysfs tree. Since I am respsonsible for the sysfs stuff, I felt it was my
> turn to draft something. Please check the attachments and let me know
> whether you think we can send it or not.

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.

Best regards,
	Sven

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2010-05-09 14:58 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 [this message]
2010-05-09 17:44   ` 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=201005091658.45998.sven.eckelmann@gmx.de \
    --to=sven.eckelmann@gmx.de \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=lindner_marek@yahoo.de \
    /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