Re: [PATCH 3/5] Make set_wrprotect() value safe

* Zachary Amsden ([email protected]) wrote:
> The macro set_wrprotect() should not be defined to have a value.  Make it
> a do {} while(0) instead of ({}).
> Noticed by Chris Wright.

I already fixed that one in the virt-2.6 git tree.

thanks,
-chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

References:
- [PATCH 3/5] Make set_wrprotect() value safe
  - From: Zachary Amsden <[email protected]>

Prev by Date: Re: question on memory barrier
Next by Date: Re: [RFC][PATCH] VFS: update documentation (take #2)
Previous by thread: [PATCH 3/5] Make set_wrprotect() value safe
Next by thread: [PATCH 4/5] Add address translation
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind]