From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Josh Triplett <josh@joshtriplett.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Andrew Morton <akpm@linux-foundation.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
linux390@de.ibm.com, linux-s390@vger.kernel.org
Subject: Re: [PATCH] s390: select CONFIG_TTY for use of tty in unconditional keyboard driver
Date: Thu, 27 Feb 2014 08:07:46 +0100 [thread overview]
Message-ID: <20140227070746.GA4343@osiris> (raw)
In-Reply-To: <20140227021305.GA23659@thin>
On Wed, Feb 26, 2014 at 06:13:06PM -0800, Josh Triplett wrote:
> The unconditionally built keyboard driver, drivers/s390/char/keyboard.c,
> requires CONFIG_TTY, so select it from CONFIG_S390 to prevent a build
> error.
>
> Signed-off-by: Josh Triplett <josh@joshtriplett.org>
> ---
> arch/s390/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
Applied, thanks!
next prev parent reply other threads:[~2014-02-27 7:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 8:16 linux-next: build failure after merge of the final tree (akpm-current tree related) Stephen Rothwell
2014-02-26 10:02 ` Josh Triplett
2014-02-26 23:00 ` Stephen Rothwell
2014-02-26 23:17 ` Andrew Morton
2014-02-26 23:19 ` Josh Triplett
2014-02-26 23:42 ` Stephen Rothwell
2014-02-27 2:13 ` [PATCH] s390: select CONFIG_TTY for use of tty in unconditional keyboard driver Josh Triplett
2014-02-27 2:43 ` Stephen Rothwell
2014-02-27 7:07 ` Heiko Carstens [this message]
2014-02-28 1:27 ` [PATCH] cris: Make ETRAX_ARCH_V10 select TTY for use in debugport Josh Triplett
2014-02-28 2:30 ` Stephen Rothwell
2014-02-27 2:21 ` linux-next: build failure after merge of the final tree (akpm-current tree related) Josh Triplett
2014-02-27 2:40 ` Stephen Rothwell
2014-02-28 1:29 ` Josh Triplett
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=20140227070746.GA4343@osiris \
--to=heiko.carstens@de.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux390@de.ibm.com \
--cc=schwidefsky@de.ibm.com \
--cc=sfr@canb.auug.org.au \
/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.