From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Thomas Perrot <thomas.perrot@bootlin.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/2] package/imx-cst: add new package
Date: Wed, 20 Apr 2022 13:25:47 +0200 [thread overview]
Message-ID: <20220420132541.7aad1182@windsurf> (raw)
In-Reply-To: <aa8ded3d92323550b31ac24dd2ad283d13307a0e.camel@bootlin.com>
Hello,
On Wed, 20 Apr 2022 10:39:16 +0200
Thomas Perrot <thomas.perrot@bootlin.com> wrote:
> > What is this location? Just someone who put the NXP code online? Or a
> > separate implementation?
>
> NXP code has been put by Debian maintainers.
OK.
> I think it is correct because from source the file
> "Software_Content_Register_CST.txt" indicates that the outgoing license
> is BSD-3-Clause, and Debian also use this BSD license.
Indeed, it seems OK.
Maybe it would have been useful to have those details somewhere (in the
commit log perhaps)? But it's probably not worth sending another
iteration just for this.
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
prev parent reply other threads:[~2022-04-20 11:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 9:21 [Buildroot] [PATCH 0/2] Support for i.MX Code Signing Tools Thomas Perrot via buildroot
2022-04-19 9:21 ` [Buildroot] [PATCH 1/2] package/byacc: add new package Thomas Perrot via buildroot
2022-04-19 12:12 ` Thomas Petazzoni via buildroot
2022-04-19 9:21 ` [Buildroot] [PATCH 2/2] package/imx-cst: " Thomas Perrot via buildroot
2022-04-19 12:26 ` Thomas Petazzoni via buildroot
2022-04-19 19:38 ` Thomas Petazzoni via buildroot
2022-04-20 8:39 ` Thomas Perrot via buildroot
2022-04-20 11:25 ` Thomas Petazzoni via buildroot [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=20220420132541.7aad1182@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.perrot@bootlin.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