From: Mark Salter <msalter@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: Mark Salter <msalter@redhat.com>
Subject: [PATCH 00/10] Kconfig: cleanup SERIO_I8042 dependencies
Date: Sat, 14 Dec 2013 11:59:26 -0500 [thread overview]
Message-ID: <1387040376-26906-1-git-send-email-msalter@redhat.com> (raw)
This patch series removes the messy dependencies from SERIO_I8042
by having it depend on one variable (ARCH_MAY_HAVE_PC_SERIO) and
having architectures which need it select that variable in
arch/*/Kconfig.
New architectures are unlikely to need SERIO_I8042, so this avoids
having an ever growing list of architectures to exclude. If an
architecture without i8042 support isn't excluded through the
dependency list for SERIO_I8042 or through explicit disabling in
a config, it will likely panic on boot with something similar to
this (from arm64):
[ 27.426181] [<ffffffc000403b1c>] i8042_flush+0x88/0x10c
[ 27.426251] [<ffffffc00084cc2c>] i8042_init+0x58/0xe8
[ 27.426320] [<ffffffc000080bec>] do_one_initcall+0xc4/0x14c
[ 27.426404] [<ffffffc000820970>] kernel_init_freeable+0x1a4/0x244
[ 27.426480] [<ffffffc0005a894c>] kernel_init+0x18/0x148
[ 27.426561] Code: d2800c82 f2bf7c02 f2dff7e2 f2ffffe2 (39400042)
[ 27.426789] ---[ end trace ac076843cf0f383e ]---
[ 27.426875] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
A tree with these patches is at:
git://github.com/mosalter/linux.git (serio-i8042 branch)
Mark Salter (10):
alpha: select ARCH_MIGHT_HAVE_PC_SERIO
arm: select ARCH_MIGHT_HAVE_PC_SERIO
ia64: select ARCH_MIGHT_HAVE_PC_SERIO
mips: select ARCH_MIGHT_HAVE_PC_SERIO
powerpc: select ARCH_MIGHT_HAVE_PC_SERIO
sh: select ARCH_MIGHT_HAVE_PC_SERIO
sparc: select ARCH_MIGHT_HAVE_PC_SERIO
unicore32: select ARCH_MIGHT_HAVE_PC_SERIO
x86: select ARCH_MIGHT_HAVE_PC_SERIO
Kconfig: cleanup SERIO_I8042 dependencies
arch/alpha/Kconfig | 1 +
arch/arm/Kconfig | 1 +
arch/ia64/Kconfig | 1 +
arch/mips/Kconfig | 1 +
arch/powerpc/Kconfig | 1 +
arch/sh/Kconfig | 1 +
arch/sparc/Kconfig | 1 +
arch/unicore32/Kconfig | 1 +
arch/x86/Kconfig | 1 +
drivers/input/serio/Kconfig | 11 ++++++++---
10 files changed, 17 insertions(+), 3 deletions(-)
--
1.8.3.1
next reply other threads:[~2013-12-14 16:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-14 16:59 Mark Salter [this message]
2013-12-14 16:59 ` [PATCH 01/10] alpha: select ARCH_MIGHT_HAVE_PC_SERIO Mark Salter
2013-12-15 8:21 ` Matt Turner
2013-12-14 16:59 ` [PATCH 02/10] arm: " Mark Salter
2013-12-14 18:41 ` Russell King - ARM Linux
2013-12-14 16:59 ` [PATCH 03/10] ia64: " Mark Salter
2013-12-14 16:59 ` [PATCH 04/10] mips: " Mark Salter
2013-12-16 16:24 ` Ralf Baechle
2013-12-14 16:59 ` [PATCH 05/10] powerpc: " Mark Salter
2013-12-14 16:59 ` [PATCH 06/10] sh: " Mark Salter
2013-12-14 16:59 ` [PATCH 07/10] sparc: " Mark Salter
2013-12-15 3:29 ` David Miller
2013-12-14 16:59 ` [PATCH 08/10] unicore32: " Mark Salter
2013-12-16 5:15 ` 回复: " 管雪涛
2013-12-14 16:59 ` [PATCH 09/10] x86: " Mark Salter
2013-12-14 18:32 ` H. Peter Anvin
2013-12-14 16:59 ` [PATCH 10/10] Kconfig: cleanup SERIO_I8042 dependencies Mark Salter
2013-12-14 18:32 ` H. Peter Anvin
2013-12-15 10:36 ` Dmitry Torokhov
2013-12-15 15:50 ` Mark Salter
2013-12-16 1:27 ` David Miller
2013-12-16 4:59 ` Dmitry Torokhov
2013-12-16 16:23 ` 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=1387040376-26906-1-git-send-email-msalter@redhat.com \
--to=msalter@redhat.com \
--cc=linux-kernel@vger.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