From: Timur Tabi <timur@freescale.com>
To: linuxppc-dev@ozlabs.org, galak@kernel.crashing.org,
benh@kernel.crashing.org, jonsmirl@gmail.com, arnd@arndb.de,
geert.uytterhoeven@sonycom.com
Subject: [PATCH 0/2] [V2] introduce macro spin_event_timeout()
Date: Tue, 26 May 2009 10:21:40 -0500 [thread overview]
Message-ID: <1243351302-32062-1-git-send-email-timur@freescale.com> (raw)
Introduce the spin_event_timeout() macro, and update the QE library to use it.
This version changes 'ret' to a return value of the macro instead of a
variable that's passed as a parameter.
next reply other threads:[~2009-05-26 15:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-26 15:21 Timur Tabi [this message]
2009-05-26 15:21 ` [PATCH 1/2] [PATCH 1/2 v9] powerpc: introduce macro spin_event_timeout() Timur Tabi
2009-05-26 15:21 ` [PATCH 2/2] [PATCH 2/2 v2] qe: add polling timeout to qe_issue_cmd() Timur Tabi
2009-06-16 23:58 ` Kumar Gala
2009-05-26 19:25 ` [PATCH 1/2] [PATCH 1/2 v9] powerpc: introduce macro spin_event_timeout() Geoff Thorpe
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=1243351302-32062-1-git-send-email-timur@freescale.com \
--to=timur@freescale.com \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=galak@kernel.crashing.org \
--cc=geert.uytterhoeven@sonycom.com \
--cc=jonsmirl@gmail.com \
--cc=linuxppc-dev@ozlabs.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).