mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, stable@vger.kernel.org
Cc: 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, 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.6 000/508] 6.6.141-rc1 review
Date: Wed, 20 May 2026 13:33:49 -0700	[thread overview]
Message-ID: <fbe52f15-5b34-4e03-88e0-005ae6200a60@gmail.com> (raw)
In-Reply-To: <20260520162058.573354582@linuxfoundation.org>

On 5/20/26 09:17, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.6.141 release.
> There are 508 patches in this series, all will be posted as a response
> to this one.  If anyone has any issues with these being applied, please
> let me know.
> 
> Responses should be made by Fri, 22 May 2026 16:20:16 +0000.
> Anything received after that time might be too late.
> 
> The whole patch series can be found in one patch at:
> 	https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.6.141-rc1.gz
> or in the git tree and branch at:
> 	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.6.y
> and the diffstat can be found below.
> 
> thanks,
> 
> greg k-h

perf fails to build with:

util/symbol-elf.c: In function 'dso__process_kernel_symbol':
util/symbol-elf.c:1379:7: warning: implicit declaration of function 
'dso__rel'; did you mean 'dso__get'? [-Wimplicit-function-declaration]
    if (dso__rel(dso))
        ^~~~~~~~
        dso__get

this is coming from this commit:

commit 8b4beba45e858aa793dd5d4d2e86d60c8c1915e6
Author: Chuck Lever <chuck.lever@oracle.com>
Date:   Mon Mar 23 11:58:04 2026 -0400

     perf tools: Fix module symbol resolution for non-zero .text sh_addr

     [ Upstream commit 9a82bfde4775b7a87cd1a7e791f46f83ae442848 ]

-- 
Florian

  parent reply	other threads:[~2026-05-20 20:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-20 16:17 Greg Kroah-Hartman
2026-05-20 19:11 ` Brett A C Sheffield
2026-05-20 20:33 ` Florian Fainelli [this message]
2026-05-21 12:55   ` Sasha Levin
2026-05-21  5:15 ` Francesco Dolcini
2026-05-21  5:22   ` Francesco Dolcini
2026-05-26 18:05     ` Leonardo Costa
2026-05-26 18:25       ` Krzysztof Wilczyński
2026-05-26 18:33         ` Krzysztof Wilczyński
2026-05-28 12:56           ` Leonardo Costa
2026-05-21  9:54 ` Pavel Machek
2026-05-21 10:36 ` Mark Brown
2026-05-21 21:57 ` Peter Schneider
2026-05-22  0:38 ` Ron Economos

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=fbe52f15-5b34-4e03-88e0-005ae6200a60@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=achill@achill.org \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=conor@kernel.org \
    --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

Powered by JetHome