From: Yeoreum Yun <yeoreum.yun@arm.com>
To: Mike Leach <mike.leach@linaro.org>
Cc: suzuki.poulose@arm.com, james.clark@linaro.org,
alexander.shishkin@linux.intel.com, bigeasy@linutronix.de,
clrkwllms@kernel.org, rostedt@goodmis.org,
coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rt-devel@lists.linux.dev
Subject: Re: [PATCH v3 2/9] coresight-etm4x: change etmv4_drvdata spinlock type to raw_spinlock_t
Date: Fri, 20 Dec 2024 10:13:17 +0000 [thread overview]
Message-ID: <Z2VDPQMUH61THA8r@e129823.arm.com> (raw)
In-Reply-To: <CAJ9a7Vj6_ek9D-ZySt6dNAGWwWV=7yX36T=n7+n-Nak=UEhMdw@mail.gmail.com>
Hi Mike.
> > diff --git a/drivers/hwtracing/coresight/coresight-config.h b/drivers/hwtracing/coresight/coresight-config.h
> > index 6ba013975741..b9ebc9fcfb7f 100644
> > --- a/drivers/hwtracing/coresight/coresight-config.h
> > +++ b/drivers/hwtracing/coresight/coresight-config.h
> > @@ -206,7 +206,7 @@ struct cscfg_feature_csdev {
> > const struct cscfg_feature_desc *feat_desc;
> > struct coresight_device *csdev;
> > struct list_head node;
> > - spinlock_t *drv_spinlock;
> > + raw_spinlock_t *drv_spinlock;
> > int nr_params;
> > struct cscfg_parameter_csdev *params_csdev;
> > int nr_regs;
>
> The above changes are not etm4x specific - should be in the previous patch.
Yes, However when this changes, etm4x should be changed at the same time
because of build failures.
That's why I modified this with etm4x where currenly cscfg is used only.
Thanks
next prev parent reply other threads:[~2024-12-20 10:22 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 11:49 [PATCH v3 0/9] coresight: change some driver' spinlock type to raw_spinlock_t Yeoreum Yun
2024-12-16 11:49 ` [PATCH v3 1/9] coresight: change coresight_device lock " Yeoreum Yun
2024-12-19 12:23 ` Mike Leach
2024-12-16 11:49 ` [PATCH v3 2/9] coresight-etm4x: change etmv4_drvdata spinlock " Yeoreum Yun
2024-12-19 12:24 ` Mike Leach
2024-12-20 10:13 ` Yeoreum Yun [this message]
2024-12-16 11:50 ` [PATCH v3 3/9] coresight: change coresight_trace_id_map's lock " Yeoreum Yun
2024-12-19 12:24 ` Mike Leach
2024-12-16 11:50 ` [PATCH v3 4/9] coresight-cti: change cti_drvdata spinlock's " Yeoreum Yun
2024-12-19 12:24 ` Mike Leach
2024-12-16 11:50 ` [PATCH v3 5/9] coresight-etb10: change etb_drvdata " Yeoreum Yun
2024-12-19 12:24 ` Mike Leach
2024-12-16 11:50 ` [PATCH v3 6/9] coresight-funnel: change funnel_drvdata " Yeoreum Yun
2024-12-19 12:24 ` Mike Leach
2024-12-16 11:50 ` [PATCH v3 7/9] coresight-replicator: change replicator_drvdata " Yeoreum Yun
2024-12-19 12:24 ` Mike Leach
2024-12-16 11:50 ` [PATCH v3 8/9] coresight-tmc: change tmc_drvdata " Yeoreum Yun
2024-12-19 12:23 ` Mike Leach
2024-12-16 11:50 ` [PATCH v3 9/9] coresight/ultrasoc: change cti_drvdata " Yeoreum Yun
2024-12-19 12:24 ` Mike Leach
2024-12-20 10:07 ` Yeoreum Yun
2024-12-19 12:27 ` [PATCH v3 0/9] coresight: change some driver' spinlock " Mike Leach
2024-12-20 10:06 ` Yeoreum Yun
2024-12-20 10:38 ` Yeoreum Yun
2024-12-20 11:35 ` Suzuki K Poulose
2024-12-20 11:39 ` Yeoreum Yun
2024-12-20 11:48 ` Suzuki K Poulose
2024-12-20 11:50 ` Yeoreum Yun
2024-12-21 17:02 ` Yeoreum Yun
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=Z2VDPQMUH61THA8r@e129823.arm.com \
--to=yeoreum.yun@arm.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bigeasy@linutronix.de \
--cc=clrkwllms@kernel.org \
--cc=coresight@lists.linaro.org \
--cc=james.clark@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=mike.leach@linaro.org \
--cc=rostedt@goodmis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.