Re: [PATCH] block/genhd.c: fix sparse warning

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Vegard Nossum
Date: Wednesday, April 15, 2009 - 9:46 pm

2009/4/16 H Hartley Sweeten <hartleys@visionengravers.com>:

Hi,

Just a heads up: There seems to be some sort of consensus that this
type of patch title is not a very good one. (What about "remove
variable shadowing"?)

It would also be nice to have an explanation of where the __mptr
symbol comes into play, because it doesn't even appear in the patch,
and reviewers would likely have an easier job if they knew where to
look it up.

Was this warning harmless, or was the code in fact broken?

Can we rewrite container_of() to not use an extra variable (__mptr),
or perhaps using an inline function for part of the computation?

Do we also have this problem in expressions like max(max(x, y), z)?

Thanks :-)


Vegard

--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[PATCH] block/genhd.c: fix sparse warning, H Hartley Sweeten, (Wed Apr 15, 6:53 pm)
Re: [PATCH] block/genhd.c: fix sparse warning, Vegard Nossum, (Wed Apr 15, 9:46 pm)
Re: [PATCH] block/genhd.c: fix sparse warning, Al Viro, (Wed Apr 15, 10:42 pm)
Re: [PATCH] block/genhd.c: fix sparse warning, Vegard Nossum, (Thu Apr 16, 12:17 am)
RE: [PATCH] block/genhd.c: fix sparse warning, H Hartley Sweeten, (Thu Apr 16, 11:03 am)
Re: [PATCH] block/genhd.c: fix sparse warning, Al Viro, (Thu Apr 16, 11:33 am)