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 for v5.16
Date: Wed, 17 Nov 2021 23:11:36 +0100 [thread overview]
Message-ID: <20211117221136.GA16740@alpha.franken.de> (raw)
The following changes since commit fa55b7dcdc43c1aa1ba12bca9d2dd4318c2a0dbf:
Linux 5.16-rc1 (2021-11-14 13:56:52 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git/ tags/mips-fixes_5.16_1
for you to fetch changes up to fc1aabb088860d6cf9dd03612b7a6f0de91ccac2:
mips: lantiq: add support for clk_get_parent() (2021-11-16 09:27:40 +0100)
----------------------------------------------------------------
- wire futex_waitv syscall
- build fixes for lantiq and bcm63xx configs
- yamon-dt bugfix
----------------------------------------------------------------
Colin Ian King (1):
MIPS: generic/yamon-dt: fix uninitialized variable error
Randy Dunlap (2):
mips: bcm63xx: add support for clk_get_parent()
mips: lantiq: add support for clk_get_parent()
Wang Haojun (1):
MIPS: syscalls: Wire up futex_waitv syscall
arch/mips/bcm63xx/clk.c | 6 ++++++
arch/mips/generic/yamon-dt.c | 2 +-
arch/mips/kernel/syscalls/syscall_n32.tbl | 1 +
arch/mips/kernel/syscalls/syscall_n64.tbl | 1 +
arch/mips/kernel/syscalls/syscall_o32.tbl | 1 +
arch/mips/lantiq/clk.c | 6 ++++++
6 files changed, 16 insertions(+), 1 deletion(-)
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next reply other threads:[~2021-11-17 22:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 22:11 Thomas Bogendoerfer [this message]
2021-11-17 23:58 ` [GIT PULL] MIPS fixes for v5.16 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2021-11-27 9:43 Thomas Bogendoerfer
2021-11-27 18:58 ` pr-tracker-bot
2021-12-19 10:54 Thomas Bogendoerfer
2021-12-19 20:34 ` 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=20211117221136.GA16740@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