From: Greg KH <gregkh@linuxfoundation.org>
To: Bhumika Goyal <bhumirks@gmail.com>
Cc: <outreachy-kernel@googlegroups.com>
Subject: Re: [Outreachy kernel] [PATCH] Staging: comedi: Use DIV_ROUND_CLOSEST
Date: Fri, 26 Feb 2016 06:43:53 +0000 [thread overview]
Message-ID: <20160226064352.GA11521@kroah.com> (raw)
In-Reply-To: <1456467894-14246-1-git-send-email-bhumirks@gmail.com>
On Fri, Feb 26, 2016 at 11:54:54AM +0530, Bhumika Goyal wrote:
> The macro DIV_ROUND_CLOSEST performs the computation (x + d/2)/d and
> makes the code more readable.
> Done using coccinelle:
>
> @@
> expression x,divisor;
> @@
> - (((x) + ((divisor) / 2)) / (divisor))
> + DIV_ROUND_CLOSEST(x,divisor)
>
> Signed-off-by: Bhumika Goyal <bhumirks@gmail.com>
> ---
> drivers/staging/comedi/drivers/ni_mio_common.c | 18 +++++++-----------
> 1 file changed, 7 insertions(+), 11 deletions(-)
Why did you sent this out twice?
Please resend it just once :)
next prev parent reply other threads:[~2016-02-26 6:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 6:24 [PATCH] Staging: comedi: Use DIV_ROUND_CLOSEST Bhumika Goyal
2016-02-26 6:43 ` Greg KH [this message]
2016-02-26 7:12 ` [RESEND PATCH] " Bhumika Goyal
2016-03-05 22:55 ` [Outreachy kernel] " Greg KH
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=20160226064352.GA11521@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bhumirks@gmail.com \
--cc=outreachy-kernel@googlegroups.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.