From: David Marchand <david.marchand@redhat.com>
To: "Zhang, XuemingX" <xuemingx.zhang@intel.com>
Cc: "viacheslavo@mellanox.com" <viacheslavo@mellanox.com>,
"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"jackmin@mellanox.com" <jackmin@mellanox.com>,
"huwei013@chinasoftinc.com" <huwei013@chinasoftinc.com>,
"dekelp@mellanox.com" <dekelp@mellanox.com>,
"Iremonger, Bernard" <bernard.iremonger@intel.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
"Xu, Qian Q" <qian.q.xu@intel.com>,
"Mcnamara, John" <john.mcnamara@intel.com>,
"Yu, PingX" <pingx.yu@intel.com>,
Ali Alnubani <alialnu@mellanox.com>,
Thomas Monjalon <thomas@monjalon.net>,
"Chen, Zhaoyan" <zhaoyan.chen@intel.com>,
"ci@dpdk.org" <ci@dpdk.org>
Subject: Re: [dpdk-ci] Master compilation failures in Intel CI
Date: Mon, 20 Jan 2020 15:49:22 +0100 [thread overview]
Message-ID: <CAJFAV8zBsKxMSFQR+s_Dn5QyD9N-w89ydm172rKh7FV5zjKHoA@mail.gmail.com> (raw)
In-Reply-To: <ededa3cb01bd4da0947c60f22b0ba894@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2403 bytes --]
On Fri, Jan 17, 2020 at 7:06 AM Zhang, XuemingX <xuemingx.zhang@intel.com>
wrote:
> >Can you give me a list of patchsets you think are problematic so
>
> >that I can test them?
>
>
>
> Filter some recent patch sets and list problematic patchsets.
>
>
>
> In the table below, which branch does it make more sense to apply the
> patchsets? Old_guess_tree or new_guess_tree or next-**?
>
> Please fill in the form guess_tree column.
>
Please, don't use html for a simple list.
>
> serite_id
>
> old_guess_tree
>
> new_guess_tree
>
> serite_url
>
> Author
>
> guess_tree
>
> 8174
>
> dpdk-next-net-mlx
>
> dpdk
>
> *http://patchwork.dpdk.org/api/series/8174
> <http://patchwork.dpdk.org/api/series/8174>*
>
> Viacheslav Ovsiienko
>
>
>
> 8158
>
> dpdk-next-crypto
>
> dpdk
>
> *http://patchwork.dpdk.org/api/series/8158
> <http://patchwork.dpdk.org/api/series/8158>*
>
> Pablo de Lara
>
>
>
> 8154
>
> dpdk-next-net
>
> dpdk
>
> *http://patchwork.dpdk.org/api/series/8154
> <http://patchwork.dpdk.org/api/series/8154>*
>
> Xiaoyu Min
>
>
>
> 8153
>
> dpdk-next-net
>
> dpdk
>
> *http://patchwork.dpdk.org/api/series/8153
> <http://patchwork.dpdk.org/api/series/8153>*
>
> Wei Hu (Xavier)
>
>
>
> 8177
>
> dpdk-next-net-mlx
>
> dpdk
>
> *http://patchwork.dpdk.org/api/series/8177
> <http://patchwork.dpdk.org/api/series/8177>*
>
> Dekel Peled
>
>
>
> 8162
>
> dpdk-next-net
>
> dpdk
>
> *http://patchwork.dpdk.org/api/series/8162
> <http://patchwork.dpdk.org/api/series/8162>*
>
> Bernard Iremonger
>
>
>
> 8169
>
> dpdk-next-net-intel
>
> dpdk
>
> *http://patchwork.dpdk.org/api/series/8169
> <http://patchwork.dpdk.org/api/series/8169>*
>
> Bernard Iremonger
>
>
>
>
>
I am ok with reverting the change on the script, but, once done some fixes
are needed in MAINTAINERS:
- 8174 should go to the main repository, since there are mbuf changes, but
mbuf is not marked to go to the main repository, to be fixed,
- 8158 touches a devtools/ script, but I suppose Thomsa and I will see this
kind of change, we can leave it in MAINTAINERS as it is,
- 8154 is ok as it is,
- 8153 is ok as it is,
- 8177 is ok too,
- 8162 and others from Bernard are not a proper series, must be resent as a
series, but I can see Ferruh already took it,
--
David Marchand
>
[-- Attachment #2: Type: text/html, Size: 18343 bytes --]
prev parent reply other threads:[~2020-01-20 14:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJFAV8wbWkMbSHgOY4aBW-v1s6jhczaH2Jyf9cxNAywG0RmTsg@mail.gmail.com>
[not found] ` <CAJFAV8xL7kdAmeyTCXaFGnyJgEApsAuGdHMtgamZqkyo1q4Y9Q@mail.gmail.com>
[not found] ` <9DEEADBC57E43F4DA73B571777FECECA41E9E23A@SHSMSX104.ccr.corp.intel.com>
2020-01-14 8:04 ` Thomas Monjalon
2020-01-14 9:51 ` David Marchand
2020-01-14 10:33 ` Thomas Monjalon
2020-01-14 10:37 ` David Marchand
2020-01-17 6:06 ` Zhang, XuemingX
2020-01-19 8:01 ` Dekel Peled
2020-01-20 14:49 ` David Marchand [this message]
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=CAJFAV8zBsKxMSFQR+s_Dn5QyD9N-w89ydm172rKh7FV5zjKHoA@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=alialnu@mellanox.com \
--cc=bernard.iremonger@intel.com \
--cc=bruce.richardson@intel.com \
--cc=ci@dpdk.org \
--cc=dekelp@mellanox.com \
--cc=ferruh.yigit@intel.com \
--cc=huwei013@chinasoftinc.com \
--cc=jackmin@mellanox.com \
--cc=john.mcnamara@intel.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=pingx.yu@intel.com \
--cc=qian.q.xu@intel.com \
--cc=thomas@monjalon.net \
--cc=viacheslavo@mellanox.com \
--cc=xuemingx.zhang@intel.com \
--cc=zhaoyan.chen@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 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).