public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	Michal Wajdeczko <michal.wajdeczko@intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [RFC 2/3] drm/i915: Extend I915_PARAMS_FOR_EACH with default member value
Date: Fri, 22 Sep 2017 22:05:11 +0300	[thread overview]
Message-ID: <87wp4qsgew.fsf@intel.com> (raw)
In-Reply-To: <150609334446.7994.13313016438649460754@mail.alporthouse.com>

On Fri, 22 Sep 2017, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> Quoting Michal Wajdeczko (2017-09-22 15:27:25)
>> By combining default value into helper macro we can initialize
>> modparams struct in the same automatic way as it was declared.
>> This will initialize members in the same order as declared
>> and additionally will disallow declaring new member without
>> proper default value for it.
>> 
>> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
>> Cc: Chris Wilson <chris@chris-wilson.co.uk>
>> Cc: Jani Nikula <jani.nikula@intel.com>
>> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
>
> Overall, I think this is a positive change. I'm not completely happy
> that the param() macro is more readable than the struct assignment, but
> that is offset by the reduction in duplication.

I'm also not completely happy that the default values get moved away
from the param descriptions. (Hmm, what next, putting the permissions
and descriptions in I915_PARAMS_FOR_EACH too?! :o)

There's also the benefit of being able to highlight the changed values
and displaying the defaults in debugfs if desired.

On the series,

Acked-by: Jani Nikula <jani.nikula@intel.com>


-- 
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:[~2017-09-22 19:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-22 14:27 [RFC 1/3] drm/i915: Make I915_PARAMS_FOR_EACH macro more flexible Michal Wajdeczko
2017-09-22 14:27 ` [RFC 2/3] drm/i915: Extend I915_PARAMS_FOR_EACH with default member value Michal Wajdeczko
2017-09-22 15:15   ` Chris Wilson
2017-09-22 19:05     ` Jani Nikula [this message]
2017-09-25  9:19       ` Joonas Lahtinen
2017-09-25  9:31       ` Michal Wajdeczko
2017-09-25  9:30   ` Joonas Lahtinen
2017-09-22 14:27 ` [RFC 3/3] drm/i915: Fix default values of some modparams Michal Wajdeczko
2017-09-22 15:18   ` Chris Wilson
2017-09-22 15:12 ` ✓ Fi.CI.BAT: success for series starting with [RFC,1/3] drm/i915: Make I915_PARAMS_FOR_EACH macro more flexible Patchwork
2017-09-22 15:12 ` [RFC 1/3] " Chris Wilson
2017-09-22 20:01 ` ✗ Fi.CI.IGT: failure for series starting with [RFC,1/3] " Patchwork
2017-09-25  9:45 ` [PATCH v2 1/3] " Michal Wajdeczko
2017-09-25  9:45   ` [PATCH v2 2/3] drm/i915: Extend I915_PARAMS_FOR_EACH with default member value Michal Wajdeczko
2017-09-25 10:23     ` Joonas Lahtinen
2017-09-25  9:45   ` [PATCH v2 3/3] drm/i915: Fix default values of some modparams Michal Wajdeczko
2017-09-25 10:06 ` ✗ Fi.CI.BAT: failure for series starting with [v2,3/3] drm/i915: Fix default values of some modparams (rev4) 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=87wp4qsgew.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=michal.wajdeczko@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