Skip to content

RFC ARM Relocation Config Cleanup

Reinhard Meyer u-boot 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 RFC Latest0 of 3 patches 0 repliesNew

Patches in v1 No applies recorded yet

None of the 3 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.

Read the v1 thread

Cover letter [U-Boot] [PATCH RFC 0/3] ARM Relocation Config Cleanup

Dear Wolfgang Denk,

Quoted 11 lines

Dear Reinhard Meyer,

Quoted 3 lines · In message <[email protected]> you wrote:
Quoted 1 line

Replace CONFIG_RELOC_FIXUP_WORKS by CONFIG_BROKEN_RELOC_FIXUP

Seems a slight misnomer to me, and a bit hides what it really does. What about CONFIG_NEEDS_DATA_RELOC_FIXUP ?

Thinking about that, I feel the name is too long. And eventually not clear enough either.

How about CONFIG_NEEDS_MANUAL_RELOC ?

OK, since I had that in mind, too. I skipped it however since "manual" for me smells like really some extra manual labour.
But I guess any full descriptive term would be too long.
Fact is, that that sort of system wide "manual" reloc is needed for "initialized data with pointer contents" only. It would be nice if that fact would peek out to avoid conceptional misunderstandings.

Would it be possible for you to apply those 3 patches to a testing branch, I am having an odd error trying to git-am patch 2/3, however I can find no wrongs in the patch at the complained about places. 1/3 did apply without problems.

Best Regards,
Reinhard