From: Daniel Stone <daniel@fooishbar.org>
To: Jacopo Mondi <jacopo.mondi@ideasonboard.com>
Cc: David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Naushir Patuck <naush@raspberrypi.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
libcamera-devel@lists.libcamera.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/2] drm/fourcc.h: Add libcamera to Open Source Waiver
Date: Thu, 9 May 2024 11:20:22 +0100 [thread overview]
Message-ID: <CAPj87rPyfgB5=09hGUgekREN-S+W6Ti1s3izo+-FSohtRtjOJw@mail.gmail.com> (raw)
In-Reply-To: <7frycd5jnd674cily3xz3p2yl2bjc2yrn3z6sw3dzqdpl4widp@hrgyml6b7vh5>
On Thu, 14 Mar 2024 at 10:12, Jacopo Mondi
<jacopo.mondi@ideasonboard.com> wrote:
> gentle nudge for
>
> *) libcamera: are we ok being listed here ?
> *) DRM/KMS: is it ok splitting the list of projects in the way I've
> done ?
My bikeshed would be to change the list to 1) OpenGL / OpenGL ES / EGL
and its extensions, 2) Vulkan and its extensions, 3) libcamera.
But it doesn't really make much difference; people are going to get the point.
With whatever reasonable wording, series is:
Reviewed-by: Daniel Stone <daniels@collabora.com>
Thanks Jacopo!
-d
prev parent reply other threads:[~2024-05-09 10:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 10:22 [PATCH 0/2] drm/fourcc.h: Add libcamera to Open Source Waiver Jacopo Mondi
2024-02-28 10:22 ` [PATCH 1/2] drm/fourcc.h: List of Open Source Waiver projects Jacopo Mondi
2024-02-28 10:22 ` [PATCH 2/2] drm/fourcc.h: Add libcamera to Open Source Waiver Jacopo Mondi
2024-05-09 10:18 ` Daniel Vetter
2024-03-14 10:12 ` [PATCH 0/2] " Jacopo Mondi
2024-03-26 17:54 ` Kieran Bingham
2024-05-09 10:20 ` Daniel Stone [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='CAPj87rPyfgB5=09hGUgekREN-S+W6Ti1s3izo+-FSohtRtjOJw@mail.gmail.com' \
--to=daniel@fooishbar.org \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jacopo.mondi@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=libcamera-devel@lists.libcamera.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=naush@raspberrypi.com \
--cc=tzimmermann@suse.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).