From: "Guillaume Tucker" <guillaume.tucker@collabora.com>
To: Johnson George <johnson.george80@gmail.com>,
"kernelci@groups.io" <kernelci@groups.io>
Subject: Re: Request to Join Email List
Date: Tue, 22 Jun 2021 14:55:33 +0100 [thread overview]
Message-ID: <011c7ee7-3d46-bf16-526b-0d1fb34882e8@collabora.com> (raw)
In-Reply-To: <03B78B61-C71F-4BC7-B956-82480DEFB541@gmail.com>
+kernelci@groups.io
On 19/06/2021 00:42, Johnson George wrote:
> Hello Guillaume,
>
> I’m in the kernelci emailing list and interested in joining the weekly meeting. Can you please include me in the attendee list?
Sure, I've added you as well.
Best wishes,
Guillaume
>> On Jun 18, 2021, at 2:48 PM, Guillaume Tucker <guillaume.tucker@collabora.com> wrote:
>>
>> Hello Isaiah,
>>
>>> On 18/06/2021 22:13, isaiahduncan via groups.io wrote:
>>> Hello everybody! Last year as an intern, I was put onto the Kernel CI team. Some of you may remember me because I was Sasha Levin's mentee. Someone like Guillaume Tucker may remember me from last year because he helped me out a lot. Now that I have started full time at Microsoft, I thought that it would be good for me to join you all again so that we can be more connected and because my org is interested in Kernel CI still. Could I please be added to the email list so that I can attend the meetings? My email is isaiahduncan@microsoft.com
>>
>> Absolutely, I've sent you an invitation to join the mailing list
>> but then realised you had already been added. So it should all
>> be sorted out already.
>>
>> Congratulations with your new job!
>>
>> Of course you can join the weekly meetings, I've added you to the
>> list of attendees. Looking forward to seeing you there again.
>>
>> Thank you again for your contributions to enabling devicetree
>> validation in KernelCI. Sadly that work is still not quite
>> complete as nobody had the time to carry it through to production
>> after your internship. However we're now looking into how to run
>> arbitrary jobs in Kubernetes (other than kernel builds) and this
>> is on the list among other hardware-independent tests such as
>> KUnit and static analysis. We can discuss it further in a weekly
>> Tuesday meeting, if you're interested in this kind of work.
>>
>> Best wishes,
>> Guillaume
>>
>>
>>
next parent reply other threads:[~2021-06-22 13:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <03B78B61-C71F-4BC7-B956-82480DEFB541@gmail.com>
2021-06-22 13:55 ` Guillaume Tucker [this message]
2021-06-18 21:13 Request to Join Email List isaiahduncan
2021-06-18 21:48 ` Guillaume Tucker
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=011c7ee7-3d46-bf16-526b-0d1fb34882e8@collabora.com \
--to=guillaume.tucker@collabora.com \
--cc=johnson.george80@gmail.com \
--cc=kernelci@groups.io \
/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.