From: Alyssa Rosenzweig <alyssa@collabora.com>
To: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, tomeu.vizoso@collabora.com,
Adri?n Larumbe <adrian.larumbe@collabora.com>,
dri-devel@lists.freedesktop.org, steven.price@arm.com,
alyssa.rosenzweig@collabora.com
Subject: Re: [PATCH v2 1/1] drm/panfrost: Add support for devcoredump
Date: Tue, 21 Jun 2022 10:32:38 -0400 [thread overview]
Message-ID: <YrHWhmNVJnIJ1iaT@maud> (raw)
In-Reply-To: <202206211114.PJcD2pJh-lkp@intel.com>
> drivers/gpu/drm/panfrost/panfrost_dump.c: In function 'panfrost_core_dump':
> >> drivers/gpu/drm/panfrost/panfrost_dump.c:115:20: error: 'struct panfrost_job' has no member named 'file_priv'
> 115 | as_nr = job->file_priv->mmu->as;
> | ^~
FWIW -- this is due to recent changes in panfrost, you should rebase on
the latest drm-misc-next which is where the patch will be applied
anyway.
WARNING: multiple messages have this Message-ID (diff)
From: Alyssa Rosenzweig <alyssa@collabora.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v2 1/1] drm/panfrost: Add support for devcoredump
Date: Tue, 21 Jun 2022 10:32:38 -0400 [thread overview]
Message-ID: <YrHWhmNVJnIJ1iaT@maud> (raw)
In-Reply-To: <202206211114.PJcD2pJh-lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 438 bytes --]
> drivers/gpu/drm/panfrost/panfrost_dump.c: In function 'panfrost_core_dump':
> >> drivers/gpu/drm/panfrost/panfrost_dump.c:115:20: error: 'struct panfrost_job' has no member named 'file_priv'
> 115 | as_nr = job->file_priv->mmu->as;
> | ^~
FWIW -- this is due to recent changes in panfrost, you should rebase on
the latest drm-misc-next which is where the patch will be applied
anyway.
next prev parent reply other threads:[~2022-06-21 14:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 2:32 [PATCH v2 0/1] devcoredump support for Panfrost GPU driver Adrián Larumbe
2022-06-21 2:32 ` [PATCH v2 1/1] drm/panfrost: Add support for devcoredump Adrián Larumbe
2022-06-21 4:37 ` kernel test robot
2022-06-21 14:32 ` Alyssa Rosenzweig [this message]
2022-06-21 14:32 ` Alyssa Rosenzweig
2022-06-22 2:30 ` [kbuild-all] " Chen, Rong A
2022-06-22 12:06 ` Alyssa Rosenzweig
2022-06-22 12:06 ` Alyssa Rosenzweig
2022-06-21 5:46 ` kernel test robot
2022-06-21 7:37 ` kernel test robot
2022-06-21 7:37 ` kernel test robot
2022-06-21 13:03 ` Alyssa Rosenzweig
2022-06-22 1:54 ` Adri??n Larumbe
2022-06-22 12:08 ` Alyssa Rosenzweig
2022-06-22 13:22 ` Lucas Stach
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=YrHWhmNVJnIJ1iaT@maud \
--to=alyssa@collabora.com \
--cc=adrian.larumbe@collabora.com \
--cc=alyssa.rosenzweig@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kbuild-all@lists.01.org \
--cc=lkp@intel.com \
--cc=steven.price@arm.com \
--cc=tomeu.vizoso@collabora.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.