From: Chia-I Wu <olvaffe@gmail.com>
To: Rob Clark <robdclark@gmail.com>
Cc: dri-devel@lists.freedesktop.org,
Rob Clark <robdclark@chromium.org>, Emma Anholt <emma@anholt.net>,
Akhil P Oommen <quic_akhilpo@quicinc.com>,
linux-arm-msm@vger.kernel.org,
Douglas Anderson <dianders@chromium.org>,
open list <linux-kernel@vger.kernel.org>,
Sean Paul <sean@poorly.run>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
freedreno@lists.freedesktop.org,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [Freedreno] [PATCH 0/3] drm/msm/a6xx: devcore dump fixes
Date: Thu, 13 Oct 2022 17:19:18 -0700 [thread overview]
Message-ID: <CAPaKu7SE+Vh9rW6MVr8fCUdrJM6f7O1ZOfSPFdzRaw9TjpG-FA@mail.gmail.com> (raw)
In-Reply-To: <20221013225520.371226-1-robdclark@gmail.com>
On Thu, Oct 13, 2022 at 3:55 PM Rob Clark <robdclark@gmail.com> wrote:
>
> From: Rob Clark <robdclark@chromium.org>
>
> First patch fixes a recently introduced memory corruption, the remaining
> two are cleanups.
Series is
Reviewed-by: Chia-I Wu <olvaffe@gmail.com>
> Rob Clark (3):
> drm/msm/a6xx: Fix kvzalloc vs state_kcalloc usage
> drm/msm/a6xx: Skip snapshotting unused GMU buffers
> drm/msm/a6xx: Remove state objects from list before freeing
>
> drivers/gpu/drm/msm/adreno/a6xx_gpu_state.c | 18 ++++++++++++++++--
> drivers/gpu/drm/msm/adreno/adreno_gpu.c | 7 ++++++-
> 2 files changed, 22 insertions(+), 3 deletions(-)
>
> --
> 2.37.3
>
next prev parent reply other threads:[~2022-10-14 0:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 22:55 [PATCH 0/3] drm/msm/a6xx: devcore dump fixes Rob Clark
2022-10-13 22:55 ` [PATCH 1/3] drm/msm/a6xx: Fix kvzalloc vs state_kcalloc usage Rob Clark
2022-10-13 22:55 ` [PATCH 2/3] drm/msm/a6xx: Skip snapshotting unused GMU buffers Rob Clark
2022-10-13 22:55 ` [PATCH 3/3] drm/msm/a6xx: Remove state objects from list before freeing Rob Clark
2022-10-14 0:19 ` Chia-I Wu [this message]
2022-10-14 6:50 ` [PATCH 0/3] drm/msm/a6xx: devcore dump fixes Akhil P Oommen
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=CAPaKu7SE+Vh9rW6MVr8fCUdrJM6f7O1ZOfSPFdzRaw9TjpG-FA@mail.gmail.com \
--to=olvaffe@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=dianders@chromium.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=emma@anholt.net \
--cc=freedreno@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_akhilpo@quicinc.com \
--cc=robdclark@chromium.org \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
/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).