Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
To: Ashutosh Dixit <ashutosh.dixit@intel.com>
Cc: <intel-xe@lists.freedesktop.org>,
	Zbigniew Kempczynski <zbigniew.kempczynski@intel.com>
Subject: Re: [PATCH] drm/xe/observation: Drop empty sysctl table entry
Date: Mon, 5 Aug 2024 10:43:21 -0700	[thread overview]
Message-ID: <ZrEPOSEfqx3m4TAs@orsosgc001> (raw)
In-Reply-To: <20240805062057.3547560-1-ashutosh.dixit@intel.com>

On Sun, Aug 04, 2024 at 11:20:57PM -0700, Ashutosh Dixit wrote:
>An empty sysctl table entry was inadvertently left behind for observation
>sysctl. The breaks on 6.11 with the following errors:
>
>[  219.654850] sysctl table check failed: dev/xe/(null) procname is null
>[  219.654862] sysctl table check failed: dev/xe/(null) No proc_handler
>
>Drop the empty entry.
>
>Fixes: 8169b2097d88 ("drm/xe/uapi: Rename xe perf layer as xe observation layer")
>Closes: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/2419
>Signed-off-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
>---
> drivers/gpu/drm/xe/xe_observation.c | 1 -
> 1 file changed, 1 deletion(-)
>
>diff --git a/drivers/gpu/drm/xe/xe_observation.c b/drivers/gpu/drm/xe/xe_observation.c
>index fcb584b42a7d5..a78c92a44ec2d 100644
>--- a/drivers/gpu/drm/xe/xe_observation.c
>+++ b/drivers/gpu/drm/xe/xe_observation.c
>@@ -66,7 +66,6 @@ static struct ctl_table observation_ctl_table[] = {
> 	 .extra1 = SYSCTL_ZERO,
> 	 .extra2 = SYSCTL_ONE,
> 	 },
>-	{}
Looks correct. I don't see this (sentinel) in other drivers using 
ctl_table, so this is 

Reviewed-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>

Umesh
> };
>
> /**
>-- 
>2.41.0
>

      parent reply	other threads:[~2024-08-05 17:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-05  6:20 [PATCH] drm/xe/observation: Drop empty sysctl table entry Ashutosh Dixit
2024-08-05  6:26 ` ✓ CI.Patch_applied: success for " Patchwork
2024-08-05  6:26 ` ✓ CI.checkpatch: " Patchwork
2024-08-05  6:27 ` ✓ CI.KUnit: " Patchwork
2024-08-05  6:39 ` [PATCH] " Chauhan, Shekhar
2024-08-05  6:37   ` Dixit, Ashutosh
2024-08-05  7:29     ` Chauhan, Shekhar
2024-08-05  6:39 ` ✓ CI.Build: success for " Patchwork
2024-08-05  6:41 ` ✓ CI.Hooks: " Patchwork
2024-08-05  6:43 ` ✓ CI.checksparse: " Patchwork
2024-08-05  7:04 ` ✓ CI.BAT: " Patchwork
2024-08-05  8:44 ` ✗ CI.FULL: failure " Patchwork
2024-08-05 17:43 ` Umesh Nerlige Ramappa [this message]

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=ZrEPOSEfqx3m4TAs@orsosgc001 \
    --to=umesh.nerlige.ramappa@intel.com \
    --cc=ashutosh.dixit@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=zbigniew.kempczynski@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