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.17
Date: Thu, 3 Feb 2022 09:56:02 +0100 [thread overview]
Message-ID: <20220203085602.GA5364@alpha.franken.de> (raw)
The following changes since commit fa62f39dc7e25fc16371b958ac59b9a6fd260bea:
MIPS: Fix build error due to PTR used in more places (2022-01-27 09:04:19 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git/ tags/mips-fixes-5.17_2
for you to fetch changes up to 2161ba070999a709f975910b6b9ad6b51cd6f120:
MIPS: KVM: fix vz.c kernel-doc notation (2022-02-01 08:36:27 +0100)
----------------------------------------------------------------
- fix missed change for PTR->PTR_WD conversion
- kernel-doc fixes
----------------------------------------------------------------
Randy Dunlap (1):
MIPS: KVM: fix vz.c kernel-doc notation
Thomas Bogendoerfer (1):
MIPS: octeon: Fix missed PTR->PTR_WD conversion
arch/mips/cavium-octeon/octeon-memcpy.S | 2 +-
arch/mips/kvm/vz.c | 12 +++++++++---
2 files changed, 10 insertions(+), 4 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-02-03 8:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 8:56 Thomas Bogendoerfer [this message]
2022-02-03 14:57 ` [GIT PULL] MIPS fixes for v5.17 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2022-03-03 16:48 Thomas Bogendoerfer
2022-03-03 19:18 ` pr-tracker-bot
2022-02-10 10:29 Thomas Bogendoerfer
2022-02-10 14:03 ` pr-tracker-bot
2022-01-28 13:33 Thomas Bogendoerfer
2022-01-28 17:36 ` 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=20220203085602.GA5364@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.