From: Jean Delvare <khali@linux-fr.org>
To: Wagner Ferenc <wferi@niif.hu>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: bonding sysfs output
Date: Wed, 5 Dec 2007 23:59:05 +0100 [thread overview]
Message-ID: <20071205235905.7e8ac1b1@hyperion.delvare> (raw)
In-Reply-To: <87lk8lflzf.fsf@szonett.ki.iif.hu>
Hi Wagner,
On Mon, 26 Nov 2007 09:29:40 +0100, Wagner Ferenc wrote:
> On the policy side: some files are not applicable to some types of
> bonds, and return a single linefeed in that case. Except for one
> single case, which returns 'NA\n'. The patch changes these cases into
> emtpy files.
IMHO a better approach would be to not create the files at all when
they make no sense for a given type of bond.
--
Jean Delvare
next prev parent reply other threads:[~2007-12-05 22:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-25 15:12 bonding sysfs output Wagner Ferenc
2007-11-26 4:51 ` Andrew Morton
2007-11-26 8:29 ` Wagner Ferenc
2007-11-27 8:44 ` Andrew Morton
2007-11-27 9:56 ` Ferenc Wagner
2007-11-27 10:14 ` Andrew Morton
2007-11-28 1:03 ` Wagner Ferenc
2007-12-05 22:59 ` Jean Delvare [this message]
2007-12-06 10:13 ` Ferenc Wagner
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=20071205235905.7e8ac1b1@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=wferi@niif.hu \
/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.