From: Steffen Klassert <steffen.klassert@secunet.com>
To: Chiachang Wang <chiachangwang@google.com>
Cc: Leon Romanovsky <leonro@nvidia.com>, <netdev@vger.kernel.org>,
<stanleyjhu@google.com>, <yumike@google.comy>
Subject: Re: [PATCH ipsec v3 1/1] xfrm: Migrate offload configuration
Date: Fri, 7 Mar 2025 06:50:49 +0100 [thread overview]
Message-ID: <Z8qJOVuMr+GamxUO@gauss3.secunet.de> (raw)
In-Reply-To: <CAOb+sWEdZ-kY6-qnG2u0h_JzeVyrf0b_eT+L=2t-5zCGaXedHA@mail.gmail.com>
On Fri, Mar 07, 2025 at 01:42:25PM +0800, Chiachang Wang wrote:
> Hi Leon,
>
> Thank you for your review and suggestions. I noticed your patches
> haven't been merged into the tree yet. I'm unsure if rebasing my patch
> onto yours would work correctly with the kernel upstream. It seems
> your patches are suitable for merging. Since I'm not familiar with the
> timeline for your patch's inclusion, could you please advise on how
> long it might take for them to be in the tree? This would help me
> rebase my patch properly. or there are any other alternative way
> rather than waiting your patch?
Rebase your patch on top of the ipsec-next tree. This is the target tree
for xfrm changes that will go to -next. Leons patchset is already merged
into this tree.
Thanks!
prev parent reply other threads:[~2025-03-07 5:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 6:15 [PATCH ipsec v3 0/1] Update offload configuration with SA Chiachang Wang
2025-02-24 6:15 ` [PATCH ipsec v3 1/1] xfrm: Migrate offload configuration Chiachang Wang
2025-02-24 12:49 ` Leon Romanovsky
2025-03-07 5:42 ` Chiachang Wang
2025-03-07 5:50 ` Steffen Klassert [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=Z8qJOVuMr+GamxUO@gauss3.secunet.de \
--to=steffen.klassert@secunet.com \
--cc=chiachangwang@google.com \
--cc=leonro@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=stanleyjhu@google.com \
--cc=yumike@google.comy \
/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