From: Sean Christopherson <seanjc@google.com>
To: David Matlack <dmatlack@google.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Ben Gardon <bgardon@google.com>,
kvm@vger.kernel.org, Andrew Jones <andrew.jones@linux.dev>,
Colton Lewis <coltonlewis@google.com>,
Ricardo Koller <ricarkol@google.com>
Subject: Re: [PATCH v2 2/3] KVM: selftests: Rename pta (short for perf_test_args) to args
Date: Wed, 12 Oct 2022 19:24:28 +0000 [thread overview]
Message-ID: <Y0cUbIZqWhU+t34f@google.com> (raw)
In-Reply-To: <20221012165729.3505266-3-dmatlack@google.com>
On Wed, Oct 12, 2022, David Matlack wrote:
> Rename the local variables "pta" (which is short for perf_test_args) for
s/for/to
> args. "pta" is not an obvious acronym and using "args" mirrors
Quotes around "args" for consistency?
> "vcpu_args".
>
> Suggested-by: Sean Christopherson <seanjc@google.com>
> Signed-off-by: David Matlack <dmatlack@google.com>
> ---
A (very small) part of me is sad that I can no longer mentally unpack "pta" to
"Pain in The Ass" :-)
Reviewed-by: Sean Christopherson <seanjc@google.com>
next prev parent reply other threads:[~2022-10-12 19:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 16:57 [PATCH v2 0/3] KVM: selftests: Rename perf_test_util to memstress David Matlack
2022-10-12 16:57 ` [PATCH v2 1/3] KVM: selftests: Rename perf_test_util.[ch] to memstress.[ch] David Matlack
2022-10-12 19:21 ` Sean Christopherson
2022-10-13 16:15 ` David Matlack
2022-10-12 16:57 ` [PATCH v2 2/3] KVM: selftests: Rename pta (short for perf_test_args) to args David Matlack
2022-10-12 19:24 ` Sean Christopherson [this message]
2022-10-12 16:57 ` [PATCH v2 3/3] KVM: selftests: Rename perf_test_util symbols to memstress David Matlack
2022-10-12 19:26 ` Sean Christopherson
2022-10-13 14:03 ` [PATCH v2 0/3] KVM: selftests: Rename perf_test_util " Andrew Jones
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=Y0cUbIZqWhU+t34f@google.com \
--to=seanjc@google.com \
--cc=andrew.jones@linux.dev \
--cc=bgardon@google.com \
--cc=coltonlewis@google.com \
--cc=dmatlack@google.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=ricarkol@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.