arm/dt: Print machine name after dt probe
PATCH 1/1 arm/dt: Print machine name after dt probe
To match the behaviour of mach_type probing
---
Hi Jeremy,
I've got this patch in my tree. I'm going to squash it into "arm/dt:
probe for platforms via the device tree".
g.
arch/arm/kernel/devtree.c | 4 +++- 1 files changed, 3 insertions(+), 1 deletions(-)
arch/arm/kernel/devtree.c +3 -1
@@ -98,8 +98,10 @@ struct machine_desc * __init parse_devicetree(unsigned int machid, dt_root =of_get_flat_dt_root ();for (mdesc = &__arch_info_begin; mdesc < &__arch_info_end; mdesc++) -if (mdesc->probe_dt && mdesc->probe_dt (dt_root)) +if (mdesc->probe_dt && mdesc->probe_dt (dt_root)) { +printk ("Machine: %s\n" , mdesc->name);return mdesc; + }return NULL ; }
Hi Grant,
Quoted 9 lines
To match the behaviour of
mach_typeprobingSigned-off-by Grant Likely <grant.likely-s3s/[email protected]>---
Hi Jeremy,
I've got this patch in my tree. I'm going to squash it into "arm/dt:
probe for platforms via the device tree".
Looks good. How do you want to manage the trees from here? Are you going to adopt my arm-dt branch (and related branches), or should I keep maintaining it?
Cheers,
Jeremy
A message that is not in the archive (sent off-list or not yet received): 1280371228.11181.9.camel-353AF/[email protected]
Quoted 7 lines · Jeremy Kerr
Hi Grant,
Quoted 5 lines
To match the behaviour of
mach_typeprobingSigned-off-by Grant Likely <grant.likely-s3s/[email protected]>---
Quoted 8 lines
Quoted 4 lines
Hi Jeremy,
I've got this patch in my tree. I'm going to squash it into "arm/dt:
probe for platforms via the device tree".Looks good. How do you want to manage the trees from here? Are you going to adopt my arm-dt branch (and related branches), or should I keep maintaining it?
I'm treating my tree as a staging point for linux-next; so I'm happy to cherry pick and stabilize patches, but unfortunately it also means I'm going to continue to rebase a lot, which could mess you up a lot. Let's talk about it on IRC tomorrow night (morning for you)
g.