From: Kumar Gala <galak@kernel.crashing.org>
To: Timur Tabi <timur@freescale.com>
Cc: Scott Wood <scottwood@freescale.com>,
Linuxppc-dev Development <linuxppc-dev@ozlabs.org>
Subject: Re: removing get_immrbase()??
Date: Wed, 22 Apr 2009 16:39:46 -0500 [thread overview]
Message-ID: <DC91BA72-AF10-41DD-B610-EDEFD106A811@kernel.crashing.org> (raw)
In-Reply-To: <49EF8D42.7010104@freescale.com>
On Apr 22, 2009, at 4:33 PM, Timur Tabi wrote:
> Kumar Gala wrote:
>
>> I disagree. If you update your kernel you should update your device
>> tree (thus we have .dts in the kernel tree and not somewhere else).
>
> Is this a new policy? I was under the impression that supporting
> older
> device trees, if not too inconvenient, is desirable. I've nack'd
> patches before that broke backwards compatibility unnecessarily.
The specific issue I'm talking about is the addition of new nodes that
might break old device trees. I have no desire to try and say that I
can't add new nodes and code related to them just because old device
tree's didn't have them.
- k
next prev parent reply other threads:[~2009-04-22 21:41 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
2009-04-22 21:31 ` Kumar Gala
2009-04-22 21:33 ` Timur Tabi
2009-04-22 21:39 ` Kumar Gala [this message]
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=DC91BA72-AF10-41DD-B610-EDEFD106A811@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.com \
--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.