From: mathieu.poirier@linaro.org (Mathieu Poirier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] coresight: fix for v4.7-rcX
Date: Tue, 14 Jun 2016 11:17:11 -0600 [thread overview]
Message-ID: <1465924634-22310-1-git-send-email-mathieu.poirier@linaro.org> (raw)
Hi Greg,
These 3 patches address problems that lead to kernel crashes. As such
I think there is value in fixing them in this cycle rather than waiting
for next merge window.
Best regards,
Mathieu
Suzuki K Poulose (3):
coresight: Fix NULL pointer dereference in _coresight_build_path
coresight: Fix tmc_read_unprepare_etr
coresight: Fix erroneous memset in tmc_read_unprepare_etr
drivers/hwtracing/coresight/coresight-tmc-etr.c | 11 ++++-------
drivers/hwtracing/coresight/coresight.c | 6 +++---
2 files changed, 7 insertions(+), 10 deletions(-)
--
2.5.0
next reply other threads:[~2016-06-14 17:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 17:17 Mathieu Poirier [this message]
2016-06-14 17:17 ` [PATCH 1/3] coresight: Fix NULL pointer dereference in _coresight_build_path Mathieu Poirier
2016-06-14 17:17 ` [PATCH 2/3] coresight: Fix tmc_read_unprepare_etr Mathieu Poirier
2016-06-14 17:17 ` [PATCH 3/3] coresight: Fix erroneous memset in tmc_read_unprepare_etr Mathieu Poirier
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=1465924634-22310-1-git-send-email-mathieu.poirier@linaro.org \
--to=mathieu.poirier@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).