Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Tejas Upadhyay <tejas.upadhyay@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [PATCH]  drm/xe/client: Limit 80 char per line
Date: Mon, 17 Feb 2025 07:39:13 -0800	[thread overview]
Message-ID: <85y0y41sym.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20250217133440.188256-1-tejas.upadhyay@intel.com>

On Mon, 17 Feb 2025 05:34:40 -0800, Tejas Upadhyay wrote:
>
> codeline exceeding 80 char per line, correct that
> to make checkpatch happy.

Checkpatch allows 100 char per line, code's fine as is, there is no
checkpatch error.

>
> Signed-off-by: Tejas Upadhyay <tejas.upadhyay@intel.com>
> ---
>  drivers/gpu/drm/xe/xe_drm_client.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_drm_client.c b/drivers/gpu/drm/xe/xe_drm_client.c
> index 2d4874d2b922..84e30a4d5f1e 100644
> --- a/drivers/gpu/drm/xe/xe_drm_client.c
> +++ b/drivers/gpu/drm/xe/xe_drm_client.c
> @@ -252,7 +252,8 @@ static void show_meminfo(struct drm_printer *p, struct drm_file *file)
>
>	xe_bo_put_commit(&deferred);
>
> -	for (mem_type = XE_PL_SYSTEM; mem_type < TTM_NUM_MEM_TYPES; ++mem_type) {
> +	for (mem_type = XE_PL_SYSTEM; mem_type < TTM_NUM_MEM_TYPES;
> +	     ++mem_type) {
>		if (!xe_mem_type_to_name[mem_type])
>			continue;
>
> --
> 2.34.1
>

  parent reply	other threads:[~2025-02-17 15:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-17 13:34 [PATCH] drm/xe/client: Limit 80 char per line Tejas Upadhyay
2025-02-17 13:34 ` ✓ CI.Patch_applied: success for " Patchwork
2025-02-17 13:34 ` ✓ CI.checkpatch: " Patchwork
2025-02-17 13:35 ` ✓ CI.KUnit: " Patchwork
2025-02-17 13:56 ` ✓ CI.Build: " Patchwork
2025-02-17 14:00 ` ✓ CI.Hooks: " Patchwork
2025-02-17 14:01 ` ✓ CI.checksparse: " Patchwork
2025-02-17 14:23 ` ✓ Xe.CI.BAT: " Patchwork
2025-02-17 15:39 ` Dixit, Ashutosh [this message]
2025-02-18  0:43 ` ✗ 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=85y0y41sym.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=tejas.upadhyay@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