DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Rafał Kozik" <rk@semihalf.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org, "Marcin Wojtas" <mw@semihalf.com>,
	"Michał Krawczyk" <mk@semihalf.com>,
	"Tzalik, Guy" <gtzalik@amazon.com>,
	"Schmeilin, Evgeny" <evgenys@amazon.com>,
	"Matushevsky, Alexander" <matua@amazon.com>,
	"Chauskin, Igor" <igorch@amazon.com>,
	"Ferruh Yigit" <ferruh.yigit@intel.com>,
	thomas@monjalon.net
Subject: Re: [dpdk-dev] [PATCH 0/4] support for write combining
Date: Tue, 26 Jun 2018 09:27:20 +0200	[thread overview]
Message-ID: <CAMG3L4-VqCf8pgmgz_uY3VnE8d6WY9yZ6s3VgipZqHgOTrHyBg@mail.gmail.com> (raw)
In-Reply-To: <CAMG3L49TwxaWqXX1B=kG5AaPrn=gUAe+aWLOc-V3r+sPz0RP4A@mail.gmail.com>

Hello Thomas,

I would like to kindly remind about question about support for write
combining patch set:
https://mails.dpdk.org/archives/dev/2018-April/096749.html

It got ack from Bruce Richardson,
what is the next step to commit them to DPDK source?

Best regards,
Rafal Kozik


2018-06-11 11:32 GMT+02:00 Rafał Kozik <rk@semihalf.com>:
> Hello Thomas,
>
> I have a question about support for write combining patch set.
> It got ack from Bruce Richardson more then month ago.
> Also no one has any further comments about it.
> What is the next step to commit them to DPDK source?
>
> Best regards,
> Rafal Kozik

  reply	other threads:[~2018-06-26  7:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-11  9:32 Rafał Kozik
2018-06-26  7:27 ` Rafał Kozik [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-04-11 14:07 Rafal Kozik
2018-04-11 14:42 ` Bruce Richardson
2018-04-16 11:36   ` Rafał Kozik
2018-04-27  8:27     ` Rafał Kozik
2018-04-27 11:30       ` Bruce Richardson
2018-04-30  8:07         ` Rafał Kozik
2018-04-30  8:58           ` Bruce Richardson

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=CAMG3L4-VqCf8pgmgz_uY3VnE8d6WY9yZ6s3VgipZqHgOTrHyBg@mail.gmail.com \
    --to=rk@semihalf.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=evgenys@amazon.com \
    --cc=ferruh.yigit@intel.com \
    --cc=gtzalik@amazon.com \
    --cc=igorch@amazon.com \
    --cc=matua@amazon.com \
    --cc=mk@semihalf.com \
    --cc=mw@semihalf.com \
    --cc=thomas@monjalon.net \
    /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).