From: WangYuli <wangyuli@uniontech.com>
To: maobibo <maobibo@loongson.cn>, Huacai Chen <chenhuacai@kernel.org>
Cc: Dandan Zhang <zhangdandan@uniontech.com>,
zhaotianrui@loongson.cn, kernel@xen0n.name, kvm@vger.kernel.org,
loongarch@lists.linux.dev, linux-kernel@vger.kernel.org,
Wentao Guan <guanwentao@uniontech.com>,
baimingcong@uniontech.com
Subject: Re: [PATCH] KVM: Loongarch: Remove undefined a6 argument comment for kvm_hypercall
Date: Mon, 29 Jul 2024 11:03:11 +0800 [thread overview]
Message-ID: <DB945E243D91EB2F+df447e7b-ddd6-459d-9951-d92fcfceb92c@uniontech.com> (raw)
In-Reply-To: <9bad6e47-dac5-82d2-1828-57df3ec840f8@loongson.cn>
Hi Bibo and Huacai,
Ah... tell me you two aren't arguing, right?
Both of you are working towards the same goal—making the upstream
code for the Loongarch architecture as clean and elegant as possible.
If it's just a disagreement about how to handle this small patch,
there's no need to make things complicated.
As a partner of yours and a community developer passionate about
Loongson CPU, I'd much rather see you two working together
harmoniously than complaining about each other's work. I have full
confidence in Bibo's judgment on the direction of KVM for Loongarch,
and I also believe that Huacai, as the Loongarch maintainer, has always
been fulfilling his responsibilities.
You are both excellent Linux developers. That's all.
To be specific about the controversy caused by this particular commit,
I think the root cause is that the KVM documentation for Loongarch
hasn't been upstreamed. In my opinion, the documentation seems
ready to be upstreamed. If you're all busy with more important work,
I can take the time to submit them and provide a Chinese translation.
If this is feasible, it would be better to merge this commit after that.
Best wishes,
--
WangYuli
next prev parent reply other threads:[~2024-07-29 3:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-25 13:48 Dandan Zhang
2024-07-26 1:49 ` maobibo
2024-07-26 2:55 ` Huacai Chen
2024-07-26 3:09 ` WangYuli
2024-07-26 3:34 ` maobibo
2024-07-26 6:32 ` Huacai Chen
2024-07-26 6:50 ` maobibo
2024-07-29 3:03 ` WangYuli [this message]
2024-07-29 3:49 ` maobibo
2024-08-06 7:45 ` Huacai Chen
2024-07-31 6:05 ` WangYuli
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=DB945E243D91EB2F+df447e7b-ddd6-459d-9951-d92fcfceb92c@uniontech.com \
--to=wangyuli@uniontech.com \
--cc=baimingcong@uniontech.com \
--cc=chenhuacai@kernel.org \
--cc=guanwentao@uniontech.com \
--cc=kernel@xen0n.name \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=maobibo@loongson.cn \
--cc=zhangdandan@uniontech.com \
--cc=zhaotianrui@loongson.cn \
/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
all inboxes | Powered by JetHome®