From: David Miller <davem@davemloft.net>
To: joe@perches.com
Cc: xemul@openvz.org, netdev@vger.kernel.org, devel@openvz.org
Subject: Re: [PATCH] Cleanup the IPv6 addresses printing in /proc files
Date: Tue, 23 Oct 2007 21:18:52 -0700 (PDT) [thread overview]
Message-ID: <20071023.211852.15263990.davem@davemloft.net> (raw)
In-Reply-To: <1193199336.11845.53.camel@localhost>
From: Joe Perches <joe@perches.com>
Date: Tue, 23 Oct 2007 21:15:36 -0700
> On Tue, 2007-10-23 at 21:10 -0700, David Miller wrote:
> > We'll break things if we change it.
>
> Maybe, but definitely the macro names should
> reflect this brokenness.
That's a good point, we don't want to encourage further
use of these things.
Pavel, I'm going to revert this patch for now. It may
save some code lines, but it does so at the expense of
creating an interface we actually don't want more users
of.
prev parent reply other threads:[~2007-10-24 4:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 16:37 [PATCH] Cleanup the IPv6 addresses printing in /proc files Pavel Emelyanov
2007-10-24 3:43 ` David Miller
2007-10-24 4:04 ` Joe Perches
2007-10-24 4:10 ` David Miller
2007-10-24 4:15 ` Joe Perches
2007-10-24 4:18 ` David Miller [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=20071023.211852.15263990.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=devel@openvz.org \
--cc=joe@perches.com \
--cc=netdev@vger.kernel.org \
--cc=xemul@openvz.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).