From: Shuah Khan <skhan@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "David Hildenbrand (Red Hat)" <david@kernel.org>,
akpm@linux-foundation.org,
Alexander Deucher <Alexander.Deucher@amd.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
amd-gfx@lists.freedesktop.org,
dri-devel <dri-devel@lists.freedesktop.org>,
Guenter Roeck <linux@roeck-us.net>,
Linux Memory Management List <linux-mm@kvack.org>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: Linux 6.18 amdgpu build error
Date: Thu, 4 Dec 2025 16:28:34 -0700 [thread overview]
Message-ID: <60fe7660-f3fb-4c94-b21f-20ebc9e14f5d@linuxfoundation.org> (raw)
In-Reply-To: <CAHk-=wiEXy+7Gd3ONQ-v0e61e6qAmrtk+WE2dpW_61p83nMgXw@mail.gmail.com>
On 12/4/25 16:23, Linus Torvalds wrote:
> On Thu, 4 Dec 2025 at 15:20, Shuah Khan <skhan@linuxfoundation.org> wrote:
>>
>> I didn't see any problems on 6.18.
>
> Ahh. So it might be just that buggy commit adfb6609c680 then, and the
> fix already being in rc7 (and final).
>
Yes - correct.
thanks,
-- Shuah
prev parent reply other threads:[~2025-12-04 23:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <74032153-813a-4a40-8363-cce264f4d5ea@linuxfoundation.org>
[not found] ` <1eb24816-530b-4470-8e58-ce7d8297996c@roeck-us.net>
[not found] ` <0425d7b4-76e4-4057-83a5-a7b17a051c54@linuxfoundation.org>
[not found] ` <ec77d11a-7613-4b75-8c9e-f2bba1595f0f@roeck-us.net>
[not found] ` <9d520a1d-0b8d-4d30-b29f-230fc0f92b8a@linuxfoundation.org>
[not found] ` <1f31b86d-283c-4878-92d0-ab90aed0c58d@roeck-us.net>
2025-12-04 2:34 ` Shuah Khan
2025-12-04 6:05 ` David Hildenbrand (Red Hat)
2025-12-04 17:40 ` Shuah Khan
2025-12-04 19:36 ` Linus Torvalds
2025-12-04 19:45 ` David Hildenbrand (Red Hat)
2025-12-04 23:20 ` Shuah Khan
2025-12-04 23:23 ` Linus Torvalds
2025-12-04 23:28 ` Shuah Khan [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=60fe7660-f3fb-4c94-b21f-20ebc9e14f5d@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=Alexander.Deucher@amd.com \
--cc=akpm@linux-foundation.org \
--cc=amd-gfx@lists.freedesktop.org \
--cc=david@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@roeck-us.net \
--cc=torvalds@linux-foundation.org \
/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