linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input <linux-input@atrey.karlin.mff.cuni.cz>
Subject: Re: bug in evdev_disconnect
Date: Fri, 27 Apr 2007 21:58:10 +0200	[thread overview]
Message-ID: <1177703890.3565.49.camel@johannes.berg> (raw)
In-Reply-To: <d120d5000704271207t3b86d32fu88f438fe3efbc612@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 209 bytes --]

Hi Dmitry,

> Please try -mm, it should be fixed there. As a temporary work wround
> you can also swap list_for_each() and wake_up_interruptible() in
> evdev_disconnect().

Alright, thanks!

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

      reply	other threads:[~2007-04-27 19:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-27 14:26 bug in evdev_disconnect Johannes Berg
2007-04-27 19:07 ` Dmitry Torokhov
2007-04-27 19:58   ` Johannes Berg [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=1177703890.3565.49.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@atrey.karlin.mff.cuni.cz \
    /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).