From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Vitaly Bordug <vbordug@ru.mvista.com>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: new IRQ stuff : some details?
Date: Fri, 14 Jul 2006 05:55:10 +1000 [thread overview]
Message-ID: <1152820510.23037.21.camel@localhost.localdomain> (raw)
In-Reply-To: <20060713220628.54c2912d@vitb.ru.mvista.com>
On Thu, 2006-07-13 at 22:06 +0400, Vitaly Bordug wrote:
> Hi Ben,
>
> As your irq rewrite touched mainstream, I am wondering about some details/directions to move fw and
> update the boards up to it. Currently, the irq numbers are messed (since the board has 2 Int controllers), and I am assuming some touch to devicetree is needed, but not sure what exactly.
>
>
> Sorry if it have been brought up somewhere...
It certainly needs some documentation update... I'm travelling at the
moment, but soon. Discussion is welcome :)
Ben.
prev parent reply other threads:[~2006-07-13 19:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-13 18:06 new IRQ stuff : some details? Vitaly Bordug
2006-07-13 19:55 ` 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=1152820510.23037.21.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=vbordug@ru.mvista.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).