From: "Enrico Weigelt, metux IT consult" <info@metux.net>
To: linux-kernel@vger.kernel.org
Cc: dmitry.torokhov@gmail.com, linux-input@vger.kernel.org
Subject: gpio-keys-polled improvements v2
Date: Fri, 26 Apr 2019 21:01:19 +0200 [thread overview]
Message-ID: <1556305282-24148-1-git-send-email-info@metux.net> (raw)
Hello folks,
here's v2 of my gpio-keys-polled queue.
changes v2:
* removed the change in mod_devicetable.h
(MODULE_DEVICE_TABLE_OF macro)
* reworked the patch for building w/o oftree, so it works
w/o the MODULE_DEVICE_TABLE_OF macro
have fun,
--mtx
next reply other threads:[~2019-04-26 19:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 19:01 Enrico Weigelt, metux IT consult [this message]
2019-04-26 19:01 ` [PATCH v2 1/3] input: keyboard: gpio-keys-polled: use input name from pdata if available Enrico Weigelt, metux IT consult
2019-04-26 19:01 ` [PATCH v2 2/3] input: keyboard: gpio_keys_polled: use gpio lookup table Enrico Weigelt, metux IT consult
2019-04-26 20:16 ` Sven Van Asbroeck
2019-04-26 19:01 ` [PATCH v2 3/3] input: keyboard: gpio-keys-polled: skip oftree code when CONFIG_OF disabled Enrico Weigelt, metux IT consult
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=1556305282-24148-1-git-send-email-info@metux.net \
--to=info@metux.net \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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).