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.18
Date: Sat, 2 Apr 2022 13:27:19 +0200 [thread overview]
Message-ID: <20220402112719.GA5234@alpha.franken.de> (raw)
The following changes since commit f8f9f21c7848e63133c16c899f3d84aa54eb79fe:
MIPS: Fix build error for loongson64 and sgi-ip27 (2022-03-24 09:45:15 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git/ tags/mips_5.18_1
for you to fetch changes up to 41022eff9c2d21e658c7a6fcd31005bf514d28b7:
MIPS: crypto: Fix CRC32 code (2022-04-01 10:19:03 +0200)
----------------------------------------------------------------
- build fix for gpio
- fix crc32 build problems
- check for failed memory allocations
----------------------------------------------------------------
Jackie Liu (1):
MIPS: rb532: move GPIOD definition into C-files
Paul Cercueil (1):
MIPS: crypto: Fix CRC32 code
Xiaoke Wang (2):
mips: sgi-ip22: add a check for the return of kzalloc()
MIPS: lantiq: check the return value of kzalloc()
arch/mips/crypto/crc32-mips.c | 46 +++++++++++++++++++--------------
arch/mips/include/asm/mach-rc32434/rb.h | 9 -------
arch/mips/lantiq/falcon/sysctrl.c | 2 ++
arch/mips/lantiq/xway/gptu.c | 2 ++
arch/mips/lantiq/xway/sysctrl.c | 46 +++++++++++++++++++++------------
arch/mips/rb532/gpio.c | 10 +++++++
arch/mips/sgi-ip22/ip22-gio.c | 2 ++
7 files changed, 72 insertions(+), 45 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-04-02 11:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-02 11:27 Thomas Bogendoerfer [this message]
2022-04-02 20:00 ` [GIT PULL] MIPS fixes vor v5.18 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=20220402112719.GA5234@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