From: David Miller <davem@davemloft.net>
To: Frank.Li@freescale.com
Cc: lznuaa@gmail.com, richardcochran@gmail.com, shawn.guo@linaro.org,
linux-arm-kernel@lists.infradead.or, netdev@vger.kernel.org,
bhutchings@solarflare.com
Subject: Re: [PATCH 2/2] net: fec: reduce spin lock time in fec_ptp_adjfreq
Date: Wed, 07 Nov 2012 18:53:04 -0500 (EST) [thread overview]
Message-ID: <20121107.185304.1774660119595460505.davem@davemloft.net> (raw)
In-Reply-To: <1352268889-16836-1-git-send-email-Frank.Li@freescale.com>
From: Frank Li <Frank.Li@freescale.com>
Date: Wed, 7 Nov 2012 14:14:49 +0800
> move below calculate out of spin lock section
> diff = fep->cc.mult;
> diff *= ppb;
> diff = div_u64(diff, 1000000000ULL);
>
> diff is local variable and not neccesary in spin lock
>
> Signed-off-by: Frank Li <Frank.Li@freescale.com>
Also applied, thanks.
prev parent reply other threads:[~2012-11-07 23:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-07 6:14 [PATCH 2/2] net: fec: reduce spin lock time in fec_ptp_adjfreq Frank Li
2012-11-07 8:33 ` Richard Cochran
2012-11-07 23:53 ` 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=20121107.185304.1774660119595460505.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Frank.Li@freescale.com \
--cc=bhutchings@solarflare.com \
--cc=linux-arm-kernel@lists.infradead.or \
--cc=lznuaa@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=shawn.guo@linaro.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;
as well as URLs for NNTP newsgroup(s).