From: Maira Canal <mairacanal@riseup.net>
To: Maxime Ripard <mripard@kernel.org>,
rodrigosiqueiramelo@gmail.com, melissa.srw@gmail.com,
hamohammed.sa@gmail.com, daniel@ffwll.ch,
dri-devel@lists.freedesktop.org,
maarten.lankhorst@linux.intel.com, tzimmermann@suse.de,
sean@poorly.run, thomas.petazzoni@bootlin.com,
linux-kernel@vger.kernel.org, seanpaul@google.com
Subject: Re: [PATCH] MAINTAINERS: Add myself as VKMS Maintainer
Date: Thu, 12 Sep 2024 12:04:01 -0300 [thread overview]
Message-ID: <386b3df4-dade-4ad0-b17a-3582b917b640@riseup.net> (raw)
In-Reply-To: <20240911-functional-finch-of-competition-ad54e9@houat>
On 9/11/24 10:01, Maxime Ripard wrote:
> On Wed, Sep 11, 2024 at 02:15:05PM GMT, Louis Chauvet wrote:
>> Le 10/09/24 - 15:57, Maira Canal a écrit :
>>> 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>
>>>
>>> Acked-by: Maíra Canal <mairacanal@riseup.net>
>>>
>>> Please, check the procedures to apply for commit rights in drm-misc and
>>> apply it. This way you will be able to commit your patches.
>>
>> Thanks for your support!
>>
>> I just checked the rules to become a commiter, and it requires at least 10
>> non-trivial patches, so I can't apply right now.
>
> As far as I'm concerned, being a maintainer of a driver in drm-misc
> gives you automatically that right :)
+1
Best Regards,
- Maíra
>
> Maxime
next prev parent reply other threads:[~2024-09-12 15:04 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 [this message]
2024-09-24 23:54 ` Maíra Canal
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=386b3df4-dade-4ad0-b17a-3582b917b640@riseup.net \
--to=mairacanal@riseup.net \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=hamohammed.sa@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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®