From: Martin Pitt <martin.pitt@ubuntu.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Bug#561711: udev: Samsung R70/R71 keymap
Date: Tue, 05 Jan 2010 15:57:15 +0000 [thread overview]
Message-ID: <20100105155715.GF26999@piware.de> (raw)
In-Reply-To: <20091219195300.GA19984@bongo.bofh.it>
[-- Attachment #1: Type: text/plain, Size: 312 bytes --]
Hello Clemens,
Clemens Buchacher [2010-01-05 16:51 +0100]:
> Good point. Yes, that fixes all keys.
Perfect, thanks for testing. I pushed your patch to udev.
Martin
--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2010-01-05 15:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-19 19:53 Bug#561711: udev: Samsung R70/R71 keymap Marco d'Itri
2009-12-21 8:25 ` Martin Pitt
2010-01-04 16:18 ` Clemens Buchacher
2010-01-05 8:58 ` Martin Pitt
2010-01-05 15:51 ` Clemens Buchacher
2010-01-05 15:57 ` Martin Pitt [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=20100105155715.GF26999@piware.de \
--to=martin.pitt@ubuntu.com \
--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).