netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Saeed Mahameed <saeed@kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>,
	Paolo Abeni <pabeni@redhat.com>,
	Eric Dumazet <edumazet@google.com>,
	Saeed Mahameed <saeedm@nvidia.com>,
	netdev@vger.kernel.org, Tariq Toukan <tariqt@nvidia.com>,
	Gal Pressman <gal@nvidia.com>,
	Leon Romanovsky <leonro@nvidia.com>
Subject: Re: [pull request][net-next V2 00/15] mlx5 updates 2024-01-26
Date: Thu, 1 Feb 2024 21:02:39 -0800	[thread overview]
Message-ID: <20240201210239.0bf80713@kernel.org> (raw)
In-Reply-To: <20240201073158.22103-1-saeed@kernel.org>

On Wed, 31 Jan 2024 23:31:43 -0800 Saeed Mahameed wrote:
> v1->v2:
>  - Fix large stack buffer usage in patch #13

The warning is still there on 32b build:

drivers/net/ethernet/mellanox/mlx5/core/steering/dr_dbg.c:1044:1: warning: the frame size of 1052 bytes is larger than 1024 bytes [-Wframe-larger-than=]
 1044 | }
      | ^

Something gets inlined? Perhaps noinline_for_stack can fence it off?

      parent reply	other threads:[~2024-02-02  5:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-01  7:31 [pull request][net-next V2 00/15] mlx5 updates 2024-01-26 Saeed Mahameed
2024-02-01  7:31 ` [net-next V2 01/15] xfrm: generalize xdo_dev_state_update_curlft to allow statistics update Saeed Mahameed
2024-02-01  7:31 ` [net-next V2 02/15] xfrm: get global statistics from the offloaded device Saeed Mahameed
2024-02-01  7:31 ` [net-next V2 03/15] net/mlx5e: Connect mlx5 IPsec statistics with XFRM core Saeed Mahameed
2024-02-01  7:31 ` [net-next V2 04/15] net/mlx5e: Delete obsolete IPsec code Saeed Mahameed
2024-02-01  7:31 ` [net-next V2 05/15] Documentation: Fix counter name of mlx5 vnic reporter Saeed Mahameed
2024-02-01  7:31 ` [net-next V2 06/15] net/mlx5: Rename mlx5_sf_dev_remove Saeed Mahameed
2024-02-01  7:31 ` [net-next V2 07/15] net/mlx5: remove fw_fatal reporter dump option for non PF Saeed Mahameed
2024-02-01  7:31 ` [net-next V2 08/15] net/mlx5: remove fw " Saeed Mahameed
2024-02-01  7:31 ` [net-next V2 09/15] net/mlx5: SF, Stop waiting for FW as teardown was called Saeed Mahameed
2024-02-01  7:31 ` [net-next V2 10/15] net/mlx5: Return specific error code for timeout on wait_fw_init Saeed Mahameed
2024-02-01  7:31 ` [net-next V2 11/15] net/mlx5: Remove initial segmentation duplicate definitions Saeed Mahameed
2024-02-01  7:31 ` [net-next V2 12/15] net/mlx5: Change missing SyncE capability print to debug Saeed Mahameed
2024-02-01  7:31 ` [net-next V2 13/15] net/mlx5: DR, Change SWS usage to debug fs seq_file interface Saeed Mahameed
2024-02-01  7:31 ` [net-next V2 14/15] net/mlx5e: XSK, Exclude tailroom from non-linear SKBs memory calculations Saeed Mahameed
2024-02-01  7:31 ` [net-next V2 15/15] net/mlx5e: XDP, Exclude headroom and tailroom from " Saeed Mahameed
2024-02-02  5:02 ` Jakub Kicinski [this message]

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=20240201210239.0bf80713@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gal@nvidia.com \
    --cc=leonro@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=saeed@kernel.org \
    --cc=saeedm@nvidia.com \
    --cc=tariqt@nvidia.com \
    /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;
as well as URLs for NNTP newsgroup(s).