All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Parth Kamani <parthvipulkamani@gmail.com>
Cc: intel-gfx@lists.freedesktop.org, Simona Vetter <simona.vetter@ffwll.ch>
Subject: Re: Offering to take a TODO item in i915
Date: Mon, 03 Aug 2026 14:24:43 +0300	[thread overview]
Message-ID: <40500b41434cf52b25d094fbfdcf56a782fd4607@intel.com> (raw)
In-Reply-To: <CACa-pC3Z6KN247yJ9tnb9BZoqSHmXWOzo4LyBodGbQj7uCN=CQ@mail.gmail.com>

On Mon, 03 Aug 2026, Parth Kamani <parthvipulkamani@gmail.com> wrote:
> Hi Jani,
>
> I was looking through drivers/gpu/drm/i915/TODO.txt and noticed that there
> are still a number of outstanding items. One that caught my attention was *"for
> discrete memory manager, merge enough dg1 to be able to refactor it to ..."*.
> I also saw items such as *"Come up with a plan what to do with
> drm/scheduler and how to get there"* and *"Roll out dma_fence critical
> section annotations"*, so it looks like there are several areas that still
> need work.
>
> From the TODO, some of these items appear more involved than others, so
> before I dive in I wanted to check with you. Is the discrete memory manager
> item still something that would be appropriate to work on, or would you
> recommend a different task for someone making a first contribution to i915?
>
> My preference is to keep patches small enough to review comfortably,
> run checkpatch
> --strict, test against current mainline, and submit them via git send-email.
>
> I'm currently in my final year of B.Tech in Computer Engineering at K J
> Somaiya College of Engineering, Mumbai (graduating mid-2027), and I have a
> meaningful amount of time to contribute before graduation. I'd much rather
> spend that time contributing to a live upstream codebase than working only
> on coursework. If there's a better first task than the TODO item above, I'd
> really appreciate your recommendation and would be happy to work on that
> instead.

Thanks for your interest!

The TODO was added in commit 6ab61ad5c1d8 ("drm/i915: add gem/gt TODO")
and has barely been touched since. The primary reason is migrating to
the xe driver for new platforms. If you're looking to work on a "live
upstream codebase", seeking tasks in the xe driver, or the display
driver under i915/display, shared between the xe and i915 drivers, is
probably more rewarding.


HTH,
Jani.


-- 
Jani Nikula, Intel

       reply	other threads:[~2026-08-03 11:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CACa-pC3Z6KN247yJ9tnb9BZoqSHmXWOzo4LyBodGbQj7uCN=CQ@mail.gmail.com>
2026-08-03 11:24 ` Jani Nikula [this message]
2026-08-03 15:10   ` Offering to take a TODO item in i915 Parth Kamani
     [not found] <CACa-pC1wVczshOD0xE0oLMDa7q25Q2ibJzCOKyDs4vW6Ga2cCA@mail.gmail.com>
2026-08-05  1:51 ` Rodrigo Vivi
2026-08-09  5:40   ` Parth Kamani

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=40500b41434cf52b25d094fbfdcf56a782fd4607@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=parthvipulkamani@gmail.com \
    --cc=simona.vetter@ffwll.ch \
    /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.