DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@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:31:45 +0000	[thread overview]
Message-ID: <30d23f16-4ed9-c960-9c8b-aa2a58c1103b@intel.com> (raw)
In-Reply-To: <AE5B2B5B-6075-428A-AED7-492E7C6E1833@pensando.io>

On 11/2/2020 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.

Hi Andrew,

If you recognized 'ionic' is marked as 'UNMAINTAINED' in the current tree.
I would like to see it to get proper updates and be back up to date.

> 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.

20.02 is no longer maintained.

xx.11 releases are long term stable releases and they are maintained for two years.
v18.11 is almost end of life, with the current release, v20.11, the v19.11 & 
v20.11 will be active LTS releases.

> 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?

As said above I am for getting updates, -rc2 is tomorrow so most probably it is 
already too late.
But I am OK to get 'ionic' specific patches for -rc3 too, this gives an 
additional week for this release, if it is enough for you.

But let me warn you, we are very close to the release, if something goes wrong 
with this last minute code, you many not have enough time to detect and fix it 
and driver may be released broken, which won't put you in a better situation.

If there are issues that you can fix and verify with confidence in this short 
time frame, lets try to squeeze them, but if the changes are big I suggest 
waiting the next release.

      parent reply	other threads:[~2020-11-02 16:31 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
2020-11-02 16:31 ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=30d23f16-4ed9-c960-9c8b-aa2a58c1103b@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=aboyer@pensando.io \
    --cc=dev@dpdk.org \


* 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).