All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: KY Srinivasan <kys@microsoft.com>
Cc: Ingo Molnar <mingo@kernel.org>, "x86@kernel.org" <x86@kernel.org>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
	"olaf@aepfle.de" <olaf@aepfle.de>,
	"apw@canonical.com" <apw@canonical.com>,
	"jasowang@redhat.com" <jasowang@redhat.com>,
	"hpa@zytor.com" <hpa@zytor.com>,
	Stephen Hemminger <sthemmin@microsoft.com>,
	"Michael Kelley (EOSG)" <Michael.H.Kelley@microsoft.com>,
	"vkuznets@redhat.com" <vkuznets@redhat.com>
Subject: RE: [PATCH 1/1] X86/Hyper-V:: Fix the circular dependency in IPI enlightenment.
Date: Fri, 6 Jul 2018 12:42:03 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.21.1807061240560.1664@nanos.tec.linutronix.de> (raw)
In-Reply-To: <alpine.DEB.2.21.1807061052410.1664@nanos.tec.linutronix.de>

On Fri, 6 Jul 2018, Thomas Gleixner wrote:
> On Fri, 6 Jul 2018, KY Srinivasan wrote:
> > > 
> > > The problem is that the wreckage is in Linus tree and needs to be fixed
> > > there, i.e. via x86/urgent.
> > > 
> > > Now we have the new bits queued in x86/hyperv already which collide. So
> > > we
> > > need to merge x86/urgent into x86/hyperv after applying the fix and mop up
> > > the merge wreckage in x86/hyperv.
> > > 
> > > I'll have a look tomorrow morning unless you beat me to it.
> > 
> > I can rebase this patch against the latest tip and resend (tomorrow).
> 
> That doesn't help as we need to push the original fix to Linus ...

Applied it to x86/urgent and fixed up the '-1' sloppy hack as pointed out
by Vitaly and merged x86/urgent into x86/hyperv.

Please check both branches for correctness.

Thanks,

	tglx


  reply	other threads:[~2018-07-06 10:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-03 23:01 [PATCH 1/1] X86/Hyper-V:: Fix the circular dependency in IPI enlightenment kys
2018-07-04  8:54 ` [tip:x86/urgent] x86/hyper-v: " tip-bot for K. Y. Srinivasan
2018-07-04  9:13 ` [PATCH 1/1] X86/Hyper-V:: " Vitaly Kuznetsov
2018-07-04 16:10 ` Ingo Molnar
2018-07-05 15:01   ` KY Srinivasan
2018-07-05 15:38     ` Ingo Molnar
2018-07-05 21:11       ` KY Srinivasan
2018-07-05 22:23         ` Ingo Molnar
2018-07-05 22:46           ` Thomas Gleixner
2018-07-06  3:59             ` KY Srinivasan
2018-07-06  8:53               ` Thomas Gleixner
2018-07-06 10:42                 ` Thomas Gleixner [this message]
2018-07-06 16:12                   ` Michael Kelley (EOSG)
2018-07-06 17:01                     ` Thomas Gleixner
2018-07-06 18:05                   ` KY Srinivasan
2018-07-06 10:00             ` Ingo Molnar
2018-07-06 10:42 ` [tip:x86/hyperv] x86/hyper-v: " tip-bot for K. Y. Srinivasan

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=alpine.DEB.2.21.1807061240560.1664@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=Michael.H.Kelley@microsoft.com \
    --cc=apw@canonical.com \
    --cc=devel@linuxdriverproject.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hpa@zytor.com \
    --cc=jasowang@redhat.com \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=olaf@aepfle.de \
    --cc=sthemmin@microsoft.com \
    --cc=vkuznets@redhat.com \
    --cc=x86@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.