All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-scsi@vger.kernel.org, jbottomley@odin.com,
	martin.petersen@oracle.com, nico@fluxnic.net,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] scsi: use sector_div instead of do_div
Date: Wed, 25 Nov 2015 22:28:34 -0500	[thread overview]
Message-ID: <yq1bnahjv6l.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <24882658.08y4bWL6tn@wuerfel> (Arnd Bergmann's message of "Fri, 20 Nov 2015 17:38:28 +0100")

>>>>> "Arnd" == Arnd Bergmann <arnd@arndb.de> writes:

Arnd> do_div is the wrong way to divide a sector_t, as it is less
Arnd> efficient when sector_t is 32-bit wide. With the upcoming do_div
Arnd> optimizations, the kernel starts warning about this:

Applied.

-- 
Martin K. Petersen	Oracle Linux Engineering

WARNING: multiple messages have this Message-ID (diff)
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-scsi@vger.kernel.org, martin.petersen@oracle.com,
	nico@fluxnic.net, jbottomley@odin.com,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] scsi: use sector_div instead of do_div
Date: Wed, 25 Nov 2015 22:28:34 -0500	[thread overview]
Message-ID: <yq1bnahjv6l.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <24882658.08y4bWL6tn@wuerfel> (Arnd Bergmann's message of "Fri, 20 Nov 2015 17:38:28 +0100")

>>>>> "Arnd" == Arnd Bergmann <arnd@arndb.de> writes:

Arnd> do_div is the wrong way to divide a sector_t, as it is less
Arnd> efficient when sector_t is 32-bit wide. With the upcoming do_div
Arnd> optimizations, the kernel starts warning about this:

Applied.

-- 
Martin K. Petersen	Oracle Linux Engineering

WARNING: multiple messages have this Message-ID (diff)
From: martin.petersen@oracle.com (Martin K. Petersen)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] scsi: use sector_div instead of do_div
Date: Wed, 25 Nov 2015 22:28:34 -0500	[thread overview]
Message-ID: <yq1bnahjv6l.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <24882658.08y4bWL6tn@wuerfel> (Arnd Bergmann's message of "Fri, 20 Nov 2015 17:38:28 +0100")

>>>>> "Arnd" == Arnd Bergmann <arnd@arndb.de> writes:

Arnd> do_div is the wrong way to divide a sector_t, as it is less
Arnd> efficient when sector_t is 32-bit wide. With the upcoming do_div
Arnd> optimizations, the kernel starts warning about this:

Applied.

-- 
Martin K. Petersen	Oracle Linux Engineering

  parent reply	other threads:[~2015-11-26  3:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-20 16:38 [PATCH] scsi: use sector_div instead of do_div Arnd Bergmann
2015-11-20 16:38 ` Arnd Bergmann
2015-11-24 12:48 ` Johannes Thumshirn
2015-11-24 12:48   ` Johannes Thumshirn
2015-11-24 12:48   ` Johannes Thumshirn
2015-11-24 12:50 ` Sagi Grimberg
2015-11-24 12:50   ` Sagi Grimberg
2015-11-24 15:03 ` Hannes Reinecke
2015-11-24 15:03   ` Hannes Reinecke
2015-11-26  3:28 ` Martin K. Petersen [this message]
2015-11-26  3:28   ` Martin K. Petersen
2015-11-26  3:28   ` Martin K. Petersen

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=yq1bnahjv6l.fsf@sermon.lab.mkp.net \
    --to=martin.petersen@oracle.com \
    --cc=arnd@arndb.de \
    --cc=jbottomley@odin.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=nico@fluxnic.net \
    /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.