Skip to content

Clean up top-level directory structure

Shinya Kuribayashi u-boot 2 versions New

Get series with b4
b4 am [email protected]

Versions newest first · linked by author and title

  1. v2 Latest posting 2/20 of 6 patches 0 repliesNew
  2. v2 posting 1/20 of 6 patches 0 repliesSuperseded

Patches in v2 posting 2/2 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 v2 yet.

Read the v2 thread

Cover letter [U-Boot] [PATCH v2 0/6] Clean up top-level directory structure
Quoted 11 lines · Peter Tyser
Quoted 4 lines

Before verifying MIPS builds, I'd like to make sure that why you take lib/$(ARCH)/ alternative, not $(ARCH)/lib/. If there were any discussion on #IRC, is there any chance we could share the summary or decision to follow?

There was no discussion, /lib/$(ARCH) just made more sense to me and it was functionally a direct translation from lib_$(ARCH) to lib/$(ARCH).

Using $(ARCH)/lib wouldn't clean up the top-level directory structure much and would open a can of worms that I'm not prepared to deal with at this time. For example, if there was an architecture specific

Oops, I wanted to say "arch/$(ARCH)/lib/", not $(ARCH)/lib/, sorry.

Quoted 16 lines

directory, it would seem logical to put cpus of that $(ARCH) type in it too, eg
ppc/

	lib/
	mpc8260
	mpc85xx/
	mpc86xx/

sh/

	lib/
	sh2/
	sh3/
	sh4/

...

Quoted 8 lines

My change was just meant to be an incremental improvement, but I could see advantages to using the $(ARCH)/... structure if we wanted to make larger changes. Anyway, I'd be curious to hear other's opinions about other directory layouts.

While we're talking about it, I'd always thought it would be nice to split out all the cmd_* files from common/ into their own command/ directory similar to u-boot-v2.

Ack. The directory structure in u-boot-v2 looks nice, at least, to me, anyway.

Quoted 5 lines
Quoted 3 lines

Please note that I agree with such cleanup, of course. I just would like to make sure that lib/$(ARCH)/ is an authorized policy or not. If authorized one, I'm fine.

I was just scratching an itch, nothing official:)

Got it.

Thanks for the kind explanation,