From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 2/6] Move lib_<ARCH> directories to lib/<ARCH>
Date: Mon, 07 Dec 2009 15:42:08 -0600 [thread overview]
Message-ID: <4B1D76B0.1040900@freescale.com> (raw)
In-Reply-To: <20091207213211.8EA773F6CC@gemini.denx.de>
Wolfgang Denk wrote:
> Dear Peter Tyser,
>
> In message <1258943983.9357.20.camel@ptyser-laptop> you wrote:
>> My personal preference would be to take it a step further and organize
>> like:
>>
>> /arch/$ARCH/
>> /lib/<sources currently in lib_$ARCH/>
>> /include/asm/<headers currently in incluce/asm-$ARCH/>
>> /cpu/<appropriate cpu directories in cpu/>
>> /config.mk (old lib_$ARCH/config.mk)
>>
>> /lib/
>> /<source files currently in lib_generic>
>> /libfdt/
>> /lzma/
>> /lzo/
>>
>> This layout would more closely match the Linux layout and is cleaner
>> overall in my opinion. What do others think of this idea?
>
> I generally agree with the idea, with the exception of
> /include/asm/<headers> - I really hate this change in the Linux
> kernel, and still fail to see any advantages of this.
I really like only having one subtree to grep for arch stuff, and it
would avoid presenting files that are in git, under a path that git
doesn't know about.
Plus, the symlink is one less thing that the makefiles would need to
keep in sync when arch changes.
-Scott
next prev parent reply other threads:[~2009-12-07 21:42 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-10 16:03 [U-Boot] [PATCH v2 0/6] Clean up top-level directory structure Peter Tyser
2009-07-10 16:03 ` [U-Boot] [PATCH v2 1/6] Move architecture specific config.mk files into subdirs Peter Tyser
2009-07-20 22:12 ` Wolfgang Denk
2009-07-10 16:03 ` [U-Boot] [PATCH v2 2/6] Move lib_<ARCH> directories to lib/<ARCH> Peter Tyser
2009-11-22 20:54 ` Wolfgang Denk
2009-11-23 2:39 ` Peter Tyser
2009-12-07 21:32 ` Wolfgang Denk
2009-12-07 21:42 ` Scott Wood [this message]
2009-12-08 5:39 ` Peter Tyser
2009-07-10 16:03 ` [U-Boot] [PATCH v2 3/6] Move lib_generic to lib/generic Peter Tyser
2009-07-10 16:03 ` [U-Boot] [PATCH v2 4/6] Move libfdt to lib/libfdt Peter Tyser
2009-07-10 16:03 ` [U-Boot] [PATCH v2 5/6] Move examples/ to examples/standalone Peter Tyser
2009-07-10 17:07 ` Mike Frysinger
2009-07-20 22:13 ` Wolfgang Denk
2009-07-22 21:56 ` [U-Boot] [PATCH] Fix "ld: cannot find -lstubs" build error Wolfgang Denk
2009-07-10 16:03 ` [U-Boot] [PATCH v2 6/6] Move api_examples to examples/api Peter Tyser
2009-07-20 22:14 ` Wolfgang Denk
2009-07-11 0:03 ` [U-Boot] [PATCH v2 0/6] Clean up top-level directory structure Shinya Kuribayashi
2009-07-11 0:40 ` Peter Tyser
2009-07-11 1:20 ` Shinya Kuribayashi
2009-07-11 2:42 ` Mike Frysinger
2009-07-12 12:54 ` Jean-Christophe PLAGNIOL-VILLARD
2009-07-14 15:20 ` Peter Tyser
2009-07-15 3:25 ` Stefan Roese
2009-07-15 3:38 ` Shinya Kuribayashi
2009-07-15 4:39 ` Peter Tyser
2009-07-18 11:19 ` Jean-Christophe PLAGNIOL-VILLARD
2009-07-18 16:37 ` Peter Tyser
2009-07-18 16:39 ` Jean-Christophe PLAGNIOL-VILLARD
2009-07-18 18:07 ` Wolfgang Denk
2009-07-19 20:01 ` Peter Tyser
2009-07-19 20:16 ` Wolfgang Denk
2009-07-20 22:15 ` Wolfgang Denk
2009-07-20 23:09 ` Peter Tyser
2009-07-15 14:50 ` Rafal Jaworowski
2009-07-18 16:52 ` Peter Tyser
2009-07-18 18:10 ` Wolfgang Denk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B1D76B0.1040900@freescale.com \
--to=scottwood@freescale.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox