From: Jani Nikula <jani.nikula@linux.intel.com>
To: Tvrtko Ursulin <tursulin@ursulin.net>,
David Laight <david.laight.linux@gmail.com>,
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: Tue, 09 Dec 2025 15:54:30 +0200 [thread overview]
Message-ID: <fc8d83613fff9944f44cd3ad5908ce45d5264476@intel.com> (raw)
In-Reply-To: <602813bb-096b-44b4-af1d-95681769c943@ursulin.net>
On Mon, 08 Dec 2025, Tvrtko Ursulin <tursulin@ursulin.net> wrote:
> Anyway, I have pushed this patch to drm-intel-gt-next so it will appear
> in 6.20. Only now I realised I could have suggested to add some Fixes:
> tag to it, so it would get automatically picked for 6.19.
>
> My colleagues who are handling drm-intel-next-fixes for 6.19 could
> perhaps manually pick it up.
Picked up with
Fixes: 3b38d3515753 ("drm/i915: Add stable memory region names")
Cc: <stable@vger.kernel.org> # v6.8+
added.
BR,
Jani.
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-12-09 13:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 16:42 [PATCH] drm/i195: Fix format string truncation warning 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
2025-12-05 18:28 ` David Laight
2025-12-08 7:37 ` Tvrtko Ursulin
2025-12-09 13:54 ` Jani Nikula [this message]
2025-11-10 15:34 ` ✓ i915.CI.BAT: success for " Patchwork
2025-11-10 19:32 ` ✓ 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=fc8d83613fff9944f44cd3ad5908ce45d5264476@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@gmail.com \
--cc=ardb+git@google.com \
--cc=ardb@kernel.org \
--cc=david.laight.linux@gmail.com \
--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 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.