DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Chao Zhu" <chaozhu@linux.vnet.ibm.com>
To: "'Thomas Monjalon'" <thomas@monjalon.net>,
	"'Christian Ehrhardt'" <christian.ehrhardt@canonical.com>,
	"'Gowrishankar Muthukrishnan'"
	<gowrishankar.m@linux.vnet.ibm.com>, <pradeep@us.ibm.com>,
	"'Alfredo Mendoza'" <mendoza1@us.ibm.com>,
	"'Gowrishankar Muthukrishnan'" <gowrishankar.m@in.ibm.com>,
	"'Gowrishankar Muthukrishnan'"
	<gowrishankar.m@linux.vnet.ibm.com>,
	"'Kevin Reilly'" <kjreilly@us.ibm.com>
Cc: <dev@dpdk.org>, <adrien.mazarguil@6wind.com>,
	"'Luca Boccassi'" <bluca@debian.org>
Subject: Re: [dpdk-dev] 18.08 build error on ppc64el - bool as vector type
Date: Fri, 31 Aug 2018 11:44:03 +0800	[thread overview]
Message-ID: <002401d440dc$df7cae20$9e760a60$@linux.vnet.ibm.com> (raw)
In-Reply-To: <3195236.p3PdHVbfnl@xps>

Thomas,

Sorry for the late reply. DPDK will definitely be supported by IBM. I think
Pradeep and the team is working on this. Personally, I don't have enough
bandwidth to do this, we'll have a discussion internally to decide who will
take over the maintenance.

Thank you!

> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas@monjalon.net]
> Sent: 2018年8月30日 16:37
> To: Christian Ehrhardt <christian.ehrhardt@canonical.com>; Gowrishankar
> Muthukrishnan <gowrishankar.m@linux.vnet.ibm.com>; Chao Zhu
> <chaozhu@linux.vnet.ibm.com>; pradeep@us.ibm.com; Alfredo Mendoza
> <mendoza1@us.ibm.com>; Gowrishankar Muthukrishnan
> <gowrishankar.m@in.ibm.com>; Gowrishankar Muthukrishnan
> <gowrishankar.m@linux.vnet.ibm.com>; Kevin Reilly <kjreilly@us.ibm.com>
> Cc: dev@dpdk.org; adrien.mazarguil@6wind.com; Luca Boccassi
> <bluca@debian.org>
> Subject: Re: [dpdk-dev] 18.08 build error on ppc64el - bool as vector type
> 
> 29/08/2018 16:37, Christian Ehrhardt:
> > Why is no-one of IBM/Power world replying at all?
> > There not even was a "oh yeah, <whatever the content would be>" mail
> > by them.
> > Is in fact ppc64 support in DPDK dead or at least "unmaintained"?
> > This is something that mid term has to be sorted out - I tried to pull
> > some strings to get attention "there" but so far I'm waiting for a
reply.
> > I'd say 18.11 should not be released with a clear re-confirmation of
> > ppc64 maintainance ppc64 by "someone".
> 
> I tend to agree.
> 
> Let's try again:
> 
> Chao, are you still available for DPDK PPC maintenance?
> 
> SHOULD WE DECLARE DPDK NOT SUPPORTED ON PPC64?
> 

  parent reply	other threads:[~2018-08-31  3:44 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-21 14:19 Christian Ehrhardt
2018-08-22 15:11 ` Christian Ehrhardt
2018-08-27 12:22   ` Adrien Mazarguil
2018-08-28 11:30     ` Christian Ehrhardt
2018-08-28 11:44       ` Adrien Mazarguil
2018-08-28 12:38         ` Christian Ehrhardt
2018-08-28 15:02           ` Adrien Mazarguil
2018-08-29  8:27             ` Christian Ehrhardt
2018-08-29 13:16               ` Adrien Mazarguil
2018-08-29 14:37                 ` Christian Ehrhardt
2018-08-30  8:36                   ` Thomas Monjalon
2018-08-30 11:22                     ` Alfredo Mendoza
2018-08-31  3:44                     ` Chao Zhu [this message]
2018-09-27 14:11                       ` Christian Ehrhardt
2018-08-30  9:48                   ` Christian Ehrhardt
2018-08-30 10:00                     ` [dpdk-dev] [PATCH] ppc64: fix compilation of when AltiVec is enabled Christian Ehrhardt
2018-08-30 10:52                     ` Takeshi T Yoshimura
2018-08-30 11:58                       ` Christian Ehrhardt
2018-11-05 14:15                         ` Thomas Monjalon
2018-11-05 21:20                           ` Pradeep Satyanarayana
2018-11-07 10:03                             ` Thomas Monjalon
2018-11-07 18:58                               ` dwilder
2018-11-07 21:21                                 ` Thomas Monjalon
2018-11-07 23:53                                   ` Pradeep Satyanarayana

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='002401d440dc$df7cae20$9e760a60$@linux.vnet.ibm.com' \
    --to=chaozhu@linux.vnet.ibm.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=bluca@debian.org \
    --cc=christian.ehrhardt@canonical.com \
    --cc=dev@dpdk.org \
    --cc=gowrishankar.m@in.ibm.com \
    --cc=gowrishankar.m@linux.vnet.ibm.com \
    --cc=kjreilly@us.ibm.com \
    --cc=mendoza1@us.ibm.com \
    --cc=pradeep@us.ibm.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).