All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sinan Kaya <okaya@kernel.org>
To: Borislav Petkov <bp@alien8.de>, "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Darren Hart <dvhart@infradead.org>,
	Andy Shevchenko <andy@infradead.org>,
	Linux-Next Mailing List <linux-next@vger.kernel.org>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
	<x86@kernel.org>,
	"open list:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
	<linux-kernel@vger.kernel.org>
Subject: Re: [for-next][PATCH] x86/Kconfig: Select PCI_LOCKLESS_CONFIG if PCI is enabled
Date: Thu, 17 Jan 2019 18:02:42 -0500	[thread overview]
Message-ID: <b92f439e-b95c-56e3-6960-52ae1e1afe71@kernel.org> (raw)
In-Reply-To: <20190117220959.GG5023@zn.tnic>

On 1/17/2019 5:09 PM, Borislav Petkov wrote:
> On Thu, Jan 17, 2019 at 11:05:43PM +0100, Rafael J. Wysocki wrote:
>> I have patches for intel_ips and intel_pmc_ipc queued up (will be
>> pushed for -rc3), plus some others.
> 
> Yeah, I saw the patchset and applied some of them locally so that I be
> able to do randconfig builds. Do you have a branch somewhere which I can
> merge locally for testing?
>

You can use this tag (next-20190116) for local test.

  reply	other threads:[~2019-01-17 23:02 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-17 16:17 [for-next][PATCH] x86/Kconfig: Select PCI_LOCKLESS_CONFIG if PCI is enabled Sinan Kaya
2019-01-17 16:17 ` Sinan Kaya
2019-01-17 16:37 ` Borislav Petkov
2019-01-17 16:37   ` Borislav Petkov
2019-01-17 16:39   ` Sinan Kaya
2019-01-17 16:39     ` Sinan Kaya
2019-01-17 16:42   ` Sinan Kaya
2019-01-17 16:42     ` Sinan Kaya
2019-01-17 21:56     ` Borislav Petkov
2019-01-17 21:56       ` Borislav Petkov
2019-01-17 22:05       ` Rafael J. Wysocki
2019-01-17 22:05         ` Rafael J. Wysocki
2019-01-17 22:09         ` Borislav Petkov
2019-01-17 22:09           ` Borislav Petkov
2019-01-17 23:02           ` Sinan Kaya [this message]
2019-01-17 23:02             ` Sinan Kaya
2019-01-18 11:45           ` Rafael J. Wysocki
2019-01-18 11:45             ` Rafael J. Wysocki
2019-01-21 23:18             ` Sinan Kaya
2019-01-21 23:18               ` Sinan Kaya

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=b92f439e-b95c-56e3-6960-52ae1e1afe71@kernel.org \
    --to=okaya@kernel.org \
    --cc=andy@infradead.org \
    --cc=bp@alien8.de \
    --cc=dvhart@infradead.org \
    --cc=hpa@zytor.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rafael@kernel.org \
    --cc=tglx@linutronix.de \
    --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.