From: Bert Karwatzki <spasswolf@web.de>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
"Anusha Srivatsa" <asrivats@redhat.com>,
"Christian König" <christian.koenig@amd.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org,
linaro-mm-sig@lists.linaro.org, stable@vger.kernel.org,
spasswolf@web.de
Subject: Re: Warnings in next-20250703 caused by commit 582111e630f5
Date: Thu, 03 Jul 2025 19:23:09 +0200 [thread overview]
Message-ID: <7a56d95dc2b15fa2dac0c8a4dd20f0e253bf414f.camel@web.de> (raw)
In-Reply-To: <75abf5c1-aa1a-4405-aae4-a2efccbc3bcb@suse.de>
Am Donnerstag, dem 03.07.2025 um 18:09 +0200 schrieb Thomas Zimmermann:
> Hi,
>
> before I give up on the issue, could you please test the attached patch?
>
> Best regards
> Thomas
>
>
> --
> Thomas Zimmermann
> Graphics Driver Developer
> SUSE Software Solutions Germany GmbH
> Frankenstrasse 146, 90461 Nuernberg, Germany
> GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
> HRB 36809 (AG Nuernberg)
I applied the patch on top of next-20250703
$ git log --oneline
18ee3ed3cb60 (HEAD -> drm_gem_object_handle_put) drm/amdgpu: Provide custom framebuffer destroy function
8d6c58332c7a (tag: next-20250703, origin/master, origin/HEAD, master) Add linux-next specific files for 20250703
and it solves the issue for me (i.e. no warnings).
Bert Karwatzki
next prev parent reply other threads:[~2025-07-03 17:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 11:59 Warnings in next-20250703 caused by commit 582111e630f5 Bert Karwatzki
2025-07-03 13:37 ` Thomas Zimmermann
2025-07-03 13:45 ` Christian König
2025-07-03 13:54 ` Thomas Zimmermann
2025-07-03 13:56 ` Christian König
2025-07-03 14:15 ` Thomas Zimmermann
2025-07-03 16:09 ` Thomas Zimmermann
2025-07-03 17:23 ` Bert Karwatzki [this message]
2025-07-04 7:51 ` Thomas Zimmermann
2025-07-04 8:21 ` Bert Karwatzki
2025-07-04 8:33 ` Thomas Zimmermann
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=7a56d95dc2b15fa2dac0c8a4dd20f0e253bf414f.camel@web.de \
--to=spasswolf@web.de \
--cc=asrivats@redhat.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=stable@vger.kernel.org \
--cc=sumit.semwal@linaro.org \
--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