From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Chris Diamand <chris@diamand.org>
Cc: Tommy Will <tommywill2011@gmail.com>,
Kevin Cernekee <cernekee@gmail.com>,
Yunkang Tang <yunkang.tang@cn.alps.com>,
david turvene <dturvene@dahetral.com>,
linux-input@vger.kernel.org
Subject: Re: [PATCH] Input: ALPS - Recognise "Dolphin V2" touchpads
Date: Tue, 7 Jan 2014 10:59:09 -0800 [thread overview]
Message-ID: <20140107185909.GC31842@core.coreip.homeip.net> (raw)
In-Reply-To: <52CC47C5.4090307@diamand.org>
Hi Chris,
On Tue, Jan 07, 2014 at 06:30:29PM +0000, Chris Diamand wrote:
> Hi, and thanks for your reply.
>
> >Umm, however, I had submited a similar patch for supporting dolphin v2
> >device last month and it was now applied into latest mainline.
>
> Do you mean commit 'ee65d4...add support for "Dolphin" devices'?
>
> It's in the dtor/input.git kernel but I don't think it's been merged
> into mainline (torvalds/linux.git).
>
> Running 'git log drivers/input/mouse/alps.c' with the latest
> mainline kernel shows the last commit as '95f75e...add support for
> DualPoint device on Dell XT2 model', which doesn't work with my
> device (Dell Vostro 3360).
>
> Are there any plans for it to be merged? It looks like your patch
> fixes it much better than mine ;)
Yes, it will be merged together with all other changes to the input
subsystem when the next merge window opens.
Thanks.
--
Dmitry
prev parent reply other threads:[~2014-01-07 18:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 20:10 [PATCH] Input: ALPS - Recognise "Dolphin V2" touchpads Chris Diamand
[not found] ` <CAKvfdtK18rQ4TOqwKCj1P3oQs-BQZr2h3db5NH18WdtNjjnH=g@mail.gmail.com>
2014-01-07 16:24 ` Tommy Will
2014-01-07 18:30 ` Chris Diamand
2014-01-07 18:59 ` Dmitry Torokhov [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=20140107185909.GC31842@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=cernekee@gmail.com \
--cc=chris@diamand.org \
--cc=dturvene@dahetral.com \
--cc=linux-input@vger.kernel.org \
--cc=tommywill2011@gmail.com \
--cc=yunkang.tang@cn.alps.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.