[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c9db67ee-4a0b-dc62-f507-c4a654fc9656@kylinos.cn>
Date: Thu, 6 Apr 2023 10:56:10 +0800
From: "gehao@...inos.cn" <gehao@...inos.cn>
To: Sean Christopherson <seanjc@...gle.com>
Cc: pbonzini@...hat.com, shuah@...nel.org, dmatlack@...gle.com,
coltonlewis@...gle.com, vipinsh@...gle.com, kvm@...r.kernel.org,
linux-kselftest@...r.kernel.org, linux-kernel@...r.kernel.org,
gehao618@....com
Subject: Re: [RESEND PATCH] kvm/selftests: Close opened file descriptor in
stable_tsc_check_supported()
在 4/5/23 22:46, Sean Christopherson 写道:
> This is not a RESEND, it is a new version. From Documentation/process/submitting-patches.rst:
>
> Don't add "RESEND" when you are submitting a modified version of your
> patch or patch series - "RESEND" only applies to resubmission of a
> patch or patch series which have not been modified in any way from the
> previous submission.
>
> And the "in any way" really does mean in _any_ way. E.g. if a patch is rebased,
> the version needs to be bumped. RESEND should only ever be used when sending
> literally the same patch/email file, e.g. if something went awry in the delivery
> of the email, or you forgot to Cc the right people, tec.
>
> On Wed, Apr 05, 2023, Hao Ge wrote:
>> Close the "current_clocksource" file descriptor before
> Wrap closer to ~75 chars, wrapping at ~55 is too aggressive.
>
>> returning or exiting from stable_tsc_check_supported()
>> in vmx_nested_tsc_scaling_test
>
> Vipin provided his Reviewed-by, that should have been captured here. Please read
> through Documentation/process/submitting-patches.rst, guidance on "using" the
> various tags is also provided there. And if you have time, pretty much all of
> Documentation/process/ is worth reading.
>
> No need to send a new version, all of this is easy to fixup when applying.
Thank you for your guidance,this has been very helpful to me for sunmitting
patches.
Powered by blists - more mailing lists