public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Evgeniy Polyakov <zbr@ioremap.net>
To: NeilBrown <neilb@suse.de>
Cc: linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH 2/2] ARM: omap_hdq: use wait_event_timeout to wait for read to complete.
Date: Wed, 2 May 2012 01:42:19 +0400	[thread overview]
Message-ID: <20120501214219.GB15560@ioremap.net> (raw)
In-Reply-To: <20120425124153.2afa318b@notabene.brown>

On Wed, Apr 25, 2012 at 12:41:53PM +1000, NeilBrown (neilb@suse.de) wrote:
> There is no gain in having a loop - there is no risk of missing the
> interrupt with wait_event_timeout.
> 
> Signed-off-by: NeilBrown <neilb@suse.de>

Both patches look good, thank you
Feel free to add my ack if needed

-- 
	Evgeniy Polyakov

  reply	other threads:[~2012-05-01 21:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-25  2:41 [PATCH 2/2] ARM: omap_hdq: use wait_event_timeout to wait for read to complete NeilBrown
2012-05-01 21:42 ` Evgeniy Polyakov [this message]
2012-05-02  6:27   ` NeilBrown

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=20120501214219.GB15560@ioremap.net \
    --to=zbr@ioremap.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=neilb@suse.de \
    /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