U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: U-Boot Mailing List <u-boot@lists.denx.de>
Cc: Tom Rini <trini@konsulko.com>, Simon Glass <sjg@chromium.org>,
	Neha Malcom Francis <n-francis@ti.com>
Subject: [PATCH v2 2/6] buildman: Add python3-pycryptodome
Date: Fri, 21 Jun 2024 07:14:18 -0600	[thread overview]
Message-ID: <20240621131423.2363294-3-sjg@chromium.org> (raw)
In-Reply-To: <20240621131423.2363294-1-sjg@chromium.org>

This is used by some Binman entry types, so add it to allow more tests
to pass.

Signed-off-by: Simon Glass <sjg@chromium.org>
---

Changes in v2:
- Add to buildman requirements instead

 tools/buildman/requirements.txt | 1 +
 1 file changed, 1 insertion(+)

diff --git a/tools/buildman/requirements.txt b/tools/buildman/requirements.txt
index 564e54898a4..052d0ed5c6f 100644
--- a/tools/buildman/requirements.txt
+++ b/tools/buildman/requirements.txt
@@ -1,4 +1,5 @@
 coverage==6.2
 jsonschema==4.17.3
+pycryptodome==3.20
 pyyaml==6.0
 yamllint==1.26.3
-- 
2.34.1


  parent reply	other threads:[~2024-06-21 13:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-21 13:14 [PATCH v2 0/6] Add Binman code-coverage test to CI Simon Glass
2024-06-21 13:14 ` [PATCH v2 1/6] buildman: Add python3-coverage Simon Glass
2024-06-21 15:22   ` Tom Rini
2024-06-21 13:14 ` Simon Glass [this message]
2024-06-21 15:22   ` [PATCH v2 2/6] buildman: Add python3-pycryptodome Tom Rini
2024-06-21 13:14 ` [PATCH v2 3/6] buildman: Fix a few typos in toolchain code Simon Glass
2024-06-21 13:14 ` [PATCH v2 4/6] buildman: Support building within a Python venv Simon Glass
2024-06-21 13:14 ` [PATCH v2 5/6] u_boot_pylib: Use correct coverage tool within venv Simon Glass
2024-06-21 13:14 ` [PATCH v2 6/6] CI: Run code-coverage test for Binman Simon Glass

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=20240621131423.2363294-3-sjg@chromium.org \
    --to=sjg@chromium.org \
    --cc=n-francis@ti.com \
    --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