public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Andrew Davis <afd@ti.com>
Cc: Manorit Chawdhry <m-chawdhry@ti.com>,
	u-boot@lists.denx.de, Vignesh Raghavendra <vigneshr@ti.com>,
	Neha Francis <n-francis@ti.com>,
	Jayesh Choudhary <j-choudhary@ti.com>
Subject: Re: [PATCH v1] configs: j7200: Merge HS and non-HS defconfigs
Date: Thu, 23 Feb 2023 17:28:06 -0500	[thread overview]
Message-ID: <Y/fodjCBupSpLGd8@bill-the-cat> (raw)
In-Reply-To: <469b8b1a-d0a8-7af1-65a7-daace104dece@ti.com>

[-- Attachment #1: Type: text/plain, Size: 733 bytes --]

On Wed, Feb 22, 2023 at 09:02:12AM -0600, Andrew Davis wrote:
> On 2/22/23 1:56 AM, Manorit Chawdhry wrote:
> > K3 devices have runtime type board detection. Make the default defconfig
> > include the secure configuration. Then remove the HS specific config.
> > 
> > Non-HS devices will continue to boot due to runtime device type detection.
> > If TI_SECURE_DEV_PKG is not set the build will emit warnings, for non-HS
> > devices these can be ignored.
> > 
> > Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com>
> > ---
> 
> This will help with keeping the HS and non-HS configs in sync :)
> 
> Acked-by: Andrew Davis <afd@ti.com>

Please re-spin both of these to update the MAINTAINERS file as well.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2023-02-23 22:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-22  7:56 [PATCH v1] configs: j7200: Merge HS and non-HS defconfigs Manorit Chawdhry
2023-02-22  7:56 ` [PATCH v1] configs: j721s2: merge " Manorit Chawdhry
2023-02-22 15:02 ` [PATCH v1] configs: j7200: Merge " Andrew Davis
2023-02-23 22:28   ` Tom Rini [this message]
2023-02-24  5:13     ` Manorit Chawdhry

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=Y/fodjCBupSpLGd8@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=afd@ti.com \
    --cc=j-choudhary@ti.com \
    --cc=m-chawdhry@ti.com \
    --cc=n-francis@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