From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] MPU-3050 defconfig updates
Date: Mon, 9 Jan 2017 19:10:49 -0800 [thread overview]
Message-ID: <20170110031049.GC22261@localhost> (raw)
In-Reply-To: <20161227120530.31190-1-linus.walleij@linaro.org>
On Tue, Dec 27, 2016 at 01:05:27PM +0100, Linus Walleij wrote:
> Here are three defconfig patches to the ARM SoC tree that replace
> the use of the partial input driver for MPU-3050 with the fully featured
> IIO replacement driver.
>
> Please apply these directly for defconfig updates post-v4.10-rc1.
>
> Linus Walleij (3):
> ARM: defconfig: replace MPU3050 driver on multi_v7
> ARM: defconfig: tegra: switch to MPU3050 IIO driver
> ARM: defconfig: pxa: cut MPU3050 input driver
Applied to next/defconfig. Thanks!
-Olof
prev parent reply other threads:[~2017-01-10 3:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-27 12:05 [PATCH 0/3] MPU-3050 defconfig updates Linus Walleij
2016-12-27 12:05 ` [PATCH 1/3] ARM: defconfig: replace MPU3050 driver on multi_v7 Linus Walleij
2016-12-27 12:05 ` [PATCH 2/3] ARM: defconfig: tegra: switch to MPU3050 IIO driver Linus Walleij
2016-12-27 12:05 ` [PATCH 3/3] ARM: defconfig: pxa: cut MPU3050 input driver Linus Walleij
2017-01-10 3:10 ` Olof Johansson [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=20170110031049.GC22261@localhost \
--to=olof@lixom.net \
--cc=linux-arm-kernel@lists.infradead.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).