[PATCH v4 2/2] x86/boot/KASLR: skip the specified crashkernel region

crashkernel=x@y or or =range1:size1[,range2:size2,...]@offset option may fail to reserve the required memory region if KASLR puts kernel into the region. To avoid this uncertainty, asking KASLR to skip the required region. Signed-off-by: Pingfan Liu Cc: Thomas Gleixner Cc: Ingo Molnar Cc:

[PATCH v4 1/2] kernel/crash_core: separate the parsing routines to lib/parse_crashkernel.c

Beside kernel, at early boot stage, the KASLR code also needs to parse the crashkernel=x@y or crashkernel=ramsize-range:size[,...][@offset] option, and avoid to put randomized kernel in the region. Extracting the parsing related routines to lib/parse_crashkernel.c, so it will be handy included by

[PATCH v4 0/2] x86/boot/KASLR: skip the specified crashkernel region

crashkernel=x@y or or =range1:size1[,range2:size2,...]@offset option may fail to reserve the required memory region if KASLR puts kernel into the region. To avoid this uncertainty, asking KASLR to skip the required region. And the parsing routine can be re-used at this early boot stage. Cc:

Re: [Update][PATCH v3 3/4] cpufreq: schedutil: Simplify iowait boosting

On 28-03-19, 11:33, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > There is not reason for the minimum iowait boost value in the > schedutil cpufreq governor to depend on the available range of CPU > frequencies. In fact, that dependency is generally confusing, > because it causes the

Re: Regression in suspend-to-ram (TPM related) with 5.1-rc1 (BISECTED)

On 21.03.19 14:41, Jarkko Sakkinen wrote: > On Tue, Mar 19, 2019 at 04:03:37PM -0700, Paul Zimmerman wrote: >> So I bisected this down to: >> >> # first bad commit: [a3fbfae82b4cb3ff9928e29f34c64d0507cad874] tpm: >> take TPM chip power gating out of tpm_transmit() >> >> but this doesn't revert

[PATCH 1/2] arm64: dts: allwinner: a64-amarula-relic: Add GT5663 CTP node

Add Goodix GT5663 capacitive touch controller node on Amarula A64-Relic board. The CTP connected to board with, - SDA, SCK from i2c1 - GPIO-LD0 as AVDD28 supply - PH4 gpio as interrupt pin - PH8 gpio as reset pin - X axis is inverted - Y axis is inverted Signed-off-by: Jagan Teki ---

[PATCH 2/2] arm64: dts: allwinner: a64-oceanic-5205-5inmfd: Enable GT911 CTP

Goodix GT911 CTP is bound with Oceanic 5205 5inMFD board. The CTP connected to board with, - SDA, SCK from i2c0 - GPIO-LD0 as AVDD28 supply - PH4 gpio as interrupt pin - PH11 gpio as reset pin - X axis is inverted - Y axis is inverted Signed-off-by: Jagan Teki ---

linux-next: Fixes tag needs some work in the nvdimm-fixes tree

Hi Dan, In commit 7c33bd4e3e97 ("libnvdimm/pmem: fix a possible OOB access when read and write pmem") Fixes tag Fixes: 98cc093cba1e "(block, THP: make block_device_operations.rw_page support THP)" has these problem(s): - Subject does not match target commit subject Just use

Re: Adding plain accesses and detecting data races in the LKMM

> > > > I'd have: > > > > > > > > *x = 1; /* A */ > > > > smp_mb__before_atomic(); > > > > r0 = xchg_relaxed(x, 2); /* B (read or write part) */ > > > > > > > > => (A ->barrier B) > > > > > > Perhaps so. It wasn't clear initially how these should be treated, so

Re: [PATCH v4 1/2] drm/bridge: sil_sii8620: make remote control optional.

On 07.04.2019 07:03, Ronald Tschalär wrote: > commit d6abe6df706c (drm/bridge: sil_sii8620: do not have a dependency > of RC_CORE) changed the driver to select both RC_CORE and INPUT. > However, this causes problems with other drivers, in particular an input > driver that depends on

[PATCH] intel-lpss: Set the device in reset state when init

In virtualized setup, when system reboots due to warm reset interrupt storm is seen. Call Trace: dump_stack+0x70/0xa5 __report_bad_irq+0x2e/0xc0 note_interrupt+0x248/0x290 ? add_interrupt_randomness+0x30/0x220 handle_irq_event_percpu+0x54/0x80 handle_irq_event+0x39/0x60

Re: [RESENT PATCH] mm/memory_hotplug: Do not unlock when fails to take the device_hotplug_lock

On Mon 08-04-19 12:07:17, zhong jiang wrote: > When adding the memory by probing memory block in sysfs interface, there is an > obvious issue that we will unlock the device_hotplug_lock when fails to takes > it. > > That issue was introduced in Commit 8df1d0e4a265 > ("mm/memory_hotplug: make

linux-next: Tree for Apr 8

Hi all, Changes since 20190405: The kspp-gustavo tree gained a conflict against Linus' tree. The drm tree inherited the build failure from the drm-misc tree for which I disabled a driver. The audit tree gained a conflict against Linus' tree. The staging tree gained a conflict against the

Re: [PATCH] cpufreq: stats: Use lock by stat to replace global spin lock

On 26-03-19, 11:43, Matthias Kaehlcke wrote: > On Mon, Mar 25, 2019 at 03:29:33PM +0800, Kyle Lin wrote: > > Stats is updated by each policy, using the lock by stat can > > reduce the contention. > > > > Signed-off-by: Kyle Lin > > --- > > drivers/cpufreq/cpufreq_stats.c | 15 --- >

Re: [PATCH] slab: fix a crash by reading /proc/slab_allocators

On Sat, Apr 6, 2019 at 12:59 PM Qian Cai wrote: > > The commit 510ded33e075 ("slab: implement slab_root_caches list") > changes the name of the list node within "struct kmem_cache" from > "list" to "root_caches_node", but leaks_show() still use the "list" > which causes a crash when reading

[PATCH 2/2] ARM: dts: exynos: Remove console argument from bootargs

Remove the "console=ttySAC..." argument from DTSes having a proper stdout-path property. To make the code functionally equivalent, add the serial port baud rate and parity. Signed-off-by: Krzysztof Kozlowski --- arch/arm/boot/dts/exynos4210-origen.dts | 4 ++--

[PATCH 1/2] ARM: dts: exynos: Use stdout-path property instead of console in bootargs

Replacing bootargs with stdout-path property in chosen node allows using early console by adding just 'earlycon' parameter to the kernel command line. Signed-off-by: Krzysztof Kozlowski --- arch/arm/boot/dts/exynos4412-trats2.dts| 3 ++- arch/arm/boot/dts/exynos5250-smdk5250.dts | 3 ++-

Re: [PATCH] slab: fix a crash by reading /proc/slab_allocators

On Sat, Apr 06, 2019 at 06:59:01PM -0400, Qian Cai wrote: > The commit 510ded33e075 ("slab: implement slab_root_caches list") > changes the name of the list node within "struct kmem_cache" from > "list" to "root_caches_node", but leaks_show() still use the "list" > which causes a crash when

[PATCH] pinctrl:intel: Retain HOSTSW_OWN for requested gpio pin

The touchpad of the ASUS laptops E403NA, X540NA, X541NA are not responsive after suspend/resume. The following error message shows after resume. i2c_hid i2c-ELAN1200:00: failed to reset device. On these laptops, the touchpad interrupt is connected via a GPIO pin which is controlled by Intel

[PATCH] alarmtimer: return correct remaining time

To calculate a remaining time, we need to subtract the current time from the expiration time. Currently, arguments of ktime_sub are swapped. Signed-off-by: Andrei Vagin --- kernel/time/alarmtimer.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/time/alarmtimer.c

Re: [PATCH] mm/memory_hotplug: Do not unlock when fails to take the device_hotplug_lock

I am sorry, It is incorrect. please ignore the patch. I will resent it. Thanks, zhong jiang On 2019/4/8 12:00, zhong jiang wrote: > When adding the memory by probing memory block in sysfs interface, there is an > obvious issue that we will unlock the device_hotplug_lock when fails to takes >

[RESENT PATCH] mm/memory_hotplug: Do not unlock when fails to take the device_hotplug_lock

When adding the memory by probing memory block in sysfs interface, there is an obvious issue that we will unlock the device_hotplug_lock when fails to takes it. That issue was introduced in Commit 8df1d0e4a265 ("mm/memory_hotplug: make add_memory() take the device_hotplug_lock") We should drop

Re: [PATCH 6/6] arm64/mm: Enable ZONE_DEVICE

On Sun, Apr 07, 2019 at 03:11:00PM -0700, Dan Williams wrote: > On Thu, Apr 4, 2019 at 2:47 AM Robin Murphy wrote: > > > > On 04/04/2019 06:04, Dan Williams wrote: > > > On Wed, Apr 3, 2019 at 9:42 PM Anshuman Khandual > > > wrote: > > >> > > >> > > >> > > >> On 04/03/2019 07:28 PM, Robin Murphy

[PATCH] mm/memory_hotplug: Do not unlock when fails to take the device_hotplug_lock

When adding the memory by probing memory block in sysfs interface, there is an obvious issue that we will unlock the device_hotplug_lock when fails to takes it. That issue was introduced in Commit 8df1d0e4a265 ("mm/memory_hotplug: make add_memory() take the device_hotplug_lock") We should drop

Re: [PATCH] ACPI / LPSS: Don't skip late system PM ops for hibernate on BYT/CHT

at 4:58 AM, Robert R. Howell wrote: On 4/3/19 2:54 AM, Hans de Goede wrote: Hi, On 03-04-19 07:43, Kai-Heng Feng wrote: i2c-designware-platdrv fails to work after the system restored from hibernation: [ 272.775692] i2c_designware 80860F41:00: Unknown Synopsys component type: 0x

Re: [RFC PATCH v2 1/3] arch/x86: add the support of ACRN guest

On 2019年04月06日 03:01, Thomas Gleixner wrote: Zhao, On Tue, 26 Mar 2019, Zhao Yakui wrote: Vs. the Subject line: arch/x86: add the support of ACRN guest The proper prefix for x86 is surprisingly 'x86:' not 'arch/x86:'. Also please start the first word after the colon with an upper case

Re: [PATCH] dt-bindings: cpu: Fix JSON schema

On 2019/04/08 7:13, Olof Johansson wrote: On Tue, Apr 02, 2019 at 08:42:02PM +0900, Sugaya, Taichi wrote: Hi, On 2019/04/01 22:02, Sugaya, Taichi wrote: Hi, On 2019/04/01 20:35, Maxime Ripard wrote: Hi, On Mon, Apr 01, 2019 at 07:52:06PM +0900, Sugaya, Taichi wrote: On 2019/04/01

Re: [RFC PATCH v2 2/3] arch/x86/acrn: Use HYPERVISOR_CALLBACK_VECTOR for Acrn upcall vector

On 2019年04月06日 03:07, Thomas Gleixner wrote: On Tue, 26 Mar 2019, Zhao Yakui wrote: diff --git a/arch/x86/include/asm/hardirq.h b/arch/x86/include/asm/hardirq.h index d9069bb..a8f4d08 100644 --- a/arch/x86/include/asm/hardirq.h +++ b/arch/x86/include/asm/hardirq.h @@ -37,7 +37,8 @@ typedef

Re: [RFC PATCH v2 3/3] arch/x86/acrn: add hypercall for acrn_guest

On 2019年04月06日 03:19, Thomas Gleixner wrote: On Tue, 26 Mar 2019, Zhao Yakui wrote: When acrn_hypervisor is detected, the hypercall is needed so that the acrn guest can query/config some settings. For example: it can be used to query the resources in hypervisor and manage the

linux-next: manual merge of the staging tree with the staging.current tree

Hi all, Today's linux-next merge of the staging tree got a conflict in: drivers/iio/industrialio-buffer.c between commit: 20ea39ef9f2f ("iio: Fix scan mask selection") from the staging.current tree and commit: 3862828a903d ("iio: buffer: Switch to bitmap_zalloc()") from the staging

[PATCH 2/2] lib/scatterlist.c: add more commit for sg_alloc_table_from_pages

The get_user_pages_fast() may mess up the page order in @pages array, We will get the wrong DMA results in this case. Add more commit to clarify it. Signed-off-by: Huang Shijie --- lib/scatterlist.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/lib/scatterlist.c b/lib/scatterlist.c

[PATCH 1/2] mm/gup.c: fix the wrong comments

When CONFIG_HAVE_GENERIC_GUP is defined, the kernel will use its own get_user_pages_fast(). In the following scenario, we will may meet the bug in the DMA case: . get_user_pages_fast(start,,, pages); ..

Re: [PATCH v13 1/3] /proc/pid/status: Add support for architecture specific output

On 2019/4/8 9:52, Andy Lutomirski wrote: > On Sun, Apr 7, 2019 at 5:38 PM Li, Aubrey wrote: >> >> On 2019/4/8 1:34, Andy Lutomirski wrote: >>> On Fri, Apr 5, 2019 at 12:32 PM Thomas Gleixner wrote: On Sun, 24 Feb 2019, Aubrey Li wrote: > The architecture specific information

Re: [PATCH v2] srcu: Remove unused vmlinux srcu linker entries

On Sun, Apr 07, 2019 at 08:47:19PM -0400, Joel Fernandes (Google) wrote: > The SRCU for modules optimization (commit title "srcu: Allocate per-CPU > data for DEFINE_SRCU() in modules") introduced vmlinux linker entries > which is unused since it applies only to the built-in vmlinux. So remove > it

Re: [patch V2 28/29] x86/irq/64: Remap the IRQ stack with guard pages

On Sun, Apr 7, 2019 at 3:44 PM Thomas Gleixner wrote: > > On Sat, 6 Apr 2019, Andy Lutomirski wrote: > > On Fri, Apr 5, 2019 at 8:11 AM Thomas Gleixner wrote: > > > > > > From: Andy Lutomirski > > > > > > The IRQ stack lives in percpu space, so an IRQ handler that overflows it > > > will

Re: [PATCH] slab: fix a crash by reading /proc/slab_allocators

On 4/7/19 9:59 PM, Tobin C. Harding wrote: > On Sat, Apr 06, 2019 at 06:59:01PM -0400, Qian Cai wrote: >> The commit 510ded33e075 ("slab: implement slab_root_caches list") >> changes the name of the list node within "struct kmem_cache" from >> "list" to "root_caches_node" > > Are you sure? It

RE: [EXT] Re: [PATCH] iio: accell: mma8452: free iio trigger pointer when cleanup

Hi, Jonathan Best Regards! Anson Huang > -Original Message- > From: Jonathan Cameron [mailto:ji...@kernel.org] > Sent: 2019年4月7日 18:40 > To: Anson Huang > Cc: knaac...@gmx.de; l...@metafoo.de; pme...@pmeerw.net; Leonard > Crestez ; gust...@embeddedor.com; > mart...@posteo.de;

Re: [PATCH v9 1/2] dt-bindings: misc: aspeed-p2a-ctrl: add support

On Fri, 5 Apr 2019, at 01:55, Patrick Venture wrote: > Document the ast2400, ast2500 PCI-to-AHB bridge control driver bindings. > > Signed-off-by: Patrick Venture > Reviewed-by: Rob Herring > --- > Changes for v9: > - Added missing details about syscon parent > Changes for v8: > - None >

Re: [PATCH] slab: fix a crash by reading /proc/slab_allocators

On Sat, Apr 06, 2019 at 06:59:01PM -0400, Qian Cai wrote: > The commit 510ded33e075 ("slab: implement slab_root_caches list") > changes the name of the list node within "struct kmem_cache" from > "list" to "root_caches_node" Are you sure? It looks to me like it adds a member to the

Re: [PATCH v13 1/3] /proc/pid/status: Add support for architecture specific output

On Sun, Apr 7, 2019 at 5:38 PM Li, Aubrey wrote: > > On 2019/4/8 1:34, Andy Lutomirski wrote: > > On Fri, Apr 5, 2019 at 12:32 PM Thomas Gleixner wrote: > >> > >> On Sun, 24 Feb 2019, Aubrey Li wrote: > >> > >>> The architecture specific information of the running processes could > >>> be useful

Re: [PATCH 08/14] powercap/intel_rapl: Support multi-die/package

On 五, 2019-04-05 at 20:27 +0200, Thomas Gleixner wrote: > On Tue, 26 Feb 2019, Len Brown wrote: > > > > > From: Zhang Rui > > > > On the new dual-die/package systems, the RAPL MSR becomes die- > > scope. > > Thus instead of one powercap device per physical package, now there > > should be one

linux-next: manual merge of the audit tree with Linus' tree

Hi all, Today's linux-next merge of the audit tree got conflicts in: arch/mips/kernel/ptrace.c kernel/seccomp.c between commit: b35f549df1d7 ("syscalls: Remove start and number from syscall_get_arguments() args") from Linus' tree and commit: 16add411645c ("syscall_get_arch: add

Re: Using device tree overlays in Linux

Hi Frank, On 8/04/19 1:05 PM, Frank Rowand wrote: > Hi Chris, > > On 4/3/19 6:50 PM, Chris Packham wrote: >> Hi, >> >> I'm implementing support for some modular Linux based systems using >> device tree overlays. The code is working but it seems a little more >> fiddly that than it should be so

Re: [PATCH] mm/gup.c: fix the wrong comments

On Thu, Apr 04, 2019 at 09:50:47AM -0700, Ira Weiny wrote: > On Thu, Apr 04, 2019 at 03:23:47PM +0800, Huang Shijie wrote: > > When CONFIG_HAVE_GENERIC_GUP is defined, the kernel will use its own > > get_user_pages_fast(). > > > > In the following scenario, we will may meet the bug in the DMA

Re: [PATCH] of: Documentation: Correct return value from of_overlay_fdt_apply

On 4/3/19 7:25 PM, Chris Packham wrote: > The return from of_overlay_fdt_apply() just indicates success or fail. > The cookie is returned via reference. > > Signed-off-by: Chris Packham > --- > Documentation/devicetree/overlay-notes.txt | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-)

Re: Using device tree overlays in Linux

Hi Chris, On 4/3/19 6:50 PM, Chris Packham wrote: > Hi, > > I'm implementing support for some modular Linux based systems using > device tree overlays. The code is working but it seems a little more > fiddly that than it should be so I'm wondering if I'm doing it right. Let me start by saying

Re: [PATCH] kprobes: fix compilation when KPROBE_EVENTS is enabled without kretpobes

On Sat, 6 Apr 2019 17:55:43 +0200 Sven Schnelle wrote: > While implementing kprobes on PA-RISC (without kretprobes) compilation > fails when CONFIG_KPROBE_EVENTS is enabled: > > kernel/trace/trace_kprobe.o: in function `trace_kprobe_create': > kernel/trace/trace_kprobe.c:666: undefined

[PATCH v2] srcu: Remove unused vmlinux srcu linker entries

The SRCU for modules optimization (commit title "srcu: Allocate per-CPU data for DEFINE_SRCU() in modules") introduced vmlinux linker entries which is unused since it applies only to the built-in vmlinux. So remove it to prevent any space usage due to the 8 byte alignment it added. vmlinux.lds.h

Re: [PATCH v13 1/3] /proc/pid/status: Add support for architecture specific output

On 2019/4/7 23:46, Alexey Dobriyan wrote: > On Sun, Apr 07, 2019 at 09:02:38PM +0800, Li, Aubrey wrote: >> On 2019/4/7 5:41, Alexey Dobriyan wrote: >>> On Fri, Apr 05, 2019 at 09:32:35PM +0200, Thomas Gleixner wrote: > +/* Add support for architecture specific output in /proc/pid/status */

[PATCH] srcu: Remove unused vmlinux srcu linker entries

The SRCU for modules optimization introduced vmlinux linker entries which is unused since it applies only to the built-in vmlinux. So remove it to prevent any space usage due to the 8 byte alignment it added. Tested with SRCU torture_type and rcutorture. Put prints in module loader to confirm it

Re: [PATCH v13 1/3] /proc/pid/status: Add support for architecture specific output

On 2019/4/8 1:34, Andy Lutomirski wrote: > On Fri, Apr 5, 2019 at 12:32 PM Thomas Gleixner wrote: >> >> On Sun, 24 Feb 2019, Aubrey Li wrote: >> >>> The architecture specific information of the running processes could >>> be useful to the userland. Add support to examine process architecture >>>

Linux 5.1-rc4

Another week, another rc. Smaller than rc3, I'm happy to say. Nothing particularly big in here, just a number of small things all over. And it really is all over. Drivers are about a third (networking, block, gpu, scsi), with the rest being a mix of arch updates, filesystem updates,

Re: [PATCH] arm64: ptrace: Add function argument access API

Hi Will, On Wed, 3 Apr 2019 13:06:49 +0100 Will Deacon wrote: > On Mon, Mar 18, 2019 at 04:59:02PM +0900, Masami Hiramatsu wrote: > > Add regs_get_argument() which returns N th argument of the function > > call. On arm64, it supports up to 8th argument. > > Note that this chooses most probably

Dear Friend (Assalamu Alaikum),

-- Dear Friend (Assalamu Alaikum), I came across your e-mail contact prior a private search while in need of your assistance. My name is Aisha Al-Qaddafi a single Mother and a Widow with three Children. I am the only biological Daughter of late Libyan President (Late Colonel Muammar Gaddafi).

Re: [PATCH 1/3] fs: stream_open - opener for stream-like files so that read and write can run simultaneously without deadlock

On Sun, Apr 7, 2019 at 10:04 AM Kirill Smelkov wrote: > > Fixing regression on FUSE side is my reason to do this whole work - > that's why I care about it the most and ask. Yeah, we can do the actual FUSE fix, I think. Preferably through the FUSE tree. Miklos? Linus

Re: [GIT PULL] ARM: SoC fixes

The pull request you sent on Sun, 7 Apr 2019 15:50:20 -0700: > git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git tags/armsoc-fixes has been merged into torvalds/linux.git: https://git.kernel.org/torvalds/c/d8491223bc243b960ee1c4a8aa5219eca0d69acf Thank you! -- Deet-doot-dot, I am a

Re: [RFC][PATCH 0/3] tracing: Make error_log per instance

Hi Steve, Sorry for replying late. On Tue, 02 Apr 2019 14:29:51 -0400 Steven Rostedt wrote: > Hi Tom, > > I noticed that you created an error_log file in every instance, but > they all show the same errors. These three patches make it so that > the errors appear in the instance directory that

[PATCH v2] Input: i8042 - disable KBD port on Razer Blade Stealth V2 (2017 model)

The late 2017 model of the Razer Blade Stealth has a built-in USB keyboard, but for some reason the BIOS exposes an i8042 controller with a connected KBD port. While this fake AT Keyboard device doesn't appear to report any events, attempting to change the state of the caps lock LED on it from on

Re: [PATCH 03/16] staging: m57621-mmc: delete driver from the tree.

On Wed, Apr 03 2019, George Hilliard wrote: > On Tue, Apr 2, 2019 at 3:45 PM Christian Lütke-Stetzkamp > wrote: >> There are two other larger differences that I found during my >> work. One is that drivers/mmc/host/mtk-sd.c has much more features, >> like voltage and clock handling and some

[PATCH 3/5] x86/MCE/AMD: Don't cache block addresses on SMCA systems

From: Yazen Ghannam On legacy systems, the addresses of the MCA_MISC* registers need to be recursively discovered based on a Block Pointer field in the registers. On Scalable MCA systems, the register space is fixed, and particular addresses can be derived by regular offsets for bank and

[PATCH 4/5] x86/MCE: Make number of MCA banks per_cpu

From: Yazen Ghannam The number of MCA banks is provided per logical CPU. Historically, this number has been the same across all CPUs, but this is not an architectural guarantee. Future AMD systems may have MCA bank counts that vary between logical CPUs in a system. This issue was partially

[PATCH 0/5] Handle MCA banks in a per_cpu way

From: Yazen Ghannam The focus of this patchset is define and use the MCA bank structures and bank count per logical CPU. With the exception of patch 4, this set applies to systems in production today. Patch 1: Moves the declaration of struct mce_banks[] to the only file it's used. Patch 2:

[PATCH 5/5] x86/MCE: Save MCA control bits that get set in hardware

From: Yazen Ghannam The OS is expected to write all bits in MCA_CTL. However, only implemented bits get set in the hardware. Read back MCA_CTL so that the value in the hardware is saved and reported through sysfs. Signed-off-by: Yazen Ghannam --- arch/x86/kernel/cpu/mce/core.c | 15

[PATCH 2/5] x86/MCE: Handle MCA controls in a per_cpu way

From: Yazen Ghannam Current AMD systems have unique MCA banks per logical CPU even though the type of the banks may all align to the same bank number. Each CPU will have control of a set of MCA banks in the hardware and these are not shared with other CPUs. For example, bank 0 may be the

[PATCH 1/5] x86/MCE: Make struct mce_banks[] static

From: Yazen Ghannam The struct mce_banks[] array is only used in mce/core.c so move the definition of struct mce_bank to mce/core.c and make the array static. Also, change the "init" field to bool type. Signed-off-by: Yazen Ghannam --- arch/x86/kernel/cpu/mce/core.c | 11 ++-

Re: [GIT PULL] ARM: SoC fixes

On Sun, Apr 7, 2019 at 3:50 PM Olof Johansson wrote: > > Hi Linus, > > The following changes since commit 79a3aaa7b82e3106be97842dedfd8429248896e6: > > Linux 5.1-rc3 (2019-03-31 14:39:29 -0700) > > are available in the git repository at: > >

Re: [PATCH] Input: i8042 - disable KBD port on Late-2016 Razer Blade Stealth

On Sun, 2019-04-07 at 15:10 -0700, Dmitry Torokhov wrote: > Hi Lyude, > > On Sun, Apr 07, 2019 at 05:37:34PM -0400, Lyude Paul wrote: > > The late 2016 model of the Razer Blade Stealth has a built-in USB > > keyboard, but for some reason the BIOS exposes an i8042 controller with > > a connected

Re: [GIT PULL v2] LM3532 backlight support improvements and relocation

Hi! > > Changes since v1: > > > > - synchronized DT label properties in DT bindings with what has been agreed > > for the patch "ARM: dts: omap4-droid4: Update backlight dt properties" > > > > The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b: > > > > Linux

[GIT PULL] ARM: SoC fixes

Hi Linus, The following changes since commit 79a3aaa7b82e3106be97842dedfd8429248896e6: Linux 5.1-rc3 (2019-03-31 14:39:29 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git tags/armsoc-fixes for you to fetch changes up to

Re: [patch V2 28/29] x86/irq/64: Remap the IRQ stack with guard pages

On Sat, 6 Apr 2019, Andy Lutomirski wrote: > On Fri, Apr 5, 2019 at 8:11 AM Thomas Gleixner wrote: > > > > From: Andy Lutomirski > > > > The IRQ stack lives in percpu space, so an IRQ handler that overflows it > > will overwrite other data structures. > > > > Use vmap() to remap the IRQ stack so

Re: [PATCH] ARM: milbeaut: fix build with !CONFIG_HOTPLUG_CPU

On Wed, Mar 13, 2019 at 10:19:16PM +0100, Arnd Bergmann wrote: > When HOTPLUG_CPU is disabled, some fields in the smp operations > are not available or needed: > > arch/arm/mach-milbeaut/platsmp.c:90:3: error: field designator 'cpu_die' does > not refer to any field in type > 'struct

Re: [PATCH v5 2/3] platform/chrome: Add Wilco EC keyboard backlight LEDs support

On Sun, Apr 7, 2019 at 3:18 PM Pavel Machek wrote: > > > > > > This document also states "The naming scheme above leaves scope > > > > for further attributes should they be needed". It does not permit, > > > > however, to redefine one of the fields to mean "location", much less > > > > the

Re: [PATCH] dt-bindings: cpu: Fix JSON schema

On Tue, Apr 02, 2019 at 08:42:02PM +0900, Sugaya, Taichi wrote: > Hi, > > On 2019/04/01 22:02, Sugaya, Taichi wrote: > > Hi, > > > > On 2019/04/01 20:35, Maxime Ripard wrote: > > > Hi, > > > > > > On Mon, Apr 01, 2019 at 07:52:06PM +0900, Sugaya, Taichi wrote: > > > > On 2019/04/01 18:10,

Re: [PATCH 1/2] ARM: orion: don't use using 64-bit DMA masks

On Mon, Mar 25, 2019 at 04:50:42PM +0100, Arnd Bergmann wrote: > clang warns about statically defined DMA masks from the DMA_BIT_MASK > macro with length 64: > > arch/arm/plat-orion/common.c:625:29: error: shift count >= width of type > [-Werror,-Wshift-count-overflow] >

Re: [PATCH 2/2] ARM: iop: don't use using 64-bit DMA masks

On Mon, Mar 25, 2019 at 04:50:43PM +0100, Arnd Bergmann wrote: > clang warns about statically defined DMA masks from the DMA_BIT_MASK > macro with length 64: > > arch/arm/mach-iop13xx/setup.c:303:35: error: shift count >= width of type > [-Werror,-Wshift-count-overflow] > static u64

Re: [PATCH v5 2/3] platform/chrome: Add Wilco EC keyboard backlight LEDs support

> > > This document also states "The naming scheme above leaves scope > > > for further attributes should they be needed". It does not permit, > > > however, to redefine one of the fields to mean "location", much less > > > the declaration that a devicename of "platform" shall refer to an > > >

Re: [PATCH v2 2/3] Input: add a driver for GPIO controllable vibrators

Hi Luca, On Sun, Apr 07, 2019 at 05:58:41PM +0200, Luca Weiss wrote: > Provide a simple driver for GPIO controllable vibrators. > It will be used by the Fairphone 2. > > Signed-off-by: Luca Weiss > --- > drivers/input/misc/Kconfig | 12 ++ > drivers/input/misc/Makefile | 1 + >

Re: [GIT PULL v2] LM3532 backlight support improvements and relocation

Hi! > Changes since v1: > > - synchronized DT label properties in DT bindings with what has been agreed > for the patch "ARM: dts: omap4-droid4: Update backlight dt properties" > > The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b: > > Linux 5.1-rc1 (2019-03-17

Re: [PATCH 6/6] arm64/mm: Enable ZONE_DEVICE

On Thu, Apr 4, 2019 at 2:47 AM Robin Murphy wrote: > > On 04/04/2019 06:04, Dan Williams wrote: > > On Wed, Apr 3, 2019 at 9:42 PM Anshuman Khandual > > wrote: > >> > >> > >> > >> On 04/03/2019 07:28 PM, Robin Murphy wrote: > >>> [ +Dan, Jerome ] > >>> > >>> On 03/04/2019 05:30, Anshuman

Re: [PATCH] Input: i8042 - disable KBD port on Late-2016 Razer Blade Stealth

Hi Lyude, On Sun, Apr 07, 2019 at 05:37:34PM -0400, Lyude Paul wrote: > The late 2016 model of the Razer Blade Stealth has a built-in USB > keyboard, but for some reason the BIOS exposes an i8042 controller with > a connected KBD port. While this fake AT Keyboard device doesn't appear > to report

Re: [PATCH v5 3/3] platform/chrome: Standardize Chrome OS keyboard backlight name

Hi Jacek, On Fri, Apr 5, 2019 at 1:00 PM Jacek Anaszewski wrote: > > Hi all, > > On 4/5/19 10:42 AM, Enric Balletbo i Serra wrote: > > Hi, > > > > On 5/4/19 0:42, Guenter Roeck wrote: > >> On Thu, Apr 4, 2019 at 3:05 PM Pavel Machek wrote: > >>> > >>> On Thu 2019-04-04 14:48:35, Dmitry Torokhov

Re: [PATCH v5 2/3] platform/chrome: Add Wilco EC keyboard backlight LEDs support

On Sat, Apr 6, 2019 at 1:41 AM Pavel Machek wrote: > > On Fri 2019-04-05 13:15:34, Guenter Roeck wrote: > > On Thu, Apr 04, 2019 at 11:10:08AM -0600, Nick Crews wrote: > > > The EC is in charge of controlling the keyboard backlight on > > > the Wilco platform. We expose a standard LED class

Re: [PATCH v4 0/6] lib/string: Add strscpy_pad() function

On Fri, Apr 05, 2019 at 12:58:53PM +1100, Tobin C. Harding wrote: > Hi Shua, Apologies for continually leaving off the 'h' from your name Shuah. Tobin

[PATCH] Input: i8042 - disable KBD port on Late-2016 Razer Blade Stealth

The late 2016 model of the Razer Blade Stealth has a built-in USB keyboard, but for some reason the BIOS exposes an i8042 controller with a connected KBD port. While this fake AT Keyboard device doesn't appear to report any events, attempting to change the state of the caps lock LED on it from on

[PATCH] perf vendor events arm64: Add Cortex-A72 events

The Cortex-A72 supports all ARMv8 recommended events up to the RC_ST_SPEC (0x91) event, create an appropriate JSON file for mapping those events and update the mapfile.csv for matching the Cortex-A72 MIDR to that file. Signed-off-by: Florian Fainelli ---

[PATCH] rtc: test: use .set_time

Use .set_time instead of the deprecated .set_mmss64. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-test.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/rtc/rtc-test.c b/drivers/rtc/rtc-test.c index f1a6dc5ad013..b298e9902f45 100644 ---

[PATCH] soc: brcmstb: Fix error path for unsupported CPUs

In case setup_hifcpubiuctrl_regs() returns an error, because of e.g: an unsupported CPU type, just catch that error and return instead of blindly continuing with the initialization. This fixes a NULL pointer de-reference with the code continuing without having a proper array of registers to use.

linux-next: manual merge of the kspp-gustavo tree with Linus' tree

Hi all, Today's linux-next merge of the kspp-gustavo tree got a conflict in: arch/x86/include/asm/syscall.h between commits: b35f549df1d7 ("syscalls: Remove start and number from syscall_get_arguments() args") 32d92586629a ("syscalls: Remove start and number from syscall_set_arguments()

[PATCH 1/3] rtc: tegra: set range

The Tegra 20 RTC is a 32bit seconds counter (with an unused millisecond counter). Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-tegra.c | 24 ++-- 1 file changed, 14 insertions(+), 10 deletions(-) diff --git a/drivers/rtc/rtc-tegra.c b/drivers/rtc/rtc-tegra.c index

[PATCH 2/3] rtc: tegra: switch to rtc_time64_to_tm/rtc_tm_to_time64

Call the 64bit versions of rtc_tm time conversion now that the range is enforced by the core. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-tegra.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/rtc/rtc-tegra.c b/drivers/rtc/rtc-tegra.c index

[PATCH 3/3] rtc: tegra: convert to SPDX identifier

Use SPDX-License-Identifier instead of a verbose license text. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-tegra.c | 15 +-- 1 file changed, 1 insertion(+), 14 deletions(-) diff --git a/drivers/rtc/rtc-tegra.c b/drivers/rtc/rtc-tegra.c index e93092aa6f7d..f0ce76865434

[PATCH 1/4] rtc: stmp3xxx: set range

>From the datasheet: "HW_RTC_SECONDS provides access to the 32-bit real-time seconds counter." Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-stmp3xxx.c | 10 -- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/drivers/rtc/rtc-stmp3xxx.c b/drivers/rtc/rtc-stmp3xxx.c

[PATCH 3/4] rtc: stmp3xxx: use .set_time

Use .set_time instead of the deprecated .set_mmss. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-stmp3xxx.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/rtc/rtc-stmp3xxx.c b/drivers/rtc/rtc-stmp3xxx.c index dc0c6cc4849d..143486f69485 100644 ---

[PATCH 2/4] rtc: stmp3xxx: switch to rtc_time64_to_tm/rtc_tm_to_time64

Call the 64bit versions of rtc_tm time conversion now that the range is enforced by the core. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-stmp3xxx.c | 8 +++- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/drivers/rtc/rtc-stmp3xxx.c b/drivers/rtc/rtc-stmp3xxx.c index

[PATCH 4/4] rtc: stmp3xxx: convert to SPDX identifier

Use SPDX-License-Identifier instead of a verbose license text. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-stmp3xxx.c | 10 +- 1 file changed, 1 insertion(+), 9 deletions(-) diff --git a/drivers/rtc/rtc-stmp3xxx.c b/drivers/rtc/rtc-stmp3xxx.c index 143486f69485..ff6488be385f

[PATCH 1/4] rtc: coh901331: set range

The COH 901 331 is a 32bit seconds counter. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-coh901331.c | 15 ++- 1 file changed, 10 insertions(+), 5 deletions(-) diff --git a/drivers/rtc/rtc-coh901331.c b/drivers/rtc/rtc-coh901331.c index 0b232c84f674..5b214db919d0 100644 ---

[PATCH 2/4] rtc: coh901331: switch to rtc_time64_to_tm/rtc_tm_to_time64

Call the 64bit versions of rtc_tm time conversion now that the range is enforced by the core. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-coh901331.c | 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/drivers/rtc/rtc-coh901331.c

[PATCH 3/4] rtc: coh901331: use .set_time

Use .set_time instead of the deprecated .set_mmss. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-coh901331.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/rtc/rtc-coh901331.c b/drivers/rtc/rtc-coh901331.c index 1fd743fefe28..bc9544329419 100644 ---

[PATCH 4/4] rtc: coh901331: convert to SPDX identifier

Use SPDX-License-Identifier instead of the custom license line. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-coh901331.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/rtc/rtc-coh901331.c b/drivers/rtc/rtc-coh901331.c index bc9544329419..4ac850837153 100644

PRINTER BUG LINUX MINT 19 TARA

Please see attached. It was working fine prior to installing Canon linux drivers. CUPS disconnect maybe? I am the only user. Local USB port. Just me. Canon D0550 image class. Has worked fine in the past. Deleted printer and reinstalled but no go. thanks JTK Page 1 ():

  1   2   >