From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtpbguseast1.qq.com (smtpbguseast1.qq.com [54.204.34.129]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 00AC22B9D2; Mon, 29 Jul 2024 03:03:59 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=54.204.34.129 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1722222243; cv=none; b=e2mFBIzG38A3CixMxk9MZ8jRLX7L9cX3tiztauMvtHTG7XeGOevo8ehiWTTnAffQe3YhH+S7pG29JjvZdq9Ucr9b+S/Ifr8m48zoDUlXV0z5RZ5o3SY1iCVqHRvOdcUAESchtyvXCGFitcF2z751IWpFH//Y+cOsmLEJOErj9vE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1722222243; c=relaxed/simple; bh=iyTLuCU18Y/3DWAq8FeUpyOEVu74g6lZH7xKIil/U9s=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=Z4JGwYmwbzAvG/amV50McS0nkMWYbKGLohom4MBeaCT5FiCW++MgsFctvhujkccMJNZGp1UOpsMuYVF+7NMKwUMiE04KVXn0uK7zEERoZIW0Z017xB2APohIh9UPZePOY2S4KFkl2JK8Ixr3fzH5aPyScBHfdryp/P40iQshZAM= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=uniontech.com; spf=pass smtp.mailfrom=uniontech.com; arc=none smtp.client-ip=54.204.34.129 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=uniontech.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=uniontech.com X-QQ-mid: bizesmtpsz13t1722222194t7q1ay X-QQ-Originating-IP: 1uHf6tV6CXls7qg6zV58CTomlkOggcYwzjNdHAf0UP4= Received: from [10.20.53.89] ( [113.57.152.160]) by bizesmtp.qq.com (ESMTP) with id ; Mon, 29 Jul 2024 11:03:12 +0800 (CST) X-QQ-SSF: 0000000000000000000000000000000 X-QQ-GoodBg: 1 X-BIZMAIL-ID: 7791691834705649597 Message-ID: Date: Mon, 29 Jul 2024 11:03:11 +0800 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH] KVM: Loongarch: Remove undefined a6 argument comment for kvm_hypercall To: maobibo , Huacai Chen Cc: Dandan Zhang , zhaotianrui@loongson.cn, kernel@xen0n.name, kvm@vger.kernel.org, loongarch@lists.linux.dev, linux-kernel@vger.kernel.org, Wentao Guan , baimingcong@uniontech.com References: <6D5128458C9E19E4+20240725134820.55817-1-zhangdandan@uniontech.com> <9bad6e47-dac5-82d2-1828-57df3ec840f8@loongson.cn> From: WangYuli Autocrypt: addr=wangyuli@uniontech.com; keydata= xjMEZoEsiBYJKwYBBAHaRw8BAQdAyDPzcbPnchbIhweThfNK1tg1imM+5kgDBJSKP+nX39DN IVdhbmdZdWxpIDx3YW5neXVsaUB1bmlvbnRlY2guY29tPsKJBBMWCAAxFiEEa1GMzYeuKPkg qDuvxdofMEb0C+4FAmaBLIgCGwMECwkIBwUVCAkKCwUWAgMBAAAKCRDF2h8wRvQL7g0UAQCH 3mrGM0HzOaARhBeA/Q3AIVfhS010a0MZmPTRGVfPbwD/SrncJwwPAL4GiLPEC4XssV6FPUAY 0rA68eNNI9cJLArOOARmgSyJEgorBgEEAZdVAQUBAQdA88W4CTLDD9fKwW9PB5yurCNdWNS7 VTL0dvPDofBTjFYDAQgHwngEGBYIACAWIQRrUYzNh64o+SCoO6/F2h8wRvQL7gUCZoEsiQIb DAAKCRDF2h8wRvQL7sKvAP4mBvm7Zn1OUjFViwkma8IGRGosXAvMUFyOHVcl1RTgFQEAuJkU o9ERi7qS/hbUdUgtitI89efbY0TVetgDsyeQiwU= In-Reply-To: <9bad6e47-dac5-82d2-1828-57df3ec840f8@loongson.cn> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-QQ-SENDSIZE: 520 Feedback-ID: bizesmtpsz:uniontech.com:qybglogicsvrgz:qybglogicsvrgz8a-1 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