From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/3] Ordered I/O accessors
Date: Tue, 27 Jul 2010 12:03:10 +0100 [thread overview]
Message-ID: <20100727110310.GA11468@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20100714145802.16555.48563.stgit@e102109-lin.cambridge.arm.com>
On Wed, Jul 14, 2010 at 04:01:12PM +0100, Catalin Marinas wrote:
> This version replaces the do { ... } while (0) constructs in the final
> patch with ({ ... }) to avoid errors in drivers putting brackets around
> the write*() accessors. To avoid the write*() macro having a non-void
> type (and possibly the compiler generating code to read a register), the
> first patch explicitly casts the __raw_write*() accessors to (void).
Ok. Can you please put this in the patch system? I think we need to
get this in prior to 2.6.35 being released.
next prev parent reply other threads:[~2010-07-27 11:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-14 15:01 [PATCH v3 0/3] Ordered I/O accessors Catalin Marinas
2010-07-14 15:01 ` [PATCH v3 1/3] ARM: Introduce *_relaxed() " Catalin Marinas
2010-07-14 15:15 ` Giuseppe Calderaro
2010-07-14 15:24 ` Catalin Marinas
2010-07-14 15:01 ` [PATCH v3 2/3] ARM: Convert L2x0 to use the IO relaxed operations Catalin Marinas
2010-07-14 15:01 ` [PATCH v3 3/3] ARM: Add barriers to the I/O accessors if ARM_DMA_MEM_BUFFERABLE Catalin Marinas
2010-07-27 11:03 ` Russell King - ARM Linux [this message]
2010-07-28 12:48 ` [PATCH v3 0/3] Ordered I/O accessors Rabin VINCENT
2010-07-28 13:06 ` Will Deacon
2010-07-29 10:43 ` Russell King - ARM Linux
2010-07-29 10:44 ` Russell King - ARM Linux
2010-07-28 21:09 ` Catalin Marinas
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=20100727110310.GA11468@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).