DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Srikanth Yalavarthi <syalavarthi@marvell.com>
Cc: Anup Prabhu <aprabhu@marvell.com>,
	dev@dpdk.org, sshankarnara@marvell.com,  ptakkar@marvell.com
Subject: Re: [PATCH v1] app/mldev: fix error reporting on IO failure
Date: Fri, 07 Jul 2023 10:18:28 +0200	[thread overview]
Message-ID: <2473443.TLkxdtWsSY@thomas> (raw)
In-Reply-To: <20230612180019.13176-1-syalavarthi@marvell.com>

12/06/2023 20:00, Srikanth Yalavarthi:
> Application is reporting the test output as success when a
> failure occurs in writing the output. Fix incorrect error
> reporting on failure to write output files.
> 
> Fixes: da6793390596 ("app/mldev: support inference validation")
> 
> Signed-off-by: Srikanth Yalavarthi <syalavarthi@marvell.com>

Applied, thanks.





      reply	other threads:[~2023-07-07  8:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-12 18:00 Srikanth Yalavarthi
2023-07-07  8:18 ` Thomas Monjalon [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=2473443.TLkxdtWsSY@thomas \
    --to=thomas@monjalon.net \
    --cc=aprabhu@marvell.com \
    --cc=dev@dpdk.org \
    --cc=ptakkar@marvell.com \
    --cc=sshankarnara@marvell.com \
    --cc=syalavarthi@marvell.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;
as well as URLs for NNTP newsgroup(s).