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.14
Date: Sat, 10 Jul 2021 14:15:23 +0200 [thread overview]
Message-ID: <20210710121523.GA8431@alpha.franken.de> (raw)
The following changes since commit cf02ce742f09188272bcc8b0e62d789eb671fc4c:
MIPS: Fix PKMAP with 32-bit MIPS huge page support (2021-06-30 14:41:32 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git/ tags/mips_5.14_1
for you to fetch changes up to 47ce8527fbba145a7723685bc9a27d9855e06491:
MIPS: vdso: Invalid GIC access through VDSO (2021-07-09 15:29:06 +0200)
----------------------------------------------------------------
- fix for accesing gic via vdso
- two build fixes
----------------------------------------------------------------
Arnd Bergmann (1):
mips: always link byteswap helpers into decompressor
Martin Fäcknitz (1):
MIPS: vdso: Invalid GIC access through VDSO
Randy Dunlap (1):
mips: disable branch profiling in boot/decompress.o
arch/mips/boot/compressed/Makefile | 4 ++--
arch/mips/boot/compressed/decompress.c | 2 ++
arch/mips/include/asm/vdso/vdso.h | 2 +-
3 files changed, 5 insertions(+), 3 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:[~2021-07-10 12:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-10 12:15 Thomas Bogendoerfer [this message]
2021-07-10 18:34 ` [GIT PULL] MIPS fixes for v5.14 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2021-08-06 13:36 Thomas Bogendoerfer
2021-08-06 18:48 ` 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=20210710121523.GA8431@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 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.