From: Shuah Khan <skhan@linuxfoundation.org>
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@denx.de,
jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
conor@kernel.org, allen.lkml@gmail.com, broonie@kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH 6.6 000/538] 6.6.54-rc1 review
Date: Wed, 2 Oct 2024 18:07:20 -0600 [thread overview]
Message-ID: <a9f2e3c6-7e4e-4fbd-8a79-b3fc011412e2@linuxfoundation.org> (raw)
In-Reply-To: <e500ad8b-07d6-413e-8fc6-2a9afd5593de@linuxfoundation.org>
On 10/2/24 17:57, Shuah Khan wrote:
> On 10/2/24 06:53, Greg Kroah-Hartman wrote:
>> This is the start of the stable review cycle for the 6.6.54 release.
>> There are 538 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, 04 Oct 2024 12:56:13 +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.54-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
>>
>
> Compile failed on my system.
>
> libbpf.c: In function ‘bpf_object__create_map’:
> libbpf.c:5215:50: error: ‘BPF_F_VTYPE_BTF_OBJ_FD’ undeclared (first use in this function)
> 5215 | create_attr.map_flags |= BPF_F_VTYPE_BTF_OBJ_FD;
> | ^~~~~~~~~~~~~~~~~~~~~~
> libbpf.c:5215:50: note: each undeclared identifier is reported only once for each function it appears in
>
> I think this is the commit. I am going to drop this and see
> if it compiles.
>
>> Martin KaFai Lau <martin.lau@kernel.org>
>> libbpf: Ensure undefined bpf_attr field stays 0
>>
>
Sorry - not the above. Here is the one:
> Kui-Feng Lee <thinker.li@gmail.com>
> libbpf: Find correct module BTFs for struct_ops maps and progs.
Upstream commit:
9e926acda0c2e ("libbpf: Find correct module BTFs for struct_ops maps and
progs.)"
thanks,
-- Shuah
next prev parent reply other threads:[~2024-10-03 0:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 12:53 Greg Kroah-Hartman
2024-10-02 17:19 ` Florian Fainelli
2024-10-02 18:35 ` Jon Hunter
2024-10-02 23:57 ` Shuah Khan
2024-10-03 0:07 ` Shuah Khan [this message]
2024-10-03 6:52 ` Greg Kroah-Hartman
2024-10-03 4:58 ` Harshit Mogalapalli
2024-10-03 5:09 ` Naresh Kamboju
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=a9f2e3c6-7e4e-4fbd-8a79-b3fc011412e2@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--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@denx.de \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--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
all inboxes | Powered by JetHome®