linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomasz Kramkowski <tk@the-tk.com>
To: "Diego Elio Pettenò" <flameeyes@flameeyes.eu>
Cc: Yuxuan Shui <yshuiv7@gmail.com>, Jiri Kosina <jikos@kernel.org>,
	Benjamin Tissoires <benjamin.tissoires@redhat.com>,
	Alex Manoussakis <amanou@gnu.org>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] HID: elecom: fix the descriptor of the EX-G trackball
Date: Sun, 19 Nov 2017 01:04:16 +0000	[thread overview]
Message-ID: <20171119010416.GB15931@gaia.local> (raw)
In-Reply-To: <CAHcsgXR0_q9tFodLYMddBa1Qc2SMqsN02ncY0WKYQ72SRq2oAQ@mail.gmail.com>

On Sun, Nov 19, 2017 at 12:31:45AM +0000, Diego Elio Pettenò wrote:
> Please do not drop the explicit documentation of the diff. Looking at what
> a driver does in three years is not going to be obvious, whether you know
> HID or not.

I'm sure there are situations where this is true but I've just gone
through the first six HID drivers in the order that grep found them in
when I searched for "report_fixup" and in all but one I was either
informed of the issue and the fix using a short and concise comment,
annotations on the replacement descriptor or the commit message. The one
report_fixup which was unclear had been moved out of hid-input-quirks.c
(when it was a thing) and I didn't actually feel like finding its
original commit message, it could probably have been clarified by a
rather simple comment.

Even the existing report_fixup of the BM084 has a one line comment which
entirely explains what the problem is.

I really don't think a big diagram showing the difference between two
report descriptors, which may or may not completely overlap with the
report descriptors of other devices exhibiting a similar issue, is
necessary.

Please also note that the documentation is not gone, it's just
shortened and generalised, there is still more than enough information
to work out exactly what the report change is.

-- 
Tomasz Kramkowski | GPG: 40B037BA0A5B8680 | Web: https://the-tk.com/

      parent reply	other threads:[~2017-11-19  1:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAGqt0zx0KZonRH9TqVEwNYe3rzkxTGPcuLqhyERvcWHk4CJueg@mail.gmail.com>
2017-10-20 17:32 ` [PATCH] HID: elecom: fix the descriptor of the EX-G trackball Yuxuan Shui
2017-11-18 22:27   ` Tomasz Kramkowski
2017-11-19  0:23     ` Tomasz Kramkowski
     [not found]       ` <CAHcsgXR0_q9tFodLYMddBa1Qc2SMqsN02ncY0WKYQ72SRq2oAQ@mail.gmail.com>
2017-11-19  1:04         ` Tomasz Kramkowski [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=20171119010416.GB15931@gaia.local \
    --to=tk@the-tk.com \
    --cc=amanou@gnu.org \
    --cc=benjamin.tissoires@redhat.com \
    --cc=flameeyes@flameeyes.eu \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yshuiv7@gmail.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 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).