Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/5] cargo: use HOST_CARGO_DL_DIR instead of CARGO_DL_DIR
Date: Mon, 2 Apr 2018 21:43:25 +0200	[thread overview]
Message-ID: <20180402214325.346c4a69@windsurf> (raw)
In-Reply-To: <20180402183626.7769-1-maxime.hadjinlian@gmail.com>

Hello,

On Mon,  2 Apr 2018 20:36:22 +0200, Maxime Hadjinlian wrote:
> The infrastructure only provides HOST_CARGO_DL_DIR, because this
> package is host only. Ideally the infra should provide CARGO_DL_DIR,
> but it doesn't currently, and that requires more significant changes.
> 
> Signed-off-by: Maxime Hadjinlian <maxime.hadjinlian@gmail.com>
> ---
>  package/cargo/cargo.mk | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)

Series applied. Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

      parent reply	other threads:[~2018-04-02 19:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-02 18:36 [Buildroot] [PATCH 1/5] cargo: use HOST_CARGO_DL_DIR instead of CARGO_DL_DIR Maxime Hadjinlian
2018-04-02 18:36 ` [Buildroot] [PATCH 2/5] cryptopp: use HOST_CRYPTOPP_DL_DIR instead of CRYPTOPP_DL_DIR Maxime Hadjinlian
2018-04-02 18:36 ` [Buildroot] [PATCH 3/5] rust-bin: use HOST_RUST_BIN_DL_DIR instead of RUST_BIN_DL_DIR Maxime Hadjinlian
2018-04-02 18:36 ` [Buildroot] [PATCH 4/5] ti-cgt-pru: use HOST_TI_CGT_PRU_DL_DIR instead of TI_CGT_PRU_DL_DIR Maxime Hadjinlian
2018-04-02 18:36 ` [Buildroot] [PATCH 5/5] zynq-boot-bin: use HOST_ZYNQ_BOOT_BIN_DL_DIR instead of ZYNQ_BOOT_BIN_DL_DIR Maxime Hadjinlian
2018-04-02 19:43 ` Thomas Petazzoni [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=20180402214325.346c4a69@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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