From: Peter Marko <peter.marko@siemens.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH v2 0/4] cve-check improvements
Date: Wed, 7 Jun 2017 08:04:27 +0200 [thread overview]
Message-ID: <1496815471-23075-1-git-send-email-peter.marko@siemens.com> (raw)
In-Reply-To: <1496647273-9693-1-git-send-email-peter.marko@siemens.com>
Hi,
this series of patches fixes some issues with cve-check functionality.
v2: drop patch for RM_OLD_IMAGE handling
Peter Marko (4):
cve-check: add do_rootfs dependency on cve-check
cve-check: do not parse error output
cve-check: clean cve-check recipe result before re-building
cve-check-tool: fix crash on exceptions
meta/classes/cve-check.bbclass | 8 +++-
.../cve-check-tool/cve-check-tool_5.6.4.bb | 1 +
...01-Fix-freeing-memory-allocated-by-sqlite.patch | 50 ++++++++++++++++++++++
3 files changed, 58 insertions(+), 1 deletion(-)
create mode 100644 meta/recipes-devtools/cve-check-tool/files/0001-Fix-freeing-memory-allocated-by-sqlite.patch
--
2.1.4
next prev parent reply other threads:[~2017-06-07 6:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 7:21 [PATCH 0/5] cve-check improvements Peter Marko
2017-06-05 7:21 ` [PATCH 1/5] cve-check: honor RM_OLD_IMAGE flag Peter Marko
2017-06-05 11:05 ` Marko, Peter
2017-06-05 7:21 ` [PATCH 2/5] cve-check: add do_rootfs dependency on cve-check Peter Marko
2017-06-05 7:21 ` [PATCH 3/5] cve-check: do not parse error output Peter Marko
2017-06-05 7:21 ` [PATCH 4/5] cve-check: clean cve-check recipe result before re-building Peter Marko
2017-06-05 7:21 ` [PATCH 5/5] cve-check-tool: fix crash on exceptions Peter Marko
2017-06-07 6:04 ` Peter Marko [this message]
2017-06-07 6:04 ` [PATCH v2 1/4] cve-check: add do_rootfs dependency on cve-check Peter Marko
2017-06-07 6:04 ` [PATCH v2 2/4] cve-check: do not parse error output Peter Marko
2017-06-07 6:04 ` [PATCH v2 3/4] cve-check: clean cve-check recipe result before re-building Peter Marko
2017-06-07 6:04 ` [PATCH v2 4/4] cve-check-tool: fix crash on exceptions Peter Marko
2017-06-07 16:03 ` Leonardo Sandoval
2017-06-07 16:20 ` Marko, Peter
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=1496815471-23075-1-git-send-email-peter.marko@siemens.com \
--to=peter.marko@siemens.com \
--cc=openembedded-core@lists.openembedded.org \
/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