From: Michael Ellerman <mpe@ellerman.id.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: nathanl@linux.ibm.com, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org, tzimmermann@suse.de
Subject: [GIT PULL] Please pull powerpc/linux.git powerpc-6.7-2 tag
Date: Sun, 12 Nov 2023 12:25:12 +1100 [thread overview]
Message-ID: <878r73930n.fsf@mail.lhotse> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi Linus,
Please pull a few more powerpc updates for 6.7:
The following changes since commit 707df298cbde200b939c70be2577b20775fe3345:
Merge tag 'powerpc-6.7-1' of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux (2023-11-03 10:07:39 -1000)
are available in the git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git tags/powerpc-6.7-2
for you to fetch changes up to 644b6025bcaff59737270d812c70302f5a8d4a8f:
powerpc/rtas: Fix ppc_rtas_rmo_buf_show() kernel-doc (2023-11-07 13:13:45 +1100)
- ------------------------------------------------------------------
powerpc fixes for 6.7 #2
- Finish a refactor of pgprot_framebuffer() which dependend on some changes
that were merged via the drm tree.
- Fix some kernel-doc warnings to quieten the bots.
Thanks to: Nathan Lynch, Thomas Zimmermann.
- ------------------------------------------------------------------
Nathan Lynch (2):
powerpc/pseries/rtas-work-area: Fix rtas_work_area_reserve_arena() kernel-doc
powerpc/rtas: Fix ppc_rtas_rmo_buf_show() kernel-doc
Thomas Zimmermann (3):
powerpc/machdep: Remove trailing whitespaces
powerpc: Remove file parameter from phys_mem_access_prot()
powerpc/fb: Call internal __phys_mem_access_prot() in fbdev code
arch/powerpc/include/asm/fb.h | 7 +------
arch/powerpc/include/asm/machdep.h | 13 ++++++-------
arch/powerpc/include/asm/pci.h | 4 +---
arch/powerpc/include/asm/pgtable.h | 10 ++++++++--
arch/powerpc/kernel/pci-common.c | 3 +--
arch/powerpc/kernel/rtas-proc.c | 2 ++
arch/powerpc/mm/mem.c | 8 ++++----
arch/powerpc/platforms/pseries/rtas-work-area.c | 1 +
8 files changed, 24 insertions(+), 24 deletions(-)
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEJFGtCPCthwEv2Y/bUevqPMjhpYAFAmVQKR4ACgkQUevqPMjh
pYCHnw//bL9g7D/SOM6cLCTFs3INADo4Tvur/Y6KzIywDGMlGAcrScwbfcplfUIZ
vjGuUdJE2VRGsoNBineyovM6njXHhQ48cpgD7smr3giU1Qz3UlrNlzIqO5N23AlO
USHFRT1enP/pv9LelapiVJocVXiqatY+nIhzJjj+yvsVYSI+5Aq+4f83jM0JvHzK
y3yNgQm0xZZy86tOkm4jQZ4UKg5M4Ua92dCxKkgwshC2gsLI+TXIxRaP1PM3NDn8
3FZtrDzj9QR0ABooLDzh5rcndU+Un1VoFJgkzlBBPh3Ad0AQ0xQxOwPAlEicrru+
uEo5/bL+CsHdvd/tgf/x+3zjhNtDCx1p7Onz2Zp/iTzGWNq1BpB356AWSnjCIOdv
neg1kH+t+pMWf5NPOs+Idn6glKXK8eICMW6Mm1xlFzqV6YLObGVSOOzZJ5ehR8nN
OdZ3l+U6KyaEnLmpAhNfbh2cPue56JvnzPINpm5vleSvTN2OaajlMVjunwxt7YJl
MBNVHawaVYLUXXS6gmFo7/0q0QXAjpHYPQOhiLETLsV2vhbF25wmmphbakj63rlH
NokpCxRf0KZ5k0sT3GNhiETFJ0//jbyUgFKAh9PfmIusv0Haqu4/GZgwXy9+cazq
V9kQnQjpeUm3FxcUKRtQ9YZSXGdIuwXsIpy54dfcRtcUF7UX+5I=
=Cqjh
-----END PGP SIGNATURE-----
next reply other threads:[~2023-11-12 1:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-12 1:25 Michael Ellerman [this message]
2023-11-12 19:18 ` [GIT PULL] Please pull powerpc/linux.git powerpc-6.7-2 tag 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=878r73930n.fsf@mail.lhotse \
--to=mpe@ellerman.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nathanl@linux.ibm.com \
--cc=torvalds@linux-foundation.org \
--cc=tzimmermann@suse.de \
/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