From: Akhil Goyal <gakhil@marvell.com>
To: Patrick Robb <probb@iol.unh.edu>
Cc: "ci@dpdk.org" <ci@dpdk.org>, Manit Mahajan <mmahajan@iol.unh.edu>
Subject: RE: [EXTERNAL] next-crypto rebase on main?
Date: Thu, 28 Aug 2025 18:47:29 +0000 [thread overview]
Message-ID: <CO6PR18MB4484F444F31D07BD02AF049CD83BA@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <CAJvnSUCBBDBcrrm2izissMB-mYA7wG7JwVN=Lqw1NALSLQwTLA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 464 bytes --]
Hi Patrick,
Thanks for notifying. It is rebased now.
ZjQcmQRYFpfptBannerEnd
Hi Akhil,
Would it be simple and harmless for you to rebase next-crypto on main? I see it is a little out of date and on the community lab CI testing side we are seeing some weird behavior for patches which are applied to next-crypto. I think it's nothing though and will go away when your branch is moved forward.
If that's an issue in any way please say so.
-Patrick
[-- Attachment #2: Type: text/html, Size: 2791 bytes --]
prev parent reply other threads:[~2025-08-28 18:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 17:50 Patrick Robb
2025-08-28 18:47 ` Akhil Goyal [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=CO6PR18MB4484F444F31D07BD02AF049CD83BA@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=ci@dpdk.org \
--cc=mmahajan@iol.unh.edu \
--cc=probb@iol.unh.edu \
/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).