From: Kieran Bingham <kieran.bingham@ideasonboard.com>
To: Jacopo Mondi <jacopo.mondi@ideasonboard.com>
Cc: Thomas Zimmermann <tzimmermann@suse.de>,
dri-devel@lists.freedesktop.org,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
libcamera-devel@lists.libcamera.org,
Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@gmail.com>
Subject: Re: [PATCH 0/2] drm/fourcc.h: Add libcamera to Open Source Waiver
Date: Tue, 26 Mar 2024 17:54:04 +0000 [thread overview]
Message-ID: <171147564465.3566204.18099513875755978001@ping.linuxembedded.co.uk> (raw)
In-Reply-To: <7frycd5jnd674cily3xz3p2yl2bjc2yrn3z6sw3dzqdpl4widp@hrgyml6b7vh5>
Quoting Jacopo Mondi (2024-03-14 10:12:47)
> Hello
>
> gentle nudge for
>
> *) libcamera: are we ok being listed here ?
I think it's fine ...
Acked-by: Kieran Bingham <kieran.bingham@ideasonboard.com>
> *) DRM/KMS: is it ok splitting the list of projects in the way I've
> done ?
>
> Thanks
> j
>
> On Wed, Feb 28, 2024 at 11:22:42AM +0100, Jacopo Mondi wrote:
> > As suggested by Sima, add libcamera to the list of projects to which the
> > Open Source Waiver notice applies.
> >
> > To maintain the paragraph readable, make a list out of the projects to which
> > such notice applies.
> >
> > Jacopo Mondi (2):
> > drm/fourcc.h: List of Open Source Waiver projects
> > drm/fourcc.h: Add libcamera to Open Source Waiver
> >
> > include/uapi/drm/drm_fourcc.h | 12 +++++++++---
> > 1 file changed, 9 insertions(+), 3 deletions(-)
> >
> > --
> > 2.43.2
> >
next prev parent reply other threads:[~2024-03-26 17:54 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 [this message]
2024-05-09 10:20 ` Daniel Stone
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=171147564465.3566204.18099513875755978001@ping.linuxembedded.co.uk \
--to=kieran.bingham@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jacopo.mondi@ideasonboard.com \
--cc=libcamera-devel@lists.libcamera.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--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).