From: keypair@tuta.io
To: Okash Khawaja <okash.khawaja@gmail.com>
Cc: Ezra Buehler <ezra@easyb.ch>,
Samiksha Palav <samiksha.palav27@gmail.com>,
Kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: Intoduction
Date: Thu, 10 Jul 2025 15:34:58 +0200 (CEST) [thread overview]
Message-ID: <OUoXxz9--F-9@tuta.io> (raw)
In-Reply-To: <CAOtcWM2xDz6jusQYPo-YYvZ4pajtABeiHCOH8yAjwa8oizLQXg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2100 bytes --]
He's right tho. It's annoying, when you can't even edit out the parts "AI" told you to. How lazy can you be?
Jul 10, 2025, 18:30 by okash.khawaja@gmail.com:
>
>
> On Thu, Jul 10, 2025 at 5:48 AM Ezra Buehler <> ezra@easyb.ch> > wrote:
>
>>
>>
>>> On 10 Jul 2025, at 12:55, Samiksha Palav <>>> samiksha.palav27@gmail.com>>> > wrote:
>>>
>>>
>>> Hi everyone,
>>>
>>> I’m Samiksha (a.k.a. Shdwcodr), an undergrad BCA student from India with a relentless drive to get deep into the Linux kernel. I've recently begun my journey contributing to the kernel, focusing on staging drivers, learning the kernel development workflow, and understanding the culture of patch submission and review.
>>>
>>> Over the past few days, I’ve:
>>> - Set up a local kernel build and testing workflow.
>>> - Sent out my first real patch (not a dummy), with more lined up.
>>> - Subscribed to key mailing lists and joined IRC channels to stay in the loop.
>>> - Started tracking patch feedback and diving into `scripts/>>> checkpatch.pl <http://checkpatch.pl>>>> `, git send-email, and the entire mailing list-based workflow.
>>>
>>> My short-term goal is to get multiple patches accepted into staging by early 2025, and long-term I’m aiming for the **LFX Kernel Mentorship Program in 2026**.
>>>
>>>
>>> I’ll be lurking, learning, and asking questions when stuck. Thanks in advance to everyone who shares knowledge and guidance — it means a lot to newcomers like me.
>>>
>>>
>>> Looking forward to learning from you all and giving back as I grow.
>>>
>>> Cheers,
>>> Samiksha (Shdwcodr)
>>> [GitLab/GitHub link if you want to include one]
>>>
>>
>> Here some unsolicited piece of advice:
>>
>> Try writing e-mails without the help of “AI”.
>>
> Please there is no need for this. Not everyone is native English speaker.
>
>
>
>
>>
>> ;-)
>> _______________________________________________
>> Kernelnewbies mailing list
>> >> Kernelnewbies@kernelnewbies.org
>> >> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>>
[-- Attachment #1.2: Type: text/html, Size: 4514 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2025-07-10 13:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 10:41 Intoduction Samiksha Palav
2025-07-10 12:31 ` Intoduction Ezra Buehler
2025-07-10 12:58 ` Intoduction Okash Khawaja
2025-07-10 13:34 ` keypair [this message]
2025-07-10 16:34 ` Intoduction Ezra Buehler
2025-07-10 17:20 ` Intoduction keypair
2025-07-11 8:29 ` Intoduction Raka Gunarto
2025-07-11 8:32 ` Intoduction Raka Gunarto
2025-07-11 9:01 ` Intoduction Ezra Buehler
2025-07-11 9:15 ` Intoduction Robert P. J. Day
2025-07-15 20:47 ` Intoduction Sima Baymani
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=OUoXxz9--F-9@tuta.io \
--to=keypair@tuta.io \
--cc=ezra@easyb.ch \
--cc=kernelnewbies@kernelnewbies.org \
--cc=okash.khawaja@gmail.com \
--cc=samiksha.palav27@gmail.com \
/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 NNTP newsgroup(s).