All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: dev@dpdk.org
Cc: David Marchand <david.marchand@6wind.com>,
	"Burakov, Anatoly" <anatoly.burakov@intel.com>
Subject: Re: [PATCH] doc: announce ivshmem support removal
Date: Thu, 28 Jul 2016 20:09:45 +0200	[thread overview]
Message-ID: <2297190.2Vac5vRVkd@xps13> (raw)
In-Reply-To: <CALwxeUtHaP3hkks41HqD9GuEKhym+WU2Pt+rWzpiwe_HMOfGiQ@mail.gmail.com>

> > There was a prior call with an explanation of what needs to be done:
> >         http://dpdk.org/ml/archives/dev/2016-June/040844.html
> > - Qemu patch upstreamed
> > - IVSHMEM PCI device managed by a PCI driver
> > - No DPDK objects (ring/mempool) allocated by EAL
> >
> > As nobody seems interested, it is time to remove this code which
> > makes EAL improvements harder.
> >
> > Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
> 
> Acked-by: David Marchand <david.marchand@6wind.com>
Acked-by: Maxime Coquelin <maxime.coquelin@redhat.com>
Acked-by: Jan Viktorin <viktorin@rehivetech.com>
Acked-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>

Applied

  reply	other threads:[~2016-07-28 18:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-20 16:35 [PATCH] doc: announce ivshmem support removal Thomas Monjalon
2016-07-22  0:36 ` Hiroshi Shimamoto
2016-07-22  7:52   ` Thomas Monjalon
2016-07-27  8:38 ` David Marchand
2016-07-28 18:09   ` Thomas Monjalon [this message]
2016-07-27 16:12 ` Maxime Coquelin
2016-07-27 19:08 ` Jan Viktorin
2016-07-28  9:20   ` Christian Ehrhardt
2016-07-28 15:23     ` Mauricio Vasquez
  -- strict thread matches above, loose matches on Subject: below --
2016-08-04  8:00 [PATCH] " 小川泰文
2016-08-04 17:18 ` 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=2297190.2Vac5vRVkd@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=anatoly.burakov@intel.com \
    --cc=david.marchand@6wind.com \
    --cc=dev@dpdk.org \
    /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.