From: Kay Sievers <kay.sievers@vrfy.org>
To: "Dr.Dre" <pharon@gmail.com>
Cc: Greg KH <greg@kroah.com>,
jirislaby@gmail.com, dominik.karall@gmx.net,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.14-rc1-mm1
Date: Sat, 17 Sep 2005 03:29:24 +0200 [thread overview]
Message-ID: <20050917012924.GA30024@vrfy.org> (raw)
In-Reply-To: <5d8b7b90509161818a4616d9@mail.gmail.com>
On Sat, Sep 17, 2005 at 04:18:37AM +0300, Dr.Dre wrote:
> On 9/17/05, Greg KH <greg@kroah.com> wrote:
> > On Fri, Sep 16, 2005 at 07:53:32PM -0400, Valdis.Kletnieks@vt.edu wrote:
> > > On Fri, 16 Sep 2005 14:30:04 PDT, Greg KH said:
> > > > > > >On Friday 16 September 2005 11:23, Andrew Morton wrote:
> > > > > > >>ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc1/2.6.14-rc1-mm1/
> > >
> > > > Yes, Andrew, can you please drop these patches, they will cause lots of
> > > > problems with users due to the above mentioned issues.
> > >
> > > For those of us playing along at home -
> > >
> > > Would doing a 'patch -R' of all 30 patches listed in "Big input/sysfs changes"
> > > be needed?
> >
> > That's probably the safest.
> >
> > > Or just the 'input-prepare-to-sysfs-integration.patch' and following?
> >
> > Don't really know if stuff would still build if you only reverted that
> > one.
> just a notice here:
> I had to install udev-70 to fix the "blocked udev" problem, then
> noticed the missing /dev/input/mice problem because neither gpm nor X
> would start.
>
> So I recompiled with this feature as a module ( mousedev ) and
> rebooted to find udev started to create the node. ( I didn't reverse
> any patches.)
Cause the "udev event" works, but "udevstart" doesn't. So, if you are
lucky, the module load will trigger the events to create the nodes.
Kay
next prev parent reply other threads:[~2005-09-17 1:29 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-16 9:23 2.6.14-rc1-mm1 Andrew Morton
2005-09-16 9:45 ` 2.6.14-rc1-mm1 Pekka Enberg
2005-09-16 10:17 ` 2.6.14-rc1-mm1 Anton Blanchard
2005-09-16 20:55 ` 2.6.14-rc1-mm1 Sonny Rao
2005-09-19 20:01 ` 2.6.14-rc1-mm1 Sonny Rao
2005-09-16 12:20 ` [PATCH] drivers/base: a little speedup and cleanup Jiri Slaby
2005-09-16 15:48 ` Dmitry Torokhov
2005-09-16 17:49 ` 2.6.14-rc1-mm1 Serge E. Hallyn
2005-09-16 18:41 ` 2.6.14-rc1-mm1 Dominik Karall
2005-09-16 19:46 ` 2.6.14-rc1-mm1 Jiri Slaby
2005-09-16 19:59 ` 2.6.14-rc1-mm1 Kay Sievers
2005-09-16 20:04 ` 2.6.14-rc1-mm1 Jiri Slaby
2005-09-16 21:30 ` 2.6.14-rc1-mm1 Greg KH
2005-09-16 23:53 ` 2.6.14-rc1-mm1 Valdis.Kletnieks
2005-09-17 0:10 ` 2.6.14-rc1-mm1 Greg KH
2005-09-17 1:18 ` 2.6.14-rc1-mm1 Dr.Dre
2005-09-17 1:29 ` Kay Sievers [this message]
2005-09-17 0:15 ` 2.6.14-rc1-mm1 Andrew Morton
2005-09-17 4:09 ` 2.6.14-rc1-mm1 Valdis.Kletnieks
2005-09-17 1:22 ` 2.6.14-rc1-mm1 Avuton Olrich
2005-09-17 4:41 ` 2.6.14-rc1-mm1 Andrew Morton
2005-09-17 10:10 ` 2.6.14-rc1-mm1 Neil Brown
2005-09-17 1:51 ` 2.6.14-rc1-mm1 Martin J. Bligh
2005-09-17 4:22 ` 2.6.14-rc1-mm1 Martin J. Bligh
2005-09-17 4:25 ` [PATCH] mips: Fixed build error Yoichi Yuasa
2005-09-17 4:33 ` Andrew Morton
2005-09-17 5:27 ` Yoichi Yuasa
2005-09-20 22:42 ` one more oops on sensor modules removal J.A. Magallon
2005-09-21 5:56 ` Andrew Morton
2005-09-21 8:52 ` Grant Coady
2005-10-01 11:39 ` Jean Delvare
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=20050917012924.GA30024@vrfy.org \
--to=kay.sievers@vrfy.org \
--cc=dominik.karall@gmx.net \
--cc=greg@kroah.com \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pharon@gmail.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