From: Sasha Levin <sashal@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, 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
Subject: Re: [PATCH 5.10 000/134] 5.10.168-rc2 review
Date: Tue, 14 Feb 2023 14:19:20 -0500 [thread overview]
Message-ID: <Y+veuKPmuGpXjnDS@sashalap> (raw)
In-Reply-To: <8c06157f-a482-a7f7-8218-863db3dfe268@roeck-us.net>
On Tue, Feb 14, 2023 at 10:07:45AM -0800, Guenter Roeck wrote:
>On 2/14/23 09:41, Greg Kroah-Hartman wrote:
>>This is the start of the stable review cycle for the 5.10.168 release.
>>There are 134 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 Thu, 16 Feb 2023 17:25:19 +0000.
>>Anything received after that time might be too late.
>>
>
>Still observed for ppc:ppc32_allmodconfig:
>
>In file included from arch/powerpc/net/bpf_jit_comp.c:16:
>arch/powerpc/net/bpf_jit32.h:131:8: error: redefinition of 'struct codegen_context'
> 131 | struct codegen_context {
> | ^~~~~~~~~~~~~~~
>In file included from arch/powerpc/net/bpf_jit32.h:13,
> from arch/powerpc/net/bpf_jit_comp.c:16:
>arch/powerpc/net/bpf_jit.h:124:8: note: originally defined here
> 124 | struct codegen_context {
> | ^~~~~~~~~~~~~~~
>arch/powerpc/net/bpf_jit_comp.c:18:20: error: redefinition of 'bpf_flush_icache'
> 18 | static inline void bpf_flush_icache(void *start, void *end)
> | ^~~~~~~~~~~~~~~~
>In file included from arch/powerpc/net/bpf_jit32.h:13,
> from arch/powerpc/net/bpf_jit_comp.c:16:
>arch/powerpc/net/bpf_jit.h:139:20: note: previous definition of 'bpf_flush_icache' with type 'void(void *, void *)'
> 139 | static inline void bpf_flush_icache(void *start, void *end)
> | ^~~~~~~~~~~~~~~~
Yes, sorry, I've dropped two broken patches.
--
Thanks,
Sasha
next prev parent reply other threads:[~2023-02-14 19:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 17:41 [PATCH 5.10 000/134] 5.10.168-rc2 review Greg Kroah-Hartman
2023-02-14 18:07 ` Guenter Roeck
2023-02-14 19:19 ` Sasha Levin [this message]
2023-02-14 19:00 ` Jon Hunter
2023-02-15 4:17 ` Guenter Roeck
2023-02-15 9:31 ` Naresh Kamboju
2023-02-15 10:01 ` Sudip Mukherjee (Codethink)
2023-02-15 16:56 ` Pavel Machek
2023-02-15 19:03 ` Allen Pais
2023-02-15 20:28 ` Florian Fainelli
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=Y+veuKPmuGpXjnDS@sashalap \
--to=sashal@kernel.org \
--cc=akpm@linux-foundation.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