From: Juergen Gross <jgross@suse.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>,
xen-devel@lists.xensource.com,
Stefano Stabellini <sstabellini@kernel.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: Please apply "partially revert "xen: Remove event channel..."
Date: Wed, 12 Apr 2017 18:24:23 +0200 [thread overview]
Message-ID: <40a3af38-ca63-ec27-8a1e-a67ddd2e905b@suse.com> (raw)
In-Reply-To: <22766.12088.396210.980914@mariner.uk.xensource.com>
On 12/04/17 15:44, Ian Jackson wrote:
> Greg KH writes ("Re: Please apply "partially revert "xen: Remove event channel...""):
>> On Wed, Apr 12, 2017 at 03:26:53PM +0200, Juergen Gross wrote:
>>> On 12/04/17 15:13, Greg KH wrote:
>>>> Is this still true? This long thread is totally confusing, is that what
>>>> you really want to have happen? Anything else?
>
> Quite!
>
>>> Please ignore this request. We will send another one to fully revert the
>>> original patch leading to the current situation.
>
> Thanks for clarifying this. (In future, perhaps kernel folks could
> take charge of requesting backports as appropriate, when the stable
> kernel branches break, so that I don't have to blunder about making
> inappropriate requests...)
The request wasn't inappropriate. It was just bad luck regarding the
timing.
> Can someone please let me know when this is fixed ? This is blocking
> switching osstest's default kernel to something more modern.
Sure.
Juergen
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-04-12 16:24 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 11:25 [linux-4.9 baseline test] 107238: tolerable FAIL osstest service owner
2017-04-07 11:58 ` Please apply "partially revert "xen: Remove event channel..." Ian Jackson
2017-04-07 11:58 ` Ian Jackson
2017-04-07 13:13 ` Boris Ostrovsky
2017-04-07 17:36 ` Stefano Stabellini
2017-04-07 17:43 ` Boris Ostrovsky
2017-04-07 17:43 ` Boris Ostrovsky
2017-04-07 22:11 ` Stefano Stabellini
2017-04-10 13:47 ` Boris Ostrovsky
2017-04-10 13:57 ` Juergen Gross
2017-04-10 14:12 ` Boris Ostrovsky
2017-04-10 15:32 ` Raslan, KarimAllah
2017-04-10 16:26 ` Juergen Gross
2017-04-10 18:35 ` Stefano Stabellini
2017-04-10 18:48 ` Boris Ostrovsky
2017-04-11 9:53 ` Andrew Cooper
2017-04-11 13:22 ` Boris Ostrovsky
2017-04-11 13:47 ` Juergen Gross
2017-04-11 14:10 ` Boris Ostrovsky
2017-04-11 14:42 ` Raslan, KarimAllah
2017-04-11 14:47 ` Juergen Gross
2017-04-11 8:57 ` Juergen Gross
2017-04-11 14:26 ` Raslan, KarimAllah
2017-04-12 13:13 ` Greg KH
2017-04-12 13:26 ` Juergen Gross
2017-04-12 13:34 ` Greg KH
2017-04-12 13:44 ` Ian Jackson
2017-04-12 16:24 ` Juergen Gross [this message]
2017-05-11 12:26 ` 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=40a3af38-ca63-ec27-8a1e-a67ddd2e905b@suse.com \
--to=jgross@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=ian.jackson@eu.citrix.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xensource.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.