From: Tom Rini <trini@konsulko.com>
To: Jason Kacines <j-kacines@ti.com>
Cc: Andrew Davis <afd@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
Bryan Brattlof <bb@ti.com>, Praneeth Bajjuri <praneeth@ti.com>,
u-boot@lists.denx.de
Subject: Re: [RFC PATCH 1/3] scripts: kconfig: Add config fragment support in board/../
Date: Wed, 9 Aug 2023 13:17:03 -0400 [thread overview]
Message-ID: <20230809171703.GK3630934@bill-the-cat> (raw)
In-Reply-To: <20230711212048.1340990-2-j-kacines@ti.com>
[-- Attachment #1: Type: text/plain, Size: 385 bytes --]
On Tue, Jul 11, 2023 at 04:20:46PM -0500, Jason Kacines wrote:
> Add support to config fragments (.config) located in the /board
> directory. This will allow only base defconfigs to live in /configs and
> all fragments to live in their respective device directory in /board/..
>
> Signed-off-by: Jason Kacines <j-kacines@ti.com>
Applied to u-boot/next, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2023-08-09 17:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 21:20 [RFC PATCH 0/3] Minimal platform configuration Jason Kacines
2023-07-11 21:20 ` [RFC PATCH 1/3] scripts: kconfig: Add config fragment support in board/../ Jason Kacines
2023-07-12 14:00 ` Simon Glass
2023-07-13 22:54 ` Tom Rini
2023-07-15 23:40 ` Simon Glass
2023-07-16 15:12 ` Tom Rini
2023-07-19 1:07 ` Simon Glass
2023-07-19 13:34 ` Tom Rini
2023-07-27 0:49 ` Simon Glass
2023-08-07 22:15 ` [PATCH] doc: Begin adding a best practices document for board ports Tom Rini
2023-08-08 20:12 ` Heinrich Schuchardt
2023-08-08 20:36 ` [v2] " Tom Rini
2023-08-09 2:03 ` Simon Glass
2023-08-09 17:17 ` Tom Rini [this message]
2023-07-11 21:20 ` [RFC PATCH 2/3] configs: Add am62x wakeup defconfigs Jason Kacines
2023-07-11 21:20 ` [RFC PATCH 3/3] board: ti: am62x: Add am62x_evm defconfig fragments Jason Kacines
2023-07-12 14:00 ` [RFC PATCH 0/3] Minimal platform configuration Simon Glass
2023-07-13 22:34 ` Nishanth Menon
2023-07-15 23:40 ` 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=20230809171703.GK3630934@bill-the-cat \
--to=trini@konsulko.com \
--cc=afd@ti.com \
--cc=bb@ti.com \
--cc=j-kacines@ti.com \
--cc=praneeth@ti.com \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@ti.com \
/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