linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Stezenbach <js@sig21.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] keymap: support for force_release quirk
Date: Mon, 14 Dec 2009 12:55:07 +0000	[thread overview]
Message-ID: <20091214125507.GA29808@sig21.net> (raw)
In-Reply-To: <20091214001219.GA17792@sig21.net>

Hello Martin,

On Mon, Dec 14, 2009 at 01:45:43PM +0100, Martin Pitt wrote:
> Johannes Stezenbach [2009-12-14 13:37 +0100]:
> 
> > However, what does not work this way is to remove scancodes from
> > force_release. I thought that was what Martin wanted to accomplish
> > on the "change" event.
> 
> Hm, it seems to work just fine here:
> 
> $ echo 133 | sudo tee /sys/devices/platform/i8042/serio0/force_release133
> $ cat /sys/devices/platform/i8042/serio0/force_release
> 133
> 
> So it seems every time you write the file you have to do it completely
> (or read the original one).

Yes, that was my question: Can I just save the original at boot
(first "add" event) into a file (like /dev/.udev/force-release/serioX)?

> So I think your approach is fine after all, and we just need the other
> small cleanups.

Yes, will resend a cleaned up patch asap.


BTW, 95-keymap.rules also doesn't handle "change". Does it need updating
or is there a difference in handling "change" for force_release?


Thanks,
Johannes

  parent reply	other threads:[~2009-12-14 12:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-14  0:12 [PATCH] keymap: support for force_release quirk Johannes Stezenbach
2009-12-14  9:14 ` Martin Pitt
2009-12-14 10:28 ` Johannes Stezenbach
2009-12-14 10:34 ` Kay Sievers
2009-12-14 12:37 ` Johannes Stezenbach
2009-12-14 12:45 ` Martin Pitt
2009-12-14 12:50 ` Kay Sievers
2009-12-14 12:55 ` Johannes Stezenbach [this message]
2009-12-14 13:32 ` Martin Pitt

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=20091214125507.GA29808@sig21.net \
    --to=js@sig21.net \
    --cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).