From: Mark Lord <kernel@teksavvy.com>
To: Tejun Heo <htejun@gmail.com>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>,
Jeff Garzik <jgarzik@pobox.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Ric Wheeler <rwheeler@redhat.com>
Subject: Re: [PATCH] Fix accesses at LBA28 boundary (old bug, but nasty)
Date: Wed, 07 Apr 2010 13:52:35 -0400 [thread overview]
Message-ID: <4BBCC663.2060001@teksavvy.com> (raw)
In-Reply-To: <4BBC1400.6030106@gmail.com>
On 07/04/10 01:11 AM, Tejun Heo wrote:
> Hello,
>
> On 04/07/2010 12:30 PM, Mark Lord wrote:
>> The cast was there already, so I left it there.
>> Just moved it to cover the entire compile-time expression as a unit,
>> rather than just the (u64)1 as the existing code did it.
>
> Oh, but there's functional difference between the two. In the
> original place, the initial casting ripples through the whole
> expression making each step of the calculation u64. It's meant to
> prevent int overflow during calculation (which isn't necessary in the
> current expression BTW) but if you cast the end result, it doesn't
> really mean anything. If you want to kill the casting, kill it but
> moving the casting outside doesn't make much sense. Can you repost
> without moving the cast?
..
No. But I can/did repost with it completely gone.
next prev parent reply other threads:[~2010-04-07 17:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-06 22:45 [PATCH] Fix accesses at LBA28 boundary (old bug, but nasty) Mark Lord
2010-04-06 22:47 ` Mark Lord
2010-04-07 1:29 ` Tejun Heo
2010-04-07 3:30 ` Mark Lord
2010-04-07 5:11 ` Tejun Heo
2010-04-07 17:52 ` Mark Lord [this message]
2010-04-07 17:52 ` [PATCH] Fix accesses at LBA28 boundary (old bug, but nasty) (v2) Mark Lord
2010-04-07 19:18 ` Alan Cox
2010-04-07 21:01 ` Tejun Heo
2010-04-08 17:00 ` Jeff Garzik
2010-04-15 13:46 ` Mark Lord
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=4BBCC663.2060001@teksavvy.com \
--to=kernel@teksavvy.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=rwheeler@redhat.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.