All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: linux-stable <stable@vger.kernel.org>,
	Netdev <netdev@vger.kernel.org>,
	linux-rdma@vger.kernel.org, lkft-triage@lists.linaro.org,
	Sasha Levin <sashal@kernel.org>,
	Leon Romanovsky <leonro@nvidia.com>,
	Saeed Mahameed <saeedm@nvidia.com>,
	"David S. Miller" <davem@davemloft.net>,
	Dan Carpenter <dan.carpenter@linaro.org>,
	Arnd Bergmann <arnd@arndb.de>
Subject: Re: stable-rc: 6.1: mlx5: params.c:994:53: error: 'MLX5_IPSEC_CAP_CRYPTO' undeclared (first use in this function)
Date: Mon, 29 Jan 2024 08:28:03 -0800	[thread overview]
Message-ID: <2024012915-enlighten-dreadlock-54e9@gregkh> (raw)
In-Reply-To: <CA+G9fYvYQRnBbZhHknSKbwYiCr_3vPwC5zPz2NsV9_1F7=paQQ@mail.gmail.com>

On Mon, Jan 29, 2024 at 09:17:31PM +0530, Naresh Kamboju wrote:
> Following build errors noticed on stable-rc linux-6.1.y for arm64.
> 
> arm64:
> --------
>   * build/gcc-13-lkftconfig
>   * build/gcc-13-lkftconfig-kunit
>   * build/clang-nightly-lkftconfig
>   * build/clang-17-lkftconfig-no-kselftest-frag
>   * build/gcc-13-lkftconfig-devicetree
>   * build/clang-lkftconfig
>   * build/gcc-13-lkftconfig-perf
> 
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> 
> Build errors:
> ------
> drivers/net/ethernet/mellanox/mlx5/core/en/params.c: In function
> 'mlx5e_build_sq_param':
> 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);
>       |
> ^~~~~~~~~~~~~~~~~~~~~
> 
> Suspecting commit:
>   net/mlx5e: Allow software parsing when IPsec crypto is enabled
>   [ Upstream commit 20f5468a7988dedd94a57ba8acd65ebda6a59723 ]

Something looks very odd here, as the proper .h file is being included,
AND this isn't a build failure on x86, so why is this only arm64 having
problems?  What's causing this not to show up?

thanks,

greg k-h

  reply	other threads:[~2024-01-29 16:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-29 15:47 stable-rc: 6.1: mlx5: params.c:994:53: error: 'MLX5_IPSEC_CAP_CRYPTO' undeclared (first use in this function) Naresh Kamboju
2024-01-29 16:28 ` Greg Kroah-Hartman [this message]
2024-01-30  2:52   ` Naresh Kamboju
2024-01-30  4:25     ` Florian Fainelli
2024-01-30  7:14       ` Leon Romanovsky
2024-01-30 18:30         ` Greg Kroah-Hartman

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=2024012915-enlighten-dreadlock-54e9@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=arnd@arndb.de \
    --cc=dan.carpenter@linaro.org \
    --cc=davem@davemloft.net \
    --cc=leonro@nvidia.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=netdev@vger.kernel.org \
    --cc=saeedm@nvidia.com \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.