From: Julien Grall <julien@xen.org>
To: Jan Beulich <jbeulich@suse.com>,
Ayan Kumar Halder <ayankuma@amd.com>,
Ayan Kumar Halder <ayan.kumar.halder@amd.com>
Cc: xen-devel@lists.xenproject.org, Penny Zheng <penny.zheng@arm.com>,
Wei Chen <wei.chen@arm.com>,
sstabellini@kernel.org, bertrand.marquis@arm.com,
michal.orzel@amd.com, Volodymyr_Babchuk@epam.com
Subject: Re: [PATCH v3 2/4] xen: make VMAP only support in MMU system
Date: Mon, 19 Aug 2024 14:01:08 +0100 [thread overview]
Message-ID: <d0adc2ad-9cfe-4270-bf77-61d0650effb6@xen.org> (raw)
In-Reply-To: <759d5d83-b09c-4853-8ec0-63a19faf8af5@suse.com>
Hi Jan,
On 19/08/2024 13:24, Jan Beulich wrote:
> On 19.08.2024 14:12, Julien Grall wrote:
>> On 19/08/2024 12:39, Jan Beulich wrote:
>>> Guys,
>>>
>>> On 19.08.2024 11:45, Ayan Kumar Halder wrote:
>>>> On 16/08/2024 17:40, Julien Grall wrote:
>>>>> On 14/08/2024 13:33, Ayan Kumar Halder wrote:
>>>
>>> mind me asking why I continue to be on the To: list of this communication
>>> between the two of you?
>>
>> You were involved in the review and AFAICT will still touch the common
>> code. I am happy to remove you from the conversation if you are not
>> interested :).
>
> That wasn't my request though. It's fine to keep me Cc-ed.
TBH, in this context, the difference between CC and TO is very blur.
For me, CC is for people that may be interested but not involved in the
conversation. In this case, Ayan was suggesting whether we should use
ARCH_VMAP or not.
Given you reviewed the rest, I feel you have your say on this decision.
Hence why the TO makes sense. But I also understand why people may view
it differently...
Personally, I don't make any filter on "cc" vs "to" because this is a
matter of opinion whether you think someone should be actively involved
(or not) in the discussion. So it is best if I look at everything even
if this is just having a glancing look at on the content.
If you have some clear and unambiguous rules on when you want to be in
the CC or TO, then I would be happy to follow them.
Cheers,
--
Julien Grall
next prev parent reply other threads:[~2024-08-19 13:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 17:13 [PATCH v3 0/4] xen: arm: Split MMU code in preparation for MPU work (part 2) Ayan Kumar Halder
2024-08-13 17:13 ` [PATCH v3 1/4] xen: arm: Add a new helper update_boot_mapping() Ayan Kumar Halder
2024-08-14 12:50 ` Michal Orzel
2024-08-20 11:27 ` Ayan Kumar Halder
2024-08-13 17:13 ` [PATCH v3 2/4] xen: make VMAP only support in MMU system Ayan Kumar Halder
2024-08-14 6:37 ` Jan Beulich
2024-08-14 10:55 ` Ayan Kumar Halder
2024-08-14 11:35 ` Jan Beulich
2024-08-14 12:33 ` Ayan Kumar Halder
2024-08-14 13:04 ` Jan Beulich
2024-08-16 9:28 ` Michal Orzel
2024-08-16 16:00 ` Ayan Kumar Halder
2024-08-16 16:40 ` Julien Grall
2024-08-19 9:45 ` Ayan Kumar Halder
2024-08-19 9:55 ` Julien Grall
2024-08-19 9:58 ` Julien Grall
2024-08-20 11:48 ` Ayan Kumar Halder
2024-08-20 12:51 ` Jan Beulich
2024-08-19 11:39 ` Jan Beulich
2024-08-19 12:12 ` Julien Grall
2024-08-19 12:24 ` Jan Beulich
2024-08-19 13:01 ` Julien Grall [this message]
2024-08-13 17:13 ` [PATCH v3 3/4] xen: arm: Move the functions of domain_page to MMU specific Ayan Kumar Halder
2024-08-14 12:59 ` Michal Orzel
2024-08-13 17:13 ` [PATCH v3 4/4] xen: arm: Enclose access to EL2 MMU specific registers under CONFIG_MMU Ayan Kumar Halder
2024-08-14 13:07 ` Michal Orzel
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=d0adc2ad-9cfe-4270-bf77-61d0650effb6@xen.org \
--to=julien@xen.org \
--cc=Volodymyr_Babchuk@epam.com \
--cc=ayan.kumar.halder@amd.com \
--cc=ayankuma@amd.com \
--cc=bertrand.marquis@arm.com \
--cc=jbeulich@suse.com \
--cc=michal.orzel@amd.com \
--cc=penny.zheng@arm.com \
--cc=sstabellini@kernel.org \
--cc=wei.chen@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.