From: Rahul Rameshbabu <rrameshbabu@nvidia.com>
To: "Asbjørn Sloth Tønnesen" <ast@fiberby.net>
Cc: Saeed Mahameed <saeedm@nvidia.com>,
Leon Romanovsky <leon@kernel.org>,
Yevgeny Kliteynik <kliteyn@nvidia.com>,
Muhammad Sammar <muhammads@nvidia.com>,
Alex Vesker <valex@nvidia.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net/mlx5: Fix reserved at offset in mlx5_ifc_fte_match_set_lyr_2_4_bits
Date: Thu, 02 Nov 2023 11:17:26 -0700 [thread overview]
Message-ID: <87o7gc58ax.fsf@nvidia.com> (raw)
In-Reply-To: <20231102175924.3456007-1-ast@fiberby.net> ("Asbjørn Sloth Tønnesen"'s message of "Thu, 2 Nov 2023 17:59:22 +0000")
On Thu, 02 Nov, 2023 17:59:22 +0000 Asbjørn Sloth Tønnesen <ast@fiberby.net> wrote:
> A member of struct mlx5_ifc_fte_match_set_lyr_2_4_bits has been mistakenly
> assigned the wrong reserved_at offset value. Correct it to align to the
> right value, thus avoid future miscalculation.
>
> Fixes: 5c422bfad2fb ("net/mlx5: DR, Add support for matching on Internet Header Length (IHL)")
> Signed-off-by: Asbjørn Sloth Tønnesen <ast@fiberby.net>
> ---
> include/linux/mlx5/mlx5_ifc.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/mlx5/mlx5_ifc.h b/include/linux/mlx5/mlx5_ifc.h
> index 4df6d1c12437..09c50e786ff4 100644
> --- a/include/linux/mlx5/mlx5_ifc.h
> +++ b/include/linux/mlx5/mlx5_ifc.h
> @@ -552,7 +552,7 @@ struct mlx5_ifc_fte_match_set_lyr_2_4_bits {
>
> u8 reserved_at_c0[0x10];
> u8 ipv4_ihl[0x4];
> - u8 reserved_at_c4[0x4];
> + u8 reserved_at_d4[0x4];
>
> u8 ttl_hoplimit[0x8];
In general, patches should target one of net or net-next on the netdev
mailing list as a heads up.
https://docs.kernel.org/process/maintainer-netdev.html#tl-dr
Reviewed-by: Rahul Rameshbabu <rrameshbabu@nvidia.com>
next prev parent reply other threads:[~2023-11-02 18:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 17:59 [PATCH] net/mlx5: Fix reserved at offset in mlx5_ifc_fte_match_set_lyr_2_4_bits Asbjørn Sloth Tønnesen
2023-11-02 18:17 ` Rahul Rameshbabu [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-02 18:14 Asbjørn Sloth Tønnesen
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=87o7gc58ax.fsf@nvidia.com \
--to=rrameshbabu@nvidia.com \
--cc=ast@fiberby.net \
--cc=kliteyn@nvidia.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=muhammads@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@nvidia.com \
--cc=valex@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 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.