From: "Maíra Canal" <mcanal@igalia.com>
To: Louis Chauvet <louis.chauvet@bootlin.com>,
rodrigosiqueiramelo@gmail.com, melissa.srw@gmail.com,
hamohammed.sa@gmail.com, daniel@ffwll.ch,
dri-devel@lists.freedesktop.org,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, sean@poorly.run
Cc: thomas.petazzoni@bootlin.com, linux-kernel@vger.kernel.org,
seanpaul@google.com
Subject: Re: [PATCH] MAINTAINERS: Add myself as VKMS Maintainer
Date: Tue, 24 Sep 2024 20:54:58 -0300 [thread overview]
Message-ID: <55fa8756-1082-45b9-8edb-5b3fd6722e08@igalia.com> (raw)
In-Reply-To: <20240910-vkms-maintainer-v1-1-e7a6c7a4ae71@bootlin.com>
Hi Louis,
On 9/10/24 12:10, Louis Chauvet wrote:
> I've been actively working on VKMS to provide new features and
> participated in reviews and testing. To help Maìra with her work, add
> myself as co-maintainer of VKMS.
>
> Signed-off-by: Louis Chauvet <louis.chauvet@bootlin.com>
I see that you're now a developer in the drm/misc repo. Therefore, I
applied this patch to misc/kernel.git (drm-misc-next).
Thanks for volunteering!
Best Regards,
- Maíra
> ---
> Hi everyone,
>
> This series [1] has been waiting for a while now, it was proposed first in
> February. The first iterations had few reactions (thanks to Arthur, Pekka,
> Maìra, ...), but since v8 (in May) no major issues were reported, Maìra
> seemed satisfied, and only minor cosmetic changes were reported. Two other
> series ([2] and [3]), that I submitted first in May, did not have receive
> any reactions.
>
> In addition, there is also some significant addition to VKMS being
> proposed, such as ConfigFS support, and without a clear maintainer having
> the time to review and approve these changes, these changes have very
> little changes to get in.
>
> VKMS is not a fundamental driver for "normal" Linux users, but I had some
> feedback from userspace developpers that VKMS could be a very good testing
> tool if only it had more features (I think P0xx formats were asked to
> test HDR for example). This could also help to detect issues in DRM core
> by emulating a wide range of configurations.
>
> I believe the only active maintainer is Maìra, but as she's mentioned before,
> she doesn't have much time to work on VKMS. So, I'd like to volunteer as a
> maintainer. I have plenty of time to dedicate to VKMS.
>
> I hope I've gained enough understanding of VKMS to be helful with this role.
> I am eager to move forward and improve this subsystem. I've also talked to Sean
> about this, and he agrees that it would be good if I could commit code to
> drm-misc.
>
> [1]: https://lore.kernel.org/all/20240809-yuv-v10-0-1a7c764166f7@bootlin.com/
> [2]: https://lore.kernel.org/all/20240814-b4-new-color-formats-v2-0-8b3499cfe90e@bootlin.com/
> [3]: https://lore.kernel.org/all/20240814-writeback_line_by_line-v2-0-36541c717569@bootlin.com/
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 10430778c998b57944c1a6c5f07d676127e47faa..62f10356e11ab7fa9c8f79ba63b335eb6580d0a8 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -7340,6 +7340,7 @@ DRM DRIVER FOR VIRTUAL KERNEL MODESETTING (VKMS)
> M: Rodrigo Siqueira <rodrigosiqueiramelo@gmail.com>
> M: Melissa Wen <melissa.srw@gmail.com>
> M: Maíra Canal <mairacanal@riseup.net>
> +M: Louis Chauvet <louis.chauvet@bootlin.com>
> R: Haneen Mohammed <hamohammed.sa@gmail.com>
> R: Daniel Vetter <daniel@ffwll.ch>
> L: dri-devel@lists.freedesktop.org
>
> ---
> base-commit: da3ea35007d0af457a0afc87e84fddaebc4e0b63
> change-id: 20240910-vkms-maintainer-7b3d2210cc1b
>
> Best regards,
prev parent reply other threads:[~2024-09-24 23:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 15:10 Louis Chauvet
2024-09-10 18:57 ` Maira Canal
2024-09-11 12:15 ` Louis Chauvet
2024-09-11 13:01 ` Maxime Ripard
2024-09-12 15:04 ` Maira Canal
2024-09-24 23:54 ` Maíra Canal [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=55fa8756-1082-45b9-8edb-5b3fd6722e08@igalia.com \
--to=mcanal@igalia.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=hamohammed.sa@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=louis.chauvet@bootlin.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=melissa.srw@gmail.com \
--cc=mripard@kernel.org \
--cc=rodrigosiqueiramelo@gmail.com \
--cc=sean@poorly.run \
--cc=seanpaul@google.com \
--cc=thomas.petazzoni@bootlin.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
all inboxes | Powered by JetHome®