public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jeffrin Thalakkottoor <jeffrin@rajagiritech.edu.in>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
	linux-kernel@vger.kernel.org, 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 5.10 000/160] 5.10.249-rc2 review
Date: Fri, 6 Feb 2026 14:18:04 +0100	[thread overview]
Message-ID: <2026020646-lash-celestial-2c7a@gregkh> (raw)
In-Reply-To: <CAG=yYwkOvV_=hhzSkQ06UqUW2X_FOm6saGqBaz4hLxqAg_WcvQ@mail.gmail.com>

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

  reply	other threads:[~2026-02-06 13:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-05 14:44 [PATCH 5.10 000/160] 5.10.249-rc2 review Greg Kroah-Hartman
2026-02-05 17:21 ` Brett A C Sheffield
2026-02-05 19:58 ` Florian Fainelli
2026-02-05 21:11 ` Mark Brown
2026-02-06  3:28 ` Woody Suwalski
2026-02-06  4:24 ` Barry K. Nathan
2026-02-06 10:59 ` Jon Hunter
2026-02-06 12:19 ` Jeffrin Thalakkottoor
2026-02-06 12:30   ` Greg Kroah-Hartman
2026-02-06 12:59     ` Jeffrin Thalakkottoor
2026-02-06 13:18       ` Greg Kroah-Hartman [this message]
2026-02-06 16:52         ` Jeffrin Thalakkottoor
2026-02-06 22:28 ` Pavel Machek

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=2026020646-lash-celestial-2c7a@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=jeffrin@rajagiritech.edu.in \
    --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