From: Segher Boessenkool <segher@kernel.crashing.org>
To: olof@lixom.net (Olof Johansson)
Cc: linuxppc-dev@ozlabs.org,
Yoder Stuart-B08248 <stuart.yoder@freescale.com>
Subject: Re: [Fwd: [PATCH Resend 01/02] Add Linux ASMP support for MPC8641D]
Date: Thu, 22 Mar 2007 17:13:10 +0100 [thread overview]
Message-ID: <9b696f240ad2e61f74162bba8fc51947@kernel.crashing.org> (raw)
In-Reply-To: <20070322155155.GA19903@lixom.net>
> This is quite a special case. Having a brand new property for it might
> be a good idea. It's a pretty big hack anyway, so adding another one to
> the device tree isn't that big a deal.
Yes please. If you must put this information in a
property in the mpic node (I'm not convinced you should,
but I haven't really looked at it either), please don't
overload the existing "interrupts" semantics -- just use
a different property name (and choose some descriptive
new name, not something too generic).
Segher
next prev parent reply other threads:[~2007-03-22 16:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 14:25 [Fwd: [PATCH Resend 01/02] Add Linux ASMP support for MPC8641D] Jon Loeliger
2007-03-22 14:46 ` Kumar Gala
2007-03-22 15:32 ` Yoder Stuart-B08248
2007-03-22 15:40 ` Kumar Gala
2007-03-22 15:51 ` Olof Johansson
2007-03-22 15:44 ` Kumar Gala
2007-03-22 15:58 ` Yoder Stuart-B08248
2007-03-22 16:11 ` Kumar Gala
2007-03-22 21:01 ` Benjamin Herrenschmidt
2007-03-22 21:25 ` Kumar Gala
2007-03-22 23:02 ` Segher Boessenkool
2007-03-22 16:13 ` Segher Boessenkool [this message]
2007-03-23 3:55 ` Milton Miller
[not found] <mailman.532.1174628450.2645.linuxppc-dev@ozlabs.org>
2007-03-28 20:40 ` Siva Prasad
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=9b696f240ad2e61f74162bba8fc51947@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=olof@lixom.net \
--cc=stuart.yoder@freescale.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).