All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [RFC] drm/i915: rename alpha_support to preliminary_support.
Date: Tue, 27 Nov 2018 10:26:35 +0200	[thread overview]
Message-ID: <87r2f7aptw.fsf@intel.com> (raw)
In-Reply-To: <20181127015134.13607-1-rodrigo.vivi@intel.com>

On Mon, 26 Nov 2018, Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
> The preliminary support protection flag exists mainly to protect
> users with brand new Hardware from having bad experience when
> using Linux distribution images containing old kernel versions from
> preliminary development times. Distro's ISO images don't get frequent
> updates.

I'd prefer it if we aligned first on what we want to achieve with the
flag, whether we want to and/or have to keep it going forward, and how
we define a platform is good enough to drop the flag. After that, we can
discuss whether a rename is in order or not.

BR,
Jani.

-- 
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      parent reply	other threads:[~2018-11-27  8:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-27  1:51 [RFC] drm/i915: rename alpha_support to preliminary_support Rodrigo Vivi
2018-11-27  2:04 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2018-11-27  2:05 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-11-27  2:22 ` ✗ Fi.CI.BAT: failure " Patchwork
2018-11-27  8:26 ` Jani Nikula [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=87r2f7aptw.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=rodrigo.vivi@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.