From: Greg KH <gregkh@linuxfoundation.org>
To: Miguel Ojeda <ojeda@kernel.org>
Cc: achill@achill.org, akpm@linux-foundation.org, broonie@kernel.org,
conor@kernel.org, f.fainelli@gmail.com, hargar@microsoft.com,
jonathanh@nvidia.com, linux-kernel@vger.kernel.org,
linux@roeck-us.net, lkft-triage@lists.linaro.org,
patches@kernelci.org, patches@lists.linux.dev,
pavel@nabladev.com, rwarsow@gmx.de, shuah@kernel.org,
sr@sladewatkins.com, stable@vger.kernel.org,
sudipm.mukherjee@gmail.com, torvalds@linux-foundation.org
Subject: Re: [PATCH 6.19 000/781] 6.19.4-rc2 review
Date: Thu, 26 Feb 2026 13:47:03 -0800 [thread overview]
Message-ID: <2026022640-ranked-resigned-83a9@gregkh> (raw)
In-Reply-To: <20260226201056.28728-1-ojeda@kernel.org>
On Thu, Feb 26, 2026 at 09:10:56PM +0100, Miguel Ojeda wrote:
> The drm/tyr build error (`COMMON_CLK`) is now fixed, from 6.19.1:
>
> https://lore.kernel.org/stable/20260215023627.56245-1-ojeda@kernel.org/
>
> The fixes for the other build error (`COMPAT`) and the warning
> (`unwrap_or`) have not arrived yet.
So should this be backported? If so, how far back?
thanks,
greg k-h
next prev parent reply other threads:[~2026-02-26 21:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 15:54 [PATCH 6.19 000/781] 6.19.4-rc2 review Greg Kroah-Hartman
2026-02-25 16:33 ` Ronald Warsow
2026-02-25 21:21 ` Luna Jernberg
2026-02-25 16:53 ` Jeffrin Thalakkottoor
2026-02-25 17:11 ` Jeffrin Thalakkottoor
2026-02-25 17:35 ` Brett A C Sheffield
2026-02-25 18:00 ` Florian Fainelli
2026-02-25 18:27 ` Peter Schneider
2026-02-25 20:09 ` Jon Hunter
2026-02-25 22:09 ` Justin Forbes
2026-02-25 23:49 ` Brett Mastbergen
2026-02-26 10:31 ` Takeshi Ogasawara
2026-02-26 20:10 ` Miguel Ojeda
2026-02-26 21:47 ` Greg KH [this message]
2026-02-26 22:16 ` Miguel Ojeda
2026-02-27 13:48 ` Mark Brown
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=2026022640-ranked-resigned-83a9@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=achill@achill.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--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=ojeda@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.