From: Troy Kisky <troy.kisky@boundarydevices.com>
To: Simon Glass <sjg@chromium.org>
Cc: Tom Rini <trini@konsulko.com>,
Fabio Estevam <fabio.estevam@nxp.com>,
U-Boot Mailing List <u-boot@lists.denx.de>
Subject: Re: [PATCH v1 3/5] scripts: Makefile.autoconf: allow CONFIG_SYS_CONFIG_NAME file to live in board directory
Date: Thu, 6 Jan 2022 13:09:25 -0800 [thread overview]
Message-ID: <b3892e5c-5a6b-50ee-82e0-7138212f0111@boundarydevices.com> (raw)
In-Reply-To: <CAPnjgZ1Ef-4b97_V=yvaARdr6m+RSJpDLDaY3SchW6FnXvPzjg@mail.gmail.com>
On 12/28/2021 12:33 AM, Simon Glass wrote:
> Hi Troy,
>
> On Fri, 17 Dec 2021 at 16:02, Troy Kisky <troy.kisky@boundarydevices.com> wrote:
>>
>> Let the board specific include file live in the board directory.
>>
>> Signed-off-by: Troy Kisky <troy.kisky@boundarydevices.com>
>> ---
>> scripts/Makefile.autoconf | 9 +++++++--
>> 1 file changed, 7 insertions(+), 2 deletions(-)
>
> We are actually working on deleting these. What is the benefit of
> putting it here?
>
Do you have an estimate on how long until the 1st one can be deleted?
The main benefit that I see is making it easier to clone or compare boards.
You just duplicate/diff everything in the board directory and rename files to taste.
My goal for this series is NOT to force everyone to update their board, but rather to allow new
boards to have all their board specific files in one directory.
BR
Troy
next prev parent reply other threads:[~2022-01-06 21:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 23:01 [PATCH v1 0/5] Move board specific files to board directory Troy Kisky
2021-12-17 23:01 ` [PATCH v1 1/5] kconfig: allow defconfigs to live in " Troy Kisky
2021-12-28 8:33 ` Simon Glass
2022-01-06 21:00 ` Troy Kisky
2021-12-17 23:01 ` [PATCH v1 2/5] dts: allow dts files " Troy Kisky
2021-12-28 8:33 ` Simon Glass
2022-01-06 21:01 ` Troy Kisky
2021-12-17 23:01 ` [PATCH v1 3/5] scripts: Makefile.autoconf: allow CONFIG_SYS_CONFIG_NAME file to live " Troy Kisky
2021-12-28 8:33 ` Simon Glass
2022-01-06 21:09 ` Troy Kisky [this message]
2022-01-30 23:14 ` Simon Glass
2021-12-17 23:01 ` [PATCH v1 4/5] genboardcfg: allow defconfigs " Troy Kisky
2021-12-28 8:33 ` Simon Glass
2021-12-17 23:01 ` [PATCH v1 5/5] nitrogen6x: move board specific files to nitrogen6x directory Troy Kisky
2021-12-28 8:33 ` Simon Glass
2021-12-28 8:33 ` [PATCH v1 0/5] Move board specific files to board directory Simon Glass
2021-12-28 13:11 ` Tom Rini
2022-01-06 21:14 ` Troy Kisky
2022-01-07 15:12 ` Tom Rini
2022-01-07 18:33 ` Troy Kisky
2022-01-30 23:14 ` Simon Glass
2022-02-08 14:30 ` Tom Rini
2022-03-15 19:08 ` Troy Kisky
2022-03-15 20:01 ` Tom Rini
2022-03-15 20:23 ` Troy Kisky
2022-03-16 14:48 ` Tom Rini
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=b3892e5c-5a6b-50ee-82e0-7138212f0111@boundarydevices.com \
--to=troy.kisky@boundarydevices.com \
--cc=fabio.estevam@nxp.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.