From: Dmitry Osipenko <digetx@gmail.com>
To: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
"Michał Mirosław" <mirq-linux@rere.qmqm.pl>
Cc: Henrik Rydberg <rydberg@bitmath.org>,
James Chen <james.chen@emc.com.tw>,
Johnny Chuang <johnny.chuang@emc.com.tw>,
Scott Liu <scott.liu@emc.com.tw>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 5/5] input: mt: cleanup open-coded __set_bit()
Date: Thu, 13 Aug 2020 21:33:19 +0300 [thread overview]
Message-ID: <eddb596c-dfd0-b32f-344f-7a494e78a43f@gmail.com> (raw)
In-Reply-To: <20200716003047.GA1665100@dtor-ws>
16.07.2020 03:30, Dmitry Torokhov пишет:
> On Mon, Jul 13, 2020 at 02:24:55AM +0200, Michał Mirosław wrote:
>> Replace open-coded __set_bit() with the function.
>>
>> Signed-off-by: Michał Mirosław <mirq-linux@rere.qmqm.pl>
>
> Applied, thank you.
>
Hello, Dmitry!
Could you please let us know how we could proceed with applying the rest
of the patches?
The device-tree for Nexus 7 2012 [1] has been merged into upcoming v5.9
and I'd want to add the touchscreen support.
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=2720008f4239cf36d57b8d0b3cb2a49d4368a378
The missing elants_i2c driver functionality doesn't really block making
a device-tree change since elants_i2c.yaml DT binding already supports
the ektf3624 TS model, but will be nice to get a full featured support.
Thanks in advance!
prev parent reply other threads:[~2020-08-13 18:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 0:24 [PATCH v6 0/5] input: elants: Support Asus TF300T touchscreen Michał Mirosław
2020-07-13 0:24 ` [PATCH v6 1/5] input: elants: document some registers and values Michał Mirosław
2020-07-13 0:24 ` [PATCH v6 2/5] input: elants: support old touch report format Michał Mirosław
2020-07-13 0:24 ` [PATCH v6 3/5] input: elants: read touchscreen size for EKTF3624 Michał Mirosław
2020-07-13 0:24 ` [PATCH v6 4/5] input: elants: support 0x66 reply opcode for reporting touches Michał Mirosław
2020-07-13 0:24 ` [PATCH v6 5/5] input: mt: cleanup open-coded __set_bit() Michał Mirosław
2020-07-16 0:30 ` Dmitry Torokhov
2020-08-13 18:33 ` Dmitry Osipenko [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=eddb596c-dfd0-b32f-344f-7a494e78a43f@gmail.com \
--to=digetx@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=james.chen@emc.com.tw \
--cc=johnny.chuang@emc.com.tw \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mirq-linux@rere.qmqm.pl \
--cc=rydberg@bitmath.org \
--cc=scott.liu@emc.com.tw \
/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.