RE: Fix unlock_buffer() to work the same way as bit_unlock()
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: "Chen, Kenneth W" <kenneth.w.chen@xxxxxxxxx>
- Subject: RE: Fix unlock_buffer() to work the same way as bit_unlock()
- From: Christoph Lameter <clameter@xxxxxxx>
- Date: Wed, 29 Mar 2006 15:50:31 -0800 (PST)
- Cc: Nick Piggin <nickpiggin@xxxxxxxxxxxx>, "Boehm, Hans" <hans.boehm@xxxxxx>, "Grundler, Grant G" <grant.grundler@xxxxxx>, Zoltan Menyhart <Zoltan.Menyhart@xxxxxxx>, akpm@xxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, linux-ia64@xxxxxxxxxxxxxxx
- In-reply-to: <200603292348.k2TNmNg12952@xxxxxxxxxxxxxxxxxxxx>
- References: <200603292348.k2TNmNg12952@xxxxxxxxxxxxxxxxxxxx>
On Wed, 29 Mar 2006, Chen, Kenneth W wrote:
> Is gcc smart enough to turn constant argument and collapse inline of
> inline function? I hope it does.
Sure we use that all the time. Look at the cmpxchg definition in
asm-ia64/system.h
-
: send the line "unsubscribe linux-ia64" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Index of Archives]
[Linux Kernel]
[Sparc Linux]
[DCCP]
[Linux ARM]
[Yosemite News]
[Linux SCSI]
[Linux x86_64]
[Linux for Ham Radio]
