From: Jarek Poplawski <jarkao2@o2.pl>
To: Satyam Sharma <satyam.sharma@gmail.com>
Cc: "Pallipadi\, Venkatesh" <venkatesh.pallipadi@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Oleg Nesterov <oleg@tv-sign.ru>
Subject: Re: [PATCH -mm] timer: parenthesis fix in tbase_get_deferrable() etc.
Date: Thu, 10 May 2007 07:52:57 +0200 [thread overview]
Message-ID: <20070510055256.GB1611@ff.dom.local> (raw)
In-Reply-To: <a781481a0705091129t6a348fb7ya2a225123fca3f6@mail.gmail.com>
On Wed, May 09, 2007 at 11:59:39PM +0530, Satyam Sharma wrote:
> On 5/9/07, Pallipadi, Venkatesh <venkatesh.pallipadi@intel.com> wrote:
> >
> >>-----Original Message-----
> >>From: Jarek Poplawski [mailto:jarkao2@o2.pl]
> >>Sent: Tuesday, May 08, 2007 10:32 PM
> >>To: Andrew Morton
> >>Cc: Pallipadi, Venkatesh; linux-kernel@vger.kernel.org; Oleg Nesterov
> >>Subject: Re: [PATCH -mm] timer: parenthesis fix in
> >>tbase_get_deferrable() etc.
> >>
> >>On Tue, May 08, 2007 at 04:33:58PM -0700, Andrew Morton wrote:
> >>> On Tue, 8 May 2007 12:33:48 +0200
> >>> Jarek Poplawski <jarkao2@o2.pl> wrote:
...
> >>> > static inline unsigned int tbase_get_deferrable(tvec_base_t *base)
> >>> > {
> >>> > - return ((unsigned int)(unsigned long)base &
> >>TBASE_DEFERRABLE_FLAG);
> >>> > + return (unsigned int)((unsigned long)base &
> >>TBASE_DEFERRABLE_FLAG);
> >>> > }
> >>...
> >>> The change makes sense, but does it actually "fix" anything?
> >>>
> >>
> >>Yes - this first place fixes logical error, so it's a sin
> >>- even if not punishable in practice. (It's also unnecessary
> >>test for long to int conversion.)
> >>
> >
> >I am sorry, I don't understand. What is the logical error in the first
> >one?
I am sorry, too - for my "logic". It seems it's all correct!
(Except, I don't know what's going here...)
> >
> >Actually, your change makes it different from what was originally
> >indended.
> >Original intention was to type convert base to a 32 bit value and
> >bitwise& with FLAG.
>
> But that is not what the original code is doing. If you wanted to
> typecast "base" to "a 32 bit value" then you should've used u32
> instead.
>
> Anyway, if you originally intended to actually typecast "base" to
> unsigned int, then you could do that directly without typecasting it
> first to unsigned long (unnecessarily) and then to unsigned int. Of
> course, if your system implements a pointer as something bigger than
> unsigned int (which is what you eventually convert "base" to), then
> you're screwed anyway and the intermediate typecast to unsigned long
> doesn't buy you anything at all.
>
> The other 3 changes in this patch were clearly meaningless, though.
>
((unsigned int)(unsigned long)base ...
((tvec_base_t *)((unsigned long)base ...
((tvec_base_t *)((unsigned long)(timer->base) ...
(tvec_base_t *)((unsigned long)(new_base) ...
Yes, if you don't count reading this one close each other, they are
clearly meaningles.
Regards,
Jarek P.
prev parent reply other threads:[~2007-05-10 5:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-08 10:33 [PATCH -mm] timer: parenthesis fix in tbase_get_deferrable() etc Jarek Poplawski
2007-05-08 23:33 ` Andrew Morton
2007-05-09 5:31 ` Jarek Poplawski
2007-05-09 15:59 ` Pallipadi, Venkatesh
2007-05-09 18:29 ` Satyam Sharma
2007-05-09 19:10 ` Pallipadi, Venkatesh
2007-05-10 7:39 ` Jarek Poplawski
2007-05-10 7:57 ` Andrew Morton
2007-05-10 9:29 ` [PATCH] timer: revert " Jarek Poplawski
2007-05-10 9:35 ` Jarek Poplawski
2007-05-10 8:26 ` [PATCH -mm] timer: " Satyam Sharma
2007-05-10 9:32 ` Satyam Sharma
2007-05-10 5:52 ` Jarek Poplawski [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=20070510055256.GB1611@ff.dom.local \
--to=jarkao2@o2.pl \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@tv-sign.ru \
--cc=satyam.sharma@gmail.com \
--cc=venkatesh.pallipadi@intel.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.