Thread (12 messages) 12 messages, 3 authors, 2012-11-06

Re: [PATCH 0/3] capebus moving omap_devices to mach-omap2

From: Pantelis Antoniou <hidden>
Date: 2012-11-06 13:55:12
Also in: linux-omap, lkml


Από το iPhone μου

6 Νοε 2012, 12:16, ο/η Grant Likely [off-list ref] έγραψε:
On Tue, Nov 6, 2012 at 8:14 AM, Pantelis Antoniou
[off-list ref] wrote:
quoted
On Nov 6, 2012, at 4:06 AM, Joel A Fernandes wrote:
quoted
Sure, so if we add data type supplementary properties to the tree to
indicate the data type as "indirect phandle", then kernel could refer
to the index in the got-like table to fetch the actual phandle address
(1-level of indirection), instead of directly using the address in the
data field.
I'm fine with this.
But if the data about phandles is already in the tree, then the need
for a GOT simply goes away. The phandles can be fixed up directly and
it is so much better because it works with existing parsing code after
the merge is applied.
Either way works. It is your call after all. 
I agree that your method is simpler. 
g.
Regards

-- Pantelis--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help