public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Roger Quadros <rogerq@kernel.org>
Cc: Apurva Nandan <a-nandan@ti.com>, Hari Nagalla <hnagalla@ti.com>,
	Lukasz Majewski <lukma@denx.de>,
	Sean Anderson <seanga2@gmail.com>,
	Jaehoon Chung <jh80.chung@samsung.com>,
	Neha Malcom Francis <n-francis@ti.com>,
	Simon Glass <sjg@chromium.org>, Andrew Davis <afd@ti.com>,
	Kamlesh Gurudasani <kamlesh@ti.com>,
	Dasnavis Sabiya <sabiya.d@ti.com>,
	Manorit Chawdhry <m-chawdhry@ti.com>,
	Aradhya Bhatia <a-bhatia1@ti.com>, Bryan Brattlof <bb@ti.com>,
	Christian Gmeiner <christian.gmeiner@gmail.com>,
	Heinrich Schuchardt <xypron.glpk@gmx.de>,
	Marcel Ziswiler <marcel.ziswiler@toradex.com>,
	Jayesh Choudhary <j-choudhary@ti.com>,
	Ralph Siemsen <ralph.siemsen@linaro.org>,
	Marek Vasut <marek.vasut+renesas@mailbox.org>,
	Rasmus Villemoes <rasmus.villemoes@prevas.dk>,
	<u-boot@lists.denx.de>,
	Sinthu Raja M <sinthu.raja@mistralsolutions.com>,
	Udit Kumar <u-kumar1@ti.com>
Subject: Re: [PATCH v7 15/17] configs: Add am69_sk_* defconfig fragments
Date: Thu, 11 Jan 2024 06:26:43 -0600	[thread overview]
Message-ID: <20240111122643.sdo6o7ubedsym2or@player> (raw)
In-Reply-To: <0105d7fb-3f81-4435-832b-c97fdbdf0995@kernel.org>

On 14:25-20240111, Roger Quadros wrote:
[...]
> > Signed-off-by: Dasnavis Sabiya <sabiya.d@ti.com>
> > Signed-off-by: Apurva Nandan <a-nandan@ti.com>
> > ---
> >  configs/am69_sk_a72.config | 3 +++
> >  configs/am69_sk_r5.config  | 3 +++
> 
> Shouldn't the config fragments lie in the board/<board>/configs directory?
> Else we will just keep polluting the configs directory.

Correct - fragments should be in board/ti/.../ folder.

-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D

  reply	other threads:[~2024-01-11 12:26 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-19 19:15 [PATCH v7 00/17] Introduce initial TI's J784S4 and AM69 support Apurva Nandan
2023-12-19 19:15 ` [PATCH v7 01/17] arm: dts: Introduce j784s4 dts from linux kernel Apurva Nandan
2024-01-03 15:57   ` Nishanth Menon
2023-12-19 19:15 ` [PATCH v7 02/17] arm: dts: Introduce am69-sk " Apurva Nandan
2024-01-03 15:58   ` Nishanth Menon
2023-12-19 19:15 ` [PATCH v7 03/17] arm: mach-k3: Add basic support for J784S4 SoC definition Apurva Nandan
2024-01-03 16:25   ` Nishanth Menon
2023-12-19 19:15 ` [PATCH v7 04/17] arm: mach-k3: Sort SoC JTAG_ID entries Apurva Nandan
2023-12-19 19:15 ` [PATCH v7 05/17] soc: ti: k3-socinfo: Add entry for J784S4 SoC Apurva Nandan
2024-01-03 17:07   ` Nishanth Menon
2023-12-19 19:15 ` [PATCH v7 06/17] arm: mach-k3: j784s4: Add clk and power support Apurva Nandan
2024-01-03 17:11   ` Nishanth Menon
2024-01-03 21:11     ` Bryan Brattlof
2023-12-19 19:15 ` [PATCH v7 07/17] drivers: dma: Add support for J784S4 SoC Apurva Nandan
2024-01-03 17:13   ` Nishanth Menon
2023-12-19 19:15 ` [PATCH v7 08/17] board: ti: j784s4: Add board support for J784S4 EVM Apurva Nandan
2024-01-03 17:28   ` Nishanth Menon
2023-12-19 19:15 ` [PATCH v7 09/17] board: ti: j748s4: Add board config yaml files Apurva Nandan
2024-01-03 17:36   ` Nishanth Menon
2024-01-04  3:46     ` Neha Malcom Francis
2023-12-19 19:15 ` [PATCH v7 10/17] board: ti: j784s4: Add boot environment variables Apurva Nandan
2024-01-03 17:39   ` Nishanth Menon
2023-12-19 19:15 ` [PATCH v7 11/17] arm: dts: Introduce j784s4 u-boot dts files Apurva Nandan
2024-01-03 17:47   ` Nishanth Menon
2023-12-19 19:15 ` [PATCH v7 12/17] arm: dts: Introduce am69-sk " Apurva Nandan
2024-01-03 17:50   ` Nishanth Menon
2023-12-19 19:15 ` [PATCH v7 13/17] arm: dts: Add bootph-all for memory node Apurva Nandan
2024-01-03 17:52   ` Nishanth Menon
2023-12-19 19:15 ` [PATCH v7 14/17] configs: j784s4_evm: Add defconfig for j784s4 evm board Apurva Nandan
2024-01-03 17:58   ` Nishanth Menon
2023-12-19 19:15 ` [PATCH v7 15/17] configs: Add am69_sk_* defconfig fragments Apurva Nandan
2024-01-03 17:59   ` Nishanth Menon
2024-01-11  9:36     ` Manorit Chawdhry
2024-01-11 12:20       ` Nishanth Menon
2024-01-11 12:25   ` Roger Quadros
2024-01-11 12:26     ` Nishanth Menon [this message]
2023-12-19 19:15 ` [PATCH v7 16/17] doc: board: ti: k3: Add J784S4 EVM and AM69 SK documentation Apurva Nandan
2024-01-03 18:39   ` Nishanth Menon
2023-12-19 19:15 ` [PATCH v7 17/17] board: ti: j784s4: Add MAINTAINERS file Apurva Nandan
2024-01-03 18:41   ` Nishanth Menon
2024-01-03 15:37 ` [PATCH v7 00/17] Introduce initial TI's J784S4 and AM69 support Nishanth Menon
2024-01-03 15:53   ` Nishanth Menon
2024-01-18  7:35     ` Enric Balletbo i Serra

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=20240111122643.sdo6o7ubedsym2or@player \
    --to=nm@ti.com \
    --cc=a-bhatia1@ti.com \
    --cc=a-nandan@ti.com \
    --cc=afd@ti.com \
    --cc=bb@ti.com \
    --cc=christian.gmeiner@gmail.com \
    --cc=hnagalla@ti.com \
    --cc=j-choudhary@ti.com \
    --cc=jh80.chung@samsung.com \
    --cc=kamlesh@ti.com \
    --cc=lukma@denx.de \
    --cc=m-chawdhry@ti.com \
    --cc=marcel.ziswiler@toradex.com \
    --cc=marek.vasut+renesas@mailbox.org \
    --cc=n-francis@ti.com \
    --cc=ralph.siemsen@linaro.org \
    --cc=rasmus.villemoes@prevas.dk \
    --cc=rogerq@kernel.org \
    --cc=sabiya.d@ti.com \
    --cc=seanga2@gmail.com \
    --cc=sinthu.raja@mistralsolutions.com \
    --cc=sjg@chromium.org \
    --cc=u-boot@lists.denx.de \
    --cc=u-kumar1@ti.com \
    --cc=xypron.glpk@gmx.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