From: Greg KH <greg@kroah.com>
To: Juergen Gross <jgross@suse.com>
Cc: stable@vger.kernel.org,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Julien Grall <julien.grall@arm.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Ross Lagerwall <ross.lagerwall@citrix.com>,
xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org, Anthony Liguori <aliguori@amazon.com>,
KarimAllah Ahmed <karahmed@amazon.de>
Subject: Re: [stable-4.10: PATCH] xen: revert commits 72a9b186292 and da72ff5bfcb0
Date: Tue, 18 Apr 2017 15:52:11 +0200 [thread overview]
Message-ID: <20170418135211.GA20659@kroah.com> (raw)
In-Reply-To: <20170413165554.GA8378@kroah.com>
On Thu, Apr 13, 2017 at 06:55:54PM +0200, Greg KH wrote:
> On Thu, Apr 13, 2017 at 06:28:33PM +0200, Juergen Gross wrote:
> > On 13/04/17 18:24, Greg KH wrote:
> > > On Thu, Apr 13, 2017 at 04:49:49PM +0200, Juergen Gross wrote:
> > >> Revert commit 72a9b186292 ("xen: Remove event channel notification
> > >> through Xen PCI platform device") as the original analysis was wrong
> > >> that all the removed code isn't in use any more. As commit da72ff5bfcb0
> > >> ("partially revert xen: Remove event channel notification through Xen
> > >> PCI platform device") reverted already some parts of it revert this
> > >> commit, too.
> > >>
> > >> It is still necessary for old Xen versions (< 4.0) and for being able
> > >> to run the Linux kernel as dom0 in a nested Xen environment.
> > >
> > > Is there a commit in Linus's tree that matches this revert as well?
> >
> > Not yet. I'm working on it.
>
> I'd prefer to take the same exact commit please. That way nothing
> diverges here.
Especially as you are asking to revert patches that are already in
releases and have been out for a while. Always get fixes into Linus's
tree first, and _then_ we can add them to stable releases.
I'm dropping this request, and the one for 4.9, from my stable "todo"
list.
thanks,
greg k-h
next prev parent reply other threads:[~2017-04-18 13:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 14:49 [stable-4.10: PATCH] xen: revert commits 72a9b186292 and da72ff5bfcb0 Juergen Gross
2017-04-13 16:24 ` Greg KH
2017-04-13 16:28 ` Juergen Gross
2017-04-13 16:55 ` Greg KH
2017-04-18 13:52 ` Greg KH [this message]
2017-04-18 13:56 ` Juergen Gross
-- strict thread matches above, loose matches on Subject: below --
2017-05-05 8:00 Juergen Gross
2017-05-05 17:55 ` Greg KH
2017-05-08 5:12 Juergen Gross
2017-05-11 12:20 ` Greg KH
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=20170418135211.GA20659@kroah.com \
--to=greg@kroah.com \
--cc=aliguori@amazon.com \
--cc=bhelgaas@google.com \
--cc=boris.ostrovsky@oracle.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=julien.grall@arm.com \
--cc=karahmed@amazon.de \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paul.gortmaker@windriver.com \
--cc=ross.lagerwall@citrix.com \
--cc=sstabellini@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).