public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Tvrtko Ursulin <tursulin@ursulin.net>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/3] drm/i915: remove a few __i915_printk() uses
Date: Wed, 07 Aug 2024 14:21:11 +0300	[thread overview]
Message-ID: <87o7644lzs.fsf@intel.com> (raw)
In-Reply-To: <fef2188f-fd25-4f21-a2cf-6d7931b7bc8b@ursulin.net>

On Wed, 07 Aug 2024, Tvrtko Ursulin <tursulin@ursulin.net> wrote:
> On 06/08/2024 14:38, Jani Nikula wrote:
>> __i915_printk() does nothing for notice/info levels. Just use the
>> regular drm_notice() and drm_info() calls.
>
> "does nothing"? You mean does nothing _special_?

Yeah, does nothing in addition to the regular drm logging that we switch
to.

>
> The patch itself looks okay.
>
> Regards,
>
> Tvrtko
>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>> ---
>>   drivers/gpu/drm/i915/i915_utils.c | 10 +++++-----
>>   1 file changed, 5 insertions(+), 5 deletions(-)
>> 
>> diff --git a/drivers/gpu/drm/i915/i915_utils.c b/drivers/gpu/drm/i915/i915_utils.c
>> index 6f9e7b354b54..bee32222f0fd 100644
>> --- a/drivers/gpu/drm/i915/i915_utils.c
>> +++ b/drivers/gpu/drm/i915/i915_utils.c
>> @@ -54,8 +54,8 @@ __i915_printk(struct drm_i915_private *dev_priv, const char *level,
>>   
>>   void add_taint_for_CI(struct drm_i915_private *i915, unsigned int taint)
>>   {
>> -	__i915_printk(i915, KERN_NOTICE, "CI tainted:%#x by %pS\n",
>> -		      taint, (void *)_RET_IP_);
>> +	drm_notice(&i915->drm, "CI tainted: %#x by %pS\n",
>> +		   taint, __builtin_return_address(0));
>>   
>>   	/* Failures that occur during fault injection testing are expected */
>>   	if (!i915_error_injected())
>> @@ -74,9 +74,9 @@ int __i915_inject_probe_error(struct drm_i915_private *i915, int err,
>>   	if (++i915_probe_fail_count < i915_modparams.inject_probe_failure)
>>   		return 0;
>>   
>> -	__i915_printk(i915, KERN_INFO,
>> -		      "Injecting failure %d at checkpoint %u [%s:%d]\n",
>> -		      err, i915_modparams.inject_probe_failure, func, line);
>> +	drm_info(&i915->drm, "Injecting failure %d at checkpoint %u [%s:%d]\n",
>> +		 err, i915_modparams.inject_probe_failure, func, line);
>> +
>>   	i915_modparams.inject_probe_failure = 0;
>>   	return err;
>>   }

-- 
Jani Nikula, Intel

  reply	other threads:[~2024-08-07 11:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-06 13:38 [PATCH 0/3] drm/i915: remove __i915_printk() Jani Nikula
2024-08-06 13:38 ` [PATCH 1/3] drm/i915: remove a few __i915_printk() uses Jani Nikula
2024-08-06 19:32   ` Cavitt, Jonathan
2024-08-07 10:27   ` Tvrtko Ursulin
2024-08-07 11:21     ` Jani Nikula [this message]
2024-08-07 14:41   ` Andi Shyti
2024-08-06 13:38 ` [PATCH 2/3] drm/i915: remove i915_report_error() Jani Nikula
2024-08-06 19:38   ` Cavitt, Jonathan
2024-08-07 10:33   ` Tvrtko Ursulin
2024-08-07 14:44   ` Andi Shyti
2024-08-06 13:38 ` [PATCH 3/3] drm/i915: remove __i915_printk() Jani Nikula
2024-08-06 19:41   ` Cavitt, Jonathan
2024-08-07 10:45   ` Tvrtko Ursulin
2024-08-07 11:40     ` Jani Nikula
2024-08-07 14:25       ` Tvrtko Ursulin
2024-08-07 14:45   ` Andi Shyti
2024-08-06 15:29 ` ✓ Fi.CI.BAT: success for " Patchwork
2024-08-06 15:30 ` ✗ Fi.CI.CHECKPATCH: warning " Patchwork
2024-08-06 15:30 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-08-07  5:48 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-08-08 14:45 ` [PATCH 0/3] " Jani Nikula

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=87o7644lzs.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=tursulin@ursulin.net \
    /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