Migrate PXA27x platforms to clock framework
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v3 Latest posting 4/40 of 6 patches 0 repliesNew
- v3 posting 3/40 of 6 patches 0 repliesSuperseded
- v3 posting 2/40 of 6 patches 0 repliesSuperseded
Earlier versions · 2
| Version | Posted | Patches | Replies | Status |
|---|---|---|---|---|
| v3 posting 1/4 | 0 of 6 patches | 0 replies | Superseded | |
| v1 | 0 of 4 patches | 0 replies | Superseded |
Patches in v3 posting 4/4 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 v3 yet.
Cover letter [PATCH v3 0/6] Migrate PXA27x platforms to clock framework
Quoted 15 lines · Mike Turquette
Quoting Arnd Bergmann (2014-09-03 12:33:31)
Quoted 14 lines · On Wednesday 03 September 2014 11:49:56 Mike Turquette wrote:
Quoted 9 lines
Quoted 5 lines
Right, makes sense. We have in the past done it either way for other platforms. When merging the patches through the clk subsystem, it still makes sense to let us know of those plans and ask for an Ack from the arm-soc maintainers, to be sure we can plan ahead in case there are other (conflicting) patch sets that are sent through arm-soc.
Do I have your Ack for the
arch/armpatches?I have no objection to the change, but we might need to be careful in case we get a lot of conflicts.
Quoted 6 lines
Quoted 2 lines
How about making it a shared branch that you plan to send upstream but that we can also include in arm-soc to avoid conflicts if necessary?
Sounds good. I'll probably need to perform a bit of surgery on my tree and rebase it in order to have the minimum set of patches that get pulled into arm-soc.
Ok, I see. We might not pull it in right away, because it's possible that there are no actual conflicts and we don't need them, but it's definitely good if your branch is ready in case we do.
Arnd