All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Timur Tabi <timur@freescale.com>
Cc: Linuxppc-dev Development <linuxppc-dev@ozlabs.org>
Subject: Re: removing get_immrbase()??
Date: Wed, 22 Apr 2009 15:20:29 -0500	[thread overview]
Message-ID: <49EF7C0D.4040509@freescale.com> (raw)
In-Reply-To: <49EF7B1C.2080105@freescale.com>

Timur Tabi wrote:
> Scott Wood wrote:
>> Timur Tabi wrote:
>>>>        these two are related and seem like we could look for "fsl,cpm2"
>>> That's okay, as long as you don't break compatibility with older
>>> device trees that don't have that property, unless you can demonstrate
>>> that these trees would never work with the current kernel anyway.
>> All CPM2 device trees should have fsl,cpm2 listed in the compatible of 
>> the CPM node.
> 
> Yes, but did they always have that compatible field? 

Yes, except for trees from the previous era of CPM2 bindings which are 
not supported at all.  This isn't new.

-Scott

  reply	other threads:[~2009-04-22 20:20 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-22 18:38 removing get_immrbase()?? Kumar Gala
2009-04-22 19:35 ` Timur Tabi
2009-04-22 20:16   ` Scott Wood
2009-04-22 20:16     ` Timur Tabi
2009-04-22 20:20       ` Scott Wood [this message]
2009-04-22 21:31       ` Kumar Gala
2009-04-22 21:33         ` Timur Tabi
2009-04-22 21:39           ` Kumar Gala
2009-04-22 21:46             ` Timur Tabi
2009-04-22 21:54               ` Kumar Gala
2009-04-22 21:57                 ` Timur Tabi
2009-04-22 22:07                   ` Kumar Gala
2009-04-22 22:00               ` Scott Wood
2009-04-22 22:00                 ` Timur Tabi
2009-04-23 13:54             ` Grant Likely
2009-04-22 21:38         ` Scott Wood
2009-04-22 21:55           ` Kumar Gala
2009-04-22 22:33             ` Scott Wood
2009-04-23  0:03               ` Timur Tabi
2009-04-23  2:26             ` David Gibson
2009-04-23  3:36               ` Kumar Gala
2009-04-23  4:06                 ` David Gibson
2009-04-23  4:41                   ` Kumar Gala
2009-04-28  4:12                     ` David Gibson
2009-04-28 13:48                       ` Timur Tabi
2009-04-23 13:07                 ` Timur Tabi
2009-04-23 15:56                 ` Scott Wood
2009-04-23 13:02               ` Timur Tabi
2009-04-23 13:50                 ` Anton Vorontsov
2009-04-23 14:02                   ` Timur Tabi
2009-04-23 14:06                     ` Kumar Gala
2009-04-23 14:09                       ` Timur Tabi
2009-04-24 14:40                       ` Wrobel Heinz-R39252
2009-04-23 14:13                     ` Anton Vorontsov
2009-04-23 16:00                   ` Scott Wood
2009-04-23 16:54                     ` Anton Vorontsov
2009-04-23 17:03                       ` Scott Wood
2009-04-23 17:26                         ` Anton Vorontsov
2009-04-23 17:59                           ` Scott Wood
2009-04-28  4:25                   ` David Gibson
2009-04-28  4:21                 ` David Gibson
2009-04-23 13:53         ` Grant Likely
2009-04-23 14:03           ` Anton Vorontsov
2009-04-28  4:26           ` David Gibson
2009-04-22 19:44 ` Scott Wood
2009-04-22 20:00   ` Kumar Gala
2009-04-22 20:30   ` Scott Wood
2009-04-23 13:53 ` Arnd Bergmann

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=49EF7C0D.4040509@freescale.com \
    --to=scottwood@freescale.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=timur@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 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.