All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: <prao@ti.com>
Cc: meta-arago@arago-project.org
Subject: Re: .master/dunfell] ti-tisdk-makefile: update Rules.mk armv7 toolchain for R5 use
Date: Wed, 1 Jul 2020 13:26:46 -0400	[thread overview]
Message-ID: <20200701172646.GD15879@beryl> (raw)
In-Reply-To: <20200630234852.28283-1-prao@ti.com>

Same comment as with the previous patch - please fix the prefix so it doesn't 
go into the git history.


On Tue, Jun 30, 2020 at 06:48:52PM -0500, prao@ti.com wrote:
> From: Praveen Rao <prao@ti.com>
> 
> Update the Rules.make addition for the R5 use of the armv7  toolchain.
> 
> Signed-off-by: Praveen Rao <prao@ti.com>
> ---
>  .../recipes-tisdk/ti-tisdk-makefile/ti-tisdk-makefile_1.0.bb    | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/meta-arago-distro/recipes-tisdk/ti-tisdk-makefile/ti-tisdk-makefile_1.0.bb b/meta-arago-distro/recipes-tisdk/ti-tisdk-makefile/ti-tisdk-makefile_1.0.bb
> index a698dd34..a441d4b1 100644
> --- a/meta-arago-distro/recipes-tisdk/ti-tisdk-makefile/ti-tisdk-makefile_1.0.bb
> +++ b/meta-arago-distro/recipes-tisdk/ti-tisdk-makefile/ti-tisdk-makefile_1.0.bb
> @@ -368,7 +368,7 @@ do_install_append_k3() {
>      cat >> ${D}/Rules.make << __EOF__
>  
>  # Add CROSS_COMPILE and UBOOT_MACHINE for the R5
> -export CROSS_COMPILE_ARMV7=\$(LINUX_DEVKIT_PATH)/sysroots/${SDKMACHINE}-arago-linux/usr/bin/arm-linux-gnueabihf-
> +export CROSS_COMPILE_ARMV7=\$(LINUX_DEVKIT_PATH)/sysroots/${SDKMACHINE}-arago-linux/usr/bin/arm-none-linux-gnueabihf-
>  UBOOT_MACHINE_R5=${K3_UBOOT_MACHINE_R5}
>  __EOF__
>  }
> -- 
> 2.17.1
> 


      reply	other threads:[~2020-07-01 17:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-30 23:48 .master/dunfell] ti-tisdk-makefile: update Rules.mk armv7 toolchain for R5 use prao
2020-07-01 17:26 ` Denys Dmytriyenko [this message]

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=20200701172646.GD15879@beryl \
    --to=denys@ti.com \
    --cc=meta-arago@arago-project.org \
    --cc=prao@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.