From: Hoang-Nam Nguyen <hnguyen@linux.vnet.ibm.com>
To: Roland Dreier <rdreier@cisco.com>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
openib-general@openib.org, hch@infradead.org, raisch@de.ibm.com,
heiko.carstens@de.ibm.com
Subject: Re: [PATCH 2.6.21-rc1 1/5] ehca: reworked irq handler to avoid/reduce missed irq events
Date: Thu, 15 Feb 2007 16:28:35 +0100 [thread overview]
Message-ID: <200702151628.35483.hnguyen@linux.vnet.ibm.com> (raw)
In-Reply-To: <adafy981jgc.fsf@cisco.com>
> Looks fine but this patch at least has serious whitespace
> damage... please resend a fixed version.
Sorry for this. Resending the patches 1-5.
Nam
next prev parent reply other threads:[~2007-02-15 15:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-14 16:40 [PATCH 2.6.21-rc1 1/5] ehca: reworked irq handler to avoid/reduce missed irq events Hoang-Nam Nguyen
2007-02-14 18:59 ` Christoph Hellwig
2007-02-14 22:08 ` Roland Dreier
2007-02-15 15:28 ` Hoang-Nam Nguyen [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-02-15 16:06 Hoang-Nam Nguyen
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=200702151628.35483.hnguyen@linux.vnet.ibm.com \
--to=hnguyen@linux.vnet.ibm.com \
--cc=hch@infradead.org \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=openib-general@openib.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