From: Jeffrey Hugo <quic_jhugo@quicinc.com>
To: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>,
<dri-devel@lists.freedesktop.org>
Cc: Oded Gabbay <ogabbay@kernel.org>,
Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
Subject: Re: [PATCH 4/4] accel/ivpu: Fix old dma_buf api usage
Date: Thu, 2 Feb 2023 08:06:25 -0700 [thread overview]
Message-ID: <7ec5bc53-1fb3-2974-852e-de44ad768b1a@quicinc.com> (raw)
In-Reply-To: <20230202092114.2637452-5-stanislaw.gruszka@linux.intel.com>
On 2/2/2023 2:21 AM, Stanislaw Gruszka wrote:
> Update according to new dma-buf locking scheme.
>
> Remove redundant WARN_ON()'s, dma_buf functions internally
> have the same warnings already.
>
> Signed-off-by: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
Reviewed-by: Jeffrey Hugo <quic_jhugo@quicinc.com>
next prev parent reply other threads:[~2023-02-02 15:06 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 [this message]
2023-02-06 8:34 ` [PATCH 0/4] accel/ivpu: Fixes for 6.3 Jacek Lawrynowicz
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=7ec5bc53-1fb3-2974-852e-de44ad768b1a@quicinc.com \
--to=quic_jhugo@quicinc.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jacek.lawrynowicz@linux.intel.com \
--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;
as well as URLs for NNTP newsgroup(s).