From: Chris Snook <csnook@redhat.com> Date: Mon, 13 Aug 2007 07:24:52 -0400 > From: Chris Snook <csnook@redhat.com> > > Use volatile consistently in atomic.h on m32r. > > Signed-off-by: Chris Snook <csnook@redhat.com> Thanks, Acked-by: Hirokazu Takata <takata@linux-m32r.org> - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [PATCH 11/23] make atomic_read() and atomic_set() behavior consistent on m32r
- From: Hirokazu Takata <takata@linux-m32r.org>
- Re: [PATCH 11/23] make atomic_read() and atomic_set() behavior consistent on m32r
- References:
- [PATCH 0/23] make atomic_read() and atomic_set() behavior consistent across all architectures
- From: Chris Snook <csnook@redhat.com>
- [PATCH 11/23] make atomic_read() and atomic_set() behavior consistent on m32r
- From: Chris Snook <csnook@redhat.com>
- [PATCH 0/23] make atomic_read() and atomic_set() behavior consistent across all architectures
- Prev by Date: Re: [linux-usb-devel] on the system with companion host controller, error -71 returns
- Next by Date: Re: [patch] add some Blackfin specific checks to checkpatch.pl
- Previous by thread: [PATCH 11/23] make atomic_read() and atomic_set() behavior consistent on m32r
- Next by thread: Re: [PATCH 11/23] make atomic_read() and atomic_set() behavior consistent on m32r
- Index(es):
![]() |