public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Fix build failure with debug and extra logging enabled
Date: Tue, 15 Nov 2022 14:56:52 +0000	[thread overview]
Message-ID: <cfa1e0fb-f2c0-e2d4-3a6b-4d40d8675a7a@linux.intel.com> (raw)
In-Reply-To: <20221115143941.32097-1-janusz.krzysztofik@linux.intel.com>


On 15/11/2022 14:39, Janusz Krzysztofik wrote:
> A comma is missing, fix it.
> 
> Signed-off-by: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
> ---
>   drivers/gpu/drm/i915/i915_vma.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/i915/i915_vma.c b/drivers/gpu/drm/i915/i915_vma.c
> index 3b969d679c1e2..947fde68e5f53 100644
> --- a/drivers/gpu/drm/i915/i915_vma.c
> +++ b/drivers/gpu/drm/i915/i915_vma.c
> @@ -73,7 +73,7 @@ static void vma_print_allocator(struct i915_vma *vma, const char *reason)
>   	char buf[512];
>   
>   	if (!vma->node.stack) {
> -		drm_dbg(&to_i915(vma->obj->base.dev)->drm
> +		drm_dbg(&to_i915(vma->obj->base.dev)->drm,
>   			"vma.node [%08llx + %08llx] %s: unknown owner\n",
>   			vma->node.start, vma->node.size, reason);
>   		return;

Yep, thanks, however already sent this morning: 
https://patchwork.freedesktop.org/series/110906/. Just waiting for CI to 
give it a green light, which is a bit pointless, nevertheless it's the 
process.

Regards,

Tvrtko

  reply	other threads:[~2022-11-15 14:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-15 14:39 [Intel-gfx] [PATCH] drm/i915: Fix build failure with debug and extra logging enabled Janusz Krzysztofik
2022-11-15 14:56 ` Tvrtko Ursulin [this message]
2022-11-15 23:45 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2022-11-16  8:12 ` [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=cfa1e0fb-f2c0-e2d4-3a6b-4d40d8675a7a@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=janusz.krzysztofik@linux.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