From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Joe Millenbach <jmillenbach@gmail.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Amit Shah <amit.shah@redhat.com>,
virtualization@lists.linux-foundation.org,
Randy Dunlap <rdunlap@infradead.org>
Subject: Re: linux-next: Tree for Feb 13 (virtio_console)
Date: Thu, 14 Feb 2013 16:02:29 -0800 [thread overview]
Message-ID: <20130215000229.GA5164@kroah.com> (raw)
In-Reply-To: <20130215105519.1d8de65d4f9195eeb9306c13@canb.auug.org.au>
On Fri, Feb 15, 2013 at 10:55:19AM +1100, Stephen Rothwell wrote:
> Hi Greg,
>
> The patch below is needed in the tty tree (which introduced CONFIG_TTY).
Ok, now done.
> Also, has someone checked to see if any of the CONFIG_ symbols that had a
> dependency on TTY added are selected anywhere else?
Joe did all of that I think. Joe?
next prev parent reply other threads:[~2013-02-15 0:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 8:35 linux-next: Tree for Feb 13 Stephen Rothwell
2013-02-13 8:35 ` Stephen Rothwell
2013-02-13 19:41 ` linux-next: Tree for Feb 13 (virtio_console) Randy Dunlap
2013-02-13 19:41 ` Randy Dunlap
2013-02-14 3:00 ` Rusty Russell
2013-02-14 3:00 ` Rusty Russell
2013-02-14 3:00 ` Rusty Russell
2013-02-14 7:06 ` Stephen Rothwell
2013-02-14 7:06 ` Stephen Rothwell
2013-02-14 18:45 ` Randy Dunlap
2013-02-14 18:55 ` Randy Dunlap
2013-02-14 23:55 ` Stephen Rothwell
2013-02-15 0:02 ` Greg KH [this message]
2013-02-15 0:23 ` Stephen Rothwell
2013-02-15 0:23 ` Stephen Rothwell
2013-02-15 0:51 ` Joe Millenbach
2013-02-15 0:51 ` Joe Millenbach
2013-02-15 0:02 ` Greg KH
2013-02-14 23:55 ` Stephen Rothwell
2013-02-14 18:55 ` Randy Dunlap
2013-02-14 18:45 ` Randy Dunlap
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=20130215000229.GA5164@kroah.com \
--to=greg@kroah.com \
--cc=amit.shah@redhat.com \
--cc=jmillenbach@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=rusty@rustcorp.com.au \
--cc=sfr@canb.auug.org.au \
--cc=virtualization@lists.linux-foundation.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.