From: Ferruh Yigit <ferruh.yigit@amd.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Qi Z Zhang <qi.z.zhang@intel.com>, Ori Kam <orika@nvidia.com>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
"david.marchand@redhat.com" <david.marchand@redhat.com>
Subject: Re: DPDK Release Status Meeting 2023-10-05
Date: Mon, 9 Oct 2023 14:17:27 +0100 [thread overview]
Message-ID: <2a406e74-ec75-4cb8-9718-a7de6d2230fc@amd.com> (raw)
In-Reply-To: <PH8PR11MB680488B0A20E543AC1C31D12FCCAA@PH8PR11MB6804.namprd11.prod.outlook.com>
On 10/5/2023 10:04 AM, Mcnamara, John wrote:
> Release status meeting minutes 2023-10-05
> =========================================
>
> Agenda:
> * Release Dates
> * Subtrees
> * Roadmaps
> * LTS
> * Defects
> * Opens
>
> Participants:
> * AMD
> * Intel
> * Marvell
> * Nvidia
> * Red Hat
>
> Release Dates
> -------------
>
> The following are the current working dates for 23.11:
>
> * V1: 12 August 2023
> * RC1: 11 October 2023
> * RC2: 27 October 2023
> * RC3: 3 November 2023
> * Release: 15 November 2023
>
>
> Subtrees
> --------
>
> * next-net
> * Initial pull done.
> * Working on the rest of the tree.
> * There are still a number of rte_flow patches pending merge but not having reviews
>
I created two public bundles for rte flow patches waiting for review,
1) rte_flow patches:
https://patchwork.dpdk.org/bundle/fyigit/rte_flow_v23.11/
2) rte_flow related testpmd patches:
https://patchwork.dpdk.org/bundle/fyigit/rte_flow_testpmd_v23.11/
Can you please help/support reviewing these patches?
Thanks in advance,
ferruh
prev parent reply other threads:[~2023-10-09 13:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 9:04 Mcnamara, John
2023-10-09 13:17 ` Ferruh Yigit [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=2a406e74-ec75-4cb8-9718-a7de6d2230fc@amd.com \
--to=ferruh.yigit@amd.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=john.mcnamara@intel.com \
--cc=orika@nvidia.com \
--cc=qi.z.zhang@intel.com \
--cc=thomas@monjalon.net \
/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).