From: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
To: Deepak R Varma <drv@mailo.com>
Cc: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>,
Oded Gabbay <ogabbay@kernel.org>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [PATCH] accel/ivpu: Delete the TODO file
Date: Thu, 26 Oct 2023 08:02:22 +0200 [thread overview]
Message-ID: <20231026060222.GA1024364@linux.intel.com> (raw)
In-Reply-To: <ZTAucrOT69/tQK2o@runicha.com>
On Thu, Oct 19, 2023 at 12:43:54AM +0530, Deepak R Varma wrote:
> The work items listed in the TODO file of this driver file are either
> completed or dropped. The file is no more significant according
> to the maintainers. Hence removing it from the sources.
>
> Suggested-by: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
> Signed-off-by: Deepak R Varma <drv@mailo.com>
Applied to drm-misc-next
Thanks
Stanislaw
> ---
> drivers/accel/ivpu/TODO | 11 -----------
> 1 file changed, 11 deletions(-)
> delete mode 100644 drivers/accel/ivpu/TODO
>
> diff --git a/drivers/accel/ivpu/TODO b/drivers/accel/ivpu/TODO
> deleted file mode 100644
> index 9077217ae10f..000000000000
> --- a/drivers/accel/ivpu/TODO
> +++ /dev/null
> @@ -1,11 +0,0 @@
> -- Move to threaded_irqs to mitigate potential infinite loop in ivpu_ipc_irq_handler()
> -- Implement support for BLOB IDs
> -- Add debugfs support to improve debugging and testing
> -- Add tracing events for performance debugging
> -- Implement HW based scheduling support
> -- Use syncobjs for submit/sync
> -- Refactor IPC protocol to improve message latency
> -- Implement BO cache and MADVISE IOCTL
> -- Add support for user allocated buffers using prime import and dma-buf heaps
> -- Refactor struct ivpu_bo to use struct drm_gem_shmem_object
> -- Add driver/device documentation
> --
> 2.39.2
>
>
>
prev parent reply other threads:[~2023-10-26 6:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 19:13 [PATCH] accel/ivpu: Delete the TODO file Deepak R Varma
2023-10-26 6:02 ` Stanislaw Gruszka [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=20231026060222.GA1024364@linux.intel.com \
--to=stanislaw.gruszka@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=drv@mailo.com \
--cc=jacek.lawrynowicz@linux.intel.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ogabbay@kernel.org \
/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