From: Nishanth Menon <nm@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2 07/12] board: LaCie: Move common headers to board-common directory
Date: Fri, 13 Nov 2015 17:57:17 -0600 [thread overview]
Message-ID: <564678DD.6070100@ti.com> (raw)
In-Reply-To: <20151113153209.GU4665@kw.sim.vm.gnt>
On 11/13/2015 09:32 AM, Simon Guinot wrote:
> On Fri, Nov 13, 2015 at 09:06:45AM -0500, Tom Rini wrote:
>> On Fri, Nov 13, 2015 at 11:30:43AM +0100, Simon Guinot wrote:
>>> Hi Nishanth,
>>>
>>> On Thu, Nov 12, 2015 at 11:43:37PM -0600, Nishanth Menon wrote:
>>>> Header files can be located in a generic location without
>>>> needing to reference them with ../common/
>>>>
>>>> Generated with the following script
>>>>
>>>> #!/bin/bash
>>>> vendor=board/LaCie
>>>> common=$vendor/common
>>>>
>>>> cfiles=`git grep "../common" $vendor|grep "#include"|cut -d '"' -f2|sort -u|grep c$`
>>>> headers=`git grep "../common" $vendor|grep "#include"|cut -d '"' -f2|sort -u|grep h$`
>>>>
>>>> mkdir -p $common/include/board-common
>>>> set -x
>>>> for header in $headers
>>>> do
>>>> echo "processing $header in $common"
>>>> hbase=`basename $header`
>>>> git mv $common/$hbase $common/include/board-common
>>>> sed -i -e "s/\"..\/common\/$hbase\"/<board-common\/$hbase>/g" $vendor/*/*.[chS]
>>>> sed -i -e "s/\"$hbase\"/<board-common\/$hbase>/g" $vendor/common/*.[chS]
>>>> done
>>>>
>>>> Cc: Simon Guinot <simon.guinot@sequanux.org>
>>>> Cc: Albert ARIBAUD <albert.u.boot@aribaud.net>
>>>>
>>>> Signed-off-by: Nishanth Menon <nm@ti.com>
>>>> ---
>>>> board/LaCie/common/cpld-gpio-bus.c | 2 +-
>>>> board/LaCie/common/{ => include/board-common}/common.h | 0
>>>
>>> Is that really a good idea to move a LaCie-specific file named common.h
>>> to a place shared with other boards ?
>>>
>>>> board/LaCie/common/{ => include/board-common}/cpld-gpio-bus.h | 0
>>>
>>> IMO, this headers are specific to LaCie boards and it don't make much
>>> sense to move them to a shared place. Moreover it is quite convenient to
>>> have them close from the board setup files.
>>>
>>> Please don't move them.
>>
>> Please read and then suggest changes in the "Makefile: Include vendor
>> common library in include search path" thread. Thanks!
>
> Hi Tom,
>
> Do you mean I answered without even really looking at the suggested
> change ? Well, it is true :)
>
> Sorry about that. I have been confused by the "git move file" notation
> which I am not familiar with. So, I withdraw my previous objections.
>
Thanks.
> Now, I have to say that I am still not convinced by the change.
>
> After applying this patch, I can see that:
>
> #include "../common/cpld-gpio-bus.h"
>
> have been replaced with:
>
> #include <board-common/cpld-gpio-bus.h>
>
> While this change is fine, I can also see that the header file has been
> moved from:
>
> board/LaCie/common/cpld-gpio-bus.h
>
> to:
>
> board/LaCie/common/include/board-common/cpld-gpio-bus.h
>
> With both the strings "board" and "common" duplicated, I am definitively
> not a big fan of this new path. Moreover I think that moving the headers
> away from the board setup files will harm a little bit the code reading.
>
> Maybe it would be better to have a shorter path like:
>
> board/LaCie/include/board-common/cpld-gpio-bus.h
That can easily be done as well. for me, it is just regenerating the
scripts..
I strongly suggest to comment on the original patch
https://patchwork.ozlabs.org/patch/544030/ and suggest this so that
other platform folks have the discussion context as well.
>
> Anyway, IMHO things are fine as they are. But if anyone thinks this
> change is needed or valuable, then I am OK with it.
IMHO, I started on this story, because we have a need to have a
board/ti/common directory and adding more cruft on top of what is
already a bunch of crufty includes is just painful.
If you are interested in the complete history:
https://patchwork.ozlabs.org/patch/540280/
https://patchwork.ozlabs.org/patch/541068/
https://patchwork.ozlabs.org/patch/542424/
Tom, Simon,
Are you guys ok with board/$(VENDOR)/include?
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2015-11-13 23:57 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 5:43 [U-Boot] [PATCH V2 00/12] Series to move headers to a consistent include location Nishanth Menon
2015-11-13 5:43 ` [U-Boot] [PATCH V2 01/12] Makefile: Include vendor common library in include search path Nishanth Menon
2015-11-15 14:45 ` Igor Grinberg
2015-11-13 5:43 ` [U-Boot] [PATCH V2 02/12] board: BuR: Move common headers to board-common directory Nishanth Menon
2015-11-13 5:43 ` [U-Boot] [PATCH V2 03/12] board: compulab: " Nishanth Menon
2015-11-13 5:43 ` [U-Boot] [PATCH V2 05/12] board: gdsys: " Nishanth Menon
2015-11-16 8:01 ` Dirk Eibach
2015-11-16 8:04 ` Dirk Eibach
2015-11-13 5:43 ` [U-Boot] [PATCH V2 06/12] board: keymile: " Nishanth Menon
2015-11-18 13:58 ` Valentin Longchamp
2015-11-13 5:43 ` [U-Boot] [PATCH V2 07/12] board: LaCie: " Nishanth Menon
2015-11-13 10:30 ` Simon Guinot
2015-11-13 14:06 ` Tom Rini
2015-11-13 15:32 ` Simon Guinot
2015-11-13 23:57 ` Nishanth Menon [this message]
2015-11-14 2:05 ` Simon Glass
2015-11-16 1:53 ` Tom Rini
2015-11-14 23:56 ` Masahiro Yamada
2015-11-15 5:38 ` Nishanth Menon
2015-11-16 3:32 ` Masahiro Yamada
2015-11-16 15:34 ` Nishanth Menon
2015-11-17 0:45 ` Tom Rini
2015-11-13 5:43 ` [U-Boot] [PATCH V2 08/12] board: mpl: " Nishanth Menon
2015-11-13 8:19 ` David Müller (ELSOFT AG)
2015-11-13 14:02 ` Tom Rini
2015-11-13 5:43 ` [U-Boot] [PATCH V2 09/12] board: seco: " Nishanth Menon
2015-11-13 5:43 ` [U-Boot] [PATCH V2 10/12] board: siemens: " Nishanth Menon
2015-11-16 9:17 ` Egli, Samuel
2015-11-13 5:43 ` [U-Boot] [PATCH V2 11/12] board: varisys: " Nishanth Menon
2015-11-16 7:42 ` Andy Fleming
2015-11-13 5:43 ` [U-Boot] [PATCH V2 12/12] board: xes: " Nishanth Menon
2015-11-13 5:51 ` [U-Boot] [PATCH RESEND V2 04/12] board: freescale: " Nishanth Menon
2015-12-19 23:07 ` [U-Boot] [PATCH V2 00/12] Series to move headers to a consistent include location Simon Glass
2015-12-20 0:25 ` Nishanth Menon
2015-12-28 4:22 ` Simon Glass
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=564678DD.6070100@ti.com \
--to=nm@ti.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