Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/i915: prefer INTEL_GEN() over INTEL_INFO()->gen
Date: Wed, 21 Mar 2018 16:14:44 +0200	[thread overview]
Message-ID: <87370tjz1n.fsf@intel.com> (raw)
In-Reply-To: <152164143793.4865.2915184666338469613@mail.alporthouse.com>

On Wed, 21 Mar 2018, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> Quoting Jani Nikula (2018-03-21 14:07:54)
>> Fix the last two direct ->gen usages.
>> 
>> Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
>> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>> ---
>>  drivers/gpu/drm/i915/intel_device_info.c | 4 ++--
>>  1 file changed, 2 insertions(+), 2 deletions(-)
>> 
>> diff --git a/drivers/gpu/drm/i915/intel_device_info.c b/drivers/gpu/drm/i915/intel_device_info.c
>> index a504281e2afa..af538c4a3aeb 100644
>> --- a/drivers/gpu/drm/i915/intel_device_info.c
>> +++ b/drivers/gpu/drm/i915/intel_device_info.c
>> @@ -119,7 +119,7 @@ void intel_device_info_dump(const struct intel_device_info *info,
>>                    INTEL_DEVID(dev_priv),
>>                    INTEL_REVID(dev_priv),
>>                    intel_platform_name(info->platform),
>> -                  info->gen);
>> +                  INTEL_GEN(dev_priv));
>
> This is wrong, this should be from the local intel_device_info *info.
> (Passed in from the caller, so dev_priv is very wrong here, and yes the
> INTEL_foo() above are on my hit list :)

Contemplated that. I guess you'll need to remove them for turning
intel_device_info into a pointer rather than a copy in dev_priv?

BR,
Jani.


-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2018-03-21 14:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-21 14:07 [PATCH 1/2] drm/i915: prefer INTEL_GEN() over INTEL_INFO()->gen Jani Nikula
2018-03-21 14:07 ` [PATCH 2/2] drm/i915: hint gen and gen_mask shouldn't be used directly Jani Nikula
2018-03-21 14:10 ` [PATCH 1/2] drm/i915: prefer INTEL_GEN() over INTEL_INFO()->gen Chris Wilson
2018-03-21 14:14   ` Jani Nikula [this message]
2018-03-21 14:36 ` ✗ Fi.CI.BAT: failure for series starting with [1/2] " 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=87370tjz1n.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@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