From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Rikard Ljungstrand <lrikard@student.chalmers.se>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
apw@canonical.com
Subject: Re: [PATCH] Input: Add keyboard quirk for HP Pavilion ZV6100 laptop
Date: Sat, 10 Jan 2009 13:29:51 -0800 [thread overview]
Message-ID: <200901101329.51731.dmitry.torokhov@gmail.com> (raw)
In-Reply-To: <4968A391.2000400@student.chalmers.se>
On Saturday 10 January 2009 05:33:05 Rikard Ljungstrand wrote:
> Hi,
>
> Sending an updated version of a trivial patch from last November which got
> no feedback on the list. Applies cleanly against the latest input.git tree
> (and probably other recent trees).
>
It got applied silently ;) Its in mainline now, as part of 2.6.29.
--
Dmitry
next prev parent reply other threads:[~2009-01-10 21:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-10 13:33 [PATCH] Input: Add keyboard quirk for HP Pavilion ZV6100 laptop Rikard Ljungstrand
2009-01-10 21:29 ` Dmitry Torokhov [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-11-25 10:53 Rikard Ljungstrand
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=200901101329.51731.dmitry.torokhov@gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=apw@canonical.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lrikard@student.chalmers.se \
/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).