From: Riana Tauro <riana.tauro@intel.com>
To: Ashutosh Dixit <ashutosh.dixit@intel.com>,
<intel-xe@lists.freedesktop.org>
Cc: Badal Nilawar <badal.nilawar@intel.com>
Subject: Re: [PATCH] drm/xe/xe_gt_idle: Drop redundant newline in name
Date: Mon, 5 Feb 2024 10:37:21 +0530 [thread overview]
Message-ID: <df3a3233-fc30-47bb-b7f9-716f0ee0ac65@intel.com> (raw)
In-Reply-To: <20240202225623.3225443-1-ashutosh.dixit@intel.com>
On 2/3/2024 4:26 AM, Ashutosh Dixit wrote:
> Newline in name is redunant and produces an unnecessary empty line during
^typo
> 'cat name'. Newline is added during sysfs_emit. See '27a1a1e2e47d ("drm/xe:
> stringify the argument to avoid potential vulnerability")'.
Should this be fixes?
>
> Signed-off-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
With the above comments
Reviewed-by: Riana Tauro <riana.tauro@intel.com>
> ---
> drivers/gpu/drm/xe/xe_gt_idle.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_gt_idle.c b/drivers/gpu/drm/xe/xe_gt_idle.c
> index 9358f73368896..9fcae65b64699 100644
> --- a/drivers/gpu/drm/xe/xe_gt_idle.c
> +++ b/drivers/gpu/drm/xe/xe_gt_idle.c
> @@ -145,10 +145,10 @@ void xe_gt_idle_sysfs_init(struct xe_gt_idle *gtidle)
> }
>
> if (xe_gt_is_media_type(gt)) {
> - sprintf(gtidle->name, "gt%d-mc\n", gt->info.id);
> + sprintf(gtidle->name, "gt%d-mc", gt->info.id);
> gtidle->idle_residency = xe_guc_pc_mc6_residency;
> } else {
> - sprintf(gtidle->name, "gt%d-rc\n", gt->info.id);
> + sprintf(gtidle->name, "gt%d-rc", gt->info.id);
> gtidle->idle_residency = xe_guc_pc_rc6_residency;
> }
>
next prev parent reply other threads:[~2024-02-05 5:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 22:56 [PATCH] drm/xe/xe_gt_idle: Drop redundant newline in name Ashutosh Dixit
2024-02-03 1:09 ` ✓ CI.Patch_applied: success for drm/xe/xe_gt_idle: Drop redundant newline in name (rev2) Patchwork
2024-02-03 1:09 ` ✓ CI.checkpatch: " Patchwork
2024-02-03 1:10 ` ✓ CI.KUnit: " Patchwork
2024-02-03 1:17 ` ✓ CI.Build: " Patchwork
2024-02-03 1:18 ` ✓ CI.Hooks: " Patchwork
2024-02-03 1:19 ` ✓ CI.checksparse: " Patchwork
2024-02-03 1:42 ` ✓ CI.BAT: " Patchwork
2024-02-03 5:36 ` [PATCH] drm/xe/xe_gt_idle: Drop redundant newline in name Lucas De Marchi
2024-02-03 6:37 ` Dixit, Ashutosh
2024-02-05 5:07 ` Riana Tauro [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-06 19:27 Ashutosh Dixit
2024-02-02 22:35 Ashutosh Dixit
2024-02-02 22:49 ` Dixit, Ashutosh
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=df3a3233-fc30-47bb-b7f9-716f0ee0ac65@intel.com \
--to=riana.tauro@intel.com \
--cc=ashutosh.dixit@intel.com \
--cc=badal.nilawar@intel.com \
--cc=intel-xe@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox