public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Philip Müller" <philm@manjaro.org>
Cc: Laura Nao <laura.nao@collabora.com>,
	stable@vger.kernel.org, Uday M Bhat <uday.m.bhat@intel.com>
Subject: Re: 5.10 kernel series fails to build on newer toolchain: FAILED unresolved symbol filp_close
Date: Thu, 5 Jun 2025 10:46:43 +0200	[thread overview]
Message-ID: <2025060532-cadmium-shaking-833e@gregkh> (raw)
In-Reply-To: <722c3acd-6735-4882-a4b1-ed5c75fd4339@manjaro.org>

On Thu, Jun 05, 2025 at 09:44:49AM +0200, Philip Müller wrote:
> On 4/1/25 11:17, Greg KH wrote:
> > On Fri, Mar 28, 2025 at 07:06:10AM -0400, Philip Müller wrote:
> > > Yes, I can confirm that with the current stable-queue patches on top of
> > > 5.10.235 it compiles. I only had to not apply the following patch
> > > 
> > > ASoC: Intel: sof_sdw: Add support for Fatcat board with BT offload enabled
> > > in PTL platform
> > 
> > I've dropped this commit from the queue now, thanks.
> > 
> > greg k-h
> 
> Somehow the issue came back with 5.10.238 ...

I have no context here, sorry...

  reply	other threads:[~2025-06-05  8:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-14  1:18 5.10 kernel series fails to build on newer toolchain: FAILED unresolved symbol filp_close Philip Müller
2025-03-14  5:39 ` Greg Kroah-Hartman
2025-03-14  9:19   ` Philip Müller
2025-03-20 11:28     ` Laura Nao
2025-03-20 12:55       ` Greg KH
2025-03-28 11:06       ` Philip Müller
2025-04-01  9:17         ` Greg KH
2025-06-05  7:44           ` Philip Müller
2025-06-05  8:46             ` Greg KH [this message]
2025-06-08  6:27               ` Philip Müller
2025-06-17 14:05                 ` Greg KH
2025-06-19  8:34                   ` Philip Müller
2025-06-19  8:47                     ` Greg KH
2025-06-24  7:05               ` Philip Müller
2025-10-26 13:26                 ` Alyssa Ross
2025-12-15 19:00                   ` David Nyström

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=2025060532-cadmium-shaking-833e@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=laura.nao@collabora.com \
    --cc=philm@manjaro.org \
    --cc=stable@vger.kernel.org \
    --cc=uday.m.bhat@intel.com \
    /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