From: Jiri Slaby <jslaby@suse.cz>
To: Joe Millenbach <jmillenbach@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Alan Cox <alan@linux.intel.com>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
team-fjord@googlegroups.com,
Josh Triplett <josh@joshtriplett.org>,
"jirisl >> Jiri Slaby" <jirislaby@gmail.com>
Subject: Re: [PATCHv2] tty: Added a CONFIG_TTY option to allow removal of TTY
Date: Mon, 03 Sep 2012 23:15:58 +0200 [thread overview]
Message-ID: <50451E0E.1050605@suse.cz> (raw)
In-Reply-To: <1346633072-29361-1-git-send-email-jmillenbach@gmail.com>
On 09/03/2012 02:44 AM, Joe Millenbach wrote:
> The option allows you to remove TTY and compile without errors. This
> saves space on systems that won't support TTY interfaces anyway.
> bloat-o-meter output is below.
...
> --- a/drivers/tty/Kconfig
> +++ b/drivers/tty/Kconfig
> @@ -1,3 +1,14 @@
> +config TTY
> + bool "Enable TTY" if EXPERT
> + default y
> + ---help---
> + Allows you to remove TTY support which can save space, and
> + blocks features that require TTY from inclusion in the kernel.
> + TTY is required for any text terminals or serial port
> + communication. Most users should leave this enabled.
> +
> +if TTY
> +
> config VT
> bool "Virtual terminal" if EXPERT
> depends on !S390 && !UML
> @@ -355,6 +366,8 @@ config TRACE_SINK
> If you select this option, you need to select
> "Trace data router for MIPI P1149.7 cJTAG standard".
>
> +endif # TTY
> +
> config PPC_EPAPR_HV_BYTECHAN
> tristate "ePAPR hypervisor byte channel driver"
> depends on PPC
Hmm, I wonder why do not you include EHV in the depends-on-tty list?
thanks,
--
js
suse labs
next prev parent reply other threads:[~2012-09-03 21:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-03 0:44 [PATCHv2] tty: Added a CONFIG_TTY option to allow removal of TTY Joe Millenbach
2012-09-03 21:15 ` Jiri Slaby [this message]
2012-09-03 21:24 ` Joe Millenbach
2012-09-03 21:45 ` Jiri Slaby
2012-09-03 21:55 ` Joe Millenbach
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=50451E0E.1050605@suse.cz \
--to=jslaby@suse.cz \
--cc=alan@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@gmail.com \
--cc=jmillenbach@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=team-fjord@googlegroups.com \
/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