From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>, Juergen Gross <jgross@suse.com>,
linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org
Cc: boris.ostrovsky@oracle.com, sstabellini@kernel.org,
stable@vger.kernel.org, hpa@zytor.com
Subject: Re: [PATCH v2] xen: Fix x86 sched_clock() interface for xen
Date: Wed, 16 Jan 2019 13:35:47 +0000 [thread overview]
Message-ID: <20190116133547.E246820859@mail.kernel.org> (raw)
In-Reply-To: <20190111120805.24852-1-jgross@suse.com>
Hi,
[This is an automated email]
This commit has been processed because it contains a "Fixes:" tag,
fixing commit: f94c8d116997 sched/clock, x86/tsc: Rework the x86 'unstable' sched_clock() interface.
The bot has tested the following trees: v4.20.2, v4.19.15, v4.14.93.
v4.20.2: Build OK!
v4.19.15: Build OK!
v4.14.93: Failed to apply! Possible dependencies:
2229f70b5bbb ("x86/xen/time: setup vcpu 0 time info page")
b88880809311 ("x86/xen/time: set pvclock flags on xen_time_init()")
How should we proceed with this patch?
--
Thanks,
Sasha
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-01-16 13:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 12:08 [PATCH v2] xen: Fix x86 sched_clock() interface for xen Juergen Gross
2019-01-11 13:12 ` Hans van Kranenburg
2019-01-11 13:12 ` Hans van Kranenburg
2019-01-11 14:01 ` [Xen-devel] " Juergen Gross
2019-01-11 15:57 ` Hans van Kranenburg
2019-01-11 15:57 ` [Xen-devel] " Hans van Kranenburg
2019-01-11 21:46 ` Hans van Kranenburg
2019-01-11 21:46 ` Hans van Kranenburg
2019-01-11 14:01 ` Juergen Gross
2019-01-11 20:35 ` Boris Ostrovsky
2019-01-11 20:35 ` Boris Ostrovsky
2019-01-14 12:43 ` Juergen Gross
2019-01-14 12:43 ` Juergen Gross
2019-01-16 13:35 ` Sasha Levin [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-01-11 12:08 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=20190116133547.E246820859@mail.kernel.org \
--to=sashal@kernel.org \
--cc=boris.ostrovsky@oracle.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sstabellini@kernel.org \
--cc=stable@vger.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 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.