public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Deepak R Varma <drv@mailo.com>
To: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
Cc: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>,
	Oded Gabbay <ogabbay@kernel.org>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	Deepak R Varma <drv@mailo.com>
Subject: Re: ivpu TODO list items
Date: Wed, 18 Oct 2023 22:49:15 +0530	[thread overview]
Message-ID: <ZTATkznuHyX4rUit@runicha.com> (raw)
In-Reply-To: <20231018075053.GB525429@linux.intel.com>

On Wed, Oct 18, 2023 at 09:50:53AM +0200, Stanislaw Gruszka wrote:
> Hi
>
> On Tue, Oct 17, 2023 at 10:25:19PM +0530, Deepak R Varma wrote:
> > On Fri, Oct 13, 2023 at 12:54:43PM +0530, Deepak R Varma wrote:
> > > Hello,
> > > I am shortlisted as a mentee for the LF Mentorship program. I looked at the TODO
> > > file for the ivpu driver for my project tasks. Could you please answer the
> > > following questions:
> > >
> > > 1. Is the TODO list up to date? If not, can we have it updated? Let me know if I
> > > can help.
> It's not. Some of those was already implemented (but yet not submitted).
> Some ideas there was dropped.
>
> I think this file can be whole removed. Feel free to post patch for
> that.

Hello,
Thank you for the response. I sincerely appreciate your time.
I will send in a patch to remove the TODO file.

>
> > > 2. Is it absolutely necessary for me to have a specialized hardware to test my
> > > patches? Is it limited to the 14thGen or above CPU or do I need more than that?
> Yes, I don't think someone can work on ivpu without hardware.

Okay. Could you suggest what would be the minimum hardware required to explore
this driver?

>
> > > 3. Is it okay for me to work on the TODO list items. Let me know if you have a
> > > preference [Please note I just started a few months ago and still learning].
> I recommend you to work on items from:
> https://www.kernel.org/doc/html/latest/gpu/todo.html

This is helpful. I will review the list tiems.
Thank you again.

Deepak.

>
> > Hello,
> > May I request the maintainer to review my questions and comment please?
>
> Sorry, I haven't seen this email before.
>
> Regards
> Stanislaw



  reply	other threads:[~2023-10-18 17:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-13  7:24 ivpu TODO list items Deepak R Varma
2023-10-17 16:55 ` Deepak R Varma
2023-10-18  7:50   ` Stanislaw Gruszka
2023-10-18 17:19     ` Deepak R Varma [this message]
2023-10-20  9:07       ` Stanislaw Gruszka

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=ZTATkznuHyX4rUit@runicha.com \
    --to=drv@mailo.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jacek.lawrynowicz@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ogabbay@kernel.org \
    --cc=stanislaw.gruszka@linux.intel.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