DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Iremonger, Bernard" <bernard.iremonger@intel.com>,
	Adrien Mazarguil <adrien.mazarguil@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] maintainers: fix responsibility of flow API bits
Date: Thu, 17 May 2018 15:45:30 +0100	[thread overview]
Message-ID: <7431a0f3-e87e-6b8b-04ae-9fd6e919a699@intel.com> (raw)
In-Reply-To: <8CEF83825BEC744B83065625E567D7C24E0CD93C@IRSMSX108.ger.corp.intel.com>

On 5/17/2018 12:26 PM, Iremonger, Bernard wrote:
> Hi Adrien,
> 
> <snip>
> 
> 
>>>>>> Subject: [PATCH] maintainers: fix responsibility of flow API
>>>>>> bits
>>>>>>
>>>>>> The following commits lack MAINTAINERS entries for this mess.
>>>>>>
>>>>>> Fixes: 4d73b6fb9907 ("doc: add generic flow API guide")
>>>>>> Fixes: 19c90af6285c ("app/testpmd: add flow command")
>>>>>> Cc: stable@dpdk.org
>>>>>>
>>>>>> Signed-off-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>
>>>>>> Cc: Bernard Iremonger <bernard.iremonger@intel.com>
>>>>>> ---
>>>>>>  MAINTAINERS | 2 ++
>>>>>>  1 file changed, 2 insertions(+)
>>>>>>
>>>>>> diff --git a/MAINTAINERS b/MAINTAINERS index
>>>>>> bd08d4292..187817fff
>>>>>> 100644
>>>>>> --- a/MAINTAINERS
>>>>>> +++ b/MAINTAINERS
>>>>>> @@ -303,6 +303,8 @@ F: devtools/test-null.sh  Flow API
>>>>>>  M: Adrien Mazarguil <adrien.mazarguil@6wind.com>
>>>>>>  T: git://dpdk.org/next/dpdk-next-net
>>>>>> +F: app/test-pmd/cmdline_flow.c
>>>>>> +F: doc/guides/prog_guide/rte_flow.rst
>>>>>
>>>>> doc/guides/testpmd_app_ug/testpmd_funcs.rst
>>>>> Should be added to the list of flow related files.
>>>>
>>>> I did not add it because there is no way to split responsibility on
>>>> a documentation section basis AFAIK, and only a fraction of this
>>>> file contains information about rte_flow-related stuff.
>>>>
>>>> --
>>>> Adrien Mazarguil
>>>> 6WIND
>>>
>>> There are already several maintainers for testpmd, adding another maintainer
>> for the flow parts of this file should be ok (I think).
>>
>> True, however providing an exact file name instead of a directory or wildcard
>> makes me the main maintainer/contact for that specific file (e.g. "app/test-
>> pmd/cmdline_flow.c" vs. "app/test-pmd"), basically I do not want to be
>> responsible for the entirety of testpmd's documentation.
>>
>> How about the following instead: another patch that extracts the flow
>> command documentation in its own file (testpmd_flow.rst?) using the include
>> directive (somewhat like cmdline_flow.c). This patch will update MAINTAINERS
>> accordingly.
>>
>> --
>> Adrien Mazarguil
>> 6WIND
> 
> Sounds good to me.

Applied to dpdk-next-net/master, thanks.

(Another patch will separate testpmd_flow.rst? and add maintainership for it)

  reply	other threads:[~2018-05-17 14:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-10  9:29 [dpdk-dev] [PATCH] maintainers: add maintainer for testpmd Bernard Iremonger
2018-05-15 16:23 ` [dpdk-dev] [PATCH] maintainers: fix responsibility of flow API bits Adrien Mazarguil
2018-05-16  9:18   ` Iremonger, Bernard
2018-05-16 14:35     ` Adrien Mazarguil
2018-05-17  9:26       ` Iremonger, Bernard
2018-05-17 11:20         ` Adrien Mazarguil
2018-05-17 11:26           ` Iremonger, Bernard
2018-05-17 14:45             ` Ferruh Yigit [this message]
2018-05-17 14:51               ` [dpdk-dev] [dpdk-stable] " Iremonger, Bernard
2018-05-17 15:50                 ` Adrien Mazarguil
2018-05-16  0:44 ` [dpdk-dev] [PATCH] maintainers: add maintainer for testpmd Lu, Wenzhuo
2018-05-22 20:54   ` Thomas Monjalon

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=7431a0f3-e87e-6b8b-04ae-9fd6e919a699@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=bernard.iremonger@intel.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.org \
    /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).