From: Jani Nikula <jani.nikula@linux.intel.com>
To: Tvrtko Ursulin <tursulin@ursulin.net>, Ard Biesheuvel <ardb@kernel.org>
Cc: Ard Biesheuvel <ardb+git@google.com>,
linux-kernel@vger.kernel.org,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/i195: Fix format string truncation warning
Date: Fri, 05 Dec 2025 13:18:55 +0200 [thread overview]
Message-ID: <cd911303d0aa820ff5c478b2759f3301096a618c@intel.com> (raw)
In-Reply-To: <f33b29bb-72bd-4925-adb6-e8cd5267c142@ursulin.net>
On Fri, 05 Dec 2025, Tvrtko Ursulin <tursulin@ursulin.net> wrote:
> On 05/12/2025 10:48, Ard Biesheuvel wrote:
>> OK, so something like
>>
>> --- a/drivers/gpu/drm/i915/intel_memory_region.h
>> +++ b/drivers/gpu/drm/i915/intel_memory_region.h
>> @@ -72,7 +72,7 @@ struct intel_memory_region {
>> u16 instance;
>> enum intel_region_id id;
>> char name[16];
>> - char uabi_name[16];
>> + char uabi_name[20];
>> bool private; /* not for userspace */
>>
>> struct {
>
> Yes please. There is only two of those objects at majority of systems,
> and 3-4 on a few discrete cards supported by i915, so no big deal to
> grow them a tiny bit.
For v2, please also fix the subject prefix: drm/i915.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-12-05 11:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 16:42 Ard Biesheuvel
2025-11-07 20:48 ` Tvrtko Ursulin
2025-11-09 18:00 ` Ard Biesheuvel
2025-12-05 10:48 ` Ard Biesheuvel
2025-12-05 11:13 ` Tvrtko Ursulin
2025-12-05 11:18 ` Jani Nikula [this message]
2025-12-05 18:28 ` David Laight
2025-12-08 7:37 ` Tvrtko Ursulin
2025-12-09 13:54 ` Jani Nikula
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=cd911303d0aa820ff5c478b2759f3301096a618c@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@gmail.com \
--cc=ardb+git@google.com \
--cc=ardb@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=simona@ffwll.ch \
--cc=tursulin@ursulin.net \
/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
Powered by JetHome