From: Joe Millenbach <jmillenbach@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Greg KH <greg@kroah.com>, 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>,
Josh Triplett <josh@joshtriplett.org>,
Jamey Sharp <jamey@minilop.net>
Subject: Re: linux-next: Tree for Feb 13 (virtio_console)
Date: Thu, 14 Feb 2013 16:51:17 -0800 [thread overview]
Message-ID: <CADwDc1AvrGP-YPd_h6jvfiUObvS3RWrt20ujTi3_cE_TrnHv9g@mail.gmail.com> (raw)
In-Reply-To: <20130215112313.f0952009747b754447fc45c7@canb.auug.org.au>
On Thu, Feb 14, 2013 at 4:23 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Greg,
>
> On Thu, 14 Feb 2013 16:02:29 -0800 Greg KH <greg@kroah.com> wrote:
>> On Fri, Feb 15, 2013 at 10:55:19AM +1100, Stephen Rothwell wrote:
>> >
>> > 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?
>
> OK, good.
>
I tried to find all of them, but I can't guarantee they're all fixed :
). I tried to search out the features that used the tty driver (using
two initialization functions), and tried enabling all features while
disabling TTY on my x86 64 bit machine. In addition to stubbing out
functions that the kernel's initialization required.
Any other suggestions for finding problems proactively are appreciated.
- Joe
prev parent reply other threads:[~2013-02-15 0:51 UTC|newest]
Thread overview: 10+ 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 19:41 ` linux-next: Tree for Feb 13 (virtio_console) Randy Dunlap
2013-02-14 3:00 ` Rusty Russell
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
2013-02-15 0:23 ` Stephen Rothwell
2013-02-15 0:51 ` Joe Millenbach [this message]
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=CADwDc1AvrGP-YPd_h6jvfiUObvS3RWrt20ujTi3_cE_TrnHv9g@mail.gmail.com \
--to=jmillenbach@gmail.com \
--cc=amit.shah@redhat.com \
--cc=greg@kroah.com \
--cc=jamey@minilop.net \
--cc=josh@joshtriplett.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).