From: Jani Nikula <jani.nikula@linux.intel.com>
To: S Sebinraj <s.sebinraj@intel.com>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
intel-xe@lists.freedesktop.org
Cc: jeevaka.badrappan@intel.com, S Sebinraj <s.sebinraj@intel.com>
Subject: Re: [PATCH v3 3/3] drm/xe: Refactoring the code as per review comment
Date: Tue, 16 Sep 2025 11:56:55 +0300 [thread overview]
Message-ID: <4f495d7ee43a7ddc7ada573f8ab6f69c6e0011f4@intel.com> (raw)
In-Reply-To: <20250916072704.2351591-4-s.sebinraj@intel.com>
On Tue, 16 Sep 2025, S Sebinraj <s.sebinraj@intel.com> wrote:
> Moved the trace file header to appropriate path
> "include/drm" and updated the code as per the same.
You're not supposed to address code review in independent patches, but
rather modify the original patches. This is kernel development basics.
BR,
Jani.
>
> Signed-off-by: S Sebinraj <s.sebinraj@intel.com>
> ---
> drivers/gpu/drm/drm_gpu_frequency_trace.c | 2 +-
> drivers/gpu/drm/xe/xe_gpu_freq_trace.h | 2 +-
> {drivers/gpu => include}/drm/drm_gpu_frequency_trace.h | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
> rename {drivers/gpu => include}/drm/drm_gpu_frequency_trace.h (96%)
>
> diff --git a/drivers/gpu/drm/drm_gpu_frequency_trace.c b/drivers/gpu/drm/drm_gpu_frequency_trace.c
> index b5fa5134226d..e33df068752d 100644
> --- a/drivers/gpu/drm/drm_gpu_frequency_trace.c
> +++ b/drivers/gpu/drm/drm_gpu_frequency_trace.c
> @@ -9,7 +9,7 @@
> #ifdef CONFIG_DRM_GPU_FREQUENCY_TRACE
>
> #define CREATE_TRACE_POINTS
> -#include "drm_gpu_frequency_trace.h"
> +#include <drm/drm_gpu_frequency_trace.h>
>
> EXPORT_TRACEPOINT_SYMBOL_GPL(gpu_frequency);
>
> diff --git a/drivers/gpu/drm/xe/xe_gpu_freq_trace.h b/drivers/gpu/drm/xe/xe_gpu_freq_trace.h
> index f188d529ae60..c15d41761296 100644
> --- a/drivers/gpu/drm/xe/xe_gpu_freq_trace.h
> +++ b/drivers/gpu/drm/xe/xe_gpu_freq_trace.h
> @@ -6,7 +6,7 @@
> #ifndef _XE_GPU_FREQ_TRACE_H_
> #define _XE_GPU_FREQ_TRACE_H_
>
> -#include "../drm_gpu_frequency_trace.h"
> +#include <drm/drm_gpu_frequency_trace.h>
>
> /* Convert MHz to KHz for tracepoint */
> #define MHZ_TO_KHZ(freq_mhz) ((freq_mhz) * 1000)
> diff --git a/drivers/gpu/drm/drm_gpu_frequency_trace.h b/include/drm/drm_gpu_frequency_trace.h
> similarity index 96%
> rename from drivers/gpu/drm/drm_gpu_frequency_trace.h
> rename to include/drm/drm_gpu_frequency_trace.h
> index cf6337847b3a..47f32fd295a4 100644
> --- a/drivers/gpu/drm/drm_gpu_frequency_trace.h
> +++ b/include/drm/drm_gpu_frequency_trace.h
> @@ -42,6 +42,6 @@ static inline void trace_gpu_frequency(unsigned int state, unsigned int gpu_id)
>
> #ifdef CONFIG_DRM_GPU_FREQUENCY_TRACE
> #undef TRACE_INCLUDE_PATH
> -#define TRACE_INCLUDE_PATH ../../drivers/gpu/drm
> +#define TRACE_INCLUDE_PATH ../../include/drm
> #include <trace/define_trace.h>
> #endif
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-09-16 8:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 7:27 [PATCH v3 0/3] drm: Add GPU frequency tracepoint S Sebinraj
2025-09-16 7:27 ` [PATCH v3 1/3] drm: Add GPU frequency tracepoint at DRM level S Sebinraj
2025-09-16 7:27 ` [PATCH v3 2/3] drm/xe: Add DRM GPU frequency tracepoint to Xe S Sebinraj
2025-09-16 7:27 ` [PATCH v3 3/3] drm/xe: Refactoring the code as per review comment S Sebinraj
2025-09-16 8:56 ` Jani Nikula [this message]
2025-09-17 4:14 ` Sebinraj, S
2025-09-17 7:23 ` Jani Nikula
2025-09-16 8:15 ` ✗ CI.checkpatch: warning for drm: Add GPU frequency tracepoint (rev2) Patchwork
2025-09-16 8:16 ` ✓ CI.KUnit: success " Patchwork
2025-09-16 8:52 ` ✓ Xe.CI.BAT: " Patchwork
2025-09-16 11:05 ` ✗ Xe.CI.Full: failure " Patchwork
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=4f495d7ee43a7ddc7ada573f8ab6f69c6e0011f4@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jeevaka.badrappan@intel.com \
--cc=s.sebinraj@intel.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