From: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
To: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>,
dri-devel@lists.freedesktop.org
Cc: Oded Gabbay <ogabbay@kernel.org>, Jeffrey Hugo <quic_jhugo@quicinc.com>
Subject: Re: [PATCH 0/4] accel/ivpu: Fixes for 6.3
Date: Mon, 6 Feb 2023 09:34:39 +0100 [thread overview]
Message-ID: <e2faebbb-8b71-e439-0c5f-e628d353948c@linux.intel.com> (raw)
In-Reply-To: <20230202092114.2637452-1-stanislaw.gruszka@linux.intel.com>
Patchset applied to drm-misc-next and cherry-picked to drm-misc-next-fixes.
Thanks.
On 02.02.2023 10:21, Stanislaw Gruszka wrote:
> Few fixes intended for 6.3.
>
> Andrzej Kacprowski (2):
> accel/ivpu: Fix FW API data alignment issues
> accel/ivpu: Send VPU_JSM_MSG_CONTEXT_DELETE when deleting context
>
> Stanislaw Gruszka (2):
> accel/ivpu: Set dma max_segment_size
> accel/ivpu: Fix old dma_buf api usage
>
> drivers/accel/ivpu/ivpu_drv.c | 2 +
> drivers/accel/ivpu/ivpu_fw.c | 37 +++++++++++------
> drivers/accel/ivpu/ivpu_gem.c | 8 +---
> drivers/accel/ivpu/ivpu_job.c | 5 ++-
> drivers/accel/ivpu/ivpu_jsm_msg.c | 11 +++++
> drivers/accel/ivpu/ivpu_jsm_msg.h | 2 +-
> drivers/accel/ivpu/vpu_jsm_api.h | 67 ++++++++++++++++++-------------
> 7 files changed, 81 insertions(+), 51 deletions(-)
>
prev parent reply other threads:[~2023-02-06 8:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 9:21 [PATCH 0/4] accel/ivpu: Fixes for 6.3 Stanislaw Gruszka
2023-02-02 9:21 ` [PATCH 1/4] accel/ivpu: Fix FW API data alignment issues Stanislaw Gruszka
2023-02-02 15:04 ` Jeffrey Hugo
2023-02-03 8:05 ` Jacek Lawrynowicz
2023-02-03 14:58 ` Jeffrey Hugo
2023-02-02 9:21 ` [PATCH 2/4] accel/ivpu: Send VPU_JSM_MSG_CONTEXT_DELETE when deleting context Stanislaw Gruszka
2023-02-02 15:05 ` Jeffrey Hugo
2023-02-02 9:21 ` [PATCH 3/4] accel/ivpu: Set dma max_segment_size Stanislaw Gruszka
2023-02-02 15:05 ` Jeffrey Hugo
2023-02-02 9:21 ` [PATCH 4/4] accel/ivpu: Fix old dma_buf api usage Stanislaw Gruszka
2023-02-02 15:06 ` Jeffrey Hugo
2023-02-06 8:34 ` Jacek Lawrynowicz [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=e2faebbb-8b71-e439-0c5f-e628d353948c@linux.intel.com \
--to=jacek.lawrynowicz@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=ogabbay@kernel.org \
--cc=quic_jhugo@quicinc.com \
--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