From: Eric Anholt <eric@anholt.net>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Stefan Wahren <stefan.wahren@i2se.com>,
bcm-kernel-feedback-list@broadcom.com,
Eric Anholt <eric@anholt.net>
Subject: [GIT PULL 3/4] bcm2835-defconfig-next-2018-07-03
Date: Tue, 3 Jul 2018 13:05:10 -0700 [thread overview]
Message-ID: <20180703200511.2725-3-eric@anholt.net> (raw)
In-Reply-To: <20180703200511.2725-1-eric@anholt.net>
The following changes since commit ce397d215ccd07b8ae3f71db689aedb85d56ab40:
Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)
are available in the Git repository at:
git://github.com/anholt/linux tags/bcm2835-defconfig-next-2018-07-03
for you to fetch changes up to 7b54aafff3ef4571567ff6a7d13ed51554f07a71:
ARM: multi_v7_defconfig: Enable RPi voltage sensor (2018-06-21 17:29:51 -0700)
----------------------------------------------------------------
This pull request enables the new RPi HWMON driver in the 32-bit
defconfigs.
----------------------------------------------------------------
Stefan Wahren (2):
ARM: bcm2835_defconfig: Enable RPi voltage sensor
ARM: multi_v7_defconfig: Enable RPi voltage sensor
arch/arm/configs/bcm2835_defconfig | 2 +-
arch/arm/configs/multi_v7_defconfig | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
next prev parent reply other threads:[~2018-07-03 20:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-03 20:05 [GIT PULL 1/4] bcm2835-dt-next-2018-07-03 Eric Anholt
2018-07-03 20:05 ` [GIT PULL 2/4] bcm2835-drivers-next-2018-07-03 Eric Anholt
2018-07-09 12:25 ` Florian Fainelli
2018-07-03 20:05 ` Eric Anholt [this message]
2018-07-09 12:25 ` [GIT PULL 3/4] bcm2835-defconfig-next-2018-07-03 Florian Fainelli
2018-07-03 20:05 ` [GIT PULL 4/4] bcm2835-defconfig-64-next-2018-07-03 Eric Anholt
2018-07-09 12:25 ` Florian Fainelli
2018-07-09 12:20 ` [GIT PULL 1/4] bcm2835-dt-next-2018-07-03 Florian Fainelli
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=20180703200511.2725-3-eric@anholt.net \
--to=eric@anholt.net \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=stefan.wahren@i2se.com \
/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
Powered by JetHome