From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Vinay Belgaumkar <vinay.belgaumkar@intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Fix format for perf_limit_reasons
Date: Tue, 14 Mar 2023 19:40:44 -0700 [thread overview]
Message-ID: <87mt4elosz.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20230315022906.2467408-1-vinay.belgaumkar@intel.com>
On Tue, 14 Mar 2023 19:29:06 -0700, Vinay Belgaumkar wrote:
>
> Use hex format so that it is easier to decode.
>
> Fixes: fe5979665f64 ('Add perf_limit_reasons in debugfs')
>
> Signed-off-by: Vinay Belgaumkar <vinay.belgaumkar@intel.com>
> ---
> drivers/gpu/drm/i915/gt/intel_gt_pm_debugfs.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/gt/intel_gt_pm_debugfs.c b/drivers/gpu/drm/i915/gt/intel_gt_pm_debugfs.c
> index 83df4cd5e06c..80dbbef86b1d 100644
> --- a/drivers/gpu/drm/i915/gt/intel_gt_pm_debugfs.c
> +++ b/drivers/gpu/drm/i915/gt/intel_gt_pm_debugfs.c
> @@ -580,7 +580,7 @@ static bool perf_limit_reasons_eval(void *data)
> }
>
> DEFINE_SIMPLE_ATTRIBUTE(perf_limit_reasons_fops, perf_limit_reasons_get,
> - perf_limit_reasons_clear, "%llu\n");
> + perf_limit_reasons_clear, "0x%llx\n");
Duh.
Reviewed-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
next prev parent reply other threads:[~2023-03-15 2:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 2:29 [Intel-gfx] [PATCH] drm/i915: Fix format for perf_limit_reasons Vinay Belgaumkar
2023-03-15 2:29 ` Vinay Belgaumkar
2023-03-15 2:40 ` Dixit, Ashutosh [this message]
2023-03-15 3:09 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2023-03-15 23:06 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=87mt4elosz.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=vinay.belgaumkar@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 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.