Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Quentin Schulz <quentin.schulz@theobroma-systems.com>
Cc: Sergey Matyukevich <geomatsi@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] boot/arm-trusted-firmware: point LICENSE_FILES to correct file
Date: Tue, 05 Oct 2021 16:43:08 +0200	[thread overview]
Message-ID: <87ee8zcz2b.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20210924162349.2802374-1-quentin.schulz@theobroma-systems.com> (Quentin Schulz's message of "Fri, 24 Sep 2021 18:23:49 +0200")

>>>>> "Quentin" == Quentin Schulz <quentin.schulz@theobroma-systems.com> writes:

 > Since v2.2 release (commits 8cc36aec912 "doc: De-duplicate readme and
 > license files" and 9f1622b018ab "doc: Move content out of readme and
 > create new index page "), the license.rst file at the root of the git
 > repo is only telling to look at docs/license.rst file.

 > Let's point the ARM_TRUSTED_FIRMWARE_LICENSE_FILES to the correct file
 > and modify the .hash file accordingly.

 > Signed-off-by: Quentin Schulz <quentin.schulz@theobroma-systems.com>

Committed to 2021.02.x, 2021.05.x and 2021.08.x, thanks.

For 2021.02.x / 2021.05.x I updated the license hash to match the
version we use there (v2.4).

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2021-10-05 14:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-24 16:23 [Buildroot] [PATCH] boot/arm-trusted-firmware: point LICENSE_FILES to correct file Quentin Schulz
2021-09-24 19:57 ` Yann E. MORIN
2021-10-05 14:43 ` Peter Korsgaard [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=87ee8zcz2b.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=geomatsi@gmail.com \
    --cc=quentin.schulz@theobroma-systems.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