From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Jonas Rebmann <jre@pengutronix.de>,
Sascha Hauer <s.hauer@pengutronix.de>,
BAREBOX <barebox@lists.infradead.org>
Cc: Tobias Waldekranz <tobias@waldekranz.com>
Subject: Re: [PATCH v2 6/9] commands: tlv: clarify error opening tlv
Date: Tue, 7 Oct 2025 11:11:26 +0200 [thread overview]
Message-ID: <e2eb1933-2436-4eb7-8ba1-d09ea2788692@pengutronix.de> (raw)
In-Reply-To: <20250929-tlv-integration-v2-6-55f75da7e670@pengutronix.de>
On 9/29/25 10:03 AM, Jonas Rebmann wrote:
> Returning PTR_ERR(tlvdev) instead of printing an error message leads to
> the same output when CONFIG_CMD_TLV and when the specified path could
> not be read:
>
> tlv: No such file or directory
>
> In the latter case, print an explanatory message instead.
>
> Signed-off-by: Jonas Rebmann <jre@pengutronix.de>
Acked-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
FWIW, this is not strictly necessary anymore since:
https://lore.barebox.org/barebox/20250926091027.1024322-2-a.fatoum@pengutronix.de/T/#u
> ---
> commands/tlv.c | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/commands/tlv.c b/commands/tlv.c
> index 53fbc2a291..6118a2947f 100644
> --- a/commands/tlv.c
> +++ b/commands/tlv.c
> @@ -28,9 +28,11 @@ static int do_tlv(int argc, char *argv[])
> if (!filename)
> return COMMAND_ERROR_USAGE;
>
> - tlvdev = tlv_register_device_by_path(argv[optind], NULL);
> - if (IS_ERR(tlvdev))
> - return PTR_ERR(tlvdev);
> + tlvdev = tlv_register_device_by_path(filename, NULL);
> + if (IS_ERR(tlvdev)) {
> + printf("Could not open \"%s\": %m\n", filename);
> + return COMMAND_ERROR;
> + }
>
> if (fixup)
> return tlv_of_register_fixup(tlvdev);
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2025-10-07 9:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-29 8:03 [PATCH v2 0/9] TLV integration tests and test/py cleanup Jonas Rebmann
2025-09-29 8:03 ` [PATCH v2 1/9] test: when testfs feature is available, always enable it Jonas Rebmann
2025-10-07 9:07 ` Ahmad Fatoum
2025-09-29 8:03 ` [PATCH v2 2/9] test: provide testfs via fixture Jonas Rebmann
2025-10-07 9:08 ` Ahmad Fatoum
2025-09-29 8:03 ` [PATCH v2 3/9] test: move dm-verity testdata generation to fixture Jonas Rebmann
2025-10-07 9:09 ` Ahmad Fatoum
2025-09-29 8:03 ` [PATCH v2 4/9] test: move fitimage testdata generation to fixture and drop script Jonas Rebmann
2025-10-07 9:09 ` Ahmad Fatoum
2025-09-29 8:03 ` [PATCH v2 5/9] test: py: test_bootchooser: remove dead code Jonas Rebmann
2025-10-07 9:10 ` Ahmad Fatoum
2025-09-29 8:03 ` [PATCH v2 6/9] commands: tlv: clarify error opening tlv Jonas Rebmann
2025-10-07 9:11 ` Ahmad Fatoum [this message]
2025-09-29 8:03 ` [PATCH v2 7/9] ci: container: install crcmod and cryptography Jonas Rebmann
2025-10-07 9:11 ` Ahmad Fatoum
2025-09-29 8:03 ` [PATCH v2 8/9] configs: enable tlv command for multi_v7 and multi_v8 Jonas Rebmann
2025-10-07 9:12 ` Ahmad Fatoum
2025-09-29 8:04 ` [PATCH v2 9/9] test: py: add TLV integration tests Jonas Rebmann
2025-10-07 9:12 ` Ahmad Fatoum
2025-10-07 9:37 ` [PATCH v2 0/9] TLV integration tests and test/py cleanup Sascha Hauer
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=e2eb1933-2436-4eb7-8ba1-d09ea2788692@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=jre@pengutronix.de \
--cc=s.hauer@pengutronix.de \
--cc=tobias@waldekranz.com \
/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