linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Tingwei Zhang <tingweiz@codeaurora.org>
To: Mike Leach <mike.leach@linaro.org>
Cc: coresight@lists.linaro.org, tingwei@codeaurora.org,
	mathieu.poirier@linaro.org, linux-arm-kernel@lists.infradead.org,
	suzuki.poulose@arm.com
Subject: Re: [PATCH 0/1] Fix issue with module unload and CTI cleanup
Date: Thu, 30 Jul 2020 10:41:34 +0800	[thread overview]
Message-ID: <20200730024134.GA23276@codeaurora.org> (raw)
In-Reply-To: <20200729195233.30369-1-mike.leach@linaro.org>

On Thu, Jul 30, 2020 at 03:52:32AM +0800, Mike Leach wrote:
> In the proposed Coresight module set v5 [1] from Tingwei, unloading the
> ETM module before the CTI module will crash on unload of the CTI module
> due to the cleanup callback from Coresight to the CTI module not working
> correctly in clearing sysfs callbacks.
> 
> Patch fixes this issue. Applies on [1].
> 
> Tingwei - could you consider adding this to your set for v6?

Sure, Mike.  I'll pick this change into v6.

Thanks, Tingwei
> 
> [1] https://lists.linaro.org/pipermail/coresight/2020-July/004349.html
> 
> Mike Leach (1):
>   coresight: cti: Fix bug clearing sysfs links on callback
> 
>  drivers/hwtracing/coresight/coresight-core.c     | 4 ++--
>  drivers/hwtracing/coresight/coresight-cti-core.c | 3 +--
>  2 files changed, 3 insertions(+), 4 deletions(-)
> 
> -- 
> 2.17.1
> 

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      parent reply	other threads:[~2020-07-30  2:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-29 19:52 [PATCH 0/1] Fix issue with module unload and CTI cleanup Mike Leach
2020-07-29 19:52 ` [PATCH 1/1] coresight: cti: Fix bug clearing sysfs links on callback Mike Leach
2020-07-30  2:41 ` Tingwei Zhang [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=20200730024134.GA23276@codeaurora.org \
    --to=tingweiz@codeaurora.org \
    --cc=coresight@lists.linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=mike.leach@linaro.org \
    --cc=suzuki.poulose@arm.com \
    --cc=tingwei@codeaurora.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).