public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 1/2] drm/i915: add struct i915_dsm to wrap dsm members together
Date: Wed, 18 Jan 2023 11:52:22 +0200	[thread overview]
Message-ID: <87v8l4cgq1.fsf@intel.com> (raw)
In-Reply-To: <Y8bh7WSIJg18ta92@intel.com>

On Tue, 17 Jan 2023, Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
> On Mon, Jan 16, 2023 at 07:34:21PM +0200, Jani Nikula wrote:
>> diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
>> index 72ca62c22797..13fab81a39b8 100644
>> --- a/drivers/gpu/drm/i915/i915_drv.h
>> +++ b/drivers/gpu/drm/i915/i915_drv.h
>> @@ -86,6 +86,35 @@ struct intel_pxp;
>>  
>>  #define GEM_QUIRK_PIN_SWIZZLED_PAGES	BIT(0)
>>  
>> +struct i915_dsm {
>> +	/*
>> +	 * Data Stolen Memory - aka "i915 stolen memory" gives us the start and
>> +	 * end of stolen 
>
> The 'Data Stolen Memory - aka "i915 stolen memory"' should probably be moved
> above along with the struct definition, and leave just the resource part,
> something like Stolen gives us the start and end of stolen...."
>
> or something like that...

Agreed.

>
> But up to you, the patch already looks like a good move
>
> Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>

Thanks, pushed to din, and took the rare liberty to update the comments
while applying.

BR,
Jani.



-- 
Jani Nikula, Intel Open Source Graphics Center

      reply	other threads:[~2023-01-18  9:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-16 17:34 [Intel-gfx] [PATCH 1/2] drm/i915: add struct i915_dsm to wrap dsm members together Jani Nikula
2023-01-16 17:34 ` [Intel-gfx] [PATCH 2/2] drm/i915: drop cast from DEFINE_RES_MEM() usage Jani Nikula
2023-01-16 18:52 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/2] drm/i915: add struct i915_dsm to wrap dsm members together Patchwork
2023-01-16 18:52 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-01-16 19:13 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-01-16 21:25 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2023-01-17 17:59 ` [Intel-gfx] [PATCH 1/2] " Rodrigo Vivi
2023-01-18  9:52   ` Jani Nikula [this message]

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=87v8l4cgq1.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=rodrigo.vivi@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