From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-172.mta0.migadu.com (out-172.mta0.migadu.com [91.218.175.172]) (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 8F0572E62DA for ; Sun, 19 Oct 2025 11:56:55 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=91.218.175.172 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1760875018; cv=none; b=DzGOE2Ypd8BvpmlFNz7/oCf9XSwnvzY+c3Dojoi9MN+lvBjYkMjxI9Lj9R6XYN8t98DXHJMBgXoJKvMienKSjFgik3uEP2ExrgwRM2Bla0jSij2dYvjBZLGwL4prhRNOTyX1MmaxoDfYYOKJYUDEynS+RUcJpPonAVWYNsAVmxQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1760875018; c=relaxed/simple; bh=51pn86PN3q/U9/Rn7p4SrVjJixfchw/ObHxdns75EEY=; h=Message-ID:Date:MIME-Version:Subject:From:To:Cc:References: In-Reply-To:Content-Type; b=knxIFxg/CZkma44JPHAqF2NGwojb2PLjqP2l2BdZ3Hjv8w4JRsPpbCMYlnVrT3+QdslEnfK8xcLi+QXn4Vyf0qcdFbDn7l+QUlg7+qIz35cuKBmszUxyCSya4J/GVQtgkHKwn028GikVdhCjiltLFrMTsJb5YbEkP8Le8SyZYXc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev; spf=pass smtp.mailfrom=linux.dev; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b=cUmX1Kag; arc=none smtp.client-ip=91.218.175.172 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.dev Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b="cUmX1Kag" Message-ID: <03707213-395c-4b3f-bf6d-3aca392a8ec1@linux.dev> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1760875012; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=L1ZbyeSiI8Nsia35zQRYjhz4FRJX3O13AYqEy6MW+M0=; b=cUmX1KaggKs/AUb6dyCXG7StXh/eHZYBENcIoJRIF71DwYqy/s5KIOfcyDUPtoS0RSq9hi NTTToCWFFsVtpFzJRpsSoaKPjelJzPTttz1zaYIvhTIz2RgxHf9HT9eCD8lP+C1LkZZlJY x2Pa6Jd9BDX4/4ISuJ2vXSf2kpTXFvg= Date: Sun, 19 Oct 2025 19:56:45 +0800 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Subject: Re: [v2 1/6] smb/server: fix return value of smb2_read() X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: ChenXiaoSong To: Steve French , Namjae Jeon , Namjae Jeon , sfrench@samba.org, Markus Elfring Cc: ChenXiaoSong , linux-cifs@vger.kernel.org, linux-kernel@vger.kernel.org References: <20251017104613.3094031-2-chenxiaosong.chenxiaosong@linux.dev> <8d9ab96f-b7cf-4ebb-9a1b-4b0f2b94461f@web.de> <3d3fe6c0-b05e-4e36-8b02-0fc16438c781@linux.dev> Content-Language: en-US In-Reply-To: <3d3fe6c0-b05e-4e36-8b02-0fc16438c781@linux.dev> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Migadu-Flow: FLOW_OUT Hi Steve and Namjae, The "Fixes:" tags of the first five patches in this patchset are the same: Fixes: e2f34481b24d ("cifsd: add server-side procedures for SMB3") Thanks, ChenXiaoSong. On 10/19/25 7:13 PM, ChenXiaoSong wrote: > Hi Steve and Markus, > > Sorry for the late reply, I’ve been ill and sleeping a lot, so I only > just saw your emails. > > Steve, thank you for your understanding of Chinese naming tradition. > > Markus, thank you too for your other suggestions (such as the suggestion > of adding a "Fixes:" tag). > > I am Chinese, and my Chinese name is "陈孝松", the pinyin is > "ChenXiaoSong". The first word is my family name, the second indicates > my generation(the second word of my siblings' names is the same), and > the third is my given name. > > In China, no characters (such as spaces or punctuation) are used between > the word of a name. > > Thanks again to Steve for your understanding of Chinese naming tradition. > > Thanks! > ChenXiaoSong. > > On 10/19/25 5:47 PM, Steve French wrote: >>  > My name pattern recognition would find a display like “… Chen Xiao >> Song” >> clearer eventually. >> >> The convention of whether and where a space is used in approximating >> an Asian name in western ASCII characters apparently varies by >> country, but apparently natively in many Asian languages there would >> be no spaces so there does not appear to be a rule on this for >> Americanized (or westernized) Asian names. In addition the convention >> of whether given name precedes family name is reversed in some asian >> countries. In general a person has some freedom in how they wish to be >> "named" in git commits eg in western languages whether a nickname or >> strict legal name is used. >> >> Thanks, >> >> Steve >> >> On Sun, Oct 19, 2025, 3:50 AM Markus Elfring > > wrote: >> >>      >> Do you care for naming requirements which are indicated by >>      >> the Developer's Certificate of Origin? >>      > >>      > Generally, these are good to follow for multiple reasons, >> >>     Thanks for another bit of positive indication. >> >> >>      > but I still don't see your point. >> >>     I hope that remaining communication difficulties can be resolved >> better. >> >>     We are >> >> >>      > If "Markus Elfring" chooses to use a (valid) email address >>     "Markus.Elfring@web.de …" which is >>     basically the same is his name how is that any different from >>     "ChenXiaoSong" choosing to use a (valid) email address that is >>     almost identical to the name ie "chenxiaosong@kylinos.cn >>     >     >" obviously this is not using an >>     Asian character set, but it appears accurate and I don't see >>     anywhere that it violates. … >> >>     You stressed constraints for the email address selection. >> >>     I dared to point a concern out for the representation of a personal >>     name. >>     https://en.wikipedia.org/wiki/Personal_name >     en.wikipedia.org/wiki/Personal_name> >> >>     We are occasionally struggling with the information >>     “using a known identity (sorry, no anonymous contributions.)”, >>     don't we? >>     https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/ >>     tree/Documentation/process/submitting-patches.rst?h=v6.18-rc1#n440 >>     >     tree/Documentation/process/submitting-patches.rst?h=v6.18-rc1#n440> >> >>     My name pattern recognition would find a display like “… Chen Xiao >> Song” >>     clearer eventually. >>     * https://en.wikipedia.org/wiki/Chen_(surname) >     en.wikipedia.org/wiki/Chen_(surname)> >>     * https://en.wikipedia.org/wiki/Xiao_(surname) >     en.wikipedia.org/wiki/Xiao_(surname)> >>     * https://en.wikipedia.org/wiki/ >>     Song_%28disambiguation%29#People_with_the_name >     en.wikipedia.org/wiki/Song_%28disambiguation%29#People_with_the_name> >> >> >>     Regards, >>     Markus >> >