ux500: Export SoC information and some platform clean-up
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 6 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 6 patches the cover letter announces are in this archive.
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 9 lines · Greg KH
Quoted 5 lines · Lee Jones
This patch-set satisfies 4 objectives:
1. Ensures each platform device can specify a suitable parent
2. Provides a bus for SoC devices as a means to export information
3. Allows ux500 to make use of the new SoC bus
4. Cleans up unnecessary complexity from ux500 codeI've applied the driver-core bits, nice job in sticking with this. I'll let the other bits trickle through the arch-specific trees.
Ok, very good. Thanks both of you for your patience. I'm looking forward to many good patches from Lee now that he has made it through this.
IIRC it was mostly an attempt for Lee to start contributing one of the "simpler" patches from the st-ericsson internal tree in order to get started. My feeling is that almost any other patch would have been easier because it does not involve infrastructure and APIs, but this was certainly a learning experience ;-).
I've applied the ux500 patches onto the ux500/soc branch of the arm-soc tree now and added the current head of the driver-core tree as the next/driver-core branch in the same tree. I will keep track of this and send out the ux500 patches during the next merge window after the core changes have been merged. Other platforms are very welcome to send patches based on the same interface for 3.4. I know from working with Greg that he does not rebase his trees, so I assume this is the best approach.
Arnd