From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 0/3] Version bumps for PRU packages
Date: Mon, 3 Feb 2020 22:17:55 +0100 [thread overview]
Message-ID: <20200203211755.GA2655@scaer> (raw)
In-Reply-To: <20200115021709.64647-1-ashcharles@gmail.com>
Ash, All,
On 2020-01-14 21:17 -0500, Ash Charles spake thusly:
> Bump versions for TI's PRU co-processor toolcahin and support libraries.
>
> Note, I don't have hardware so I'm unable to confirm that these versions
> do more than build correctly.
>
> v2: Add signed-off-by, correct license files and update/add hashes for
> licenses per [1,2]. Underlying licenses are the same.
> [1] https://patchwork.ozlabs.org/patch/1222414/#2341881
> [2] https://patchwork.ozlabs.org/patch/1222415/#2341882
>
> Ash Charles (3):
> ti-cgt-pru: bump to latest version 2.3.3
> pru-software-support: bump to latest version 5.6.0
> pru_software_support: add license file to hash
Series applied to master.
I just folded the third patch into the second one, because we already
had a hash for the license file (that was applied a bit earlier today).
Thanks! :-)
Regards,
Yann E. MORIN.
> package/pru-software-support/pru-software-support.hash | 3 ++-
> package/pru-software-support/pru-software-support.mk | 9 +++++----
> package/ti-cgt-pru/ti-cgt-pru.hash | 6 +++---
> package/ti-cgt-pru/ti-cgt-pru.mk | 6 +++---
> 4 files changed, 13 insertions(+), 11 deletions(-)
>
> --
> 2.24.1
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2020-02-03 21: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 ` [Buildroot] [PATCH v2 3/3] pru_software_support: add license file to hash Ash Charles
2020-02-03 21:17 ` Yann E. MORIN [this message]
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=20200203211755.GA2655@scaer \
--to=yann.morin.1998@free.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.