All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Hall <mhall@mhcomputing.net>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: difficulty w/ RTE_NEXT_ABI
Date: Sun, 22 Nov 2015 22:53:13 -0500	[thread overview]
Message-ID: <20151123035313.GA31612@mhcomputing.net> (raw)
In-Reply-To: <1629381.JoeoXysOOK@xps13>

On Mon, Nov 23, 2015 at 01:13:32AM +0100, Thomas Monjalon wrote:
> If your change is sent upstream, you must rely on the new ABI because the old one
> will be removed when your change will be integrated.
> If it is a local change, it depends on which ABI you want to use.

I submitted separately to Bruce & Co. It is for LPM field expansion.

My question what to do came up in the context of a rebase to master.

> Yes. Hope my detailed answer is enough.

Thanks. It is less confusing now.

Matthew.

      reply	other threads:[~2015-11-23  3:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-21  8:49 difficulty w/ RTE_NEXT_ABI Matthew Hall
2015-11-21 10:44 ` Thomas Monjalon
2015-11-22  0:25   ` Matthew Hall
2015-11-22 20:59     ` Thomas Monjalon
2015-11-22 23:25       ` Matthew Hall
2015-11-23  0:13         ` Thomas Monjalon
2015-11-23  3:53           ` Matthew Hall [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=20151123035313.GA31612@mhcomputing.net \
    --to=mhall@mhcomputing.net \
    --cc=dev@dpdk.org \
    --cc=thomas.monjalon@6wind.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.