All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sinan Kaya <okaya@kernel.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: linux-next@vger.kernel.org, linux-acpi@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	"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 2/2] x86/Kconfig: Select PCI_LOCKLESS_CONFIG if PCI is enabled
Date: Thu, 24 Jan 2019 12:42:32 -0500	[thread overview]
Message-ID: <cd9774f9-ba35-23ae-7083-6645c7a526c7@kernel.org> (raw)
In-Reply-To: <37767989.Gns3VtERSa@aspire.rjw.lan>

On 1/24/2019 5:51 AM, Rafael J. Wysocki wrote:
>>
> Is anyone taking this or should I?
> 
> 
> 

This got applied:

https://git.kernel.org/tip/625210cfa6c0c26ea422f655bf68288176f174e6

  reply	other threads:[~2019-01-24 17:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-21 23:19 [for next][PATCH 1/2] mfd: Fix unmet dependency warning for MFD_TPS68470 Sinan Kaya
2019-01-21 23:19 ` Sinan Kaya
2019-01-21 23:19 ` [for next][PATCH 2/2] x86/Kconfig: Select PCI_LOCKLESS_CONFIG if PCI is enabled Sinan Kaya
2019-01-21 23:19   ` Sinan Kaya
2019-01-22 12:54   ` Borislav Petkov
2019-01-22 12:54     ` Borislav Petkov
2019-01-22 14:39     ` Sinan Kaya
2019-01-22 14:39       ` Sinan Kaya
2019-01-22 21:51   ` [tip:x86/urgent] " tip-bot for Sinan Kaya
2019-01-24 10:51   ` [for next][PATCH 2/2] " Rafael J. Wysocki
2019-01-24 10:51     ` Rafael J. Wysocki
2019-01-24 17:42     ` Sinan Kaya [this message]
2019-01-24 17:42       ` Sinan Kaya
2019-01-24 10:51 ` [for next][PATCH 1/2] mfd: Fix unmet dependency warning for MFD_TPS68470 Rafael J. Wysocki
2019-01-24 17:43   ` Sinan Kaya
2019-01-28  7:21     ` Lee Jones
2019-01-30 23:55       ` Rafael J. Wysocki

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=cd9774f9-ba35-23ae-7083-6645c7a526c7@kernel.org \
    --to=okaya@kernel.org \
    --cc=bp@alien8.de \
    --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=rjw@rjwysocki.net \
    --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.