The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Borislav Petkov <bp@alien8.de>, "H. Peter Anvin" <hpa@zytor.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Ingo Molnar <mingo@kernel.org>
Subject: Re: [Intel-gfx] [GIT pull] x86 APIC updates for 4.15
Date: Mon, 11 Dec 2017 12:06:55 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.20.1712111206040.1699@nanos> (raw)
In-Reply-To: <alpine.DEB.2.20.1712111155330.1699@nanos>

On Mon, 11 Dec 2017, Thomas Gleixner wrote:

> On Mon, 11 Dec 2017, Daniel Vetter wrote:
> > Anything else we can do to move this? I just had to resolve a small
> > conflict when moving forward to -rc3. Carrying a revert for the entire
> > apic pull (too many deps to just revert the bisected patch) is a bit
> > annoying.
> 
>   https://lkml.kernel.org/r/alpine.DEB.2.20.1712081129450.1840@nanos

Another question. Is this broken on mainline or just with your new bits
targeted for next?

Thanks,

	tglx

  reply	other threads:[~2017-12-11 11:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-13 12:05 [GIT pull] x86 APIC updates for 4.15 Thomas Gleixner
2017-11-29 13:27 ` Maarten Lankhorst
2017-11-30  9:18   ` Thomas Gleixner
2017-11-30 12:04     ` Maarten Lankhorst
2017-11-30 22:47       ` Thomas Gleixner
2017-12-06 11:13         ` Maarten Lankhorst
2017-12-11 10:02           ` [Intel-gfx] " Daniel Vetter
2017-12-11 10:57             ` Thomas Gleixner
2017-12-11 11:06               ` Thomas Gleixner [this message]
2017-12-11 17:31                 ` Maarten Lankhorst

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.20.1712111206040.1699@nanos \
    --to=tglx@linutronix.de \
    --cc=bp@alien8.de \
    --cc=daniel@ffwll.ch \
    --cc=hpa@zytor.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=torvalds@linux-foundation.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