linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: "linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 0/7] coresight: Miscellaneous fixes
Date: Tue, 21 Jun 2016 11:38:27 -0600	[thread overview]
Message-ID: <CANLsYkwVnrK9VF6Fem2FNvRt_mY+WGi5SD11JG2E5f5pw0RUQw@mail.gmail.com> (raw)
In-Reply-To: <1466525454-14702-1-git-send-email-suzuki.poulose@arm.com>

On 21 June 2016 at 10:10, Suzuki K Poulose <suzuki.poulose@arm.com> wrote:
> This is a collection of cleanups and minor enhancements to the
> coresight driver. Applies on v4.7-rc4
>
> Changes since V2:
>  - Removed patches already queued as fixes for 4.7
>  - Addressed comments on V2.
>
> Changes since V1:
>  - Added a patch to limit the trace data
>  - Added a patch to fix tmc_read_unprepare_etr (another crash)
>  - Split the patch to remove erraneous dma_free_coherent.
>  - Use consistent error message format for coresight_timeout cleanup.
>  - Fixed checkpatch warnings on the commit description, there are
>    some errors reported on the "crash output" in the commit description.
>    May be the checkpatch needs to be fixed ?
>
>
> Suzuki K Poulose (7):
>   coresight: Remove erroneous dma_free_coherent in tmc_probe
>   coresight: Consolidate error handling path for tmc_probe
>   coresight: Fix csdev connections initialisation
>   coresight: tmc: Limit the trace to available data
>   coresight: etmv4: Fix ETMv4x peripheral ID table
>   coresight: Cleanup TMC status check
>   coresight: Add better messages for coresight_timeout
>
>  drivers/hwtracing/coresight/coresight-etb10.c   |  6 +--
>  drivers/hwtracing/coresight/coresight-etm4x.c   | 14 +++----
>  drivers/hwtracing/coresight/coresight-tmc-etf.c |  2 +
>  drivers/hwtracing/coresight/coresight-tmc-etr.c | 12 ++++--
>  drivers/hwtracing/coresight/coresight-tmc.c     | 51 +++++++++++--------------
>  drivers/hwtracing/coresight/coresight-tmc.h     |  4 +-
>  drivers/hwtracing/coresight/coresight.c         | 24 +++++++-----
>  7 files changed, 58 insertions(+), 55 deletions(-)
>
> --
> 1.9.1
>

I have applied the whole set.

Thanks,
Mathieu

      parent reply	other threads:[~2016-06-21 17:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-21 16:10 [PATCH v3 0/7] coresight: Miscellaneous fixes Suzuki K Poulose
2016-06-21 16:10 ` [PATCH v3 1/7] coresight: Remove erroneous dma_free_coherent in tmc_probe Suzuki K Poulose
2016-06-21 16:10 ` [PATCH v3 2/7] coresight: Consolidate error handling path for tmc_probe Suzuki K Poulose
2016-06-21 16:10 ` [PATCH v3 3/7] coresight: Fix csdev connections initialisation Suzuki K Poulose
2016-06-21 16:10 ` [PATCH v3 4/7] coresight: tmc: Limit the trace to available data Suzuki K Poulose
2016-06-21 16:10 ` [PATCH v3 5/7] coresight: etmv4: Fix ETMv4x peripheral ID table Suzuki K Poulose
2016-06-21 16:10 ` [PATCH v3 6/7] coresight: Cleanup TMC status check Suzuki K Poulose
2016-06-21 16:10 ` [PATCH v3 7/7] coresight: Add better messages for coresight_timeout Suzuki K Poulose
2016-06-21 17:38 ` Mathieu Poirier [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=CANLsYkwVnrK9VF6Fem2FNvRt_mY+WGi5SD11JG2E5f5pw0RUQw@mail.gmail.com \
    --to=mathieu.poirier@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=suzuki.poulose@arm.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).