From: Peter Zijlstra <peterz@infradead.org>
To: Jean Delvare <khali@linux-fr.org>
Cc: "Darrick J. Wong" <djwong@us.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
lm-sensors <lm-sensors@lm-sensors.org>,
Julia Lawall <julia@diku.dk>
Subject: Re: [PATCH 1/2] Create a DIV_ROUND_CLOSEST macro to do division with rounding
Date: Mon, 03 Aug 2009 14:27:21 +0200 [thread overview]
Message-ID: <1249302441.7924.70.camel@twins> (raw)
In-Reply-To: <20090803142138.51738a18@hyperion.delvare>
On Mon, 2009-08-03 at 14:21 +0200, Jean Delvare wrote:
> > The proposed thing is simply DIV_ROUND, but this DIV_ROUND_CLOSEST name
> > is just wonky.
>
> I can't disagree. I even think I argued about it back then, but then
> finally gave up. You should have participated in the debate when it was
> hot rather than 8 months later :(
Yeah, sometimes its hard to keep up with all on lkml, I only noticed it
because I ran into some code that used it.
Agreed on the other points.
prev parent reply other threads:[~2009-08-03 12:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 1:01 [PATCH 1/2] Create a DIV_ROUND_CLOSEST macro to do division with rounding Darrick J. Wong
2008-11-11 1:01 ` [PATCH 2/2] adt74{62, 70, 73}: Use DIV_ROUND_CLOSEST for rounded division Darrick J. Wong
2008-11-11 10:04 ` [PATCH 1/2] Create a DIV_ROUND_CLOSEST macro to do division with rounding Jean Delvare
2008-11-11 17:07 ` Andrew Morton
2008-11-11 17:11 ` Jean Delvare
2008-11-11 18:51 ` Joe Perches
2008-11-11 23:05 ` [lm-sensors] " Trent Piepho
2008-11-11 23:20 ` Andrew Morton
2008-11-11 23:42 ` Trent Piepho
2008-11-12 0:08 ` Andrew Morton
2008-11-14 21:46 ` Trent Piepho
2008-11-14 22:24 ` Andrew Morton
2008-11-11 23:50 ` Jochen Voß
2009-08-03 11:57 ` Peter Zijlstra
2009-08-03 12:21 ` Jean Delvare
2009-08-03 12:27 ` Peter Zijlstra [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=1249302441.7924.70.camel@twins \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=djwong@us.ibm.com \
--cc=julia@diku.dk \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.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