[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2026020646-lash-celestial-2c7a@gregkh>
Date: Fri, 6 Feb 2026 14:18:04 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Jeffrin Thalakkottoor <jeffrin@...agiritech.edu.in>
Cc: stable@...r.kernel.org, patches@...ts.linux.dev,
linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
akpm@...ux-foundation.org, linux@...ck-us.net, shuah@...nel.org,
patches@...nelci.org, lkft-triage@...ts.linaro.org,
pavel@...ladev.com, jonathanh@...dia.com, f.fainelli@...il.com,
sudipm.mukherjee@...il.com, rwarsow@....de, conor@...nel.org,
hargar@...rosoft.com, broonie@...nel.org, achill@...ill.org,
sr@...dewatkins.com
Subject: Re: [PATCH 5.10 000/160] 5.10.249-rc2 review
On Fri, Feb 06, 2026 at 06:29:08PM +0530, Jeffrin Thalakkottoor wrote:
> >
> > What config causes this? What target are you building, libbpf?
> >
>
> May be the attached config causes this. iam not building libbpf alone.
I tried your config, with gcc:
$ gcc --version
gcc (GCC) 15.2.1 20260103
And it built just fine.
I did have to do a 'make clean' first. Did you try that out?
Have you ever built this kernel successfully? If so, can you use 'git
bisect' to track down the offending commit for you?
thanks,
greg k-h
Powered by blists - more mailing lists