From: "David S. Miller" <davem@redhat.com>
To: adilger@turbolabs.com
Cc: tim@physik3.uni-rostock.de, jgarzik@mandrakesoft.com,
andrewm@uow.edu.au, linux-kernel@vger.kernel.org,
torvalds@transmeta.com, netdev@oss.sgi.com, ak@muc.de,
kuznet@ms2.inr.ac.ru
Subject: Re: [PATCH] net/ipv4/*, net/core/neighbour.c jiffies cleanup
Date: Wed, 07 Nov 2001 20:39:54 -0800 (PST) [thread overview]
Message-ID: <20011107.203954.118627544.davem@redhat.com> (raw)
In-Reply-To: <20011107213218.U5922@lynx.no>
In-Reply-To: <20011107173626.S5922@lynx.no> <20011107.164426.35502643.davem@redhat.com> <20011107213218.U5922@lynx.no>
From: Andreas Dilger <adilger@turbolabs.com>
Date: Wed, 7 Nov 2001 21:32:18 -0700
I don't see that it harms anything to use the macros instead.
Maybe if this code were literally etched into the back your skull like
it is for some of us, you'd understand what a detriment it is to make
changes like this when it isn't necessary :-)
Franks a lot,
David S. Miller
davem@redhat.com
next prev parent reply other threads:[~2001-11-08 4:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-08 0:00 [PATCH] net/ipv4/*, net/core/neighbour.c jiffies cleanup Tim Schmielau
2001-11-08 0:09 ` David S. Miller
2001-11-08 0:36 ` Andreas Dilger
2001-11-08 0:44 ` David S. Miller
2001-11-08 0:58 ` Tim Schmielau
2001-11-08 1:09 ` David S. Miller
2001-11-08 1:20 ` Tim Schmielau
2001-11-08 1:36 ` David S. Miller
2001-11-08 4:32 ` Andreas Dilger
2001-11-08 4:39 ` David S. Miller [this message]
2001-11-08 1:22 ` Linus Torvalds
2001-11-08 17:54 ` kuznet
2001-11-08 18:10 ` Tim Schmielau
2001-11-08 18:10 ` Andreas Dilger
2001-11-08 18:32 ` kuznet
-- strict thread matches above, loose matches on Subject: below --
2001-11-08 3:07 Krishna Kumar
2001-11-08 5:26 ` Linus Torvalds
2001-11-08 16:55 Krishna Kumar
2001-11-08 17:10 ` Linus Torvalds
2001-11-08 18:01 ` Andreas Dilger
2001-11-09 10:43 ` Vino Thomas
2001-11-08 17:47 Krishna Kumar
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=20011107.203954.118627544.davem@redhat.com \
--to=davem@redhat.com \
--cc=adilger@turbolabs.com \
--cc=ak@muc.de \
--cc=andrewm@uow.edu.au \
--cc=jgarzik@mandrakesoft.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=tim@physik3.uni-rostock.de \
--cc=torvalds@transmeta.com \
/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.