public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: dada1@cosmosbay.com
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Introduce jiffies_32 and related compare functions
Date: Tue, 12 Dec 2006 00:00:37 -0800 (PST)	[thread overview]
Message-ID: <20061212.000037.93024784.davem@davemloft.net> (raw)
In-Reply-To: <457E52A3.6060503@cosmosbay.com>

From: Eric Dumazet <dada1@cosmosbay.com>
Date: Tue, 12 Dec 2006 07:56:35 +0100

> But keeping 64bits values 'just because hardware allows us this kind of 
> expenditure' seems not reasonable to me, but lazy...

I agree with you for the most part.

Flexibility is pretty easy to maintain, and you seem to
alude to this, by allowing the jiffies_32 thing to have
a configurable type.

With this in mind maybe it's better to give the type some other more
descriptive name, something that states what the type represents,
rather than it's likely implementation :-)

      reply	other threads:[~2006-12-12  8:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200612112027.kBBKR4nG006298@shell0.pdx.osdl.net>
2006-12-11 21:23 ` [PATCH] reorder struct pipe_buf_operations Eric Dumazet
2006-12-11 22:58   ` [PATCH] Introduce jiffies_32 and related compare functions Eric Dumazet
2006-12-12  1:31     ` David Miller
2006-12-12  3:47       ` Eric Dumazet
2006-12-12  3:57         ` David Miller
2006-12-12  4:09           ` Eric Dumazet
2006-12-12  4:27             ` David Miller
2006-12-12  6:56               ` Eric Dumazet
2006-12-12  8:00                 ` 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=20061212.000037.93024784.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=akpm@osdl.org \
    --cc=dada1@cosmosbay.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