Introduce generic relocation feature
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v3 posting 3/30 of 6 patches 0 repliesNew
- v4 Latest3 of 13 patches 0 repliesNew
- v3 posting 2/30 of 6 patches 0 repliesSuperseded
Earlier versions · 4
| Version | Posted | Patches | Replies | Status |
|---|---|---|---|---|
| v3 posting 1/3 | 0 of 6 patches | 0 replies | Superseded | |
| v2 posting 2/2 | 2 of 6 patches | 0 replies | Superseded | |
| v2 posting 1/2 | 5 of 6 patches | 0 replies | Superseded | |
| v1 RFC | 3 of 7 patches | 0 replies | Superseded |
3 of 13 patches are in this archive. The cover letter announces 13.
Patches in v4 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 2/13 | Add generic relocation feature | +0 | 1 reply | |
| 4/13 | arm: Add start_call_board_init_r() to each start.S | +0 | 2 replies | |
| 7/13 | davinci: Use correct #ifdef around gdata/bdata | +0 | 1 reply |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v4 yet.
Cover letter [U-Boot] [PATCH v4 0/13] Introduce generic relocation feature
Hi Simon,
One general question: am I right in saying that in the current implementation, relocate_code executes mostly on the final stack, whereas in your proposal, it runs on the initial stack?
Amicalement,
Signature · 1 line
Albert.