public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jerome Forissier <jerome.forissier@linaro.org>
To: u-boot@lists.denx.de
Cc: Ilias Apalodimas <ilias.apalodimas@linaro.org>,
	Tom Rini <trini@konsulko.com>, Simon Glass <sjg@chromium.org>,
	Jerome Forissier <jerome.forissier@linaro.org>
Subject: [PATCH v2 0/3] Add 'trace wipe'
Date: Fri, 13 Dec 2024 13:45:35 +0100	[thread overview]
Message-ID: <cover.1734093566.git.jerome.forissier@linaro.org> (raw)

This short series adds the 'trace wipe' command which clears the trace
buffer, allowing to re-start a capture from scratch.

Jerome Forissier (3):
  trace: add support for 'trace wipe'
  test: test_trace.py: test 'trace wipe'
  trace: document 'trace wipe'

 cmd/trace.c                 |  5 ++++
 doc/develop/trace.rst       | 11 +++++++++
 include/trace.h             |  2 ++
 lib/trace.c                 | 47 ++++++++++++++++++++++++++-----------
 test/py/tests/test_trace.py | 30 +++++++++++++++++++++++
 5 files changed, 81 insertions(+), 14 deletions(-)

v2:
- Change 'trace clear' to 'trace wipe'
- Add doc patch
- Minor edits to the patch descriptions

v1:
- Added patch: 'test: test_trace.py: test "trace clear" command'

v0:
- Sent as a single patch:
https://lists.denx.de/pipermail/u-boot/2024-December/574148.html

-- 
2.43.0


             reply	other threads:[~2024-12-13 12:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-13 12:45 Jerome Forissier [this message]
2024-12-13 12:45 ` [PATCH v2 1/3] trace: add support for 'trace wipe' Jerome Forissier
2024-12-15  7:31   ` Ilias Apalodimas
2024-12-13 12:45 ` [PATCH v2 2/3] test: test_trace.py: test " Jerome Forissier
2024-12-13 12:45 ` [PATCH v2 3/3] trace: document " Jerome Forissier
2024-12-15  9:20   ` Ilias Apalodimas
2025-01-01 17:54 ` [PATCH v2 0/3] Add " Tom Rini

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=cover.1734093566.git.jerome.forissier@linaro.org \
    --to=jerome.forissier@linaro.org \
    --cc=ilias.apalodimas@linaro.org \
    --cc=sjg@chromium.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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