intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v3] drm/i915: replace platform flags with a platform enum
Date: Wed, 07 Dec 2016 15:23:19 +0200	[thread overview]
Message-ID: <8760mvyit4.fsf@intel.com> (raw)
In-Reply-To: <878trsxd77.fsf@intel.com>

On Wed, 07 Dec 2016, Jani Nikula <jani.nikula@intel.com> wrote:
> On Wed, 07 Dec 2016, Joonas Lahtinen <joonas.lahtinen@linux.intel.com> wrote:
>> On to, 2016-12-01 at 14:49 +0200, Jani Nikula wrote:
>>> The platform flags in device info are (mostly) mutually
>>> exclusive. Replace the flags with an enum. Add the platform enum also
>>> for platforms that previously didn't have a flag, and give them codename
>>> logging in dmesg.
>>> 
>>> Pineview remains an exception, the platform being G33 for that.
>>> 
>>> v2: Sort enum by gen and date
>>> 
>>> v3: rebase on geminilake enabling
>>> 
>>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>>
>> Still looking good;
>>
>> Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
>
> Pushed this one, thanks for the review - which I failed to add to the
> commit itself. /o\ Apologies!
>
> Dare I still ask for review on patch 2/6...?

And pushed the rest, thanks for the review.

BR,
Jani.



>
> BR,
> Jani.
>
>
>>
>> Regards, Joonas

-- 
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:[~2016-12-07 13:23 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-30 15:43 [PATCH 0/6] drm/i915: introduce platform enum Jani Nikula
2016-11-30 15:43 ` [PATCH 1/6] drm/i915: replace platform flags with a " Jani Nikula
2016-12-01  7:54   ` Joonas Lahtinen
2016-12-01 12:49   ` [PATCH v3] " Jani Nikula
2016-12-07  9:51     ` Joonas Lahtinen
2016-12-07 10:09       ` Jani Nikula
2016-12-07 13:23         ` Jani Nikula [this message]
2016-11-30 15:43 ` [PATCH 2/6] drm/i915: keep intel device info structs in gen based order Jani Nikula
2016-12-07 10:37   ` Joonas Lahtinen
2016-11-30 15:43 ` [PATCH 3/6] drm/i915: rename BROADWATER and CRESTLINE to I965G and I965GM, respectively Jani Nikula
2016-12-01  8:07   ` Joonas Lahtinen
2016-12-07 10:13   ` [PATCH v2] " Jani Nikula
2016-11-30 15:43 ` [PATCH 4/6] drm/i915: add some more "i" in platform names for consistency Jani Nikula
2016-12-01  8:03   ` Joonas Lahtinen
2016-11-30 15:43 ` [PATCH 5/6] drm/i915: give G45 and GM45 their own platform enums Jani Nikula
2016-12-01  7:58   ` Joonas Lahtinen
2016-11-30 15:43 ` [PATCH 6/6] drm/i915: use platform enum instead of duplicating PCI ID if possible Jani Nikula
2016-12-01  8:00   ` Joonas Lahtinen
2016-12-01  4:15 ` ✓ Fi.CI.BAT: success for drm/i915: introduce platform enum Patchwork
2016-12-01 13:15 ` ✓ Fi.CI.BAT: success for drm/i915: introduce platform enum (rev2) Patchwork
2016-12-07 12:15 ` ✓ Fi.CI.BAT: success for drm/i915: introduce platform enum (rev3) 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=8760mvyit4.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=joonas.lahtinen@linux.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;
as well as URLs for NNTP newsgroup(s).