From: Eric Anholt <eric@anholt.net>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: dri-devel@lists.freedesktop.org, Dave Airlie <airlied@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2 v2] drm/doc: Allow new UAPI to be used once it's in drm-next/drm-misc-next.
Date: Thu, 16 May 2019 09:38:05 -0700 [thread overview]
Message-ID: <87a7fmbbiq.fsf@anholt.net> (raw)
In-Reply-To: <20190425063321.GX9857@phenom.ffwll.local>
[-- Attachment #1: Type: text/plain, Size: 710 bytes --]
Daniel Vetter <daniel@ffwll.ch> writes:
> On Wed, Apr 24, 2019 at 03:06:38PM -0700, Eric Anholt wrote:
>> I was trying to figure out if it was permissible to merge the Mesa
>> side of V3D's CSD support yet while it's in drm-misc-next but not
>> drm-next, and developers on #dri-devel IRC had differing opinions of
>> what the requirement was.
>>
>> v2: Restrict to just drm-next or drm-misc-next on airlied's request.
>
> Personally I think that's a bit too strict (if people want to screw up,
> they will be able to anyway). But since I'm all for clearer rules where
> possible, this has my support too.
>
> Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Pushed to drm-misc-next now.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2019-05-16 16:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 18:56 [PATCH 1/2] drm/doc: Allow new UAPI to be used once it's in the driver's -next Eric Anholt
2019-04-24 18:56 ` [PATCH 2/2] drm/doc: Document expectation that userspace review looks at kernel uAPI Eric Anholt
2019-04-24 19:36 ` Daniel Vetter
2019-04-24 19:36 ` Daniel Vetter
2019-05-21 7:47 ` Pekka Paalanen
2019-05-21 7:47 ` Pekka Paalanen
2019-05-21 8:26 ` Daniel Vetter
2019-04-24 19:35 ` [PATCH 1/2] drm/doc: Allow new UAPI to be used once it's in the driver's -next Daniel Vetter
2019-04-24 20:16 ` Dave Airlie
2019-04-24 22:06 ` [PATCH 1/2 v2] drm/doc: Allow new UAPI to be used once it's in drm-next/drm-misc-next Eric Anholt
2019-04-25 6:33 ` Daniel Vetter
2019-05-16 16:38 ` Eric Anholt [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=87a7fmbbiq.fsf@anholt.net \
--to=eric@anholt.net \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.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 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.