linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rafael@kernel.org>
To: okaya@kernel.org
Cc: 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>, Borislav Petkov <bp@alien8.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	"the arch/x86 maintainers" <x86@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 10/11] x86: select IOSF_MBI only when CONFIG_PCI is set
Date: Tue, 25 Dec 2018 10:13:49 +0100	[thread overview]
Message-ID: <CAJZ5v0is-DSV15AxRyNG93vazzQsY_8vM6crzgZXeEmhTyQBVQ@mail.gmail.com> (raw)
In-Reply-To: <20181223232521.11320-11-okaya@kernel.org>

On Mon, Dec 24, 2018 at 12:25 AM Sinan Kaya <okaya@kernel.org> wrote:
>
> Need CONFIG_PCI to be set in order to be able to use IOSF_MBI
> functionality.
>
> Signed-off-by: Sinan Kaya <okaya@kernel.org>

The subject and changelog here don't match the changes below.  Please fix.

> ---
>  arch/x86/Kconfig | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> index cc4f0c6ee1ed..322a58ababb0 100644
> --- a/arch/x86/Kconfig
> +++ b/arch/x86/Kconfig
> @@ -617,7 +617,7 @@ config X86_INTEL_QUARK
>
>  config X86_INTEL_LPSS
>         bool "Intel Low Power Subsystem Support"
> -       depends on X86 && ACPI
> +       depends on X86 && ACPI && PCI
>         select COMMON_CLK
>         select PINCTRL
>         select IOSF_MBI
> --
> 2.19.0
>

  reply	other threads:[~2018-12-25  9:14 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20181223232521.11320-1-okaya@kernel.org>
2018-12-23 23:25 ` [PATCH v3 01/11] ACPI / LPSS: Make PCI dependency explicit Sinan Kaya
2018-12-23 23:25 ` [PATCH v3 02/11] ata: make PCI dependency explicit for PATA_ACPI Sinan Kaya
2018-12-23 23:25 ` [PATCH v3 03/11] vga-switcheroo: make PCI dependency explicit Sinan Kaya
2018-12-23 23:25 ` [PATCH v3 04/11] platform/x86: intel_ips: " Sinan Kaya
2018-12-23 23:25 ` [PATCH v3 05/11] platform/x86: intel_pmc: Make " Sinan Kaya
2018-12-23 23:25 ` [PATCH v3 06/11] apple-gmux: " Sinan Kaya
2018-12-23 23:25 ` [PATCH v3 07/11] drivers: thermal: int3406_thermal: " Sinan Kaya
2018-12-23 23:25 ` [PATCH v3 08/11] ASoC: Intel: atom: " Sinan Kaya
2018-12-26 17:35   ` Pierre-Louis Bossart
2018-12-26 20:07     ` Sinan Kaya
2018-12-23 23:25 ` [PATCH v3 09/11] mmc: add PCI dependency into IOSF_MBI Sinan Kaya
2018-12-26  9:40   ` Rafael J. Wysocki
2018-12-30 18:56     ` Sinan Kaya
2018-12-31  9:40       ` Rafael J. Wysocki
2019-01-02 14:03         ` Adrian Hunter
2019-01-02 14:15           ` Sinan Kaya
2018-12-23 23:25 ` [PATCH v3 10/11] x86: select IOSF_MBI only when CONFIG_PCI is set Sinan Kaya
2018-12-25  9:13   ` Rafael J. Wysocki [this message]
2018-12-30 19:04     ` Sinan Kaya
2018-12-23 23:25 ` [PATCH v3 11/11] drivers: thermal: int340x_thermal: Make PCI dependency explicit 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=CAJZ5v0is-DSV15AxRyNG93vazzQsY_8vM6crzgZXeEmhTyQBVQ@mail.gmail.com \
    --to=rafael@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=okaya@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 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).