xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@arm.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
	Wei Liu <wei.liu2@citrix.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	George Dunlap <George.Dunlap@eu.citrix.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
	tee-dev@lists.linaro.org,
	xen-devel <xen-devel@lists.xenproject.org>,
	Volodymyr Babchuk <volodymyr_babchuk@epam.com>
Subject: Re: [PATCH v5 01/10] xen/arm: add generic TEE mediator framework
Date: Wed, 22 May 2019 13:04:12 +0100	[thread overview]
Message-ID: <cd9aac43-66b3-67ae-9674-70fe736d21b7@arm.com> (raw)
In-Reply-To: <5CE51E2A020000780023144D@prv1-mh.provo.novell.com>

Hi Jan,

On 22/05/2019 11:02, Jan Beulich wrote:
>>>> On 22.05.19 at 11:27, <julien.grall@arm.com> wrote:
> 
>>
>> On 22/05/2019 09:45, Jan Beulich wrote:
>>>>>> On 21.05.19 at 23:25, <Volodymyr_Babchuk@epam.com> wrote:
>>>>    MAINTAINERS                   |   6 ++
>>>>    xen/arch/arm/Kconfig          |   7 +++
>>>>    xen/arch/arm/Makefile         |   1 +
>>>>    xen/arch/arm/domain.c         |  18 ++++++
>>>>    xen/arch/arm/setup.c          |   2 +
>>>>    xen/arch/arm/tee/Makefile     |   1 +
>>>>    xen/arch/arm/tee/tee.c        |  93 +++++++++++++++++++++++++++++
>>>>    xen/arch/arm/vsmc.c           |   5 ++
>>>>    xen/arch/arm/xen.lds.S        |   7 +++
>>>>    xen/include/asm-arm/domain.h  |   1 +
>>>>    xen/include/asm-arm/tee/tee.h | 109 ++++++++++++++++++++++++++++++++++
>>>>    xen/include/public/arch-arm.h |   3 +
>>>>    12 files changed, 253 insertions(+)
>>>>    create mode 100644 xen/arch/arm/tee/Makefile
>>>>    create mode 100644 xen/arch/arm/tee/tee.c
>>>>    create mode 100644 xen/include/asm-arm/tee/tee.h
>>>
>>> I don't think I'm asking this for the first time: Why am I being Cc-ed
>>> here? It's all Arm code that gets changed, and the MAINTAINERS
>>> addition alone imo doesn't warrant widening the Cc list.
>>
>> A lot of users uses the scripts/{add, get}_maintainers.pl to get the list of
>>
>> maintainers to CCed. Both of them output "THE REST" because of the file
>> MAINTAINERS is modified.
>>
>> I don't think it is sensible to expect users to know when to strip the
>> list...
> 
> Hmm, well, I see your point, but I think applying some common sense
> still can be expected. It's also not sensible for unrelated people to
> get Cc-ed. I think anyone knowing enough to modify MAINTAINERS
> can be expected to know whom to Cc.

I disagree here, someone in "THE REST" may have an opinion in adding Volodymyr 
as a maintainer (this is only example).

This is a bit similar to when you send a patch to add a 3 lines timer helper in 
a common header but it is only used by x86. Even if I will not necessary answer 
on the patch because it does not impact Arm directly, I will still have a quick 
look to see if it makes sense.

Anyway, you can't expect the contributor to guess your will on MAINTAINERS. You 
should update the documentation/script if this is the expectation you have.

Cheers,

-- 
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

WARNING: multiple messages have this Message-ID (diff)
From: Julien Grall <julien.grall@arm.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
	Wei Liu <wei.liu2@citrix.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	George Dunlap <George.Dunlap@eu.citrix.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
	tee-dev@lists.linaro.org,
	xen-devel <xen-devel@lists.xenproject.org>,
	Volodymyr Babchuk <volodymyr_babchuk@epam.com>
Subject: Re: [Xen-devel] [PATCH v5 01/10] xen/arm: add generic TEE mediator framework
Date: Wed, 22 May 2019 13:04:12 +0100	[thread overview]
Message-ID: <cd9aac43-66b3-67ae-9674-70fe736d21b7@arm.com> (raw)
Message-ID: <20190522120412.bHQs2PlktEJ98RmNO1GSOrA89_hIS1N39THnt8cohdg@z> (raw)
In-Reply-To: <5CE51E2A020000780023144D@prv1-mh.provo.novell.com>

Hi Jan,

On 22/05/2019 11:02, Jan Beulich wrote:
>>>> On 22.05.19 at 11:27, <julien.grall@arm.com> wrote:
> 
>>
>> On 22/05/2019 09:45, Jan Beulich wrote:
>>>>>> On 21.05.19 at 23:25, <Volodymyr_Babchuk@epam.com> wrote:
>>>>    MAINTAINERS                   |   6 ++
>>>>    xen/arch/arm/Kconfig          |   7 +++
>>>>    xen/arch/arm/Makefile         |   1 +
>>>>    xen/arch/arm/domain.c         |  18 ++++++
>>>>    xen/arch/arm/setup.c          |   2 +
>>>>    xen/arch/arm/tee/Makefile     |   1 +
>>>>    xen/arch/arm/tee/tee.c        |  93 +++++++++++++++++++++++++++++
>>>>    xen/arch/arm/vsmc.c           |   5 ++
>>>>    xen/arch/arm/xen.lds.S        |   7 +++
>>>>    xen/include/asm-arm/domain.h  |   1 +
>>>>    xen/include/asm-arm/tee/tee.h | 109 ++++++++++++++++++++++++++++++++++
>>>>    xen/include/public/arch-arm.h |   3 +
>>>>    12 files changed, 253 insertions(+)
>>>>    create mode 100644 xen/arch/arm/tee/Makefile
>>>>    create mode 100644 xen/arch/arm/tee/tee.c
>>>>    create mode 100644 xen/include/asm-arm/tee/tee.h
>>>
>>> I don't think I'm asking this for the first time: Why am I being Cc-ed
>>> here? It's all Arm code that gets changed, and the MAINTAINERS
>>> addition alone imo doesn't warrant widening the Cc list.
>>
>> A lot of users uses the scripts/{add, get}_maintainers.pl to get the list of
>>
>> maintainers to CCed. Both of them output "THE REST" because of the file
>> MAINTAINERS is modified.
>>
>> I don't think it is sensible to expect users to know when to strip the
>> list...
> 
> Hmm, well, I see your point, but I think applying some common sense
> still can be expected. It's also not sensible for unrelated people to
> get Cc-ed. I think anyone knowing enough to modify MAINTAINERS
> can be expected to know whom to Cc.

I disagree here, someone in "THE REST" may have an opinion in adding Volodymyr 
as a maintainer (this is only example).

This is a bit similar to when you send a patch to add a 3 lines timer helper in 
a common header but it is only used by x86. Even if I will not necessary answer 
on the patch because it does not impact Arm directly, I will still have a quick 
look to see if it makes sense.

Anyway, you can't expect the contributor to guess your will on MAINTAINERS. You 
should update the documentation/script if this is the expectation you have.

Cheers,

-- 
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  parent reply	other threads:[~2019-05-22 12:04 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-21 21:25 [PATCH v5 00/10] TEE mediator (and OP-TEE) support in XEN Volodymyr Babchuk
2019-05-21 21:25 ` [Xen-devel] " Volodymyr Babchuk
2019-05-21 21:25 ` [PATCH v5 01/10] xen/arm: add generic TEE mediator framework Volodymyr Babchuk
2019-05-21 21:25   ` [Xen-devel] " Volodymyr Babchuk
2019-05-22  8:45   ` Jan Beulich
2019-05-22  8:45     ` [Xen-devel] " Jan Beulich
2019-05-22  9:27     ` Julien Grall
2019-05-22  9:27       ` [Xen-devel] " Julien Grall
2019-05-22 10:02       ` Jan Beulich
2019-05-22 10:02         ` [Xen-devel] " Jan Beulich
2019-05-22 12:04         ` Julien Grall [this message]
2019-05-22 12:04           ` Julien Grall
2019-06-03 11:46   ` Julien Grall
2019-06-03 11:46     ` [Xen-devel] " Julien Grall
2019-06-03 11:48   ` Julien Grall
2019-06-03 11:48     ` [Xen-devel] " Julien Grall
2019-06-06 16:02   ` Julien Grall
2019-06-07  9:36     ` Julien Grall
2019-06-11 18:18       ` Volodymyr Babchuk
2019-06-11 18:26         ` Julien Grall
2019-05-21 21:25 ` [PATCH v5 02/10] xen/arm: optee: add OP-TEE header files Volodymyr Babchuk
2019-05-21 21:25   ` [Xen-devel] " Volodymyr Babchuk
2019-06-03 11:49   ` Julien Grall
2019-06-03 11:49     ` [Xen-devel] " Julien Grall
2019-06-10 18:20     ` Volodymyr Babchuk
2019-06-10 18:53       ` Julien Grall
2019-05-21 21:25 ` [PATCH v5 03/10] xen/arm: optee: add OP-TEE mediator skeleton Volodymyr Babchuk
2019-05-21 21:25   ` [Xen-devel] " Volodymyr Babchuk
2019-06-03 12:34   ` Julien Grall
2019-06-03 12:34     ` [Xen-devel] " Julien Grall
2019-05-21 21:25 ` [PATCH v5 04/10] xen/arm: optee: add fast calls handling Volodymyr Babchuk
2019-05-21 21:25   ` [Xen-devel] " Volodymyr Babchuk
2019-06-03 12:34   ` Julien Grall
2019-06-03 12:34     ` [Xen-devel] " Julien Grall
2019-05-21 21:26 ` [PATCH v5 05/10] xen/arm: optee: add std call handling Volodymyr Babchuk
2019-05-21 21:26   ` [Xen-devel] " Volodymyr Babchuk
2019-06-03 12:34   ` Julien Grall
2019-06-03 12:34     ` [Xen-devel] " Julien Grall
2019-05-21 21:26 ` [PATCH v5 06/10] xen/arm: optee: add support for RPC SHM buffers Volodymyr Babchuk
2019-05-21 21:26   ` [Xen-devel] " Volodymyr Babchuk
2019-06-03 12:33   ` Julien Grall
2019-06-03 12:33     ` [Xen-devel] " Julien Grall
2019-05-21 21:26 ` [PATCH v5 07/10] xen/arm: optee: add support for arbitrary shared memory Volodymyr Babchuk
2019-05-21 21:26   ` [Xen-devel] " Volodymyr Babchuk
2019-06-03 12:29   ` Julien Grall
2019-06-03 12:29     ` [Xen-devel] " Julien Grall
2019-05-21 21:26 ` [PATCH v5 08/10] xen/arm: optee: add support for RPC commands Volodymyr Babchuk
2019-05-21 21:26   ` [Xen-devel] " Volodymyr Babchuk
2019-06-03 12:33   ` Julien Grall
2019-06-03 12:33     ` [Xen-devel] " Julien Grall
2019-05-21 21:26 ` [PATCH v5 09/10] tools/arm: tee: add "tee" option for xl.cfg Volodymyr Babchuk
2019-05-21 21:26   ` [Xen-devel] " Volodymyr Babchuk
2019-06-03 12:44   ` Julien Grall
2019-06-03 12:44     ` [Xen-devel] " Julien Grall
2019-06-03 14:47   ` Ian Jackson
2019-06-03 14:47     ` [Xen-devel] " Ian Jackson
2019-05-21 21:26 ` [PATCH v5 10/10] tools/arm: optee: create optee firmware node in DT if tee=optee Volodymyr Babchuk
2019-05-21 21:26   ` [Xen-devel] " Volodymyr Babchuk
2019-06-03 14:50   ` Ian Jackson
2019-06-03 14:50     ` [Xen-devel] " Ian Jackson
2019-06-01 14:50 ` [PATCH v5 00/10] TEE mediator (and OP-TEE) support in XEN Julien Grall
2019-06-01 14:50   ` [Xen-devel] " Julien Grall
2019-06-01 16:07   ` Volodymyr Babchuk
2019-06-01 16:07     ` [Xen-devel] " Volodymyr Babchuk
2019-06-01 16:55     ` Julien Grall
2019-06-01 16:55       ` [Xen-devel] " Julien Grall
2019-06-04 13:31       ` Volodymyr Babchuk
2019-06-06 15:33         ` Julien Grall

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=cd9aac43-66b3-67ae-9674-70fe736d21b7@arm.com \
    --to=julien.grall@arm.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=sstabellini@kernel.org \
    --cc=tee-dev@lists.linaro.org \
    --cc=tim@xen.org \
    --cc=volodymyr_babchuk@epam.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.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).