All of lore.kernel.org
 help / color / mirror / Atom feed
From: pidoux <bpidoux@free.fr>
To: David Miller <davem@davemloft.net>
Cc: f6bvp@free.fr, ralf@linux-mips.org, netdev@vger.kernel.org,
	linux-hams@vger.kernel.org
Subject: Re: [PATCH][ROSE][NETROM] display neigh instead of address
Date: Sun, 09 Mar 2008 10:00:09 +0100	[thread overview]
Message-ID: <47D3A719.9080105@free.fr> (raw)
In-Reply-To: <20080303.205304.225449154.davem@davemloft.net>

David Miller a écrit :
> From: Bernard Pidoux F6BVP <f6bvp@free.fr>
> Date: Fri, 29 Feb 2008 23:45:03 +0100
>
>   
>> I submit the following patch against kernel 2.6.24.3 to replace
>> labels "addr" in /proc/net/rose_neigh and /proc/net/nr_neigh
>> by labels "neigh" for the display of neighbour numbers in the
>> first columns.
>>
>> This makes the reading of proc more consistent with the labels of
>> /proc/net/rose_nodes and /proc/net/nr_nodes.
>> Finding the callsign of a given node neighbour number becomes easier.
>>     
>
> I'm not so sure there is much value to this.
> "address", "neigh", it's all about the same.
>
> Yes, it's inconsistent in various areas, but procfs
> output is like a fixed API with userspace and we generally
> cannot change it without potentially breaking userspace.
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>
>   
I thought that the patch would only affect /proc/net/rose and 
/proc/net/netrom, not /proc/net.
However I understand your objection.
Meanwhile application programs can deal with the present labels as far 
as we keep in mind that "addr" and "neigh" are talking about the same thing.
Thanks for the explanation.

Bernard Pidoux

 
--
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2008-03-09  9:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-11  8:56 [BUG][AX25] mkiss and ax25_route lockdep warning Jann Traschewski
2008-02-11 12:42 ` [PATCH][AX25] ax25_route: make ax25_route_lock BH safe Jarek Poplawski
2008-02-12  5:26   ` David Miller
2008-02-29 22:45     ` [PATCH][ROSE][NETROM] display neigh instead of address Bernard Pidoux F6BVP
2008-03-04  4:53       ` David Miller
2008-03-09  9:00         ` pidoux [this message]
2008-02-12  8:43   ` [PATCH][AX25] ax25_route: make ax25_route_lock BH safe Jann Traschewski
2008-02-12  9:44     ` Jarek Poplawski

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=47D3A719.9080105@free.fr \
    --to=bpidoux@free.fr \
    --cc=davem@davemloft.net \
    --cc=f6bvp@free.fr \
    --cc=linux-hams@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=ralf@linux-mips.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 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.