linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jamie@jamieiles.com (Jamie Iles)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: L2X0: add explicit cpu_relax() for busy wait loop
Date: Wed, 24 Aug 2011 15:44:46 +0100	[thread overview]
Message-ID: <20110824144446.GN23757@pulham.picochip.com> (raw)
In-Reply-To: <1314149411-5063-1-git-send-email-Baohua.Song@csr.com>

Hi Barry,

On Tue, Aug 23, 2011 at 06:30:11PM -0700, Barry Song wrote:
> using cpu_relax in busy loops is a well-known idiom in the kernel. It's more
> for documentation purposes than technically needed here.
> 
> Cc: Jamie Iles <jamie@jamieiles.com>

Reviewed-by: Jamie Iles <jamie@jamieiles.com>

for both patches!

Jamie

      parent reply	other threads:[~2011-08-24 14:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-24  1:30 [PATCH 1/2] ARM: L2X0: add explicit cpu_relax() for busy wait loop Barry Song
2011-08-24 14:35 ` Arnd Bergmann
2011-08-24 14:44 ` Jamie Iles [this message]

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=20110824144446.GN23757@pulham.picochip.com \
    --to=jamie@jamieiles.com \
    --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).