From: Hans de Goede <hdegoede@redhat.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Hans de Goede <hdegoede@redhat.com>, linux-input@vger.kernel.org
Subject: [PATCH resend 0/4] Input: axp20x-pek and gpio_keys patches
Date: Wed, 8 Mar 2017 09:54:09 +0100 [thread overview]
Message-ID: <20170308085413.5185-1-hdegoede@redhat.com> (raw)
Hi,
These 4 patches seem to have fallen through the cracks, so I'm
resending them. They have been rebased on top of 4.11-rc1 (trivial
rebase).
Regards,
Hans
next reply other threads:[~2017-03-08 9:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 8:54 Hans de Goede [this message]
2017-03-08 8:54 ` [PATCH resend 1/4] Input: axp20x-pek - Use our own device for errors Hans de Goede
2017-03-08 8:54 ` [PATCH resend 2/4] Input: axp20x_pek - Add axp20x_pek_probe_input_device helper Hans de Goede
2017-03-08 8:54 ` [PATCH resend 3/4] Input: axp20x-pek - Do not register input device on some systems Hans de Goede
2017-03-08 17:16 ` Dmitry Torokhov
2017-03-09 7:56 ` Hans de Goede
2017-03-08 8:54 ` [PATCH resend 4/4] Input: gpio_keys - Do not report wake button presses as evdev events Hans de Goede
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=20170308085413.5185-1-hdegoede@redhat.com \
--to=hdegoede@redhat.com \
--cc=dmitry.torokhov@gmail.com \
--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).