From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Daniel Mack <daniel@caiaq.de>
Cc: linux-input@vger.kernel.org
Subject: Re: [PATCH] generic driver for rotary encoders on GPIOs
Date: Tue, 3 Mar 2009 00:52:00 -0800 [thread overview]
Message-ID: <20090303085200.GA13793@dtor-d630.eng.vmware.com> (raw)
In-Reply-To: <20090302144308.GB11072@buzzloop.caiaq.de>
Hi Daniel,
On Mon, Mar 02, 2009 at 03:43:08PM +0100, Daniel Mack wrote:
> On Fri, Feb 27, 2009 at 03:15:23PM -0500, hartleys wrote:
> > Not sure if it matters but you can add my Tested-by if you like.
> >
> > Tested-by: H Hartley Sweeten <hsweeten@visionengravers.com>
> >
> > >> I have a minor patch to it that allows the platform init to
> > >> configure the absolute/relative axis to report the encoder on.
> > >> If you would like to see it I can put together a patch.
> > >
> > > Yes, and probably just post it as follow-up as soon as this one
> > > has been commited. I'm new to this list, so I don't know who
> > > can/will/wants to do this?
> >
> > Dmitry Torokhov is listed as the maintainer of the input drivers. I
> > think he needs to Ack the driver in order for it to be accepted and then
> > committed to the kernel.
>
> Dmitry, are you willing to take this patch? Just wanted to make sure
> it's not getting lost :)
>
I am willing, however I would like you to change it so you call
input_unregister_device() instead of input_free_device() in cases
when input device was successfully registered with the input core.
When input_register_device() fails (or if it wasn't invoked) then
you should call input_free_device().
Thanks!
--
Dmitry
next prev parent reply other threads:[~2009-03-03 8:52 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-26 18:00 [PATCH] generic driver for rotary encoders on GPIOs Daniel Mack
2009-02-26 18:42 ` Daniel Mack
2009-02-27 3:18 ` hartleys
2009-02-27 6:43 ` Daniel Mack
2009-02-27 8:48 ` Daniel Mack
2009-02-27 17:13 ` hartleys
2009-02-27 17:17 ` Daniel Mack
2009-02-27 18:00 ` Daniel Mack
2009-02-27 18:30 ` hartleys
2009-02-27 18:34 ` Daniel Mack
2009-02-27 20:15 ` hartleys
2009-03-02 14:43 ` Daniel Mack
2009-03-03 8:52 ` Dmitry Torokhov [this message]
2009-03-03 9:03 ` Dmitry Torokhov
2009-03-03 9:59 ` Daniel Mack
2009-03-04 8:48 ` Dmitry Torokhov
2009-03-04 9:50 ` Daniel Mack
2009-03-04 17:02 ` hartleys
2009-03-04 17:20 ` Daniel Mack
2009-03-07 17:06 ` Daniel Mack
2009-04-13 23:06 ` [PATCH] add REL_* axes support to the rotary encoder driver H Hartley Sweeten
2009-04-14 5:50 ` Daniel Mack
2009-04-14 15:33 ` H Hartley Sweeten
2009-04-16 2:08 ` Dmitry Torokhov
2009-04-16 2:24 ` H Hartley Sweeten
2009-04-16 2:33 ` Dmitry Torokhov
2009-04-16 3:11 ` H Hartley Sweeten
2009-04-16 6:35 ` Daniel Mack
2009-04-16 8:05 ` Daniel Mack
2009-04-16 16:48 ` H Hartley Sweeten
2009-04-16 8:39 ` Daniel Mack
2009-04-16 17:09 ` H Hartley Sweeten
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=20090303085200.GA13793@dtor-d630.eng.vmware.com \
--to=dmitry.torokhov@gmail.com \
--cc=daniel@caiaq.de \
--cc=linux-input@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).