From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Haren Myneni <haren@us.ibm.com>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] powerpc: EOI and clear IPI fix in xics_teardown_cpu()
Date: Sun, 09 Jul 2006 14:08:43 +1000 [thread overview]
Message-ID: <1152418123.4128.16.camel@localhost.localdomain> (raw)
In-Reply-To: <44B06756.8090301@us.ibm.com>
> Ok, Are you talking about the patch posted
> http://ozlabs.org/pipermail/linuxppc-dev/2006-July/024350.html? Sorry, I
> did not notice it before I posted. Yes, it is fixed passing proper ipi
> value to desc->chip->eoi(). But, we also to need to clear IPI in
> xics_teardown_cpu().
Ok, I'll fix that too.
Ben.
prev parent reply other threads:[~2006-07-09 4:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-09 1:28 [PATCH] powerpc: EOI and clear IPI fix in xics_teardown_cpu() Haren Myneni
2006-07-09 1:37 ` Benjamin Herrenschmidt
2006-07-09 2:17 ` Haren Myneni
2006-07-09 4:08 ` Benjamin Herrenschmidt [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=1152418123.4128.16.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=haren@us.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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).