Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Nirmoy Das <nirmoy.das@linux.intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH RESEND 1/3] drm/i915: make some error capture functions static
Date: Thu, 02 Nov 2023 14:23:47 +0200	[thread overview]
Message-ID: <87msvw2vjg.fsf@intel.com> (raw)
In-Reply-To: <4ac1d8f8-d108-9ff4-024f-85bc5394fb5d@linux.intel.com>

On Tue, 31 Oct 2023, Nirmoy Das <nirmoy.das@linux.intel.com> wrote:
> On 10/31/2023 1:45 PM, Jani Nikula wrote:
>> Not needed outside of i915_gpu_error.c.
>>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> Reviewed-by: Nirmoy Das <nirmoy.das@intel.com>

Thanks, series pushed to din.

BR,
Jani.

>> ---
>>   drivers/gpu/drm/i915/i915_gpu_error.c | 8 ++++----
>>   drivers/gpu/drm/i915/i915_gpu_error.h | 5 -----
>>   2 files changed, 4 insertions(+), 9 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/i915_gpu_error.c b/drivers/gpu/drm/i915/i915_gpu_error.c
>> index 8275f9b6a47d..889db834f07d 100644
>> --- a/drivers/gpu/drm/i915/i915_gpu_error.c
>> +++ b/drivers/gpu/drm/i915/i915_gpu_error.c
>> @@ -520,7 +520,7 @@ __find_vma(struct i915_vma_coredump *vma, const char *name)
>>   	return NULL;
>>   }
>>   
>> -struct i915_vma_coredump *
>> +static struct i915_vma_coredump *
>>   intel_gpu_error_find_batch(const struct intel_engine_coredump *ee)
>>   {
>>   	return __find_vma(ee->vma, "batch");
>> @@ -609,9 +609,9 @@ void i915_error_printf(struct drm_i915_error_state_buf *e, const char *f, ...)
>>   	va_end(args);
>>   }
>>   
>> -void intel_gpu_error_print_vma(struct drm_i915_error_state_buf *m,
>> -			       const struct intel_engine_cs *engine,
>> -			       const struct i915_vma_coredump *vma)
>> +static void intel_gpu_error_print_vma(struct drm_i915_error_state_buf *m,
>> +				      const struct intel_engine_cs *engine,
>> +				      const struct i915_vma_coredump *vma)
>>   {
>>   	char out[ASCII85_BUFSZ];
>>   	struct page *page;
>> diff --git a/drivers/gpu/drm/i915/i915_gpu_error.h b/drivers/gpu/drm/i915/i915_gpu_error.h
>> index 4ce227f7e1e1..8f9cdf056181 100644
>> --- a/drivers/gpu/drm/i915/i915_gpu_error.h
>> +++ b/drivers/gpu/drm/i915/i915_gpu_error.h
>> @@ -277,11 +277,6 @@ static inline void intel_klog_error_capture(struct intel_gt *gt,
>>   
>>   __printf(2, 3)
>>   void i915_error_printf(struct drm_i915_error_state_buf *e, const char *f, ...);
>> -void intel_gpu_error_print_vma(struct drm_i915_error_state_buf *m,
>> -			       const struct intel_engine_cs *engine,
>> -			       const struct i915_vma_coredump *vma);
>> -struct i915_vma_coredump *
>> -intel_gpu_error_find_batch(const struct intel_engine_coredump *ee);
>>   
>>   struct i915_gpu_coredump *i915_gpu_coredump(struct intel_gt *gt,
>>   					    intel_engine_mask_t engine_mask, u32 dump_flags);

-- 
Jani Nikula, Intel

  reply	other threads:[~2023-11-02 12:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-31 12:45 [Intel-gfx] [PATCH RESEND 1/3] drm/i915: make some error capture functions static Jani Nikula
2023-10-31 12:45 ` [Intel-gfx] [PATCH RESEND 2/3] drm/i915: move gpu error debugfs to i915_gpu_error.c Jani Nikula
2023-10-31 12:59   ` Nirmoy Das
2023-10-31 14:18     ` Jani Nikula
2023-10-31 16:12       ` Nirmoy Das
2023-10-31 12:45 ` [Intel-gfx] [PATCH RESEND 3/3] drm/i915: move gpu error sysfs " Jani Nikula
2023-10-31 13:04   ` Nirmoy Das
2023-10-31 12:48 ` [Intel-gfx] [PATCH RESEND 1/3] drm/i915: make some error capture functions static Nirmoy Das
2023-11-02 12:23   ` Jani Nikula [this message]
2023-10-31 21:39 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [RESEND,1/3] " Patchwork
2023-10-31 21:39 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-10-31 21:58 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-11-02  9:29 ` [Intel-gfx] ✗ Fi.CI.IGT: 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=87msvw2vjg.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=nirmoy.das@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