From: Arnd Bergmann <arnd@arndb.de>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Input: two merge window build fixes
Date: Thu, 19 May 2016 15:52:23 +0200 [thread overview]
Message-ID: <1463665954-3898044-1-git-send-email-arnd@arndb.de> (raw)
Hi Dmitry,
I ran into two new build regressions in the input subsystem with
today's linux-next, maybe you can apply these fixes before sending
off the pull request for v4.7.
Arnd
[PATCH 1/2] Input: atmel captouch depends on i2c
[PATCH 2/2] Input: migor-ts: mark PM functions as __maybe_unused
next reply other threads:[~2016-05-19 13:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 13:52 Arnd Bergmann [this message]
2016-05-19 13:52 ` [PATCH 1/2] Input: atmel captouch depends on i2c Arnd Bergmann
2016-05-19 13:52 ` [PATCH 2/2] Input: migor-ts: mark PM functions as __maybe_unused Arnd Bergmann
2016-05-19 16:15 ` Input: two merge window build fixes 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=1463665954-3898044-1-git-send-email-arnd@arndb.de \
--to=arnd@arndb.de \
--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).