From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2 2/5] drm/i915: Convert i915_params to use shortnames for its types
Date: Mon, 06 Feb 2017 10:39:14 +0200 [thread overview]
Message-ID: <1486370354.3076.1.camel@linux.intel.com> (raw)
In-Reply-To: <20170202085513.6710-2-chris@chris-wilson.co.uk>
On to, 2017-02-02 at 08:55 +0000, Chris Wilson wrote:
> In order to specialise a pretty printer for different types of module
> parameters using macro construction, the type names must be a single
> word. Use typedefs to construct the parameters using the modparams type
> shortnames.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
We have __builtin_strcmp, so should not be needed.
Regards, Joonas
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-02-06 8:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-02 8:55 [PATCH v2 1/5] drm/i915: Generate i915_params {} using a macro Chris Wilson
2017-02-02 8:55 ` [PATCH v2 2/5] drm/i915: Convert i915_params to use shortnames for its types Chris Wilson
2017-02-06 8:39 ` Joonas Lahtinen [this message]
2017-02-02 8:55 ` [PATCH v2 3/5] drm/i915: Use bool i915_param.alpha_support Chris Wilson
2017-02-03 19:29 ` Vivi, Rodrigo
2017-02-02 8:55 ` [PATCH v2 4/5] drm/i915: Capture module parameters for the GPU error state Chris Wilson
2017-02-02 8:55 ` [PATCH v2 5/5] drm/i915: Show the current i915_params in debugfs/i915_capabilites Chris Wilson
2017-02-02 9:24 ` ✓ Fi.CI.BAT: success for series starting with [v2,1/5] drm/i915: Generate i915_params {} using a macro Patchwork
2017-02-02 9:37 ` [PATCH v2 1/5] " Jani Nikula
2017-02-02 10:04 ` Chris Wilson
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=1486370354.3076.1.camel@linux.intel.com \
--to=joonas.lahtinen@linux.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;
as well as URLs for NNTP newsgroup(s).