From: Hoang-Nam Nguyen <hnguyen@linux.vnet.ibm.com>
To: Roland Dreier <rdreier@cisco.com>
Cc: heiko.carstens@de.ibm.com, linux-kernel@vger.kernel.org,
hch@infradead.org, linuxppc-dev@ozlabs.org, raisch@de.ibm.com,
general@lists.openfabrics.org
Subject: Re: [PATCH 2.6.21-rc2] ehca: fix mismatched sync between completion handler and destroy cq
Date: Fri, 2 Mar 2007 09:37:46 +0100 [thread overview]
Message-ID: <200703020937.47012.hnguyen@linux.vnet.ibm.com> (raw)
In-Reply-To: <ada8xegr7zu.fsf@cisco.com>
> > +#include <linux/completion.h>
> This can just be <linux/wait.h>, because you're only using
> wait_queue_head_t and not struct completion, right?
> I fixed this up before merging.
Yes, right. Thanks for your help!
Regards
Nam
prev parent reply other threads:[~2007-03-02 8:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-28 17:01 [PATCH 2.6.21-rc2] ehca: fix mismatched sync between completion handler and destroy cq Hoang-Nam Nguyen
2007-03-01 21:04 ` Roland Dreier
2007-03-02 8:37 ` Hoang-Nam Nguyen [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=200703020937.47012.hnguyen@linux.vnet.ibm.com \
--to=hnguyen@linux.vnet.ibm.com \
--cc=general@lists.openfabrics.org \
--cc=hch@infradead.org \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=raisch@de.ibm.com \
--cc=rdreier@cisco.com \
/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).