From: Ash Charles <ashcharles@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 3/3] pru_software_support: add license file to hash
Date: Tue, 14 Jan 2020 21:17:09 -0500 [thread overview]
Message-ID: <20200115021709.64647-4-ashcharles@gmail.com> (raw)
In-Reply-To: <20200115021709.64647-1-ashcharles@gmail.com>
Signed-off-by: Ash Charles <ashcharles@gmail.com>
---
package/pru-software-support/pru-software-support.hash | 1 +
1 file changed, 1 insertion(+)
diff --git a/package/pru-software-support/pru-software-support.hash b/package/pru-software-support/pru-software-support.hash
index f7c2d505a2..675773c96c 100644
--- a/package/pru-software-support/pru-software-support.hash
+++ b/package/pru-software-support/pru-software-support.hash
@@ -1,2 +1,3 @@
# Locally-calculated hash
sha256 d6d1f76ab5a50dbdf1dff834b271f9d3ffa7424e4d9615e00713f3f81ed5787e pru-software-support-package-v5.6.0.tar.gz
+sha256 a68530804624227e4f2e007eacb5c2d616695426082e895ee1e2d77d3833f5f7 PRU-Package-v6.0-Manifest.html
--
2.24.1
next prev parent reply other threads:[~2020-01-15 2:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 0:58 [Buildroot] [PATCH 0/2] Version bumps for PRU packages Ash Charles
2020-01-14 0:58 ` [Buildroot] [PATCH 1/2] ti-cgt-pru: bump to latest version 2.3.3 Ash Charles
2020-01-14 21:46 ` Thomas Petazzoni
2020-01-15 2:17 ` [Buildroot] [PATCH v2 0/3] Version bumps for PRU packages Ash Charles
2020-01-15 2:17 ` [Buildroot] [PATCH v2 1/3] ti-cgt-pru: bump to latest version 2.3.3 Ash Charles
2020-01-15 2:17 ` [Buildroot] [PATCH v2 2/3] pru-software-support: bump to latest version 5.6.0 Ash Charles
2020-01-15 2:17 ` Ash Charles [this message]
2020-02-03 21:17 ` [Buildroot] [PATCH v2 0/3] Version bumps for PRU packages Yann E. MORIN
2020-01-14 0:58 ` [Buildroot] [PATCH 2/2] pru-software-support: bump to latest version 5.6.0 Ash Charles
2020-01-14 21:46 ` Thomas Petazzoni
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=20200115021709.64647-4-ashcharles@gmail.com \
--to=ashcharles@gmail.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