From: "Chad N. Tindel" <chad@tindel.net>
To: James Morris <jmorris@intercode.com.au>
Cc: Stephen Hemminger <shemminger@osdl.org>,
Jay Vosburgh <fubar@us.ibm.com>,
"David S. Miller" <davem@redhat.com>,
Jeff Garzik <jgarzik@pobox.com>,
bonding-devel@lists.sourceforge.net, netdev@oss.sgi.com
Subject: Re: [PATCH] convering bonding driver /proc interface to seq_file
Date: Thu, 21 Aug 2003 20:27:42 -0400 [thread overview]
Message-ID: <20030822002742.GA99843@calma.pair.com> (raw)
In-Reply-To: <Mutt.LNX.4.44.0308221016320.993-100000@excalibur.intercode.com.au>
> > The name "/proc/net/bond0/info" is kind of unconventional, but now
> > changing that in a almost stable release would be bad. Better choice
> > would be "/proc/net/bonding/bond0".
>
> I'm not sure it's too late to do this.
It certainly would match what other drivers do.
Chad
next prev parent reply other threads:[~2003-08-22 0:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-21 23:52 [PATCH] convering bonding driver /proc interface to seq_file Stephen Hemminger
2003-08-22 0:17 ` James Morris
2003-08-22 0:27 ` Chad N. Tindel [this message]
2003-08-22 20:03 ` [PATCH] change /proc/bond0/info to /proc/bonding/bond0 Stephen Hemminger
-- strict thread matches above, loose matches on Subject: below --
2003-08-23 13:35 [PATCH] convering bonding driver /proc interface to seq_file Hen, Shmulik
2003-08-23 14:25 Hen, Shmulik
2003-08-24 15:15 ` James Morris
2003-08-24 17:12 ` Shmulik Hen
2003-08-25 15:45 ` Stephen Hemminger
2003-08-25 18:43 Hen, Shmulik
2003-08-25 19:27 ` Stephen Hemminger
[not found] <E791C176A6139242A988ABA8B3D9B38A0251EB62@hasmsx403.iil.intel.com>
2003-08-26 7:45 ` Shmulik Hen
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=20030822002742.GA99843@calma.pair.com \
--to=chad@tindel.net \
--cc=bonding-devel@lists.sourceforge.net \
--cc=davem@redhat.com \
--cc=fubar@us.ibm.com \
--cc=jgarzik@pobox.com \
--cc=jmorris@intercode.com.au \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.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;
as well as URLs for NNTP newsgroup(s).