arm64: don't call early_*map() post paging_init()
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v2 Latest posting 3/32 patches 0 repliesNew
- v2 posting 2/30 of 2 patches 0 repliesSuperseded
- v2 posting 1/30 of 2 patches 0 repliesSuperseded
Patches in v2 posting 3/3 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | arm64: don't make early_*map() calls post paging_init() | +0 | 2 replies | |
| 1/2 | arm64: don't make early_*map() calls post paging_init() | +0 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.
Cover letter [PATCH v2 0/2] arm64: don't call early_*map() post paging_init()
Quoted 21 lines · Ard Biesheuvel
Quoted 20 lines · Will Deacon
Quoted 18 lines · Ard Biesheuvel
Quoted 7 lines · Leif Lindholm
Quoted 6 lines · Ard Biesheuvel
Quoted 6 lines
Quoted 5 lines
Changes since v1:
- Rebased to v3.19-rc3
- Added 'Fixes:' tags
- Reworked 1/2 to restore call toefi_setup_idmap()to the original location in the boot process.Quoted 7 lines
Quoted 4 lines
Quoted 1 line
Looks reasonable to me; do they need a CC stable,
Yes, but with a note that both patches should be taken and the order is retained, or we break bisect.
Where would one add such a note?
I guess the best way would be to not add a 'Cc: stable' tag, but send an email to Greg once the patches have been merged by Linus.
Quoted 7 lines
Quoted 3 lines
I thought Greg didn't take anything until it had hit mainline anyway? I think it should be fine with just the Cc...
I know he doesn't, but do you know for a fact that he always takes patches in the same order they appear in mainline? It would seem like the reasonable thing to do, I guess, but we just have to make sure.
If we really want to make sure we could either fold the two patches into one or add a dependency without a corresponding sha. I don't like waiting until they've hit mainline, because I'm sure that I'll forget!
Will