From: Jani Nikula <jani.nikula@intel.com>
To: Matt Roper <matthew.d.roper@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: make dbuf configurations const
Date: Sun, 23 Feb 2020 17:28:54 +0200 [thread overview]
Message-ID: <87k14dtj9l.fsf@intel.com> (raw)
In-Reply-To: <20200219174631.GC2733348@mdroper-desk1.amr.corp.intel.com>
On Wed, 19 Feb 2020, Matt Roper <matthew.d.roper@intel.com> wrote:
> On Wed, Feb 19, 2020 at 05:45:42PM +0200, Jani Nikula wrote:
>> Ensure const data goes to rodata.
>>
>> Fixes: ff2cd8635e41 ("drm/i915: Correctly map DBUF slices to pipes")
>> Cc: Matt Roper <matthew.d.roper@intel.com>
>> Cc: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
>> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>
> Reviewed-by: Matt Roper <matthew.d.roper@intel.com>
Thanks for the review, pushed to dinq.
BR,
Jani.
>
>> ---
>> drivers/gpu/drm/i915/intel_pm.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drivers/gpu/drm/i915/intel_pm.c
>> index ffac0b862ca5..9b74c37e4fa4 100644
>> --- a/drivers/gpu/drm/i915/intel_pm.c
>> +++ b/drivers/gpu/drm/i915/intel_pm.c
>> @@ -4178,7 +4178,7 @@ struct dbuf_slice_conf_entry {
>> * as is from BSpec itself - that way it is at least easier
>> * to compare, change and check.
>> */
>> -static struct dbuf_slice_conf_entry icl_allowed_dbufs[] =
>> +static const struct dbuf_slice_conf_entry icl_allowed_dbufs[] =
>> /* Autogenerated with igt/tools/intel_dbuf_map tool: */
>> {
>> {
>> @@ -4240,7 +4240,7 @@ static struct dbuf_slice_conf_entry icl_allowed_dbufs[] =
>> * as is from BSpec itself - that way it is at least easier
>> * to compare, change and check.
>> */
>> -static struct dbuf_slice_conf_entry tgl_allowed_dbufs[] =
>> +static const struct dbuf_slice_conf_entry tgl_allowed_dbufs[] =
>> /* Autogenerated with igt/tools/intel_dbuf_map tool: */
>> {
>> {
>> --
>> 2.20.1
>>
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-02-23 15:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 15:45 [Intel-gfx] [PATCH] drm/i915: make dbuf configurations const Jani Nikula
2020-02-19 17:46 ` Matt Roper
2020-02-23 15:28 ` Jani Nikula [this message]
2020-02-19 19:31 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2020-02-21 16: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=87k14dtj9l.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.d.roper@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.