From: Thomas Monjalon <thomas@monjalon.net>
To: David Marchand <david.marchand@redhat.com>
Cc: "Chen, Zhaoyan" <zhaoyan.chen@intel.com>,
"Zhang, XuemingX" <xuemingx.zhang@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>,
ci@dpdk.org
Subject: Re: [dpdk-ci] Master compilation failures in Intel CI
Date: Tue, 14 Jan 2020 11:33:26 +0100 [thread overview]
Message-ID: <15331133.hlxOUv9cDv@xps> (raw)
In-Reply-To: <CAJFAV8yq7YmJBVVsDSB4HeieFwr4LyiVyjoWEGDs=UBiEWpfBA@mail.gmail.com>
14/01/2020 10:51, David Marchand:
> On Tue, Jan 14, 2020 at 9:04 AM Thomas Monjalon <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.
However some basic doc files may need to be filtered out.
Examples:
doc/api/
doc/guides/conf.py
We should also filter out .gitignore
next prev parent reply other threads:[~2020-01-14 10:33 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 [this message]
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
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=15331133.hlxOUv9cDv@xps \
--to=thomas@monjalon.net \
--cc=alialnu@mellanox.com \
--cc=bruce.richardson@intel.com \
--cc=ci@dpdk.org \
--cc=david.marchand@redhat.com \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=pingx.yu@intel.com \
--cc=qian.q.xu@intel.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).