From: Krister Johansen <kjlx@templeofstupid.com>
To: xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org
Cc: Juergen Gross <jgross@suse.com>, Jan Beulich <jbeulich@suse.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Anthony Liguori <aliguori@amazon.com>,
David Reaver <me@davidreaver.com>,
Brendan Gregg <brendan@intel.com>
Subject: [PATCH linux-next v2 0/2] x86/xen TSC related cleanups
Date: Wed, 22 Feb 2023 09:54:29 -0800 [thread overview]
Message-ID: <cover.1677038165.git.kjlx@templeofstupid.com> (raw)
Hi,
Enclosed please find a pair of patches that perform some additional cleanup
that was suggested by Boris, Jan and Thomas.
Specifically: this resync's arch/x86/include/asm/xen/cpuid.h from its
upstream source in the Xen tree, and then uses one of the new #define-s to
replace a constant in x86/xen/time.c that was previously only numerically
defined. Pedantic code from v1 is dropped in favor of a more appropriate
return statement.
Changes from v1:
- Coding style fixup in arch/x86/xen/time.c (Feedback from Thomas Gleixner)
Krister Johansen (2):
xen: update arch/x86/include/asm/xen/cpuid.h
x86/xen/time: cleanup xen_tsc_safe_clocksource
arch/x86/include/asm/xen/cpuid.h | 22 ++++++++++++++++++----
arch/x86/xen/time.c | 7 ++-----
2 files changed, 20 insertions(+), 9 deletions(-)
--
2.25.1
next reply other threads:[~2023-02-22 17:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 17:54 Krister Johansen [this message]
2023-02-22 17:54 ` [PATCH linux-next v2 1/2] xen: update arch/x86/include/asm/xen/cpuid.h Krister Johansen
2023-02-22 17:54 ` [PATCH linux-next v2 2/2] x86/xen/time: cleanup xen_tsc_safe_clocksource Krister Johansen
2023-02-23 5:43 ` [PATCH linux-next v2 0/2] x86/xen TSC related cleanups Juergen Gross
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=cover.1677038165.git.kjlx@templeofstupid.com \
--to=kjlx@templeofstupid.com \
--cc=aliguori@amazon.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=brendan@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=me@davidreaver.com \
--cc=mingo@redhat.com \
--cc=mtosatti@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/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