From: Rusty Trivial Russell <rusty@rustcorp.com.au>
To: torvalds@transmeta.com, linux-kernel@vger.kernel.org,
Roman Zippel <zippel@linux-m68k.org>
Subject: [TRIVIAL] [Tiny PATCH]driver_char_Kconfig bug (fwd)
Date: Tue, 14 Jan 2003 13:27:23 +1100 [thread overview]
Message-ID: <20030114025452.74FCA2C3A2@lists.samba.org> (raw)
[ Roman, I've put you down as maintainer for *Kconfig*, so any trivial
patches which touch those files get CC'd to you. Is that OK? --RR ]
From: Adrian Bunk <bunk@fs.tum.de>
Hi Linus,
the issue described in the mail forwarded below is still present in
2.5.54. Please apply the simple patch supplied there.
TIA
Adrian
----- Forwarded message from Rusty Lynch <rusty@stinkycat.com> -----
Date: Fri, 22 Nov 2002 21:56:12 -0800
From: Rusty Lynch <rusty@stinkycat.com>
To: esr@thyrsus.com
Cc: linux-kernel@vger.kernel.org
Subject: [Tiny PATCH]driver/char/Kconfig bug
VT support requires drivers/char/keyboard.c which makes function
calls implemented in drivers/input/, so that attempting to set
CONFIG_INPUT=m or just not setting CONFIG_INPUT will result in a
compile error if CONFIG_VT is on.
Here is a trivial patch against 2.5.49.
-rustyl
--- trivial-2.5.57/drivers/char/Kconfig.orig 2003-01-14 12:11:57.000000000 +1100
+++ trivial-2.5.57/drivers/char/Kconfig 2003-01-14 12:11:57.000000000 +1100
@@ -6,6 +6,7 @@
config VT
bool "Virtual terminal"
+ requires INPUT=y
---help---
If you say Y here, you will get support for terminal devices with
display and keyboard devices. These are called "virtual" because you
--
Don't blame me: the Monkey is driving
File: Adrian Bunk <bunk@fs.tum.de>: [Tiny PATCH]driver_char_Kconfig bug (fwd)
next reply other threads:[~2003-01-14 2:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-14 2:27 Rusty Trivial Russell [this message]
2003-01-14 16:24 ` [TRIVIAL] [Tiny PATCH]driver_char_Kconfig bug (fwd) Roman Zippel
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=20030114025452.74FCA2C3A2@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
--cc=zippel@linux-m68k.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.