From: Boris Brezillon <boris.brezillon@collabora.com>
To: Kamil Konieczny <kamil.konieczny@linux.intel.com>
Cc: igt-dev@lists.freedesktop.org,
"Petri Latvala" <adrinael@adrinael.net>,
"Arkadiusz Hiler" <arek@hiler.eu>,
"Juha-Pekka Heikkila" <juhapekka.heikkila@gmail.com>,
"Bhanuprakash Modem" <bhanuprakash.modem@gmail.com>,
"Steven Price" <steven.price@arm.com>,
"Liviu Dudau" <liviu.dudau@arm.com>,
"Adrián Larumbe" <adrian.larumbe@collabora.com>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
kernel@collabora.com
Subject: Re: [PATCH i-g-t v1 v1 1/3] drm-uapi/panthor: Sync panthor uapi
Date: Fri, 28 Nov 2025 10:39:46 +0100 [thread overview]
Message-ID: <20251128103946.1849dfd0@fedora> (raw)
In-Reply-To: <20251127145641.wba63sp4h3pjs5gh@kamilkon-DESK.igk.intel.com>
On Thu, 27 Nov 2025 15:56:41 +0100
Kamil Konieczny <kamil.konieczny@linux.intel.com> wrote:
> Hi Boris,
> On 2025-11-26 at 11:55:56 +0100, Boris Brezillon wrote:
> > Will be needed for the scheduler tests.
>
> Rather than that just describe to which kernel commit you sync,
> for example look into commit 909157f3cc3c0676a4f896752276d438c3ec3959
> ("include/drm-uapi: Update uapi headers")
>
> You could use for example:
>
> Sync with drm-next kernel commit 3b1dc21d6d80 ("drm/panthor: Add
> support for Mali-Gx15 family of GPUs")
>
> No need for resend unless you will send v2.
>
> With above fixed this is
> Reviewed-by: Kamil Konieczny <kamil.konieczny@linux.intel.com>
I fixed it since there were things to address on patch 3 anyway.
next prev parent reply other threads:[~2025-11-28 9:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 10:55 [PATCH i-g-t v1 v1 0/3] tests/panthor: Add more tests Boris Brezillon
2025-11-26 10:55 ` [PATCH i-g-t v1 v1 1/3] drm-uapi/panthor: Sync panthor uapi Boris Brezillon
2025-11-27 14:56 ` Kamil Konieczny
2025-11-28 9:39 ` Boris Brezillon [this message]
2025-11-26 10:55 ` [PATCH i-g-t v1 v1 2/3] tests/panthor: Add a test to make sure the buffer is zeroed at alloc time Boris Brezillon
2025-11-27 14:57 ` Kamil Konieczny
2025-11-27 15:32 ` Daniel Almeida
2025-11-26 10:55 ` [PATCH i-g-t v1 v1 3/3] tests/panthor: Add scheduler tests Boris Brezillon
2025-11-27 15:00 ` Kamil Konieczny
2025-11-28 9:40 ` Boris Brezillon
2025-11-26 14:25 ` ✓ i915.CI.BAT: success for tests/panthor: Add more tests Patchwork
2025-11-26 15:06 ` ✓ Xe.CI.BAT: " Patchwork
2025-11-26 16:53 ` ✗ Xe.CI.Full: failure " Patchwork
2025-11-26 21:35 ` ✗ i915.CI.Full: " Patchwork
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=20251128103946.1849dfd0@fedora \
--to=boris.brezillon@collabora.com \
--cc=adrian.larumbe@collabora.com \
--cc=adrinael@adrinael.net \
--cc=arek@hiler.eu \
--cc=bhanuprakash.modem@gmail.com \
--cc=daniel.almeida@collabora.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=juhapekka.heikkila@gmail.com \
--cc=kamil.konieczny@linux.intel.com \
--cc=kernel@collabora.com \
--cc=liviu.dudau@arm.com \
--cc=steven.price@arm.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