All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Mark Salter <msalter@redhat.com>
Cc: linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	x86@kernel.org
Subject: Re: [PATCH v2 13/14] x86: select ARCH_MAY_HAVE_PC_PARPORT
Date: Tue, 8 Oct 2013 07:43:14 +0200	[thread overview]
Message-ID: <20131008054314.GD14353@gmail.com> (raw)
In-Reply-To: <1381209030-351-14-git-send-email-msalter@redhat.com>


* Mark Salter <msalter@redhat.com> wrote:

> Architectures which support CONFIG_PARPORT_PC should select
> ARCH_MAY_HAVE_PC_PARPORT.
> 
> Signed-off-by: Mark Salter <msalter@redhat.com>
> CC: Thomas Gleixner <tglx@linutronix.de>
> CC: Ingo Molnar <mingo@redhat.com>
> CC: "H. Peter Anvin" <hpa@zytor.com>
> CC: x86@kernel.org
> ---
>  arch/x86/Kconfig | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> index ee2fb9d..72fca40 100644
> --- a/arch/x86/Kconfig
> +++ b/arch/x86/Kconfig
> @@ -22,6 +22,7 @@ config X86_64
>  config X86
>  	def_bool y
>  	select ARCH_HAS_DEBUG_STRICT_USER_COPY_CHECKS
> +	select ARCH_MAY_HAVE_PC_PARPORT
>  	select HAVE_AOUT if X86_32
>  	select HAVE_UNSTABLE_SCHED_CLOCK
>  	select ARCH_SUPPORTS_NUMA_BALANCING

Acked-by: Ingo Molnar <mingo@kernel.org>

Thanks,

	Ingo

  reply	other threads:[~2013-10-08  5:43 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-08  5:10 [PATCH v2 00/14] Kconfig cleanup (PARPORT_PC dependencies) Mark Salter
2013-10-08  5:10 ` [PATCH v2 01/14] alpha: select ARCH_MAY_HAVE_PC_PARPORT Mark Salter
2013-10-08  5:10 ` [PATCH v2 02/14] arc: " Mark Salter
2013-10-08  5:44   ` Vineet Gupta
2013-10-08  5:10 ` [PATCH v2 03/14] arm: " Mark Salter
2013-10-08  5:10   ` Mark Salter
2013-10-08  5:10 ` [PATCH v2 04/14] ia64: " Mark Salter
2013-10-08  5:10   ` Mark Salter
2013-10-08  5:10 ` [PATCH v2 05/14] m68k: " Mark Salter
2013-10-08  5:10 ` [PATCH v2 06/14] microblaze: " Mark Salter
2013-10-08  5:10 ` [PATCH v2 07/14] mips: " Mark Salter
2013-10-08  7:02   ` Ralf Baechle
2013-10-08  5:10 ` [PATCH v2 08/14] parisc: " Mark Salter
2013-10-08  5:10 ` [PATCH v2 09/14] powerpc: " Mark Salter
2013-10-08  5:10   ` Mark Salter
2013-10-08  5:10 ` [PATCH v2 10/14] sh: " Mark Salter
2013-10-08  5:10   ` Mark Salter
2013-10-08  5:10 ` [PATCH v2 11/14] sparc: " Mark Salter
2013-10-08  5:10   ` Mark Salter
2013-10-08  5:10 ` [PATCH v2 12/14] unicore32: " Mark Salter
2013-10-08  5:10 ` [PATCH v2 13/14] x86: " Mark Salter
2013-10-08  5:43   ` Ingo Molnar [this message]
2013-10-08  5:10 ` [PATCH v2 14/14] Kconfig cleanup (PARPORT_PC dependencies) Mark Salter
2013-10-08  5:10   ` Mark Salter
2013-10-08  5:10   ` Mark Salter
2013-10-08  5:10   ` Mark Salter
2013-10-08  5:10   ` Mark Salter
2013-10-08  5:46   ` Ingo Molnar
2013-10-08  5:46     ` Ingo Molnar
2013-10-08  5:46     ` Ingo Molnar
2013-10-08  5:46     ` Ingo Molnar
2013-10-08  7:00   ` Ralf Baechle
2013-10-08  7:00     ` Ralf Baechle
2013-10-08  7:00     ` Ralf Baechle
2013-10-08  7:00     ` Ralf Baechle
2013-10-08  7:00     ` Ralf Baechle
2013-10-08  7:00     ` Ralf Baechle

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=20131008054314.GD14353@gmail.com \
    --to=mingo@kernel.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=msalter@redhat.com \
    --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.