DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jan Viktorin <viktorin@rehivetech.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org, Matej Vido <matejvido@gmail.com>
Subject: Re: [dpdk-dev] [PATCH] doc: announce ABI change for link speed
Date: Tue, 15 Dec 2015 12:16:23 +0100	[thread overview]
Message-ID: <20151215121623.21c7ed47@jvn> (raw)
In-Reply-To: <1450164074-16090-1-git-send-email-thomas.monjalon@6wind.com>

On Tue, 15 Dec 2015 08:21:14 +0100
Thomas Monjalon <thomas.monjalon@6wind.com> wrote:

> A rework was prepared by Marc Sune:
> http://dpdk.org/ml/archives/dev/2015-October/026037.html
> The goal is to retrieve the supported link speed of a device
> and to allow 100G devices while having a consistent API.
> 
> Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>

Acked-by: Jan Viktorin <viktorin@rehivetech.com>

  parent reply	other threads:[~2015-12-15 11:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-15  7:21 Thomas Monjalon
2015-12-15  9:22 ` Olga Shern
2015-12-15 10:54 ` Adrien Mazarguil
2015-12-15 11:16 ` Jan Viktorin [this message]
2015-12-15 11:59 ` Matej Vido
2015-12-15 12:52   ` 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=20151215121623.21c7ed47@jvn \
    --to=viktorin@rehivetech.com \
    --cc=dev@dpdk.org \
    --cc=matejvido@gmail.com \
    --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 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).