From: Greg KH <gregkh@linuxfoundation.org>
To: Juergen Gross <jgross@suse.com>
Cc: stable@vger.kernel.org
Subject: Re: [Patch-for-stable-4.14 0/6] x86/xen: backport of commit 867cefb4cb1012
Date: Tue, 29 Jan 2019 11:26:42 +0100 [thread overview]
Message-ID: <20190129102642.GC12232@kroah.com> (raw)
In-Reply-To: <20190123115636.19710-1-jgross@suse.com>
On Wed, Jan 23, 2019 at 12:56:30PM +0100, Juergen Gross wrote:
> This is the backport of commit 867cefb4cb1012 ("xen: Fix x86
> sched_clock() interface for xen") for stable 4.14 kernel. This series
> includes the upstream patches said commit depends on.
>
> Juergen Gross (6):
> ptp_kvm: probe for kvm guest availability
> x86/pvclock: add setter for pvclock_pvti_cpu0_va
> x86/xen/time: set pvclock flags on xen_time_init()
> x86/xen/time: setup vcpu 0 time info page
> x86/xen/time: Output xen sched_clock time from 0
> xen: Fix x86 sched_clock() interface for xen
Again, you didn't author all of these :(
now queued up.
greg k-h
prev parent reply other threads:[~2019-01-29 10:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 11:56 [Patch-for-stable-4.14 0/6] x86/xen: backport of commit 867cefb4cb1012 Juergen Gross
2019-01-23 11:56 ` [Patch-for-stable-4.14 1/6] ptp_kvm: probe for kvm guest availability Juergen Gross
2019-01-29 10:24 ` Greg KH
2019-01-23 11:56 ` [Patch-for-stable-4.14 2/6] x86/pvclock: add setter for pvclock_pvti_cpu0_va Juergen Gross
2019-01-23 11:56 ` [Patch-for-stable-4.14 3/6] x86/xen/time: set pvclock flags on xen_time_init() Juergen Gross
2019-01-23 11:56 ` [Patch-for-stable-4.14 4/6] x86/xen/time: setup vcpu 0 time info page Juergen Gross
2019-01-23 11:56 ` [Patch-for-stable-4.14 5/6] x86/xen/time: Output xen sched_clock time from 0 Juergen Gross
2019-01-23 11:56 ` [Patch-for-stable-4.14 6/6] xen: Fix x86 sched_clock() interface for xen Juergen Gross
2019-01-29 10:26 ` Greg KH [this message]
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=20190129102642.GC12232@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jgross@suse.com \
--cc=stable@vger.kernel.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 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.