From: "Udo A. Steinberg" <reality@delusion.de>
To: Andrew Morton <akpm@zip.com.au>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: release() locking
Date: Fri, 07 Dec 2001 15:54:54 +0100 [thread overview]
Message-ID: <3C10D83E.81261D74@delusion.de> (raw)
Hi Andrew,
According to Linus' 2.5.1-pre changelog, the release locking changes
introduced in -pre5 are your work. Those changes, however, seem to
break the keyboard driver:
keyboard: Timeout - AT keyboard not present?(f4)
Other people (i.e. Mike Galbraith) have been experiencing the same.
Do you have an updated patch which fixes those issues? -pre6 still
contains the same stuff as -pre5 and if it's broken then Linus should
probably back it out.
Regards,
Udo.
next reply other threads:[~2001-12-07 14:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-07 14:54 Udo A. Steinberg [this message]
2001-12-07 17:35 ` release() locking Andrew Morton
2001-12-07 17:42 ` Udo A. Steinberg
2001-12-07 21:49 ` David C. Hansen
2001-12-07 22:06 ` Udo A. Steinberg
2001-12-07 22:16 ` Andrew Morton
2001-12-07 22:51 ` David C. Hansen
2001-12-07 23:17 ` Udo A. Steinberg
2001-12-07 23:32 ` Andrew Morton
2001-12-07 23:54 ` Udo A. Steinberg
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=3C10D83E.81261D74@delusion.de \
--to=reality@delusion.de \
--cc=akpm@zip.com.au \
--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