From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Andrew Boyer <aboyer@pensando.io>, dev@dpdk.org
Subject: Re: [dpdk-dev] Ionic PMD - can we still get patches into a 20.02 stable?
Date: Mon, 2 Nov 2020 16:25:42 +0000 [thread overview]
Message-ID: <339701f0-cc59-7a66-23fc-b975478f8958@intel.com> (raw)
In-Reply-To: <AE5B2B5B-6075-428A-AED7-492E7C6E1833@pensando.io>
On 02-Nov-20 4:17 PM, Andrew Boyer wrote:
> Hello DPDK folks,
> I am ready to start submitting some patches to bring the Pensando ionic PMD up to speed. The first batch will be a practice run of some minor things, if that’s acceptable.
>
> It appears that the 20.02 release is no longer being maintained. Is that correct? Is it possible for us to get patches into a new stable release of 20.02? They would only affect our PMD and not affect the ABI or anything.
>
> It looks like I have just about missed the boat on 20.11 - would you prefer patches this week or should I hold them until December?
>
> Thank you,
> Andrew
> Pensando
>
20.02 is not an LTS so there won't be any more releases.
You can send the patches any time, but at this stage they won't be
pulled in to 20.11. You may help maintainers by creating an account at
patchwork [1] and marking your patches as "Deferred" once you send them.
They will be marked as "New" once the development of the new release
commences.
[1] https://patchwork.dpdk.org
--
Thanks,
Anatoly
next prev parent reply other threads:[~2020-11-02 16:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 16:17 Andrew Boyer
2020-11-02 16:25 ` Burakov, Anatoly [this message]
2020-11-02 16:31 ` Ferruh Yigit
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=339701f0-cc59-7a66-23fc-b975478f8958@intel.com \
--to=anatoly.burakov@intel.com \
--cc=aboyer@pensando.io \
--cc=dev@dpdk.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 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).