All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew.lunn@ascom.ch>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@lists.open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] [batman-adv] Use prinkt instead of debug_log
Date: Mon, 24 Aug 2009 12:08:17 +0200	[thread overview]
Message-ID: <20090824100817.GL30255@ma.tech.ascom.ch> (raw)
In-Reply-To: <200908241702.32201.lindner_marek@yahoo.de>

> Does this patch mean you got in touch with a maintainer and he/she suggested 
> to do that ? What else did he/she suggest ?

No i've not asked yet. However, i don't know of any other kernel
module which does debug output in a similar way. So my guess is this
needs changing.

I keep intending to make a ToDo list. Here is what i have in my mind
at the moment. Some are just questions/ideas and all of it needs
discussing.

Finish stripping out debug_log.

Make batctl standalone.

Maybe make batctl _The_ tool for configuration and status and
depreciate direct proc access, so that we can restructure it without
too much pain for users.

Take out the dot_draw/josm formatting in vis and put it into batctl.

Think if /proc/net/batman-adv should be renamed /proc/net/bat0 giving
the option of /proc/net/bat1 etc in the future?

Should /proc/net/batman-adv/interface be replaced with an IOCTL interface
similar to brctl?

Maybe move orig_interval, aggregate_ogm and write half of vis to /sys?
At least spit vis into two.

Investigate if there is a generic linux hash algorithm which should be used?

Strip out all backward compatibility support.

Make use of printk %pM support.

     Andrew



  reply	other threads:[~2009-08-24 10:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-23 13:09 [B.A.T.M.A.N.] [batman-adv] Use prinkt instead of debug_log Andrew Lunn
2009-08-23 13:54 ` Andrew Lunn
2009-08-24  9:02 ` Marek Lindner
2009-08-24 10:08   ` Andrew Lunn [this message]
2009-08-24 12:16     ` Marek Lindner
2009-08-24 13:05       ` Andrew Lunn

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=20090824100817.GL30255@ma.tech.ascom.ch \
    --to=andrew.lunn@ascom.ch \
    --cc=b.a.t.m.a.n@lists.open-mesh.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.