From: Jakub Kicinski <kuba@kernel.org>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH ipsec-next 6/8] netdevsim: rely on XFRM state direction instead of flags
Date: Thu, 5 May 2022 09:53:07 -0700 [thread overview]
Message-ID: <20220505095307.488c093b@kernel.org> (raw)
In-Reply-To: <54be8183fb49a5486a8137627c204f00595e21af.1651743750.git.leonro@nvidia.com>
On Thu, 5 May 2022 13:06:43 +0300 Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
>
> Make sure that netdevsim relies on direction and not on flags.
>
> Reviewed-by: Raed Salem <raeds@nvidia.com>
> Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
Acked-by: Jakub Kicinski <kuba@kernel.org>
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Leon Romanovsky <leon@kernel.org>
Cc: Steffen Klassert <steffen.klassert@secunet.com>,
Leon Romanovsky <leonro@nvidia.com>,
"David S . Miller" <davem@davemloft.net>,
David Ahern <dsahern@kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
intel-wired-lan@lists.osuosl.org,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
netdev@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>,
Raed Salem <raeds@nvidia.com>, Saeed Mahameed <saeedm@nvidia.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>
Subject: Re: [PATCH ipsec-next 6/8] netdevsim: rely on XFRM state direction instead of flags
Date: Thu, 5 May 2022 09:53:07 -0700 [thread overview]
Message-ID: <20220505095307.488c093b@kernel.org> (raw)
In-Reply-To: <54be8183fb49a5486a8137627c204f00595e21af.1651743750.git.leonro@nvidia.com>
On Thu, 5 May 2022 13:06:43 +0300 Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
>
> Make sure that netdevsim relies on direction and not on flags.
>
> Reviewed-by: Raed Salem <raeds@nvidia.com>
> Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
Acked-by: Jakub Kicinski <kuba@kernel.org>
next prev parent reply other threads:[~2022-05-05 16:53 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 10:06 [Intel-wired-lan] [PATCH ipsec-next 0/8] Be explicit with XFRM offload direction Leon Romanovsky
2022-05-05 10:06 ` Leon Romanovsky
2022-05-05 10:06 ` [Intel-wired-lan] [PATCH ipsec-next 1/8] xfrm: free not used XFRM_ESP_NO_TRAILER flag Leon Romanovsky
2022-05-05 10:06 ` Leon Romanovsky
2022-05-05 11:02 ` [Intel-wired-lan] " David Miller
2022-05-05 11:02 ` David Miller
2022-05-05 10:06 ` [Intel-wired-lan] [PATCH ipsec-next 2/8] xfrm: delete not used number of external headers Leon Romanovsky
2022-05-05 10:06 ` Leon Romanovsky
2022-05-05 11:03 ` [Intel-wired-lan] " David Miller
2022-05-05 11:03 ` David Miller
2022-05-05 10:06 ` [Intel-wired-lan] [PATCH ipsec-next 3/8] xfrm: rename xfrm_state_offload struct to allow reuse Leon Romanovsky
2022-05-05 10:06 ` Leon Romanovsky
2022-05-05 11:03 ` [Intel-wired-lan] " David Miller
2022-05-05 11:03 ` David Miller
2022-05-05 10:06 ` [Intel-wired-lan] [PATCH ipsec-next 4/8] xfrm: store and rely on direction to construct offload flags Leon Romanovsky
2022-05-05 10:06 ` Leon Romanovsky
2022-05-05 10:06 ` [Intel-wired-lan] [PATCH ipsec-next 5/8] ixgbe: propagate XFRM offload state direction instead of flags Leon Romanovsky
2022-05-05 10:06 ` Leon Romanovsky
2022-05-05 10:06 ` [Intel-wired-lan] [PATCH ipsec-next 6/8] netdevsim: rely on XFRM " Leon Romanovsky
2022-05-05 10:06 ` Leon Romanovsky
2022-05-05 16:53 ` Jakub Kicinski [this message]
2022-05-05 16:53 ` Jakub Kicinski
2022-05-05 10:06 ` [Intel-wired-lan] [PATCH ipsec-next 7/8] net/mlx5e: Use " Leon Romanovsky
2022-05-05 10:06 ` Leon Romanovsky
2022-05-05 10:06 ` [Intel-wired-lan] [PATCH ipsec-next 8/8] xfrm: drop not needed flags variable in XFRM offload struct Leon Romanovsky
2022-05-05 10:06 ` Leon Romanovsky
2022-05-07 7:28 ` [Intel-wired-lan] [PATCH ipsec-next 0/8] Be explicit with XFRM offload direction Steffen Klassert
2022-05-07 7:28 ` Steffen Klassert
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=20220505095307.488c093b@kernel.org \
--to=kuba@kernel.org \
--cc=intel-wired-lan@osuosl.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.