All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Slepov <sir-lexa@yandex.ru>
To: Rob Herring <robh@kernel.org>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Donghoon Han <nazgul33@gmail.com>,
	linux-input@vger.kernel.org, Daniel Mack <daniel@caiaq.de>,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: Re: [PATCH V2 2/2] Input: rotaty-encoder - Add DT binding document
Date: Fri, 22 Mar 2019 02:04:59 +0100	[thread overview]
Message-ID: <f780ef34-474b-3e23-b495-f2e80e87c18b@yandex.ru> (raw)
In-Reply-To: <20190115202948.GA26482@bogus>

Hello,

i used this rotary-encoder patch in my embedded project and found two 
errors:


First, in drivers/input/misc/rotary_encoder.c,
at @@ -237,6 +244,16 @@:
instead of

+        if (err)
+            dev_err(dev, "unable to get keycodes: %d\n", err);
+        return err;

it must be

+        if (err) {
+            dev_err(dev, "unable to get keycodes: %d\n", err);
+            return err;
+        }

otherwise successful creation of device is not possible.


Second, a typo in 
Documentation/devicetree/bindings/input/rotary-encoder.txt,
at @@ -48,3 +52,11 @@:
instead of

+            rotary-encoder,relative-keycode = <103>, <108>;

it should be

+            rotary-encoder,relative-keycodes = <103>, <108>;

otherwise keycodes are not found.


I am sorry, I know that E-Mail style is not good.
I have no time right now, but I'll be back in two weeks.
Someone, maybe Mr. Han, could submit a new version of the patch.
If not, I'll try to do it on my return. (it could take some time, since 
I am new to patchwork)

Best Regards and thanks
Alexey Slepov

  reply	other threads:[~2019-03-22  1:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-07 16:42 [PATCH V2 0/2] input: rotary-encoder: Support key events Donghoon Han
2019-01-07 16:42 ` [PATCH V2 1/2] Input: rotary_encoder - " Donghoon Han
2019-01-07 16:42 ` [PATCH V2 2/2] Input: rotaty-encoder - Add DT binding document Donghoon Han
2019-01-14 20:16   ` Rob Herring
2019-01-15  3:52   ` Dmitry Torokhov
2019-01-15 20:29     ` Rob Herring
2019-03-22  1:04       ` Alexey Slepov [this message]
2019-01-15  3:53   ` Dmitry Torokhov

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=f780ef34-474b-3e23-b495-f2e80e87c18b@yandex.ru \
    --to=sir-lexa@yandex.ru \
    --cc=daniel@caiaq.de \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nazgul33@gmail.com \
    --cc=robh@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 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.