All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: John McNamara <john.mcnamara@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v1] doc: add template release notes for 17.11
Date: Tue, 08 Aug 2017 15:50:05 +0200	[thread overview]
Message-ID: <1826242.fXvBPhMe3n@xps> (raw)
In-Reply-To: <1502195467-24712-1-git-send-email-john.mcnamara@intel.com>

Hi,

Thanks for sending the next release notes so quickly.
Unfortunately...

08/08/2017 14:31, John McNamara:
> +The libraries prepended with a plus sign were incremented in this version.
> +
> +.. code-block:: diff
> +
> +     librte_acl.so.2
> +     librte_bitratestats.so.1
> +     librte_cfgfile.so.2
> +     librte_cmdline.so.2
> +     librte_cryptodev.so.3
> +     librte_distributor.so.1
> +     librte_eal.so.4
> +     librte_ethdev.so.7
> +     librte_gro.so.1
> +     librte_hash.so.2
> +     librte_ip_frag.so.1
> +     librte_jobstats.so.1
> +     librte_kni.so.2
> +     librte_kvargs.so.1
> +     librte_latencystats.so.1
> +     librte_lpm.so.2
> +     librte_mbuf.so.3
> +     librte_mempool.so.2
> +     librte_meter.so.1
> +     librte_metrics.so.1
> +     librte_net.so.1
> +     librte_pdump.so.1
> +     librte_pipeline.so.3
> +     librte_pmd_bond.so.1
> +     librte_pmd_ring.so.2
> +     librte_port.so.3
> +     librte_power.so.1
> +     librte_reorder.so.1
> +     librte_ring.so.1
> +     librte_sched.so.1
> +     librte_table.so.2
> +     librte_timer.so.1
> +     librte_vhost.so.3

... we are going to bump some ABIVER which were forgotten during 17.08.
You will probably need to update after 17.08 release.

  reply	other threads:[~2017-08-08 13:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-08 12:31 [PATCH v1] doc: add template release notes for 17.11 John McNamara
2017-08-08 13:50 ` Thomas Monjalon [this message]
2017-08-08 15:29   ` Mcnamara, John
2017-08-09  8:22 ` [PATCH v2] " John McNamara
2017-08-10  8:11   ` Thomas Monjalon

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=1826242.fXvBPhMe3n@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.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.