From: Greg KH <greg@kroah.com>
To: Sven.Riedel@tu-clausthal.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: USB Keyboards with recent 2.4.19-pre/rcXX and 2.5.2X
Date: Thu, 25 Jul 2002 11:50:25 -0700 [thread overview]
Message-ID: <20020725185025.GI16518@kroah.com> (raw)
In-Reply-To: <20020725184637.GA12366@moog.heim1.tu-clausthal.de>
On Thu, Jul 25, 2002 at 08:46:37PM +0200, Sven.Riedel@tu-clausthal.de wrote:
> On Thu, Jul 25, 2002 at 11:15:19AM -0700, Greg KH wrote:
> > > > You _did_ run 'make oldconfig' when upgrading kernel versions, right?
> > > Uhm, no. What does that do? Never heard of it before...
> >
> > EVERY TIME you move a different .config file from a different kernel
> > version you HAVE to run 'make oldconfig' to fix up the differences.
> > This means everytime you upgrade your kernel version, you have to do it
> > before rebuilding the kernel.
>
> Well, actually I usually do go through the kernel in menuconfig and set
> all the options by hand. But I didn't consider that kernel option to be
> important for actually using the keyboard and mouse, because so far it
> had worked without this new option. And it didn't really scream for any
> attention whatsoever. So it got ignored. Happened to some of my friends
> too :). Maybe rename it to something that grabs your attention before
> .19 gets released :)
Nope, that's what 'make oldconfig' is there for. That combined with
reading the help entry for the new config items would have told you that
this was a necessary thing for you to enable.
thanks,
greg k-h
next prev parent reply other threads:[~2002-07-25 18:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-24 14:00 Sven.Riedel
2002-07-24 17:35 ` Greg KH
[not found] ` <20020725161221.GA10866@moog.heim1.tu-clausthal.de>
2002-07-25 18:15 ` Greg KH
[not found] ` <20020725184637.GA12366@moog.heim1.tu-clausthal.de>
2002-07-25 18:50 ` Greg KH [this message]
2002-07-25 21:39 ` Brad Hards
2002-07-26 18:47 ` Greg KH
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=20020725185025.GI16518@kroah.com \
--to=greg@kroah.com \
--cc=Sven.Riedel@tu-clausthal.de \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®