From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/ptm2human: new package
Date: Sun, 26 Jan 2020 16:08:05 +0100 [thread overview]
Message-ID: <20200126150805.GN32369@scaer> (raw)
In-Reply-To: <20200124182447.17295-1-juju@cotds.org>
Julien, All,
On 2020-01-24 19:24 +0100, Julien Olivain spake thusly:
> ptm2human is a decoder for trace data outputted by Program
> Trace Macrocell (PTM) and Embedded Trace Macrocell (ETMv4).
> It deconstructs ID packets and data packets from the
> formatter of ARM Coresight ETB, and then translates the
> trace data to a human-readable format.
>
> ./utils/test-pkg --package ptm2human --all
> 44 builds, 29 skipped, 0 build failed, 0 legal-info failed
>
> Signed-off-by: Julien Olivain <juju@cotds.org>
I've applied to msater, with the folowing chamges:
- drop the host variant
- introduce _ARCH_SUPPORTS
- comment why we need autoreconf
- drop spurious empty line
For the host variant, I dropped it because I don't see how this would be
usefull as a build-time tool. If you believe you have a good case for
it, please resend a patch adding the host variant with a commit log that
explains why it is nice to have it.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| 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. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2020-01-26 15:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 18:24 [Buildroot] [PATCH 1/1] package/ptm2human: new package Julien Olivain
2020-01-26 15:08 ` Yann E. MORIN [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=20200126150805.GN32369@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox