From: Stefan Wahren <wahrenst@gmx.net>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Stefan Wahren <wahrenst@gmx.net>, Eric Anholt <eric@anholt.net>,
linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/3] bcm2835-defconfig-next-2019-08-15
Date: Thu, 15 Aug 2019 20:34:02 +0200 [thread overview]
Message-ID: <1565894043-5249-2-git-send-email-wahrenst@gmx.net> (raw)
In-Reply-To: <1565894043-5249-1-git-send-email-wahrenst@gmx.net>
Hi Florian,
The following changes since commit 5f9e832c137075045d15cd6899ab0505cfb2ca4b:
Linus 5.3-rc1 (2019-07-21 14:05:38 -0700)
are available in the git repository at:
git://github.com/anholt/linux tags/bcm2835-defconfig-next-2019-08-15
for you to fetch changes up to 4c6f5d4038af2c7332630bdd75cfdc0309e97242:
ARM: defconfig: enable cpufreq driver for RPi (2019-07-23 22:53:35 +0200)
----------------------------------------------------------------
This pull request enables the new RPi cpufreq driver in the 32-bit
defconfigs.
----------------------------------------------------------------
Nicolas Saenz Julienne (1):
ARM: defconfig: enable cpufreq driver for RPi
arch/arm/configs/bcm2835_defconfig | 9 +++++++++
arch/arm/configs/multi_v7_defconfig | 2 ++
2 files changed, 11 insertions(+)
next prev parent reply other threads:[~2019-08-15 18:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 18:34 [GIT PULL 1/3] bcm2835-dt-next-2019-08-15 Stefan Wahren
2019-08-15 18:34 ` Stefan Wahren [this message]
2019-08-15 22:56 ` [GIT PULL 2/3] bcm2835-defconfig-next-2019-08-15 Florian Fainelli
2019-08-15 18:34 ` [GIT PULL 3/3] bcm2835-defconfig-64-next-2019-08-15 Stefan Wahren
2019-08-15 22:57 ` Florian Fainelli
2019-08-15 22:56 ` [GIT PULL 1/3] bcm2835-dt-next-2019-08-15 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=1565894043-5249-2-git-send-email-wahrenst@gmx.net \
--to=wahrenst@gmx.net \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=eric@anholt.net \
--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 \
/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).