From: Erik Faye-Lund <Erik.Faye-Lund@arm.com>
To: "mripard@kernel.org" <mripard@kernel.org>
Cc: Steven Price <Steven.Price@arm.com>,
Karunika Choo <Karunika.Choo@arm.com>,
"tzimmermann@suse.de" <tzimmermann@suse.de>,
"simona@ffwll.ch" <simona@ffwll.ch>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"olvaffe@gmail.com" <olvaffe@gmail.com>,
"airlied@gmail.com" <airlied@gmail.com>,
Liviu Dudau <Liviu.Dudau@arm.com>,
"Boris Brezillon (boris.brezillon@collabora.com)"
<boris.brezillon@collabora.com>,
"maarten.lankhorst@linux.intel.com"
<maarten.lankhorst@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] odrm/panthor: fix immortalis condition
Date: Tue, 13 Oct 2026 09:49:58 +0000 [thread overview]
Message-ID: <f9bfd50ed3d30da1f47de791fba3bf30f8fc41b3.camel@arm.com> (raw)
In-Reply-To: <as3-CKkuP54UMDKe@houat>
On Tue, 2026-10-13 at 11:47 +0200, Maxime Ripard wrote:
> Hi,
>
> There's a typo in the patch title (odrm vs drm)
>
> On Tue, Oct 13, 2026 at 11:31:50AM +0200, Erik Faye-Lund wrote:
> > Exactly 10 cores is also valid for an Immortalis configuration,
> > according to the public documentation:
> >
> > https://support.arm.com/compute-ip/immortalis-g715
> >
> > So let's report this G715 with 10 cores as Immortalis as well, as
> > long
> > as it supports the ray-intersection feature. This matches what we
> > do for
> > more recent GPUs as well.
> >
> > Fixes: 3b1dc21d6d80 ("drm/panthor: Add support for Mali-Gx15 family
> > of GPUs")
>
> And you're missing your SoB
>
> Maxime
My appologies, I intentionally left it out locally while verifying
internal approvals for sending it out, and forgot to apply before
sending. Here's the SoB line, in case anyone wants to add it while
applying the patch. If not, I can resend.
Signed-off-by: Erik Faye-Lund <erik.faye-lund@arm.com>
next prev parent reply other threads:[~2026-10-13 9:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 9:31 Erik Faye-Lund
2026-10-13 9:43 ` Liviu Dudau
2026-10-13 9:47 ` Maxime Ripard
2026-10-13 9:49 ` Erik Faye-Lund [this message]
2026-10-13 10:20 ` Boris Brezillon
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=f9bfd50ed3d30da1f47de791fba3bf30f8fc41b3.camel@arm.com \
--to=erik.faye-lund@arm.com \
--cc=Karunika.Choo@arm.com \
--cc=Liviu.Dudau@arm.com \
--cc=Steven.Price@arm.com \
--cc=airlied@gmail.com \
--cc=boris.brezillon@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=olvaffe@gmail.com \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
/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
all inboxes | Powered by JetHome®