From: James Hogan <james.hogan@mips.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: <jhs@mojatatu.com>, <xiyou.wangcong@gmail.com>,
<jiri@resnulli.us>, <davem@davemloft.net>,
<netdev@vger.kernel.org>,
Stephen Hemminger <sthemmin@microsoft.com>
Subject: Re: [net-next,v2,0/2] netem: fix compilation on 32 bit
Date: Tue, 14 Nov 2017 21:23:12 +0000 [thread overview]
Message-ID: <20171114212312.GA448@jhogan-linux.mipstec.com> (raw)
In-Reply-To: <20171114192702.31193-1-sthemmin@microsoft.com>
[-- Attachment #1: Type: text/plain, Size: 551 bytes --]
On Tue, Nov 14, 2017 at 11:27:00AM -0800, Stephen Hemminger wrote:
> A couple of places where 64 bit CPU was being assumed incorrectly.
>
> Stephen Hemminger (2):
> netem: fix 64 bit divide
> netem: remove unnecessary 64 bit modulus
>
> net/sched/sch_netem.c | 17 +++++++----------
> 1 file changed, 7 insertions(+), 10 deletions(-)
> Acked-by: Randy Dunlap <rdunlap@infradead.org>
> Acked-by: Dave Taht <dave.taht@gmail.com>
These appears to fix the MIPS build, so
Tested-by: James Hogan <jhogan@kernel.org>
Thanks
James
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-11-14 21:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 19:27 [PATCH net-next v2 0/2] netem: fix compilation on 32 bit Stephen Hemminger
2017-11-14 19:27 ` [PATCH net-next v2 1/2] netem: use 64 bit divide by rate Stephen Hemminger
2017-11-14 19:27 ` [PATCH net-next v2 2/2] netem: remove unnecessary 64 bit modulus Stephen Hemminger
2017-11-14 19:40 ` [PATCH net-next v2 0/2] netem: fix compilation on 32 bit Randy Dunlap
2017-11-14 20:20 ` Dave Taht
2017-11-14 21:23 ` James Hogan [this message]
2017-11-15 5:18 ` David Miller
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=20171114212312.GA448@jhogan-linux.mipstec.com \
--to=james.hogan@mips.com \
--cc=davem@davemloft.net \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=sthemmin@microsoft.com \
--cc=xiyou.wangcong@gmail.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 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).