From: Steven Rostedt <rostedt@goodmis.org>
To: Michael Petlan <mpetlan@redhat.com>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH 0/3] Fix several Coverity andf Clang warnings in libtraceevent
Date: Thu, 20 Oct 2022 15:15:12 -0400 [thread overview]
Message-ID: <20221020151512.3bdc783b@gandalf.local.home> (raw)
In-Reply-To: <20220930111002.6107-1-mpetlan@redhat.com>
On Fri, 30 Sep 2022 13:09:59 +0200
Michael Petlan <mpetlan@redhat.com> wrote:
> Hello.
>
> When rebasing to libtraceevent-1.5.3 in RHEL, Coverity has found some
> issues. I have tried to fix them. Could you please have a look at the
> patches attached?
>
> Thank you.
Applied. Thanks Michael!
-- Steve
prev parent reply other threads:[~2022-10-20 19:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 11:09 [PATCH 0/3] Fix several Coverity andf Clang warnings in libtraceevent Michael Petlan
2022-09-30 11:10 ` [PATCH 1/3] libtraceevent: Fix uninitialized has_0x compiler warning Michael Petlan
2022-09-30 11:10 ` [PATCH 2/3] libtraceevent: Fix check-after-deref coverity flaw Michael Petlan
2022-09-30 11:10 ` [PATCH 3/3] libtraceevent: Fix Branch condition garbage value compiler warning Michael Petlan
2022-10-20 19:15 ` Steven Rostedt [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=20221020151512.3bdc783b@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=mpetlan@redhat.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).