From: David Marchand <david.marchand@redhat.com>
To: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
Cc: dev <dev@dpdk.org>,
Lukasz Wojciechowski <l.wojciechow@partner.samsung.com>,
Aaron Conole <aconole@redhat.com>, nd <nd@arm.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
Nipun Gupta <nipun.gupta@nxp.com>,
Pavan Nikhilesh <pbhagavatula@marvell.com>
Subject: Re: [dpdk-dev] [PATCH v2] eal: change the log level for test assert macro
Date: Fri, 17 Jul 2020 10:54:36 +0200 [thread overview]
Message-ID: <CAJFAV8zzYnZmq0o6FPjUFMsAvB6_sA5UsD+va3FAS4txT93cMA@mail.gmail.com> (raw)
In-Reply-To: <20200716183927.32967-1-honnappa.nagarahalli@arm.com>
On Thu, Jul 16, 2020 at 8:39 PM Honnappa Nagarahalli
<honnappa.nagarahalli@arm.com> wrote:
>
> Change the log level for RTE_TEST_ASSERT macro to error to help
> log errors while running test cases.
>
> Suggested-by: David Marchand <david.marchand@redhat.com>
> Signed-off-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
> Acked-by: Aaron Conole <aconole@redhat.com>
> Acked-by: Lukasz Wojciechowski <l.wojciechow@partner.samsung.com>
We need this patch for the CI.
The change looks safe to me, so I went and applied it without waiting
for feedback from eventdev guys.
Thanks Honnappa.
--
David Marchand
prev parent reply other threads:[~2020-07-17 8:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200715202024eucas1p2d1ddce75f7e5b1181d7a8f29b50fc4b5@eucas1p2.samsung.com>
2020-07-15 20:20 ` [dpdk-dev] [PATCH] " Honnappa Nagarahalli
2020-07-16 13:00 ` Aaron Conole
2020-07-16 18:40 ` Honnappa Nagarahalli
2020-07-16 15:06 ` David Marchand
2020-07-16 18:41 ` Honnappa Nagarahalli
2020-07-16 15:16 ` Lukasz Wojciechowski
2020-07-16 18:39 ` [dpdk-dev] [PATCH v2] " Honnappa Nagarahalli
2020-07-17 8:54 ` David Marchand [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=CAJFAV8zzYnZmq0o6FPjUFMsAvB6_sA5UsD+va3FAS4txT93cMA@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=aconole@redhat.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=honnappa.nagarahalli@arm.com \
--cc=jerinj@marvell.com \
--cc=l.wojciechow@partner.samsung.com \
--cc=nd@arm.com \
--cc=nipun.gupta@nxp.com \
--cc=pbhagavatula@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).