All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Xuanhao Shi via buildroot <buildroot@buildroot.org>
Cc: Alden Benedick Agcon <alden@ti.com>, Xuanhao Shi <x-shi@ti.com>,
	Sergey Ostrovsky <sergeyo@ti.com>
Subject: Re: [Buildroot] [PATCH 1/1] boot/arm-trusted-firmware: add target board options
Date: Fri, 22 Jul 2022 09:55:03 +0200	[thread overview]
Message-ID: <20220722095503.27868873@windsurf> (raw)
In-Reply-To: <91ff193c-5e66-b80c-538c-7ebcddd9bd87@ti.com>

Hello,

On Thu, 21 Jul 2022 15:38:56 -0500
Xuanhao Shi via buildroot <buildroot@buildroot.org> wrote:

> Some platforms such as TI's k3 outputs a TARGET_BOARD directory
> in their ATF build output paths after PLATFORM.
> $(@D)/build/<PLATFORM>/ does not contain the debug or release
> directories for these platforms.
> They are under $(@D)/build/<PLATFORM>/<TARGET_BOARD>/
> 
> Signed-off-by: Xuanhao Shi <x-shi@ti.com>

Thanks for your patch. Could you resend it with "git send-email"?
Indeed, your e-mail client has mangled the patch, so it cannot be
applied.

Thanks!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-07-22  7:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220721203307.30488-1-x-shi@ti.com>
2022-07-21 20:38 ` [Buildroot] [PATCH 1/1] boot/arm-trusted-firmware: add target board options Xuanhao Shi via buildroot
2022-07-22  7:55   ` Thomas Petazzoni via buildroot [this message]
2022-07-22 13:56     ` Xuanhao Shi via buildroot
2022-07-22 14:33     ` Xuanhao Shi via buildroot
2022-07-23 15:39       ` Arnout Vandecappelle

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=20220722095503.27868873@windsurf \
    --to=buildroot@buildroot.org \
    --cc=alden@ti.com \
    --cc=sergeyo@ti.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=x-shi@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 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.