ux500: Export SoC information and some platform clean-up
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 of 6 patches 0 repliesNew
2 of 6 patches are in this archive. The cover letter announces 6.
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 2/6 | drivers/base: add bus for System-on-Chip devices | +0 | 1 reply | |
| 2/6 | drivers/base: add bus for System-on-Chip devices | +0 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/6] ux500: Export SoC information and some platform clean-up
Quoted 16 lines · Arnd Bergmann
Quoted 8 lines · Lee Jones
Quoted 8 lines
Quoted 7 lines
Quoted 1 line
Everyone else, who is planning to use the infrastructure besides ux500?
I can easily see this being used in the ARM reference designs (Integrator, Versatile, RealView and Versatile Express) some of them I can possibly patch myself even. OMAP has expressed interest in "some way of getting the SoC ID out", and I guess this is the means to that end.
Quoted 6 lines
Quoted 3 lines
Ah, good. Once these patches are merged, we can easily refer anyone to this infrastructure if they try to add a different way of finding a SoC ID.
Okay, so this sounds promising. Which route are the patches likely to take? Will they go up through your SoC tree Arnd?
Quoted 6 lines
That's probably the best way. Of course you need to have Acks from Greg (for the bus) and Linus Walleij (for the ux500 stuff) before I can merge them. Linus can decide whether he wants to submit them to me through a pull request from his ux500 tree (with Signed-off-by) or whether I should apply them myself (with Ack).
I'll try to review these again tomorrow...