From: Arnd Bergmann <arnd@arndb.de>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Stefan Wahren <stefan.wahren@i2se.com>,
Kevin Hilman <khilman@kernel.org>, Eric Anholt <eric@anholt.net>,
arm-soc <arm@kernel.org>,
bcm-kernel-feedback-list <bcm-kernel-feedback-list@broadcom.com>,
Olof Johansson <olof@lixom.net>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL 2/2] Broadcom soc fixes for 5.1
Date: Mon, 25 Mar 2019 17:06:19 +0100 [thread overview]
Message-ID: <CAK8P3a0vUYrqvJs-MMJWT59pbDyGY_FxSzqB_kPVGbzOSRTYdw@mail.gmail.com> (raw)
In-Reply-To: <20190319201642.4155-2-f.fainelli@gmail.com>
On Tue, Mar 19, 2019 at 9:16 PM Florian Fainelli <f.fainelli@gmail.com> wrote:
>
> The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:
>
> Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)
>
> are available in the Git repository at:
>
> https://github.com/Broadcom/stblinux.git tags/arm-soc/for-5.1/soc-fixes
>
> for you to fetch changes up to 4823a031f096d6d5fd16fccd8a3dd51b05a6becf:
>
> Merge tag 'tags/bcm2835-drivers-next-2019-03-12' into soc/fixes (2019-03-18 10:31:24 -0700)
>
> ----------------------------------------------------------------
> This pull request contains Broadcom ARM/ARM64-based SoCs fixes for 5.1,
> please pull the following:
>
> - Eric provides fixes for the bcm2835-pm driver: added missing depends
> on MFD_CORE for the ARM64 definition of ARCH_BCM2835, fixing error
> paths on initialization and fixing the PM_IMAGE_PERI power domain
>
Pulled into arm/fixes, thanks!
Arnd
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-03-25 16:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 20:16 [GIT PULL 1/2] Broadcom devicetree fixes for 5.1 Florian Fainelli
2019-03-19 20:16 ` [GIT PULL 2/2] Broadcom soc " Florian Fainelli
2019-03-25 16:06 ` Arnd Bergmann [this message]
2019-03-25 16:05 ` [GIT PULL 1/2] Broadcom devicetree " Arnd Bergmann
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=CAK8P3a0vUYrqvJs-MMJWT59pbDyGY_FxSzqB_kPVGbzOSRTYdw@mail.gmail.com \
--to=arnd@arndb.de \
--cc=arm@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=eric@anholt.net \
--cc=f.fainelli@gmail.com \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=olof@lixom.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.