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.] [PATCH] batman-adv: export compatibility version via debugfs
Date: Sun, 7 Oct 2012 00:43:34 +0800 [thread overview]
Message-ID: <201210070043.34560.lindner_marek@yahoo.de> (raw)
In-Reply-To: <20121003211800.GH10663@ritirata.org>
On Thursday, October 04, 2012 05:18:00 Antonio Quartulli wrote:
> On Thu, Oct 04, 2012 at 01:06:55AM +0800, Marek Lindner wrote:
> > On Thursday, October 04, 2012 00:35:36 Antonio Quartulli wrote:
> > > @@ -355,6 +366,13 @@ void batadv_debugfs_init(void)
> > >
> > > if (!file)
> > >
> > > pr_err("Can't add debugfs file: %s\n",
> > >
> > > bat_debug->attr.name);
> > > + bat_debug = &batadv_debuginfo_compat_version;
> > > + file = debugfs_create_file(bat_debug->attr.name,
> > > + S_IFREG | bat_debug->attr.mode,
> > > + batadv_debugfs, NULL,
> > > &bat_debug->fops); + if (!file)
> > > + pr_err("Can't add debugfs file: %s\n",
> > > bat_debug->attr.name); +
> > >
> > > out:
> > > return;
> > >
> > > }
> >
> > If we start to create more files here you should add a a loop like in
> > batadv_debugfs_add_meshif() to avoid duplicate code.
>
> do you think we should do that for two files already?
> I do not think there will be so much to add in this debugfs folder. Maybe
> we can add a loop as soon as add the next one, but for two I think we can
> still leave with this implementation.
Well, when I added the 'routing_algos' file I also thought nobody else would
want to add something there ...
Cheers,
Marek
prev parent reply other threads:[~2012-10-06 16:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-03 16:35 [B.A.T.M.A.N.] [PATCH] batman-adv: export compatibility version via debugfs Antonio Quartulli
2012-10-03 17:06 ` Marek Lindner
2012-10-03 21:18 ` Antonio Quartulli
2012-10-06 16:43 ` 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=201210070043.34560.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