From: Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
To: dri-devel@lists.freedesktop.org
Cc: Oded Gabbay <ogabbay@kernel.org>,
Jeffrey Hugo <quic_jhugo@quicinc.com>,
Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
Subject: Re: [PATCH v3 00/11] accel/ivpu: Update for -next 2023.08.25
Date: Mon, 4 Sep 2023 11:11:24 +0200 [thread overview]
Message-ID: <20230904091124.GA184247@linux.intel.com> (raw)
In-Reply-To: <20230901094957.168898-1-stanislaw.gruszka@linux.intel.com>
On Fri, Sep 01, 2023 at 11:49:46AM +0200, Stanislaw Gruszka wrote:
> Update for -next:
> - various cleanups
> - begin preparation for conversion to GEM SHMEM
> - print information about used workarounds
>
> v3:
> - fix commit messages
> - split patch 2 into separate patches
>
> v2:
> - fix compilation without CONFIG_PM
Made changes requested by Jeffrey and applied to drm-misc-next .
Except patch 8 which require small change from mainline to apply
cleanly. I will wait until 6.6-rc back-merge for it.
Thanks
Stanislaw
prev parent reply other threads:[~2023-09-04 9:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 9:49 [PATCH v3 00/11] accel/ivpu: Update for -next 2023.08.25 Stanislaw Gruszka
2023-09-01 9:49 ` [PATCH v3 01/11] accel/ivpu: Move set autosuspend delay to HW specific code Stanislaw Gruszka
2023-09-01 9:49 ` [PATCH v3 02/11] accel/ivpu: Remove duplicated error messages Stanislaw Gruszka
2023-09-01 14:19 ` Jeffrey Hugo
2023-09-01 9:49 ` [PATCH v3 03/11] accel/ivpu: Make ivpu_pm_init() void Stanislaw Gruszka
2023-09-01 14:22 ` Jeffrey Hugo
2023-09-01 14:45 ` Stanislaw Gruszka
2023-09-01 9:49 ` [PATCH v3 04/11] accel/ivpu: Add information about context on failure Stanislaw Gruszka
2023-09-01 14:54 ` Jeffrey Hugo
2023-09-01 9:49 ` [PATCH v3 05/11] accel/ivpu: Print information about used workarounds Stanislaw Gruszka
2023-09-01 9:49 ` [PATCH v3 06/11] accel/ivpu: Initialize context with SSID = 1 Stanislaw Gruszka
2023-09-01 9:49 ` [PATCH v3 07/11] accel/ivpu: Move ivpu_fw_load() to ivpu_fw_init() Stanislaw Gruszka
2023-09-01 9:49 ` [PATCH v3 08/11] accel/ivpu: Add ivpu_bo_vaddr() and ivpu_bo_size() Stanislaw Gruszka
2023-09-01 9:49 ` [PATCH v3 09/11] accel/ivpu/37xx: Change register rename leftovers Stanislaw Gruszka
2023-09-01 9:49 ` [PATCH v3 10/11] accel/ivpu/37xx: White space cleanup Stanislaw Gruszka
2023-09-01 9:49 ` [PATCH v3 11/11] accel/ivpu: Move MMU register definitions to ivpu_mmu.c Stanislaw Gruszka
2023-09-04 9:11 ` 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=20230904091124.GA184247@linux.intel.com \
--to=stanislaw.gruszka@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jacek.lawrynowicz@linux.intel.com \
--cc=ogabbay@kernel.org \
--cc=quic_jhugo@quicinc.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 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.