From: "David S. Miller" <davem@redhat.com>
To: ak@suse.de
Cc: dj.barrow@asitatech.com, linux-kernel@vger.kernel.org
Subject: Re: novice coding in /linux/net/ipv4/util.c From: DJ Barrow <dj.barrow@asitatech.com>
Date: Tue, 23 Apr 2002 07:15:44 -0700 (PDT) [thread overview]
Message-ID: <20020423.071544.71966255.davem@redhat.com> (raw)
In-Reply-To: <p73it6j8xwl.fsf@oldwotan.suse.de>
From: Andi Kleen <ak@suse.de>
Date: 22 Apr 2002 19:07:38 +0200
Best would be probably to convert the few remaining users of in_ntoa
to NIPQUAD and drop this function.
I'm doing this in my tree.
next prev parent reply other threads:[~2002-04-23 14:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020422151025Z314220-22651+13849@vger.kernel.org.suse.lists.linux.kernel>
2002-04-22 17:07 ` novice coding in /linux/net/ipv4/util.c From: DJ Barrow <dj.barrow@asitatech.com> Andi Kleen
2002-04-22 17:19 ` DJ Barrow
2002-04-23 14:15 ` David S. Miller [this message]
2002-04-22 15:12 DJ Barrow
2002-04-22 15:48 ` Richard B. Johnson
2002-04-22 16:03 ` DJ Barrow
2002-04-22 16:21 ` Ben Greear
2002-04-22 20:32 ` Olaf Titz
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=20020423.071544.71966255.davem@redhat.com \
--to=davem@redhat.com \
--cc=ak@suse.de \
--cc=dj.barrow@asitatech.com \
--cc=linux-kernel@vger.kernel.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