From: Chris Wilson <chris@chris-wilson.co.uk>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2 0/3] drm/i915: Misc improvements around module params
Date: Thu, 22 Jun 2017 16:03:41 +0100 [thread overview]
Message-ID: <149814382195.24649.9967457660139337016@mail.alporthouse.com> (raw)
In-Reply-To: <20170609102757.14984-1-michal.wajdeczko@intel.com>
Quoting Michal Wajdeczko (2017-06-09 11:27:54)
> Earlier RFC proposed to extend param macros with default values.
> This series goes step further.
>
> v2: rename modparam instead of i915_params field
>
> Michal Wajdeczko (3):
> drm/i915: Rename lvds_use_ssc modparam to panel_use_ssc
> drm/i915: Extend PARAMS_FOR_EACH macro with more data
> drm/i915/debugfs: Highlight modified i915 params
Whilst having it as a single large macro is unwieldy, it is just pulling
together the modparam macros into one large block. I was pondering if we
could use the modparam .section to decode the parameters later, but the
features added and the code consolidation here is worth the larger macro.
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2017-06-22 15:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 10:27 [PATCH v2 0/3] drm/i915: Misc improvements around module params Michal Wajdeczko
2017-06-09 10:27 ` [PATCH v2 1/3] drm/i915: Rename lvds_use_ssc modparam to panel_use_ssc Michal Wajdeczko
2017-06-09 10:27 ` [PATCH v2 2/3] drm/i915: Extend PARAMS_FOR_EACH macro with more data Michal Wajdeczko
2017-06-09 10:27 ` [PATCH v2 3/3] drm/i915/debugfs: Highlight modified i915 params Michal Wajdeczko
2017-06-09 11:54 ` Fiedorowicz, Lukasz
2017-06-09 10:47 ` ✓ Fi.CI.BAT: success for drm/i915: Misc improvements around module params (rev2) Patchwork
2017-06-22 15:03 ` Chris Wilson [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=149814382195.24649.9967457660139337016@mail.alporthouse.com \
--to=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 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.