public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: sagig@dev•mellanox.co.il (Sagi Grimberg)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] IB/iser: use sector_div instead of do_div
Date: Sat, 21 Nov 2015 04:18:11 +0200	[thread overview]
Message-ID: <564FD463.2020205@dev.mellanox.co.il> (raw)
In-Reply-To: <5922990.8IJpyksX8K@wuerfel>


> do_div is the wrong way to divide a sector_t, as it is less
> efficient when sector_t is 32-bit wide. With the upcoming
> do_div optimizations, the kernel starts warning about this:
>
> drivers/infiniband/ulp/iser/iser_verbs.c:1296:4: note: in expansion of macro 'do_div'
> include/asm-generic/div64.h:224:22: warning: passing argument 1 of '__div64_32' from incompatible pointer type
>
> This changes the code to use sector_div instead, which always
> produces optimal code.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb•de>

Thanks Arnd,

Reviewed-by: Sagi Grimberg <sagig@mellanox•com>

      reply	other threads:[~2015-11-21  2:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-20 16:41 [PATCH] IB/iser: use sector_div instead of do_div Arnd Bergmann
2015-11-21  2:18 ` Sagi Grimberg [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=564FD463.2020205@dev.mellanox.co.il \
    --to=sagig@dev$(echo .)mellanox.co.il \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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