Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Walle <michael@walle.cc>
To: Arnout Vandecappelle <arnout@mind.be>
Cc: geomatsi@gmail.com,
	Chris Dimich <chris.dimich@boundarydevices.com>,
	Changming Huang <jerry.huang@nxp.com>,
	thomas.petazzoni@bootlin.com, buildroot@busybox.net,
	heiko.thiery@gmail.com,
	Michael Trimarchi <michael@amarulasolutions.com>,
	matthew.weber@collins.com
Subject: Re: [Buildroot] [PATCH v5 1/9] package/nxp: new package directory
Date: Thu, 06 Jan 2022 16:00:37 +0100	[thread overview]
Message-ID: <70c6686e301152345e96b4a199d2a96c@walle.cc> (raw)
In-Reply-To: <737df820-79da-b710-22fc-dc8c53e9223c@mind.be>

Am 2022-01-06 15:45, schrieb Arnout Vandecappelle:
>  In this series, the only commonality that I found is the binary
> extraction, but it ends up to be used only by
> qoriq-cadence-dp-firmware. That's not worth it IMHO.

mh? all the imx stuff is using this method.

> 
>  Therefore, I marked this patch and rejected.
> 
>  Note that it would make sense to do this if we would also move the
> freescale-imx stuff into the same directory (freescale is anyway nxp
> now so it should be OK to do that).

ah. yes. that was the idea back then IMHO.

-michael
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2022-01-06 15:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-07  8:38 [Buildroot] [PATCH v5 1/9] package/nxp: new package directory Changming Huang
2020-02-07  8:38 ` [Buildroot] [PATCH v5 2/9] package/qoriq-rcw: move rcw into nxp and rename it Changming Huang
2020-04-14  9:35   ` Heiko Thiery
2020-12-16 21:02   ` Yann E. MORIN
2020-02-07  8:38 ` [Buildroot] [PATCH v5 3/9] package/qoriq-rcw: bump to version LSDK-19.09 Changming Huang
2020-02-07  8:38 ` [Buildroot] [PATCH v5 4/9] package/qoriq-rcw: add target rcw binary support Changming Huang
2022-01-06 14:48   ` Arnout Vandecappelle
2020-02-07  8:38 ` [Buildroot] [PATCH v5 5/9] boot/arm-trusted-firmware: allow additional make dependencies Changming Huang
2022-01-06 15:05   ` Arnout Vandecappelle
2020-02-07  8:38 ` [Buildroot] [PATCH v5 6/9] package/qoriq-cadence-dp-firmware: new package Changming Huang
2022-01-06 15:14   ` Michael Walle
2022-01-06 15:19   ` Arnout Vandecappelle
2020-02-07  8:38 ` [Buildroot] [PATCH v5 7/9] package/qoriq-rcw:Enable IIC5_PMUX and CLK_OUT_PMUX for GPIO Changming Huang
2022-01-06 15:54   ` Arnout Vandecappelle
2020-02-07  8:38 ` [Buildroot] [PATCH v5 8/9] package/nxp/qoriq-rcw: introduce BR2_PACKAGE_HOST_QORIQ_RCW_BOOT_MODE for boot mode Changming Huang
2022-01-06 15:55   ` Arnout Vandecappelle
2020-02-07  8:38 ` [Buildroot] [PATCH v5 9/9] board/nxp/ls1028ardb: new board Changming Huang
2022-01-06 16:27   ` Arnout Vandecappelle
2022-01-06 14:45 ` [Buildroot] [PATCH v5 1/9] package/nxp: new package directory Arnout Vandecappelle
2022-01-06 15:00   ` Michael Walle [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=70c6686e301152345e96b4a199d2a96c@walle.cc \
    --to=michael@walle.cc \
    --cc=arnout@mind.be \
    --cc=buildroot@busybox.net \
    --cc=chris.dimich@boundarydevices.com \
    --cc=geomatsi@gmail.com \
    --cc=heiko.thiery@gmail.com \
    --cc=jerry.huang@nxp.com \
    --cc=matthew.weber@collins.com \
    --cc=michael@amarulasolutions.com \
    --cc=thomas.petazzoni@bootlin.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