From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: torvalds@linux-foundation.org
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] MIPS fixes vor v5.19
Date: Thu, 23 Jun 2022 18:40:32 +0200 [thread overview]
Message-ID: <20220623164032.GA14476@alpha.franken.de> (raw)
The following changes since commit a111daf0c53ae91e71fd2bfe7497862d14132e3e:
Linux 5.19-rc3 (2022-06-19 15:06:47 -0500)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git/ tags/mips-fixes_5.19_2
for you to fetch changes up to 3748d2185ac4c2c6f80989672253aad909ecaf95:
mips: lantiq: Add missing of_node_put() in irq.c (2022-06-21 22:34:03 +0200)
----------------------------------------------------------------
- several refcount fixes
- added missing clock for ingenic
- fix wrong irq_err_count for vr41xx
----------------------------------------------------------------
Aidan MacDonald (1):
mips: dts: ingenic: Add TCU clock to x1000/x1830 tcu device node
Liang He (7):
arch: mips: generic: Add missing of_node_put() in board-ranchu.c
mips: mti-malta: Fix refcount leak in malta-time.c
mips: ralink: Fix refcount leak in of.c
mips: lantiq: falcon: Fix refcount leak bug in sysctrl
mips: lantiq: xway: Fix refcount leak bug in sysctrl
mips/pic32/pic32mzda: Fix refcount leak bugs
mips: lantiq: Add missing of_node_put() in irq.c
huhai (1):
MIPS: Remove repetitive increase irq_err_count
arch/mips/boot/dts/ingenic/x1000.dtsi | 5 +++--
arch/mips/boot/dts/ingenic/x1830.dtsi | 5 +++--
arch/mips/generic/board-ranchu.c | 1 +
arch/mips/lantiq/falcon/sysctrl.c | 6 ++++++
arch/mips/lantiq/irq.c | 1 +
arch/mips/lantiq/xway/sysctrl.c | 4 ++++
arch/mips/mti-malta/malta-time.c | 2 ++
arch/mips/pic32/pic32mzda/init.c | 7 ++++++-
arch/mips/pic32/pic32mzda/time.c | 3 +++
arch/mips/ralink/of.c | 2 ++
arch/mips/vr41xx/common/icu.c | 2 --
drivers/gpio/gpio-vr41xx.c | 2 --
12 files changed, 31 insertions(+), 9 deletions(-)
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next reply other threads:[~2022-06-23 16:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 16:40 Thomas Bogendoerfer [this message]
2022-06-23 17:19 ` [GIT PULL] MIPS fixes vor v5.19 pr-tracker-bot
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=20220623164032.GA14476@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=torvalds@linux-foundation.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