From: "Zhang, XuemingX" <xuemingx.zhang@intel.com>
To: "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>
Cc: "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>,
David Marchand <david.marchand@redhat.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: Fri, 17 Jan 2020 06:06:47 +0000 [thread overview]
Message-ID: <ededa3cb01bd4da0947c60f22b0ba894@intel.com> (raw)
In-Reply-To: <CAJFAV8yq7YmJBVVsDSB4HeieFwr4LyiVyjoWEGDs=UBiEWpfBA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2325 bytes --]
++ Viacheslav Ovsiienko && Pablo de Lara && Xiaoyu && Wei Hu && Dekel Peled && Bernard Iremonger
On Tue, Jan 14, 2020 at 11:33 AM Thomas Monjalon <thomas@monjalon.net<mailto:thomas@monjalon.net>> wrote:
>
> 14/01/2020 10:51, David Marchand:
> > On Tue, Jan 14, 2020 at 9:04 AM Thomas Monjalon <thomas@monjalon.net<mailto:thomas@monjalon.net>> wrote:
> > > 14/01/2020 08:18, Chen, Zhaoyan:
> > > > - one patchset includes document change and other specific PMD driver change.
> > > > This kind of patchset will be pointed to dpdk master
> > >
> > > For doc/, we must make sure each part of the doc is well sorted in
> > > MAINTAINERS so we can distinguish crypto and ethdev docs for instance.
> >
> > The doc/ pattern is currently filtered out, if this is what you are
> > referring to.
>
> I think the doc/ directory should be not filtered out, because patches
> which are updating only the doc of a driver or a tool need to be
> directed to the right tree/maintainer.
>
>I sent an update on MAINTAINERS, and I am about to send the change
>that filters mk/, config/ and MAINTAINERS.
>
>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.
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
Viacheslav Ovsiienko
8158
dpdk-next-crypto
dpdk
http://patchwork.dpdk.org/api/series/8158
Pablo de Lara
8154
dpdk-next-net
dpdk
http://patchwork.dpdk.org/api/series/8154
Xiaoyu Min
8153
dpdk-next-net
dpdk
http://patchwork.dpdk.org/api/series/8153
Wei Hu (Xavier)
8177
dpdk-next-net-mlx
dpdk
http://patchwork.dpdk.org/api/series/8177
Dekel Peled
8162
dpdk-next-net
dpdk
http://patchwork.dpdk.org/api/series/8162
Bernard Iremonger
8169
dpdk-next-net-intel
dpdk
http://patchwork.dpdk.org/api/series/8169
Bernard Iremonger
thanks
[-- Attachment #2: Type: text/html, Size: 19819 bytes --]
next prev parent reply other threads:[~2020-01-17 6:06 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 [this message]
2020-01-19 8:01 ` Dekel Peled
2020-01-20 14:49 ` David Marchand
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=ededa3cb01bd4da0947c60f22b0ba894@intel.com \
--to=xuemingx.zhang@intel.com \
--cc=alialnu@mellanox.com \
--cc=bernard.iremonger@intel.com \
--cc=bruce.richardson@intel.com \
--cc=ci@dpdk.org \
--cc=david.marchand@redhat.com \
--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=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).