From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: Julia Lawall <julia@diku.dk>
Cc: Kurt Garloff <garloff@suse.de>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 3/5] drivers/scsi: Use DIV_ROUND_CLOSEST
Date: Sun, 2 Aug 2009 22:44:42 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0908022235310.12625@axis700.grange> (raw)
In-Reply-To: <Pine.LNX.4.64.0908012149050.25693@ask.diku.dk>
On Sat, 1 Aug 2009, Julia Lawall wrote:
> From: Julia Lawall <julia@diku.dk>
>
> The kernel.h macro DIV_ROUND_CLOSEST performs the computation (x + d/2)/d
> but is perhaps more readable.
>
> The semantic patch that makes this change is as follows:
> (http://www.emn.fr/x-info/coccinelle/)
>
> // <smpl>
> @haskernel@
> @@
>
> #include <linux/kernel.h>
>
> @depends on haskernel@
> expression x,__divisor;
> @@
>
> - (((x) + ((__divisor) / 2)) / (__divisor))
> + DIV_ROUND_CLOSEST(x,__divisor)
> // </smpl>
>
> Signed-off-by: Julia Lawall <julia@diku.dk>
>
> ---
> drivers/scsi/tmscsim.c | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> Diff --git a/drivers/scsi/tmscsim.c b/drivers/scsi/tmscsim.c
> index 9a42734..7322f30 100644
> --- a/drivers/scsi/tmscsim.c
> +++ b/drivers/scsi/tmscsim.c
> @@ -1125,7 +1125,8 @@ dc390_MsgIn_set_sync (struct dc390_acb* pACB, struct dc390_srb* pSRB)
> {
> if (! (bval & FAST_SCSI)) wval1++;
> printk (KERN_INFO "DC390: Target %i: Sync transfer %i.%1i MHz, Offset %i\n", pDCB->TargetID,
> - 40/wval1, ((40%wval1)*10+wval1/2)/wval1, pDCB->SyncOffset & 0x0f);
> + 40/wval1, DIV_ROUND_CLOSEST((40 % wval1) * 10, wval1),
> + pDCB->SyncOffset & 0x0f);
> }
>
> dc390_reprog (pACB, pDCB);
With all my respect to these scripted clean-up efforts, I am not sure this
really improves anything. I.e., I am not sure, that
z = DIV_ROUND_CLOSEST(x, y);
is better readable than
z = (x + y / 2) / y;
Besides, I do realise, that tmscsim.c indentation is dreadful (legacy
code...) but this patch changes it further from
printk("...",
x,
y);
to
printk("...",
x,
y);
which doesn't seem like an improvement to me either. That said, this does
compile, and I don't see why this shouldn't work, so, if we really want
this change here's the
Acked-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/
next prev parent reply other threads:[~2009-08-02 20:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-01 19:49 Julia Lawall
2009-08-02 20:44 ` Guennadi Liakhovetski [this message]
2009-08-03 9:21 ` Julia Lawall
2009-08-03 9:22 ` Julia Lawall
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=Pine.LNX.4.64.0908022235310.12625@axis700.grange \
--to=g.liakhovetski@gmx.de \
--cc=garloff@suse.de \
--cc=julia@diku.dk \
--cc=kernel-janitors@vger.kernel.org \
--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
all inboxes | Powered by JetHome®