From: "liuqi (BA)" <liuqi115@huawei.com>
To: Randy Dunlap <rdunlap@infradead.org>,
<mathieu.poirier@linaro.org>, <suzuki.poulose@arm.com>,
<mike.leach@linaro.org>
Cc: <coresight@lists.linaro.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <linuxarm@huawei.com>
Subject: Re: [PATCH v2] drivers/coresight: ultrasoc: Add System Memory Buffer driver
Date: Sat, 6 Nov 2021 15:31:20 +0800 [thread overview]
Message-ID: <477a4a27-2cd7-e9bc-363c-577271abac93@huawei.com> (raw)
In-Reply-To: <af9dbbbf-64f0-f3c6-fa30-4e306e6156d2@infradead.org>
On 2021/11/5 9:36, Randy Dunlap wrote:
> On 11/4/21 6:20 PM, Qi Liu wrote:
>> diff --git a/drivers/hwtracing/coresight/ultrasoc/Kconfig
>> b/drivers/hwtracing/coresight/ultrasoc/Kconfig
>> new file mode 100644
>> index 000000000000..c18c25bf9df3
>> --- /dev/null
>> +++ b/drivers/hwtracing/coresight/ultrasoc/Kconfig
>> @@ -0,0 +1,12 @@
>> +# SPDX-License-Identifier: MIT
>> +#
>> +# ultrasoc configuration
>> +#
>> +config ULTRASOC_SMB
>> + tristate "Ultrasoc system memory buffer drivers"
>> + depends on ARM64 && CORESIGHT
>
> The "depends" line should be indented with a tab instead of spaces...
>
ah, yes, my editor might be set incorrectly, thanks for the reminder,
I'll correct it next time.
Qi
>> + help
>> + This enables support for the Ultrasoc system memory buffer
>> + driver that is responsible for receiving the trace data from
>> + Coresight ETM devices and storing them to a system buffer
>> + respectively.
>
>
next prev parent reply other threads:[~2021-11-06 7:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-05 1:20 Qi Liu
2021-11-05 1:36 ` Randy Dunlap
2021-11-06 7:31 ` liuqi (BA) [this message]
2021-11-17 18:09 ` Mathieu Poirier
2021-11-18 1:39 ` liuqi (BA)
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=477a4a27-2cd7-e9bc-363c-577271abac93@huawei.com \
--to=liuqi115@huawei.com \
--cc=coresight@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mathieu.poirier@linaro.org \
--cc=mike.leach@linaro.org \
--cc=rdunlap@infradead.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
all inboxes | Powered by JetHome®