From: Segher Boessenkool <segher@kernel.crashing.org>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org,
Stuart Yoder <b08248@freescale.com>
Subject: Re: [RFC] powerpc: Document new property called interrupt-parents
Date: Wed, 28 Feb 2007 02:09:49 +0100 [thread overview]
Message-ID: <58f8dd3e83ff9ec2936e4cc735d9ff25@kernel.crashing.org> (raw)
In-Reply-To: <20070228005615.GE11775@localhost.localdomain>
>> +Note: each interrupt parent in the interrupt-parents array can
>> +potentially specify a different value for #interrupt-cells. The
>> number
>> +of #interrupt-cells for each parent must be determined to correctly
>> +parser the interrupts property.
>
> I suggest your example actually show this case, since it's the more
> general.
But it won't very likely happen in reality, unlike
the nested-identical-PICs case.
Segher
next prev parent reply other threads:[~2007-02-28 1:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-27 22:54 [RFC] powerpc: Document new property called interrupt-parents Stuart Yoder
2007-02-27 23:40 ` Segher Boessenkool
2007-02-28 0:56 ` David Gibson
2007-02-28 1:09 ` Segher Boessenkool [this message]
2007-02-28 15:56 ` Yoder Stuart-B08248
2007-02-28 18:54 ` Segher Boessenkool
2007-02-28 23:38 ` David Gibson
2007-03-01 1:55 ` Segher Boessenkool
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=58f8dd3e83ff9ec2936e4cc735d9ff25@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=b08248@freescale.com \
--cc=david@gibson.dropbear.id.au \
--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).