From: Florian Fainelli <f.fainelli@gmail.com>
To: soc@kernel.org
Cc: Liang He <windhl@126.com>,
Florian Fainelli <f.fainelli@gmail.com>,
linux-arm-kernel@lists.infradead.org, arnd@arndb.de,
olof@lixom.net, khilman@kernel.org,
bcm-kernel-feedback-list@broadcom.com
Subject: [GIT PULL 2/2] Broadcom drivers fixes for 6.0
Date: Mon, 29 Aug 2022 15:51:03 -0700 [thread overview]
Message-ID: <20220829225103.753223-2-f.fainelli@gmail.com> (raw)
In-Reply-To: <20220829225103.753223-1-f.fainelli@gmail.com>
The following changes since commit 568035b01cfb107af8d2e4bd2fb9aea22cf5b868:
Linux 6.0-rc1 (2022-08-14 15:50:18 -0700)
are available in the Git repository at:
https://github.com/Broadcom/stblinux.git tags/arm-soc/for-6.0/drivers-fixes
for you to fetch changes up to 1085f5080647f0c9f357c270a537869191f7f2a1:
soc: brcmstb: pm-arm: Fix refcount leak and __iomem leak bugs (2022-08-29 10:30:22 -0700)
----------------------------------------------------------------
This pull request contains Broadcom SoCs driver fixes for 6.0, please
pull the following:
- Liang fixes the legacy Broadcom STB ARM system suspend/resume code
error paths that were leaking ioremap() and other of_* operations
----------------------------------------------------------------
Liang He (1):
soc: brcmstb: pm-arm: Fix refcount leak and __iomem leak bugs
drivers/soc/bcm/brcmstb/pm/pm-arm.c | 50 +++++++++++++++++++++++++++++--------
1 file changed, 39 insertions(+), 11 deletions(-)
next prev parent reply other threads:[~2022-08-29 22:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 22:51 [GIT PULL 1/2] Broadcom devicetree fixes for 6.0 Florian Fainelli
2022-08-29 22:51 ` Florian Fainelli [this message]
2022-09-02 11:00 ` patchwork-bot+linux-soc
2022-09-02 11:00 ` patchwork-bot+linux-soc
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=20220829225103.753223-2-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=olof@lixom.net \
--cc=soc@kernel.org \
--cc=windhl@126.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