Skip to content
This repository was archived by the owner on Oct 31, 2024. It is now read-only.

Commit ff3dae8

Browse files
committed
Merge tag 'v6.7.12' into 6.7
This is the 6.7.12 stable release
2 parents 10422a2 + dacf7e8 commit ff3dae8

484 files changed

Lines changed: 4983 additions & 2783 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

Documentation/admin-guide/kernel-parameters.txt

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3331,9 +3331,7 @@
33313331

33323332
mem_encrypt= [X86-64] AMD Secure Memory Encryption (SME) control
33333333
Valid arguments: on, off
3334-
Default (depends on kernel configuration option):
3335-
on (CONFIG_AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT=y)
3336-
off (CONFIG_AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT=n)
3334+
Default: off
33373335
mem_encrypt=on: Activate SME
33383336
mem_encrypt=off: Do not activate SME
33393337

Documentation/arch/x86/amd-memory-encryption.rst

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -87,14 +87,14 @@ The state of SME in the Linux kernel can be documented as follows:
8787
kernel is non-zero).
8888

8989
SME can also be enabled and activated in the BIOS. If SME is enabled and
90-
activated in the BIOS, then all memory accesses will be encrypted and it will
91-
not be necessary to activate the Linux memory encryption support. If the BIOS
92-
merely enables SME (sets bit 23 of the MSR_AMD64_SYSCFG), then Linux can activate
93-
memory encryption by default (CONFIG_AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT=y) or
94-
by supplying mem_encrypt=on on the kernel command line. However, if BIOS does
95-
not enable SME, then Linux will not be able to activate memory encryption, even
96-
if configured to do so by default or the mem_encrypt=on command line parameter
97-
is specified.
90+
activated in the BIOS, then all memory accesses will be encrypted and it
91+
will not be necessary to activate the Linux memory encryption support.
92+
93+
If the BIOS merely enables SME (sets bit 23 of the MSR_AMD64_SYSCFG),
94+
then memory encryption can be enabled by supplying mem_encrypt=on on the
95+
kernel command line. However, if BIOS does not enable SME, then Linux
96+
will not be able to activate memory encryption, even if configured to do
97+
so by default or the mem_encrypt=on command line parameter is specified.
9898

9999
Secure Nested Paging (SNP)
100100
==========================

Documentation/conf.py

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -345,9 +345,9 @@ def get_cline_version():
345345
html_static_path = ['sphinx-static']
346346

347347
# If true, Docutils "smart quotes" will be used to convert quotes and dashes
348-
# to typographically correct entities. This will convert "--" to "—",
349-
# which is not always what we want, so disable it.
350-
smartquotes = False
348+
# to typographically correct entities. However, conversion of "--" to "—"
349+
# is not always what we want, so enable only quotes.
350+
smartquotes_action = 'q'
351351

352352
# Custom sidebar templates, maps document names to template names.
353353
# Note that the RTD theme ignores this

Documentation/userspace-api/media/mediactl/media-types.rst

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -375,12 +375,11 @@ Types and flags used to represent the media graph elements
375375
are origins of links.
376376

377377
* - ``MEDIA_PAD_FL_MUST_CONNECT``
378-
- If this flag is set and the pad is linked to any other pad, then
379-
at least one of those links must be enabled for the entity to be
380-
able to stream. There could be temporary reasons (e.g. device
381-
configuration dependent) for the pad to need enabled links even
382-
when this flag isn't set; the absence of the flag doesn't imply
383-
there is none.
378+
- If this flag is set, then for this pad to be able to stream, it must
379+
be connected by at least one enabled link. There could be temporary
380+
reasons (e.g. device configuration dependent) for the pad to need
381+
enabled links even when this flag isn't set; the absence of the flag
382+
doesn't imply there is none.
384383

385384

386385
One and only one of ``MEDIA_PAD_FL_SINK`` and ``MEDIA_PAD_FL_SOURCE``

Makefile

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
# SPDX-License-Identifier: GPL-2.0
22
VERSION = 6
33
PATCHLEVEL = 7
4-
SUBLEVEL = 11
4+
SUBLEVEL = 12
55
EXTRAVERSION =
66
NAME = Hurr durr I'ma ninja sloth
77

arch/arm/Kconfig

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -591,8 +591,8 @@ source "arch/arm/mm/Kconfig"
591591

592592
config IWMMXT
593593
bool "Enable iWMMXt support"
594-
depends on CPU_XSCALE || CPU_XSC3 || CPU_MOHAWK || CPU_PJ4 || CPU_PJ4B
595-
default y if PXA27x || PXA3xx || ARCH_MMP || CPU_PJ4 || CPU_PJ4B
594+
depends on CPU_XSCALE || CPU_XSC3 || CPU_MOHAWK
595+
default y if PXA27x || PXA3xx || ARCH_MMP
596596
help
597597
Enable support for iWMMXt context switching at run time if
598598
running on a CPU that supports it.

arch/arm/boot/dts/marvell/mmp2-brownstone.dts

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@
2828
&twsi1 {
2929
status = "okay";
3030
pmic: max8925@3c {
31-
compatible = "maxium,max8925";
31+
compatible = "maxim,max8925";
3232
reg = <0x3c>;
3333
interrupts = <1>;
3434
interrupt-parent = <&intcmux4>;

arch/arm/configs/imx_v6_v7_defconfig

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -297,6 +297,7 @@ CONFIG_FB_MODE_HELPERS=y
297297
CONFIG_LCD_CLASS_DEVICE=y
298298
CONFIG_LCD_L4F00242T03=y
299299
CONFIG_LCD_PLATFORM=y
300+
CONFIG_BACKLIGHT_CLASS_DEVICE=y
300301
CONFIG_BACKLIGHT_PWM=y
301302
CONFIG_BACKLIGHT_GPIO=y
302303
CONFIG_FRAMEBUFFER_CONSOLE=y

arch/arm/include/asm/mman.h

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
/* SPDX-License-Identifier: GPL-2.0 */
2+
#ifndef __ASM_MMAN_H__
3+
#define __ASM_MMAN_H__
4+
5+
#include <asm/system_info.h>
6+
#include <uapi/asm/mman.h>
7+
8+
static inline bool arch_memory_deny_write_exec_supported(void)
9+
{
10+
return cpu_architecture() >= CPU_ARCH_ARMv6;
11+
}
12+
#define arch_memory_deny_write_exec_supported arch_memory_deny_write_exec_supported
13+
14+
#endif /* __ASM_MMAN_H__ */

arch/arm/kernel/Makefile

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -75,8 +75,6 @@ obj-$(CONFIG_HAVE_HW_BREAKPOINT) += hw_breakpoint.o
7575
obj-$(CONFIG_CPU_XSCALE) += xscale-cp0.o
7676
obj-$(CONFIG_CPU_XSC3) += xscale-cp0.o
7777
obj-$(CONFIG_CPU_MOHAWK) += xscale-cp0.o
78-
obj-$(CONFIG_CPU_PJ4) += pj4-cp0.o
79-
obj-$(CONFIG_CPU_PJ4B) += pj4-cp0.o
8078
obj-$(CONFIG_IWMMXT) += iwmmxt.o
8179
obj-$(CONFIG_PERF_EVENTS) += perf_regs.o perf_callchain.o
8280
obj-$(CONFIG_HW_PERF_EVENTS) += perf_event_xscale.o perf_event_v6.o \

0 commit comments

Comments
 (0)