From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Matt Sealey" <matt@genesi-usa.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: use of fsl, in lite5200b.dts in git current
Date: Wed, 7 Nov 2007 17:18:09 -0500 [thread overview]
Message-ID: <9e4733910711071418u5914f188nffc7ab50e62cc88e@mail.gmail.com> (raw)
In-Reply-To: <4732396D.4040904@genesi-usa.com>
On 11/7/07, Matt Sealey <matt@genesi-usa.com> wrote:
> Jon Smirl wrote:
> > Sometimes the fsl prefix is being used and sometimes it isn't. Look at
> > the two compatible strings. Which way is it going to be? Is
> > fsl,has-wdt right?
>
> fsl,has-wdt is right, at least since someone changed it.
What's the story with compatible?
I would think the gdt entries are wrong.
gpt@600 { // General Purpose Timer
compatible = "fsl,mpc5200b-gpt","fsl,mpc5200-gpt";
code in drivers/watchdog/mpc5200_wdt.c would need to be changed to.
drivers/watchdog/mpc5200_wdt.c: { .compatible = "fsl,mpc5200-gpt", },
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2007-11-07 22:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 21:55 use of fsl, in lite5200b.dts in git current Jon Smirl
2007-11-07 22:17 ` Matt Sealey
2007-11-07 22:18 ` Jon Smirl [this message]
2007-11-08 20:40 ` Jon Smirl
2007-11-08 20:47 ` Scott Wood
2007-11-08 20:51 ` Jon Smirl
2007-11-08 20:56 ` Scott Wood
2007-11-08 21:53 ` Jon Smirl
2007-11-08 22:03 ` Scott Wood
2007-11-08 22:17 ` Jon Smirl
2007-11-08 22:30 ` Scott Wood
2007-11-08 20:50 ` Grant Likely
2007-11-07 22:21 ` Jon Smirl
2007-11-08 0:30 ` Matt Sealey
2007-11-08 2:15 ` Jon Smirl
2007-11-08 16:28 ` Scott Wood
2007-11-08 17:04 ` Jon Smirl
2007-11-08 19:48 ` Matt Sealey
2007-11-08 19:57 ` Jon Loeliger
2007-11-10 14:09 ` Matt Sealey
2007-11-08 20:39 ` Jon Smirl
2007-11-08 3:14 ` Grant Likely
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=9e4733910711071418u5914f188nffc7ab50e62cc88e@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=matt@genesi-usa.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).