From: Andi Shyti <andi.shyti@linux.intel.com>
To: Krzysztof Karas <krzysztof.karas@intel.com>
Cc: intel-gfx@lists.freedesktop.org,
Andi Shyti <andi.shyti@linux.intel.com>,
Sebastian Brzezinka <sebastian.brzezinka@intel.com>,
Krzysztof Niemiec <krzysztof.niemiec@intel.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>
Subject: Re: [PATCH v7 0/2] Miscellaneous fixes in drm code
Date: Tue, 10 Mar 2026 14:37:49 +0100 [thread overview]
Message-ID: <abAerdMOOa8TEV0U@ashyti-mobl2.lan> (raw)
In-Reply-To: <20260226104033.2073002-1-krzysztof.karas@intel.com>
Ping, is there anyone looking at these patches?
On Thu, Feb 26, 2026 at 10:40:31AM +0000, Krzysztof Karas wrote:
> v7:
> * Rebase and add maintainers to CC;
>
> v6 (Jani Nikula):
> * Remove the last patch from the series;
>
> v5 (Jani Nikula):
> * Split first two patches;
>
> v4:
> * Rebase and remove unnecessary patches.
>
> v3:
> * Change the casts in the last patch in the series.
>
> v2 (Jani Nikula):
> * Remove i915 patches from drm series.
> * Split the last patch into 3 separate changes.
>
> Krzysztof Karas (2):
> drm: Warn before division by 0 would occur
> drm: Avoid suspicious operations in drm_fb_dma_get_gem_addr()
>
> drivers/gpu/drm/drm_fb_dma_helper.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
>
> --
> 2.34.1
prev parent reply other threads:[~2026-03-10 13:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 10:40 [PATCH v7 0/2] Miscellaneous fixes in drm code Krzysztof Karas
2026-02-26 10:40 ` [PATCH v7 1/2] drm: Warn before division by 0 would occur Krzysztof Karas
2026-02-26 10:40 ` [PATCH v7 2/2] drm: Avoid suspicious operations in drm_fb_dma_get_gem_addr() Krzysztof Karas
2026-02-26 12:25 ` Andi Shyti
2026-02-26 11:47 ` ✓ i915.CI.BAT: success for Miscellaneous fixes in drm code (rev2) Patchwork
2026-02-26 15:38 ` ✗ i915.CI.Full: failure " Patchwork
2026-03-10 13:37 ` Andi Shyti [this message]
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=abAerdMOOa8TEV0U@ashyti-mobl2.lan \
--to=andi.shyti@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=krzysztof.karas@intel.com \
--cc=krzysztof.niemiec@intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=sebastian.brzezinka@intel.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