From: Segher Boessenkool <segher@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Paul Mackerras <paulus@samba.org>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH v2]: Fix e500 v2 core reboot bug
Date: Wed, 30 May 2007 17:21:25 +0200 [thread overview]
Message-ID: <e868acb03f9976b619eac6b988a10144@kernel.crashing.org> (raw)
In-Reply-To: <976AFF56-7590-46B9-ADCA-4FA6673D4C9B@kernel.crashing.org>
>> I'm thinking have a guts block and putting a property in it makes the
>> most sense.
>
> After some discussion on IRC I think the following is the suggested
> node we should add in.
>
> guts@e00000 {
> compatible = "fsl,mpc8548-guts";
> reg = <e00000 1000>;
> fsl,has-rstcr;
> };
Except you shouldn't call it "guts".
Segher
next prev parent reply other threads:[~2007-05-30 15:21 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 2:36 [PATCH v2]: Fix e500 v2 core reboot bug Zang Roy-r61911
2007-05-29 17:38 ` Andy Fleming
2007-05-29 19:29 ` Kumar Gala
2007-05-30 2:34 ` Zang Roy-r61911
2007-05-30 2:40 ` Kumar Gala
2007-05-30 5:46 ` Zang Roy-r61911
2007-05-30 12:25 ` Kumar Gala
2007-05-30 13:49 ` Kumar Gala
2007-05-30 15:21 ` Segher Boessenkool [this message]
2007-05-31 5:32 ` Zang Roy-r61911
2007-05-31 5:52 ` Benjamin Herrenschmidt
2007-05-31 3:40 ` Zang Roy-r61911
2007-06-04 8:28 ` Zang Roy-r61911
2007-06-04 8:41 ` Segher Boessenkool
2007-06-04 9:01 ` Zang Roy-r61911
2007-06-04 10:37 ` Segher Boessenkool
2007-06-05 2:15 ` Zang Roy-r61911
2007-05-31 2:38 ` Zang Roy-r61911
2007-06-12 9:08 ` [PATCH v3]: " Zang Roy-r61911
2007-06-12 16:18 ` Timur Tabi
2007-06-13 4:44 ` Segher Boessenkool
2007-06-13 5:45 ` Zang Roy-r61911
2007-06-13 6:24 ` Zang Roy-r61911
2007-06-13 6:43 ` Zang Roy-r61911
2007-06-13 6:57 ` Segher Boessenkool
2007-06-13 7:04 ` Segher Boessenkool
2007-06-13 6:16 ` Zang Roy-r61911
2007-06-13 6:28 ` Segher Boessenkool
2007-06-13 6:31 ` Zang Roy-r61911
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=e868acb03f9976b619eac6b988a10144@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=galak@kernel.crashing.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.