dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: "Timur Kristóf" <timur.kristof@gmail.com>
To: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
Cc: Alex Deucher <alexander.deucher@amd.com>,
	Leo Li <sunpeng.li@amd.com>,  David Airlie <airlied@gmail.com>,
	amd-gfx list <amd-gfx@lists.freedesktop.org>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	linux-kernel@vger.kernel.org
Subject: Re: linux-next-20251029 - build error in amdgpu
Date: Sun, 2 Nov 2025 10:27:54 +0100	[thread overview]
Message-ID: <CAFF-SiU3XL5pZAzsB=eXi7e1LKzx5XwiNOyfGpPXOnnc6uo2cw@mail.gmail.com> (raw)
In-Reply-To: <1296761.1762045181@turing-police>

[-- Attachment #1: Type: text/plain, Size: 1239 bytes --]

Hello Valdis,

I use Fedora and I developed that patch on Fedora, using the same GCC
version. It did not give me an error or warning when I wrote the patch. It
is still not giving me an error or warning about that code now.

I am working with the amd-staging-drm-next branch.

What do I need to do to trigger the warning?

Thanks & best regards,
Timur

Valdis Klētnieks <valdis.kletnieks@vt.edu> ezt írta (időpont: 2025. nov.
2., Vas 1:59):

> On Thu, 30 Oct 2025 19:05:30 +0100, Timur Kristóf said:
>
> > Can you say how to reproduce that?
> > I use the same version of GCC but it hasn't given me any warning or
> > error for that patch.
>
> Upon further testing,
>
> [/usr/src/linux-next] make
>
> is sufficient on my system. Turns out that it errors out even without W=1.
> My
> next guess was that it had to do with -Werror, which would cause warnings
> to
> be treated as errors, but my .config has
>
> # CONFIG_WERROR is not set
> # CONFIG_DRM_WERROR is not set
> # CONFIG_DRM_AMDGPU_WERROR is not set
>
> Do you perhaps have patches in your tree that aren't in next-20251029?
>
> I wonder if Fedora's build of gcc 15.2.1 is different somehow from the
> build you're using....
>
>
>
>

[-- Attachment #2: Type: text/html, Size: 1797 bytes --]

  reply	other threads:[~2025-11-02  9:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-30 17:20 linux-next-20251029 - build error in amdgpu Valdis Klētnieks
2025-10-30 18:05 ` Timur Kristóf
2025-11-02  0:59   ` Valdis Klētnieks
2025-11-02  9:27     ` Timur Kristóf [this message]
2025-11-06  2:34       ` Amit Dhingra
2025-11-06  2:40         ` Timur Kristóf
2025-11-06  3:24           ` Amit Dhingra
2025-11-06  3:29             ` Timur Kristóf
2025-11-06  3:32               ` Amit Dhingra
2025-11-06  3:31             ` Valdis Klētnieks
2025-11-06  3:18         ` Valdis Klētnieks
2025-11-06 14:02           ` Kees Cook
2025-11-06 23:49             ` Bill Wendling
2025-11-08 15:10             ` Valdis Klētnieks

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='CAFF-SiU3XL5pZAzsB=eXi7e1LKzx5XwiNOyfGpPXOnnc6uo2cw@mail.gmail.com' \
    --to=timur.kristof@gmail.com \
    --cc=airlied@gmail.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sunpeng.li@amd.com \
    --cc=valdis.kletnieks@vt.edu \
    /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;
as well as URLs for NNTP newsgroup(s).