All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Hall <mhall@mhcomputing.net>
To: "Mcnamara, John" <john.mcnamara@intel.com>
Cc: dev <dev@dpdk.org>,
	Christian Ehrhardt <christian.ehrhardt@canonical.com>,
	Markos Chandras <mchandras@suse.de>,
	Panu Matilainen <pmatilai@redhat.com>
Subject: Re: RFC: DPDK Long Term Support
Date: Fri, 3 Jun 2016 11:17:10 -0700	[thread overview]
Message-ID: <20160603181710.GA13454@mhcomputing.net> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE20257B8E3@IRSMSX103.ger.corp.intel.com>

On Fri, Jun 03, 2016 at 03:07:49PM +0000, Mcnamara, John wrote:
> What changes should be backported
> ---------------------------------
> 
> * Bug fixes that don't break the ABI.
> 
> 
> What changes should not be backported
> -------------------------------------
> 
> * API or ABI breaking changes.

I think this part needs some adjusting.

It seems like there should be allowance for bug fixes where the original does 
break ABI but it is possible to make a version that doesn't.

A lot of DPDK bug fixes I see would fall into this category and it isn't 
discussed.

Matthew.

  parent reply	other threads:[~2016-06-03 18:17 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-03 15:07 RFC: DPDK Long Term Support Mcnamara, John
2016-06-03 16:05 ` Thomas Monjalon
2016-06-06 11:49   ` Yuanhan Liu
2016-06-06 13:31     ` Thomas Monjalon
2016-06-06 14:14       ` Yuanhan Liu
2016-06-06 14:23         ` Thomas Monjalon
2016-06-07 13:17   ` Mcnamara, John
2016-06-03 18:17 ` Matthew Hall [this message]
2016-06-07 12:53   ` Mcnamara, John
2016-06-05 18:15 ` Neil Horman
2016-06-06  9:27   ` Thomas Monjalon
2016-06-06 13:47     ` Neil Horman
2016-06-06 14:21       ` Thomas Monjalon
2016-06-06 15:07         ` Neil Horman
2016-06-07 16:21       ` Mcnamara, John
2016-06-07 15:55   ` Mcnamara, John
2016-06-06 13:44 ` Nirmoy Das
2016-06-06 14:16   ` Yuanhan Liu
2016-06-07 12:36 ` Christian Ehrhardt
2016-06-07 19:39   ` Martinx - ジェームズ

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=20160603181710.GA13454@mhcomputing.net \
    --to=mhall@mhcomputing.net \
    --cc=christian.ehrhardt@canonical.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=mchandras@suse.de \
    --cc=pmatilai@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.