Linux CXL
 help / color / mirror / Atom feed
From: Dave Jiang <dave.jiang@intel.com>
To: Arvind Nanjundaswamy <nanjundaswamy.arvind@gmail.com>,
	linux-cxl@vger.kernel.org
Subject: Re: Interest in contributing to the CXL community
Date: Thu, 20 Nov 2025 08:07:16 -0700	[thread overview]
Message-ID: <cd3a11f8-88a1-4c9e-9ebe-2675bb292c93@intel.com> (raw)
In-Reply-To: <CAK8XrEWTauMKpWpuzfnpxGuY3gbr8EuuoAgaHm+awyhZnZ3EiQ@mail.gmail.com>



On 11/20/25 5:04 AM, Arvind Nanjundaswamy wrote:
> Hello All,
> 
> I'm Aravind, ex-HP-UX kernel developer and have worked in virtual
> memory solutions during 2002 - 2010. I have a decent understanding of
> system architecture and its programming aspects related to VM. I have
> worked on ccNUMA extensions, memory Online/offline solutions and
> enabling largepage support.
> 
> I have ventured elsewhere since 2010 and want to get back to VM
> development, especially about CXL implications on VM operations.
> 
> I'm open to taking up small beginner-friendly patches since this is my
> first time contributing to the community. I'm looking for mentors who
> can help me through the process.
> 
> Kindly help.
> 
> Thank you,
> Aravind Nanjundaswamy
> 

You should just start contributing on topics of interest and we can go from there. Also take a look at the maturity map [1] and see what areas need work. And if you are new to Linux patch submission, please take a look at this [2] doc.

[1]: https://docs.kernel.org/driver-api/cxl/maturity-map.html
[2]: https://www.kernel.org/doc/html/v5.17/process/submitting-patches.html


      reply	other threads:[~2025-11-20 15:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-20 12:04 Interest in contributing to the CXL community Arvind Nanjundaswamy
2025-11-20 15:07 ` Dave Jiang [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=cd3a11f8-88a1-4c9e-9ebe-2675bb292c93@intel.com \
    --to=dave.jiang@intel.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=nanjundaswamy.arvind@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