mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh@nvidia.com>
To: "Daniel Díaz" <daniel.diaz@linaro.org>,
	"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,
	f.fainelli@gmail.com, sudipm.mukherjee@gmail.com,
	srw@sladewatkins.net, rwarsow@gmx.de, conor@kernel.org,
	allen.lkml@gmail.com,
	SW-Mobile-Linux-Upstreaming
	<SW-Mobile-Linux-Upstreaming@exchange.nvidia.com>
Subject: Re: [PATCH 6.1 000/185] 6.1.76-rc1 review
Date: Tue, 30 Jan 2024 13:01:24 +0000	[thread overview]
Message-ID: <23a727d7-aba4-4c90-8052-4523a8a21e79@nvidia.com> (raw)
In-Reply-To: <4a2b55da-ee57-4fca-bb7b-240792b25460@linaro.org>


On 30/01/2024 01:31, Daniel Díaz wrote:
> Hello!
> 
> On 29/01/24 11:03 a. m., Greg Kroah-Hartman wrote:
>> This is the start of the stable review cycle for the 6.1.76 release.
>> There are 185 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 Wed, 31 Jan 2024 16:59:28 +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.1.76-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.1.y
>> and the diffstat can be found below.
>>
>> thanks,
>>
>> greg k-h
> 
> We see build regressions on Arm64, as reported by Naresh earlier, and 
> System/390:
> 
> -----8<-----
>    /builds/linux/drivers/net/ethernet/mellanox/mlx5/core/en/params.c: In 
> function 'mlx5e_build_sq_param':
>    
> /builds/linux/drivers/net/ethernet/mellanox/mlx5/core/en/params.c:994:53: error: 'MLX5_IPSEC_CAP_CRYPTO' undeclared (first use in this function)
>      994 |                     (mlx5_ipsec_device_caps(mdev) & 
> MLX5_IPSEC_CAP_CRYPTO);
>          |                                                     
> ^~~~~~~~~~~~~~~~~~~~~
>    
> /builds/linux/drivers/net/ethernet/mellanox/mlx5/core/en/params.c:994:53: note: each undeclared identifier is reported only once for each function it appears in
>    make[7]: *** [/builds/linux/scripts/Makefile.build:250: 
> drivers/net/ethernet/mellanox/mlx5/core/en/params.o] Error 1
> ----->8-----
> 
> Bisection points to:
> 
>    commit 1288b23c9c528796ab656d2796705f52c5ffad8a
>    Author: Leon Romanovsky <leonro@nvidia.com>
>    Date:   Tue Dec 12 13:52:55 2023 +0200
> 
>        net/mlx5e: Allow software parsing when IPsec crypto is enabled
>        [ Upstream commit 20f5468a7988dedd94a57ba8acd65ebda6a59723 ]
> 
> 
> Reverting that commit made the build pass again.
> 
> Reproducers:
> 
>    tuxmake --runtime podman --target-arch arm64 --toolchain gcc-13 
> --kconfig defconfig
>    tuxmake --runtime podman --target-arch s390  --toolchain gcc-13 
> --kconfig defconfig
> 
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>

FWIW, I am observing the same build issue.

Jon

-- 
nvpublic

  reply	other threads:[~2024-01-30 13:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-29 17:03 Greg Kroah-Hartman
2024-01-29 19:27 ` SeongJae Park
2024-01-29 23:16 ` Shuah Khan
2024-01-30  0:13 ` Allen
2024-01-30  1:31 ` Daniel Díaz
2024-01-30 13:01   ` Jon Hunter [this message]
2024-01-30 15:10   ` Pavel Machek
2024-01-30  3:49 ` Florian Fainelli
2024-01-30  9:52 ` Shreeya Patel
2024-01-30 20:15 ` Sven Joachim
2024-01-31  9:12 ` Yann Sionneau

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=23a727d7-aba4-4c90-8052-4523a8a21e79@nvidia.com \
    --to=jonathanh@nvidia.com \
    --cc=SW-Mobile-Linux-Upstreaming@exchange.nvidia.com \
    --cc=akpm@linux-foundation.org \
    --cc=allen.lkml@gmail.com \
    --cc=conor@kernel.org \
    --cc=daniel.diaz@linaro.org \
    --cc=f.fainelli@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --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®