From: Sudeep Holla <sudeep.holla@arm.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: James Clark <james.clark@arm.com>,
linux-arm-kernel@lists.infradead.org,
Sudeep Holla <sudeep.holla@arm.com>,
suzuki.poulose@arm.com, Lorenzo Pieralisi <lpieralisi@kernel.org>,
Mike Leach <mike.leach@linaro.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
coresight@lists.linaro.org,
linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH V2 6/7] coresight: stm: Move ACPI support from AMBA driver to platform driver
Date: Tue, 5 Dec 2023 09:35:08 +0000 [thread overview]
Message-ID: <ZW7uzBS2diyEKldn@bogus> (raw)
In-Reply-To: <81cad3a6-a080-424c-ad0b-0f08c4fe51a2@arm.com>
On Tue, Dec 05, 2023 at 10:50:19AM +0530, Anshuman Khandual wrote:
> Something like this works ?
>
> diff --git a/drivers/hwtracing/coresight/coresight-stm.c b/drivers/hwtracing/coresight/coresight-stm.c
> index 3387ebc9d8ab..2b6834c4cac6 100644
> --- a/drivers/hwtracing/coresight/coresight-stm.c
> +++ b/drivers/hwtracing/coresight/coresight-stm.c
> @@ -906,7 +906,7 @@ static int __stm_probe(struct device *dev, struct resource *res, void *dev_caps)
> pm_runtime_put(dev);
>
> dev_info(&drvdata->csdev->dev, "%s initialized\n",
> - (char *)dev_caps);
> + dev_caps ? (char *)dev_caps: "STM");
> return 0;
>
> cs_unregister:
Yes, looks good to me.
--
Regards,
Sudeep
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-12-05 9:35 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 6:20 [PATCH V2 0/7] coresight: Move remaining AMBA ACPI devices into platform driver Anshuman Khandual
2023-12-01 6:20 ` [PATCH V2 1/7] coresight: replicator: Move ACPI support from AMBA driver to " Anshuman Khandual
2023-12-01 12:35 ` Sudeep Holla
2023-12-04 4:26 ` Anshuman Khandual
2023-12-04 4:48 ` Anshuman Khandual
2023-12-04 9:57 ` James Clark
2023-12-04 11:37 ` Anshuman Khandual
2023-12-01 6:20 ` [PATCH V2 2/7] coresight: funnel: " Anshuman Khandual
2023-12-01 12:35 ` Sudeep Holla
2023-12-01 6:20 ` [PATCH V2 3/7] coresight: catu: " Anshuman Khandual
2023-12-01 12:35 ` Sudeep Holla
2023-12-01 13:41 ` Suzuki K Poulose
2023-12-04 6:48 ` Anshuman Khandual
2023-12-01 6:20 ` [PATCH V2 4/7] coresight: tpiu: " Anshuman Khandual
2023-12-01 12:36 ` Sudeep Holla
2023-12-01 6:20 ` [PATCH V2 5/7] coresight: tmc: " Anshuman Khandual
2023-12-01 12:36 ` Sudeep Holla
2023-12-04 10:42 ` James Clark
2023-12-04 10:50 ` Suzuki K Poulose
2023-12-04 10:54 ` James Clark
2023-12-04 11:40 ` Sudeep Holla
2023-12-05 3:56 ` Anshuman Khandual
2023-12-01 6:20 ` [PATCH V2 6/7] coresight: stm: " Anshuman Khandual
2023-12-01 12:36 ` Sudeep Holla
2023-12-04 10:23 ` James Clark
2023-12-04 11:50 ` Anshuman Khandual
2023-12-04 13:17 ` James Clark
2023-12-05 5:20 ` Anshuman Khandual
2023-12-05 9:35 ` Sudeep Holla [this message]
2023-12-05 10:18 ` Suzuki K Poulose
2023-12-04 11:58 ` Sudeep Holla
2023-12-01 6:20 ` [PATCH V2 7/7] coresight: debug: " Anshuman Khandual
2023-12-01 12:37 ` Sudeep Holla
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=ZW7uzBS2diyEKldn@bogus \
--to=sudeep.holla@arm.com \
--cc=alexandre.torgue@foss.st.com \
--cc=anshuman.khandual@arm.com \
--cc=coresight@lists.linaro.org \
--cc=james.clark@arm.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=lpieralisi@kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=mike.leach@linaro.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).