public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: Alejandro Bonilla Beeche <abonilla@linuxwireless.org>,
	linux-kernel@vger.kernel.org, rml@novell.com
Subject: Re: Kernel Badness 2.6.14-Git
Date: Tue, 1 Nov 2005 00:14:33 -0800	[thread overview]
Message-ID: <20051101081433.GB28048@kroah.com> (raw)
In-Reply-To: <200511010258.14313.dtor_core@ameritech.net>

On Tue, Nov 01, 2005 at 02:58:13AM -0500, Dmitry Torokhov wrote:
> On Tuesday 01 November 2005 02:35, Greg KH wrote:
> > On Mon, Oct 31, 2005 at 10:21:12PM -0500, Dmitry Torokhov wrote:
> > > On Friday 28 October 2005 22:17, Greg KH wrote:
> > > > On Fri, Oct 28, 2005 at 06:18:57PM -0600, Alejandro Bonilla Beeche wrote:
> > > > > Hi,
> > > > > 
> > > > >    I just pulled from Linus Tree and I'm getting this badness in dmesg.
> > > > > 
> > > > > Please let me know if it is too soon to start reporting this. 2.6.14 is 
> > > > > OK and does not output this.
> > > > 
> > > > If you disable PNP does it go away?
> > > > 
> > > > Dmitry, any thoughts?  This looks like the other reported issue.
> > > >
> > > 
> > > I was looking and looking and the only thing I could come up with is
> > > that we probably need to initialize input core earlier, before other
> > > modules had a chance to use input interface so input class is fully
> > > initialized. We don't need to have input/{ev|mouse|ts|joy}dev.o,
> > > just input/input.o itself.
> > 
> > Then why not move this input driver into a different directory so it
> > doesn't cause this issue?
> >
> 
> Can't we move just input.o closer to the top of drivers/Makefile? It is
> kinda silly to have a subdirectory with only one file. And I would move
> serio.o there as well.

I don't have a problem with this, try it out and see what breaks :)

thanks,

greg k-h

  reply	other threads:[~2005-11-01  8:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-29  0:18 Kernel Badness 2.6.14-Git Alejandro Bonilla Beeche
2005-10-29  3:17 ` Greg KH
2005-11-01  3:21   ` Dmitry Torokhov
2005-11-01  7:35     ` Greg KH
2005-11-01  7:58       ` Dmitry Torokhov
2005-11-01  8:14         ` Greg KH [this message]
2005-11-01 14:11           ` Robert Love
2005-11-01 14:45             ` Alejandro Bonilla
2005-11-01 16:38               ` Dmitry Torokhov
2005-11-01 17:22                 ` Alejandro Bonilla
2005-11-01 18:00                   ` Dmitry Torokhov
2005-11-03  4:37                   ` Dmitry Torokhov
2005-11-01 15:21             ` Bill Davidsen
2005-11-01 15:28               ` Dmitry Torokhov

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=20051101081433.GB28048@kroah.com \
    --to=greg@kroah.com \
    --cc=abonilla@linuxwireless.org \
    --cc=dtor_core@ameritech.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@novell.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