From: Sudeep Holla <sudeep.holla@arm.com>
To: lukasz.luba@arm.com
Cc: linux-kernel@vger.kernel.org, rostedt@goodmis.org,
mingo@redhat.com, james.quinlan@broadcom.com,
Sudeep Holla <sudeep.holla@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/2] include: trace: Add SCMI header with trace events
Date: Tue, 24 Dec 2019 18:34:49 +0000 [thread overview]
Message-ID: <20191224183403.GA13926@bogus> (raw)
In-Reply-To: <20191217134345.14004-1-lukasz.luba@arm.com>
On Tue, Dec 17, 2019 at 01:43:44PM +0000, lukasz.luba@arm.com wrote:
> From: Lukasz Luba <lukasz.luba@arm.com>
>
> Adding trace events would help to measure the speed of the communication
> channel. It can be also potentially used helpful during investigation
> of some issues platforms which use different transport layer.
>
> Update also MAINTAINERS file with information that the new trace events
> are maintained.
>
Applied both the patches for v5.6
--
Regards,
Sudeep
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Sudeep Holla <sudeep.holla@arm.com>
To: lukasz.luba@arm.com
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, mingo@redhat.com,
james.quinlan@broadcom.com, rostedt@goodmis.org,
Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: [PATCH v2 1/2] include: trace: Add SCMI header with trace events
Date: Tue, 24 Dec 2019 18:34:49 +0000 [thread overview]
Message-ID: <20191224183403.GA13926@bogus> (raw)
In-Reply-To: <20191217134345.14004-1-lukasz.luba@arm.com>
On Tue, Dec 17, 2019 at 01:43:44PM +0000, lukasz.luba@arm.com wrote:
> From: Lukasz Luba <lukasz.luba@arm.com>
>
> Adding trace events would help to measure the speed of the communication
> channel. It can be also potentially used helpful during investigation
> of some issues platforms which use different transport layer.
>
> Update also MAINTAINERS file with information that the new trace events
> are maintained.
>
Applied both the patches for v5.6
--
Regards,
Sudeep
next prev parent reply other threads:[~2019-12-24 18:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 13:43 [PATCH v2 1/2] include: trace: Add SCMI header with trace events lukasz.luba
2019-12-17 13:43 ` lukasz.luba
2019-12-17 13:43 ` [PATCH v2 2/2] drivers: firmware: scmi: Extend SCMI transport layer by " lukasz.luba
2019-12-17 13:43 ` lukasz.luba
2019-12-24 18:34 ` Sudeep Holla [this message]
2019-12-24 18:34 ` [PATCH v2 1/2] include: trace: Add SCMI header with " 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=20191224183403.GA13926@bogus \
--to=sudeep.holla@arm.com \
--cc=james.quinlan@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.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 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.