All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Stone <daniel@fooishbar.org>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: "Marek Olšák" <maraeo@gmail.com>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	"Daniel Vetter" <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH v3] drm/fourcc: document modifier uniqueness requirements
Date: Fri, 29 May 2020 15:30:38 +0100	[thread overview]
Message-ID: <CAPj87rP+Hxhohb4dEjRwtZzy34fYk+hAdgVfCkLF1u4JufJ=CQ@mail.gmail.com> (raw)
In-Reply-To: <CADnq5_OX9o5_Gc4SjU5M4B=fthT9++J-FjX3UqTS7x_u6cJHOQ@mail.gmail.com>

On Fri, 29 May 2020 at 15:29, Alex Deucher <alexdeucher@gmail.com> wrote:
> Maybe I'm over thinking this.  I just don't want to get into a
> situation where we go through a lot of effort to add modifier support
> and then performance ends up being worse than it is today in a lot of
> cases.

I'm genuinely curious: what do you imagine could cause a worse result?

Cheers,
Daniel
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2020-05-29 14:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-28 14:38 [PATCH v3] drm/fourcc: document modifier uniqueness requirements Simon Ser
2020-05-28 15:49 ` Marek Olšák
2020-05-29  8:59   ` Simon Ser
2020-05-29 13:28     ` Alex Deucher
2020-05-29 13:43       ` Daniel Vetter
2020-05-29 13:56       ` Daniel Stone
2020-05-29 14:29         ` Alex Deucher
2020-05-29 14:30           ` Daniel Stone [this message]
2020-05-29 14:36             ` Alex Deucher
2020-05-29 15:01               ` Daniel Stone
2020-05-29 15:31                 ` Alex Deucher
2020-05-30 13:08                 ` Michel Dänzer
2020-06-01 14:25                 ` Alex Deucher
2020-06-03  9:48                   ` Daniel Stone
2020-06-03 18:53                     ` Marek Olšák
2020-06-04  9:14                       ` Daniel Stone
2020-06-01 13:43         ` Neil Armstrong
2020-06-01 11:01 ` Brian Starkey

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='CAPj87rP+Hxhohb4dEjRwtZzy34fYk+hAdgVfCkLF1u4JufJ=CQ@mail.gmail.com' \
    --to=daniel@fooishbar.org \
    --cc=alexdeucher@gmail.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=maraeo@gmail.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.