public inbox for patches@lists.linux.dev
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: "Barry K. Nathan" <barryn@pobox.com>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	gregkh@linuxfoundation.org, patches@lists.linux.dev,
	torvalds@linux-foundation.org, akpm@linux-foundation.org,
	linux@roeck-us.net, shuah@kernel.org, patches@kernelci.org,
	lkft-triage@lists.linaro.org, pavel@nabladev.com,
	jonathanh@nvidia.com, f.fainelli@gmail.com,
	sudipm.mukherjee@gmail.com, rwarsow@gmx.de, conor@kernel.org,
	hargar@microsoft.com, broonie@kernel.org, achill@achill.org,
	sr@sladewatkins.com
Subject: Re: [PATCH 6.19 000/844] 6.19.6-rc1 review
Date: Sun, 1 Mar 2026 19:49:03 -0500	[thread overview]
Message-ID: <aaTef1CyYVhpE4k2@laps> (raw)
In-Reply-To: <bf650251-9254-4d42-9224-0b8db08042c7@pobox.com>

On Sun, Mar 01, 2026 at 08:43:43AM -0800, Barry K. Nathan wrote:
>On 3/1/26 00:49, Barry K. Nathan wrote:
>>Unfortunately, 6.19.6-rc1 won't even build for me:
>>
>>Warning: drivers/gpu/drm/i915/intel_wakeref.h:156 expecting prototype for __intel_wakeref_put(). Prototype was for INTEL_WAKEREF_PUT_ASYNC() instead
>>1 warnings as errors
>>make[9]: *** [drivers/gpu/drm/i915/Makefile:449: drivers/gpu/drm/i915/intel_wakeref.hdrtest] Error 3
>>make[8]: *** [scripts/Makefile.build:546: drivers/gpu/drm/i915] Error 2
>>make[8]: *** Waiting for unfinished jobs....
>>
>>This only happens with 6.19.6-rc1, not any of this weekend's other
>>stable rc's. (I'm still testing 6.12.75-rc1 and 6.18.16-rc1, but
>>they're doing well so far. I have successfully built 5.15.202-rc1
>>and 6.1.165-rc1 but I won't have a chance to do any further testing
>>of them before they're released.)
>>
>>As soon as I can (in the next hour or two) I'll minimize my config
>>a little to shorten the compile time, then I'll start bisecting.
>
>Result of bisecting:
>first bad commit: [0ef5d235ab57bc90831ddf38eb1742ff68f345e1]
>docs: kdoc: fix logic to handle unissued warnings
>
>This commit breaks the i915 DRM build if (and only if)
>CONFIG_DRM_I915_WERROR=y, whether CONFIG_WERROR is enabled or
>disabled. However, the "bad" commit is definitely fixing a real
>bug, and this build failure doesn't happen on current mainline
>as of this writing (commit eb71ab2bf722), so I don't think
>dropping the patch is the correct way forward.
>
>Rather, adding commit 524696a19e34598c9173fdd5b32fb7e5d16a91d3
>    drm/i915/wakeref: clean up INTEL_WAKEREF_PUT_* flag macros
>(it applies cleanly) fixes the warning, thereby fixing the build.
>
>The resulting kernel works fine in my testing, too. I'm using
>6.19.6-rc1 + 524696a19e34598c9173fdd5b32fb7e5d16a91d3 to write
>and send this email from my ThinkPad T14 Gen 1, which uses the
>i915 DRM driver for its Intel integrated graphics. (I also
>tested it on my 2017 MacBook Air, which also uses i915 DRM for
>its Intel integrated graphics.)

I'll queue 524696a19e345 up, thanks for the report!

-- 
Thanks,
Sasha

  reply	other threads:[~2026-03-02  0:49 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-28 17:18 [PATCH 6.19 000/844] 6.19.6-rc1 review Sasha Levin
2026-02-28 18:12 ` Ronald Warsow
2026-02-28 22:13   ` Woody Suwalski
2026-02-28 23:41     ` Barry K. Nathan
2026-03-01  0:33     ` Peter Schneider
2026-03-01  1:17     ` Sasha Levin
2026-03-01  2:46 ` Peter Schneider
2026-03-01  8:36 ` Takeshi Ogasawara
2026-03-01  8:49 ` Barry K. Nathan
2026-03-01 16:43   ` Barry K. Nathan
2026-03-02  0:49     ` Sasha Levin [this message]
2026-03-02  6:34       ` Barry K. Nathan
2026-03-01  8:54 ` Brett A C Sheffield
2026-03-01 12:05 ` Mark Brown
2026-03-01 15:15   ` Peter Schneider
2026-03-01 16:11     ` Sasha Levin
2026-03-01 16:20       ` Mark Brown
2026-03-01 21:49 ` Ron Economos
2026-03-01 23:48 ` Miguel Ojeda
2026-03-02  0:53 ` Hardik Garg
2026-03-02 13:13 ` Jon Hunter

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=aaTef1CyYVhpE4k2@laps \
    --to=sashal@kernel.org \
    --cc=achill@achill.org \
    --cc=akpm@linux-foundation.org \
    --cc=barryn@pobox.com \
    --cc=broonie@kernel.org \
    --cc=conor@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hargar@microsoft.com \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=patches@kernelci.org \
    --cc=patches@lists.linux.dev \
    --cc=pavel@nabladev.com \
    --cc=rwarsow@gmx.de \
    --cc=shuah@kernel.org \
    --cc=sr@sladewatkins.com \
    --cc=stable@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --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