From: Sean Christopherson <seanjc@google.com>
To: Hao Ge <gehao@kylinos.cn>
Cc: pbonzini@redhat.com, shuah@kernel.org, dmatlack@google.com,
coltonlewis@google.com, vipinsh@google.com, kvm@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
gehao618@163.com
Subject: Re: [RESEND PATCH] kvm/selftests: Close opened file descriptor in stable_tsc_check_supported()
Date: Wed, 5 Apr 2023 07:46:04 -0700 [thread overview]
Message-ID: <ZC2JrJwKM3KrgNgm@google.com> (raw)
In-Reply-To: <20230405101350.259000-1-gehao@kylinos.cn>
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.
next prev parent reply other threads:[~2023-04-05 14:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 10:13 [RESEND PATCH] kvm/selftests: Close opened file descriptor in stable_tsc_check_supported() Hao Ge
2023-04-05 14:46 ` Sean Christopherson [this message]
2023-04-06 2:56 ` gehao
2023-04-06 8:07 ` Hao Ge
2023-04-06 0:13 ` Sean Christopherson
2023-04-06 0:18 ` Sean Christopherson
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=ZC2JrJwKM3KrgNgm@google.com \
--to=seanjc@google.com \
--cc=coltonlewis@google.com \
--cc=dmatlack@google.com \
--cc=gehao618@163.com \
--cc=gehao@kylinos.cn \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=shuah@kernel.org \
--cc=vipinsh@google.com \
/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