Linux Trace Kernel
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: sashiko-bot@kernel.org
Cc: sashiko-reviews@lists.linux.dev,
	"Georgi Djakov" <georgi.djakov@oss.qualcomm.com>,
	devicetree@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
	robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 3/6] trace: qpace: Add tracepoints for QPaCE operations
Date: Tue, 13 Oct 2026 19:29:31 -0400	[thread overview]
Message-ID: <20261013192931.7b208d17@226.227.38.69.naturalwireless.com> (raw)
In-Reply-To: <20260930150006.4FB591F000FF@smtp.kernel.org>

On Wed, 30 Sep 2026 15:00:05 +0000
sashiko-bot@kernel.org wrote:

> 
> > diff --git a/include/trace/events/qpace.h b/include/trace/events/qpace.h
> > new file mode 100644
> > index 0000000000000..3f0ccdb8f2060
> > --- /dev/null
> > +++ b/include/trace/events/qpace.h
> > @@ -0,0 +1,99 @@
> > +/* SPDX-License-Identifier: GPL-2.0-only */
> > +/*
> > + * Copyright (c) Qualcomm Technologies, Inc. and/or its subsidiaries.
> > + */
> > +
> > +#undef TRACE_SYSTEM
> > +#define TRACE_SYSTEM qpace
> > +
> > +#if !defined(_TRACE_QPACE_H) || defined(TRACE_HEADER_MULTI_READ)
> > +#define _TRACE_QPACE_H
> > +#include <linux/tracepoint.h>
> > +
> > +TRACE_EVENT(start_qpace_urgent_decompress,  
> 
> [Severity: Low]
> Does this tracepoint name violate the mandatory subsystem_event naming
> convention by using an action prefix instead of the subsystem prefix?

There is no mandatory subsystem_event naming convention. It just should
be unique. The naming is fine.

-- Steve


> 
> Could these be renamed to use the subsystem prefix, such as
> qpace_start_urgent_decompress?
> 


  reply	other threads:[~2026-10-13 23:29 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-30 14:52 [PATCH 0/6] soc: qcom: Add Qualcomm Page Compression Engine (QPaCE) driver Georgi Djakov
2026-09-30 14:52 ` [PATCH 1/6] dt-bindings: soc: qcom: Add QPaCE binding Georgi Djakov
2026-10-02  6:10   ` Krzysztof Kozlowski
2026-09-30 14:52 ` [PATCH 2/6] soc: qcom: qpace: Add Qualcomm Page Compression Engine driver Georgi Djakov
2026-09-30 15:04   ` sashiko-bot
2026-10-03  0:06     ` Oreoluwa Babatunde
2026-10-01  8:50   ` Krzysztof Kozlowski
2026-10-06 23:51     ` Oreoluwa Babatunde
2026-10-07  7:51       ` Krzysztof Kozlowski
2026-10-08  0:08         ` Oreoluwa Babatunde
2026-10-15 13:25     ` Georgi Djakov
2026-09-30 14:52 ` [PATCH 3/6] trace: qpace: Add tracepoints for QPaCE operations Georgi Djakov
2026-09-30 15:00   ` sashiko-bot
2026-10-13 23:29     ` Steven Rostedt [this message]
2026-09-30 14:52 ` [PATCH 4/6] zram: Add QPaCE zcomp backend Georgi Djakov
2026-09-30 15:08   ` sashiko-bot
2026-10-01  5:43   ` Sergey Senozhatsky
2026-10-06 23:53     ` Oreoluwa Babatunde
2026-10-08  3:52       ` Sergey Senozhatsky
2026-10-01  8:51   ` Krzysztof Kozlowski
2026-10-01 10:27     ` Sergey Senozhatsky
2026-10-07  0:04       ` Oreoluwa Babatunde
2026-10-09 23:54       ` Georgi Djakov
2026-10-13  4:22         ` Sergey Senozhatsky
2026-10-07  0:03     ` Oreoluwa Babatunde
2026-09-30 14:52 ` [PATCH 5/6] soc: qcom: qpace: Add LLCC slice support Georgi Djakov
2026-09-30 15:08   ` sashiko-bot
2026-09-30 14:52 ` [PATCH 6/6] arm64: dts: qcom: hawi: Add QPaCE DT node Georgi Djakov
2026-09-30 14:59   ` sashiko-bot

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=20261013192931.7b208d17@226.227.38.69.naturalwireless.com \
    --to=rostedt@goodmis.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=georgi.djakov@oss.qualcomm.com \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-bot@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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