[PATCH v2] ARM: Parse kdump DT properties

2020-12-03 Thread Geert Uytterhoeven
Parse the following DT properties in the crash dump kernel, to provide a modern interface between kexec and the crash dump kernel: - linux,elfcorehdr: ELF core header segment, similar to the "elfcorehdr=" kernel parameter. - linux,usable-memory-range: Usable memory reserved for the crash

RE: [PATCH v2 0/5] memory: renesas-rpc-if: Trivial fixes

2020-12-03 Thread Prabhakar Mahadev Lad
Hi Geert, > -Original Message- > From: Geert Uytterhoeven > Sent: 03 December 2020 10:52 > To: Lad, Prabhakar > Cc: Krzysztof Kozlowski ; Sergei Shtylyov > ; Prabhakar > Mahadev Lad ; Philipp Zabel > ; Jiri > Kosina ; Mark Brown ; Linux-Renesas > s...@vger.kernel.org>; Pavel Machek

Re: [PATCH V4 1/6] PCI: tegra: Fix ASPM-L1SS advertisement disable code

2020-12-03 Thread Vidya Sagar
-Original Message- From: Thierry Reding Sent: Thursday, November 26, 2020 5:03 PM To: Vidya Sagar Cc: lorenzo.pieral...@arm.com; robh...@kernel.org; bhelg...@google.com; Jonathan Hunter ; amanharitsh...@gmail.com; dinghao@zju.edu.cn; k...@linux.com; linux-...@vger.kernel.org;

Re: [MOCKUP] x86/mm: Lightweight lazy mm refcounting

2020-12-03 Thread Matthew Wilcox
On Wed, Dec 02, 2020 at 09:25:51PM -0800, Andy Lutomirski wrote: > This code compiles, but I haven't even tried to boot it. The earlier > part of the series isn't terribly interesting -- it's a handful of > cleanups that remove all reads of ->active_mm from arch/x86. I've > been meaning to do

[PATCH 1/2] MIPS: Don't round up kernel sections size for memblock_add()

2020-12-03 Thread Alexander A Sverdlin
From: Alexander Sverdlin Linux doesn't own the memory immediately after the kernel image. On Octeon bootloader places a shared structure right close after the kernel _end, refer to "struct cvmx_bootinfo *octeon_bootinfo" in cavium-octeon/setup.c. If check_kernel_sections_mem() rounds the PFNs

Re: [PATCH 18/18] ipu3: Add driver for dummy INT3472 ACPI device

2020-12-03 Thread Dan Scally
On 02/12/2020 15:08, Andy Shevchenko wrote: > On Wed, Dec 02, 2020 at 02:42:28PM +0200, Laurent Pinchart wrote: >> On Wed, Dec 02, 2020 at 01:09:56PM +0200, Sakari Ailus wrote: >>> On Tue, Dec 01, 2020 at 08:37:58PM +0200, Laurent Pinchart wrote: > > ... > >> I think we should consider ACPI to

[PATCH 2/2] MIPS: OCTEON: Don't add kernel sections into memblock allocator

2020-12-03 Thread Alexander A Sverdlin
From: Alexander Sverdlin Because check_kernel_sections_mem() does exactly this for all platforms. Signed-off-by: Alexander Sverdlin --- arch/mips/cavium-octeon/setup.c | 9 - 1 file changed, 9 deletions(-) diff --git a/arch/mips/cavium-octeon/setup.c b/arch/mips/cavium-octeon/setup.c

[PATCH v2] RISC-V: enable XIP

2020-12-03 Thread Vitaly Wool
Introduce XIP (eXecute In Place) support for RISC-V platforms. It allows code to be executed directly from non-volatile storage directly addressable by the CPU, such as QSPI NOR flash which can be found on many RISC-V platforms. This makes way for significant optimization of RAM footprint. The XIP

Re: [PATCH v2 1/3] x86/uprobes: Fix not using prefixes.nbytes for loop over prefixes.bytes

2020-12-03 Thread Borislav Petkov
On Thu, Dec 03, 2020 at 01:50:37PM +0900, Masami Hiramatsu wrote: > Since the insn.prefixes.nbytes can be bigger than the size of > insn.prefixes.bytes[] when a same prefix is repeated, we have to > check whether the insn.prefixes.bytes[i] != 0 and i < 4 instead > of insn.prefixes.nbytes. > This

Re: [PATCH v2 1/3] x86/uprobes: Fix not using prefixes.nbytes for loop over prefixes.bytes

2020-12-03 Thread Borislav Petkov
On Thu, Dec 03, 2020 at 01:37:57PM +0100, Borislav Petkov wrote: > Btw, looking at the struct insn definition, that prefixes member should > have a comment above it that those are the legacy prefixes which can be > <= 4. But that's minor. And that naked 4 is poking my eye too - It'd be better if

Re: [RFC][PATCH 1/2] cpufreq: Add special-purpose fast-switching callback for drivers

2020-12-03 Thread Peter Zijlstra
On Mon, Nov 30, 2020 at 07:37:01PM +0100, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > First off, some cpufreq drivers (eg. intel_pstate) can pass hints > beyond the current target frequency to the hardware and there are no Everything CPPC, which is quite a bit these days. > +

Re: linux-next boot error: kernel BUG at include/linux/page-flags.h:LINE!

2020-12-03 Thread Lorenzo Stoakes
On Thu, 3 Dec 2020 at 12:24, Mike Rapoport wrote: > Yeah, the change to initialization of "unavailable" memory missed pfn 0 :( > This should fix it: Tried locally and it fixes the issue for me :)

Re: [PATCH v3 1/1] kasan: fix object remain in offline per-cpu quarantine

2020-12-03 Thread Andrey Konovalov
On Wed, Dec 2, 2020 at 8:58 AM Kuan-Ying Lee wrote: > > We hit this issue in our internal test. > When enabling generic kasan, a kfree()'d object is put into per-cpu > quarantine first. If the cpu goes offline, object still remains in > the per-cpu quarantine. If we call kmem_cache_destroy() now,

Re: [PATCH v6 0/5] Bluetooth: Add new MGMT interface for advertising add

2020-12-03 Thread Marcel Holtmann
Hi Daniel, > This patch series defines the new two-call MGMT interface for adding > new advertising instances. Similarly to the hci advertising commands, a > mgmt call to set parameters is expected to be first, followed by a mgmt > call to set advertising data/scan response. The members of the >

Re: [PATCH v2 1/3] x86/uprobes: Fix not using prefixes.nbytes for loop over prefixes.bytes

2020-12-03 Thread Borislav Petkov
So it ended up like this: --- >From 5014e4e902778d63ce392f864b3654baa4b72384 Mon Sep 17 00:00:00 2001 From: Masami Hiramatsu Date: Thu, 3 Dec 2020 13:50:37 +0900 Subject: [PATCH] x86/uprobes: Do not use prefixes.nbytes when looping over prefixes.bytes Since insn.prefixes.nbytes can be bigger

Re: [PATCH 0/2] RFC: Precise TSC migration

2020-12-03 Thread Maxim Levitsky
On Tue, 2020-12-01 at 20:35 +0100, Thomas Gleixner wrote: > On Mon, Nov 30 2020 at 15:35, Maxim Levitsky wrote: > > The idea of masterclock is that when the host TSC is synchronized > > (or as kernel call it, stable), and the guest TSC is synchronized as well, > > then we can base the kvmclock, on

Re: linux-next: build failure after merge of the akpm tree

2020-12-03 Thread Andrey Konovalov
On Thu, Dec 3, 2020 at 9:52 AM Stephen Rothwell wrote: > > Hi all, > > After merging the akpm tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > mm/kasan/quarantine.c: In function 'quarantine_put': > mm/kasan/quarantine.c:197:15: error: 'info' undeclared (first use in

Re: [PATCH v10 1/3] ARM: uncompress: Add be32tocpu macro

2020-12-03 Thread Ard Biesheuvel
Hallo Geert, On Thu, 3 Dec 2020 at 13:19, Geert Uytterhoeven wrote: > > DTB stores all values as 32-bit big-endian integers. > Add a macro to convert such values to native CPU endianness, to reduce > duplication. > > Signed-off-by: Geert Uytterhoeven > --- > v10: > - New. > --- >

[PATCH 07/11] drivers: staging: vc04_services: remove unneeded MODULE_VERSION() call

2020-12-03 Thread Enrico Weigelt, metux IT consult
Remove MODULE_VERSION(), as it doesn't seem to have any practical purpose. For in-tree drivers, the kernel version really matters. OTOH, the module version doesn't seem to be actively maintained - the code received changes while the version remained constant. Signed-off-by: Enrico Weigelt ---

[PATCH 02/11] drivers: staging: gasket: remove unneeded MODULE_VERSION() call

2020-12-03 Thread Enrico Weigelt, metux IT consult
Remove MODULE_VERSION(), as it doesn't seem to serve any practical purpose. For in-tree drivers, the kernel version matters. The code has received lots of changes, w/o the versions being actively maintained, so it doesn't seem to have much practical meaning. Signed-off-by: Enrico Weigelt ---

[PATCH 11/11] drivers: staging: rtl8723bs: remove unneeded MODULE_VERSION() call

2020-12-03 Thread Enrico Weigelt, metux IT consult
Remove MODULE_VERSION(), as it doesn't seem to serve any practical purpose. The driver received lots of changes, but module remained constant since it landed in mainline, several years ago. Signed-off-by: Enrico Weigelt --- drivers/staging/rtl8723bs/os_dep/os_intfs.c | 1 - 1 file changed, 1

[PATCH 09/11] drivers: staging: rtl8192e: remove unneeded MODULE_VERSION() call

2020-12-03 Thread Enrico Weigelt, metux IT consult
Remove MODULE_VERSION(), as it doesn't seem to have any practical purpose: the driver has received lots of changes, while the module version remained constant. Unmaintained version numbers aren't actually useful. Signed-off-by: Enrico Weigelt --- drivers/staging/rtl8192e/rtl8192e/rtl_core.c | 1

[PATCH 04/11] drivers: staging: goldfish: remove unneeded MODULE_VERSION() call

2020-12-03 Thread Enrico Weigelt, metux IT consult
Remove MODULE_VERSION(), as it doesn't seem to have much practical purpose. For in-kernel drivers, the kernel version matters. The driver received lots of changes, but version number has remained the same since it's introducing into mainline, seven years ago. So, it doesn't seem to have much

[PATCH 06/11] drivers: staging: qlge: remove unneeded MODULE_VERSION() call

2020-12-03 Thread Enrico Weigelt, metux IT consult
Remove MODULE_VERSION(), as it doesn't seem to serve any practical purpose. For in-tree drivers, the kernel version really matters. The module version doesn't seem to be maintained and having much practical meaning anymore. Signed-off-by: Enrico Weigelt --- drivers/staging/qlge/qlge_main.c | 1

Re: [PATCH v10 2/3] ARM: uncompress: Add OF_DT_MAGIC macro

2020-12-03 Thread Ard Biesheuvel
On Thu, 3 Dec 2020 at 13:19, Geert Uytterhoeven wrote: > > The DTB magic marker is stored as a 32-bit big-endian value, and thus > depends on the CPU's endianness. Add a macro to define this value in > native endianness, to reduce #ifdef clutter and (future) duplication. > > Signed-off-by: Geert

[PATCH 01/11] drivers: staging: speakup: remove unneeded MODULE_VERSION() call

2020-12-03 Thread Enrico Weigelt, metux IT consult
Remove MODULE_VERSION(), as it doesn't seem to serve any practical purpose. For in-tree drivers, the kernel version matters. The drivers have received lots of changes, without the module version (or the underlying DRV_VERSION macro) ever changed, since the code landed in the kernel tree. So, it

[PATCH 10/11] drivers: staging: rtl8723bs: remove unneeded MODULE_VERSION() call

2020-12-03 Thread Enrico Weigelt, metux IT consult
Remove MODULE_VERSION(), as it doesn't seem to have any pratical purpose. The code received lots of huge changes, but module version remained constant, since it landed in mainline tree, back 11 years go. Unmaintained version numbers aren't actually useful. For in-tree drivers, the kernel version

[PATCH 08/11] drivers: staging: rtl8188eu: remove unneeded MODULE_VERSION() call

2020-12-03 Thread Enrico Weigelt, metux IT consult
Remove MODULE_VERSION(), as it doesn't seem to serve any practical purpose. For in-kernel drivers, the kernel version matters most. The driver received lots of changes, while module version remained constant, since it landed in mainline, back 7 years ago. Signed-off-by: Enrico Weigelt ---

[PATCH 03/11] drivers: staging: gdm724x: remove unneeded MODULE_VERSION() call

2020-12-03 Thread Enrico Weigelt, metux IT consult
Remove MODULE_VERSION(), as it doesn't seem to serve any practical purpose. For in-kernel drivers, the kernel version matters. And the code has received lots of changes, without the version ever been touched (remained constant since landing in the mainline tree), so it doesn't seem to have any

[PATCH 05/11] drivers: staging: media: remove unneeded MODULE_VERSION() call

2020-12-03 Thread Enrico Weigelt, metux IT consult
Remove MODULE_VERSION(), as it doesn't seem to serve any practical purpose. For in-tree drivers, the kernel version matters. The code received lots of changes, but module version remained constant, since the driver landed in mainline. So, this version doesn't seem have any practical meaning

Re: [PATCH 1/4] reset: hisilicon: correct vendor prefix

2020-12-03 Thread Philipp Zabel
On Thu, 2020-12-03 at 20:02 +0800, Zhen Lei wrote: > The vendor prefix of "Hisilicon Limited" is "hisilicon", it is clearly > stated in "vendor-prefixes.yaml". > > Fixes: 1527058736fa ("reset: hisilicon: add reset-hi3660") > Signed-off-by: Zhen Lei > Cc: Zhangfei Gao > --- >

Re: WARNING: filesystem loop5 was created with 512 inodes, the real maximum is 511, mounting anyway

2020-12-03 Thread Dmitry Vyukov
On Thu, Dec 3, 2020 at 5:15 AM Randy Dunlap wrote: > > On 12/1/20 1:17 PM, Randy Dunlap wrote: > > On 11/30/20 11:47 PM, Dmitry Vyukov wrote: > >> On Tue, Dec 1, 2020 at 2:03 AM Randy Dunlap wrote: > >>> > >>> On 11/30/20 12:43 AM, Dmitry Vyukov wrote: > On Mon, Nov 30, 2020 at 5:29 AM

Re: [PATCH v1 2/5] vfio: platform: Switch to use platform_get_mem_or_io_resource()

2020-12-03 Thread Auger Eric
Hi Andy, On 10/27/20 6:58 PM, Andy Shevchenko wrote: > Switch to use new platform_get_mem_or_io_resource() instead of > home grown analogue. > > Cc: Eric Auger > Cc: Alex Williamson > Cc: Cornelia Huck > Cc: k...@vger.kernel.org > Signed-off-by: Andy Shevchenko Acked-by: Eric Auger Thanks

[PATCH] media: pixfmt-meta-rkisp1.rst: fix two build warnings

2020-12-03 Thread Mauro Carvalho Chehab
With Sphinx 2.x: those two warnings are produced: /devel/v4l/docs/sphinx2/Documentation/output/videodev2.h.rst:6: WARNING: undefined label: v4l2-meta-fmt-rk-isp1-params (if the link has no caption the label must precede a section header)

Re: WARNING: filesystem loop5 was created with 512 inodes, the real maximum is 511, mounting anyway

2020-12-03 Thread Dmitry Vyukov
On Thu, Dec 3, 2020 at 1:55 PM Dmitry Vyukov wrote: > > On Thu, Dec 3, 2020 at 5:15 AM Randy Dunlap wrote: > > > > On 12/1/20 1:17 PM, Randy Dunlap wrote: > > > On 11/30/20 11:47 PM, Dmitry Vyukov wrote: > > >> On Tue, Dec 1, 2020 at 2:03 AM Randy Dunlap > > >> wrote: > > >>> > > >>> On

Re: [PATCH V4 2/6] PCI: tegra: Map configuration space as nGnRnE

2020-12-03 Thread Vidya Sagar
-Original Message- From: Thierry Reding Sent: Thursday, November 26, 2020 5:04 PM To: Vidya Sagar Cc: lorenzo.pieral...@arm.com; robh...@kernel.org; bhelg...@google.com; Jonathan Hunter ; amanharitsh...@gmail.com; dinghao@zju.edu.cn; k...@linux.com; linux-...@vger.kernel.org;

Re: [PATCH 18/18] ipu3: Add driver for dummy INT3472 ACPI device

2020-12-03 Thread Andy Shevchenko
On Thu, Dec 03, 2020 at 12:37:12PM +, Dan Scally wrote: > On 02/12/2020 15:08, Andy Shevchenko wrote: > > On Wed, Dec 02, 2020 at 02:42:28PM +0200, Laurent Pinchart wrote: > >> On Wed, Dec 02, 2020 at 01:09:56PM +0200, Sakari Ailus wrote: > >>> On Tue, Dec 01, 2020 at 08:37:58PM +0200, Laurent

Re: [RFC PATCH 16/27] KVM: arm64: Prepare Hyp memory protection

2020-12-03 Thread Fuad Tabba
Hi Quentin, On Tue, Nov 17, 2020 at 6:17 PM 'Quentin Perret' via kernel-team wrote: > > When memory protection is enabled, the Hyp code needs the ability to > create and manage its own page-table. To do so, introduce a new set of > hypercalls to initialize Hyp memory protection. > > During the

[PATCH] gcc-plugins: simplify GCC plugin-dev capability test

2020-12-03 Thread Masahiro Yamada
Linus pointed out a third of the time in the Kconfig parse stage comes from the single invocation of cc1plus in scripts/gcc-plugin.sh [1], and directly testing plugin-version.h for existence cuts down the overhead a lot. [2] This commit takes one step further to kill the build test entirely. The

Re: [PATCH v2 4/5] amba: Make the remove callback return void

2020-12-03 Thread Uwe Kleine-König
Hello, [This is a resend because somehow my MUA failed to parse the To: list and dropped it without me noticing it. Sorry to those who got it twice now.] On Tue, Nov 24, 2020 at 02:31:38PM +0100, Uwe Kleine-König wrote: > From: Uwe Kleine-König > > All amba drivers return 0 in their remove

Re: [PATCH v13 05/15] iommu/smmuv3: Get prepared for nested stage support

2020-12-03 Thread Auger Eric
Hi Kunkun, On 12/3/20 1:32 PM, Kunkun Jiang wrote: > Hi Eric, > > On 2020/11/18 19:21, Eric Auger wrote: >> When nested stage translation is setup, both s1_cfg and >> s2_cfg are set. >> >> We introduce a new smmu domain abort field that will be set >> upon guest stage1 configuration passing. >>

Re: [PATCH v2 2/6] genirq: Allow an interrupt to be marked as 'raw'

2020-12-03 Thread Peter Zijlstra
On Thu, Nov 26, 2020 at 06:18:33PM +, Valentin Schneider wrote: > If I got the RCU bits right from what Thomas mentioned in > > https://lore.kernel.org/r/87ft5q18qs@nanos.tec.linutronix.de > https://lore.kernel.org/r/87lfewnmdz@nanos.tec.linutronix.de > > then we're still missing

Re: [PATCH v1 2/5] vfio: platform: Switch to use platform_get_mem_or_io_resource()

2020-12-03 Thread Andy Shevchenko
On Thu, Dec 03, 2020 at 01:54:38PM +0100, Auger Eric wrote: > Hi Andy, > > On 10/27/20 6:58 PM, Andy Shevchenko wrote: > > Switch to use new platform_get_mem_or_io_resource() instead of > > home grown analogue. > > > > Cc: Eric Auger > > Cc: Alex Williamson > > Cc: Cornelia Huck > > Cc:

Re: [PATCH v2 2/5] thermal: devfreq_cooling: get a copy of device status

2020-12-03 Thread Daniel Lezcano
On 18/11/2020 13:03, Lukasz Luba wrote: > Devfreq cooling needs to now the correct status of the device in order > to operate. Do not rely on Devfreq last_status which might be a stale data > and get more up-to-date values of the load. > > Devfreq framework can change the device status in the

ANTWORT AUF SPENDENANSPRUCH...

2020-12-03 Thread Charles W. Jackson Jr
IHR E-MAIL-KONTO WURDE FÜR EINE SPENDE VON 3.500.000,00 USD FÜR CHARITY AUSGEWÄHLT. Antworten Sie auf die folgende E-Mail, um weitere Informationen zu erhalten E-Mail: charlesjacksn...@gmail.com -- This email has been checked for viruses by Avast antivirus software.

Re: [PATCH 3/3] ARM: dts: exynos: Fix charging regulator voltage and current for i9100

2020-12-03 Thread Stephan Gerhold
On Thu, Dec 03, 2020 at 11:50:41AM +0200, Krzysztof Kozlowski wrote: > > Unfortunately it seems Samsung started to remove most of older > kernel source code from their OS compliance page. S1, S2 and S3 are > mostly gone. I was able to find just few remaining sources and I am now > updating my

Re: [PATCH v10 3/3] ARM: uncompress: Validate start of physical memory against passed DTB

2020-12-03 Thread Ard Biesheuvel
On Thu, 3 Dec 2020 at 13:19, Geert Uytterhoeven wrote: > > Currently, the start address of physical memory is obtained by masking > the program counter with a fixed mask of 0xf800. This mask value > was chosen as a balance between the requirements of different platforms. > However, this does

[PATCH 1/1] target: Make sure no zero value in the buffer

2020-12-03 Thread Xiaohui Zhang
From: Zhang Xiaohui The fix makes sure no zero value in the buffer, by comparing the strlen() of the original buffer with the size variable. Signed-off-by: Zhang Xiaohui --- drivers/target/target_core_iblock.c | 2 ++ 1 file changed, 2 insertions(+) diff --git

Re: [PATCH v11 1/5] Bluetooth: Interleave with allowlist scan

2020-12-03 Thread Marcel Holtmann
Hi Howard, > This patch implements the interleaving between allowlist scan and > no-filter scan. It'll be used to save power when at least one monitor is > registered and at least one pending connection or one device to be > scanned for. > > The durations of the allowlist scan and the no-filter

Re: [PATCH v2 0/5] memory: renesas-rpc-if: Trivial fixes

2020-12-03 Thread Krzysztof Kozlowski
On Thu, Dec 03, 2020 at 10:41:54AM +, Lad, Prabhakar wrote: > Hi Krzysztof, > > On Thu, Nov 26, 2020 at 7:11 PM Lad Prabhakar > wrote: > > > > Hi All, > > > > This patch series fixes trivial issues in RPC-IF driver. > > > > Changes for v2: > > * Balanced PM in rpcif_disable_rpm > > * Fixed

Re: [PATCH v11 5/5] Bluetooth: Add toggle to switch off interleave scan

2020-12-03 Thread Marcel Holtmann
Hi Howard, > This patch add a configurable parameter to switch off the interleave > scan feature. > > Signed-off-by: Howard Chung > Reviewed-by: Alain Michaud > --- > > (no changes since v9) > > Changes in v9: > - Update and rename the macro TLV_GET_LE8 > > Changes in v7: > - Fix

Re: [PATCH v11 4/5] Bluetooth: Refactor read default sys config for various types

2020-12-03 Thread Marcel Holtmann
Hi Howard, > Refactor read default system configuration function so that it's capable > of returning different types than u16 > > Signed-off-by: Howard Chung > --- > > (no changes since v8) > > Changes in v8: > - Update the commit title and message > > net/bluetooth/mgmt_config.c | 140

Re: [PATCH v11 3/5] Bluetooth: Handle active scan case

2020-12-03 Thread Marcel Holtmann
Hi Howard, > This patch adds code to handle the active scan during interleave > scan. The interleave scan will be canceled when users start active scan, > and it will be restarted after active scan stopped. > > Signed-off-by: Howard Chung > Reviewed-by: Alain Michaud > Reviewed-by: Manish

Re: [PATCH v11 2/5] Bluetooth: Handle system suspend resume case

2020-12-03 Thread Marcel Holtmann
Hi Howard, > This patch adds code to handle the system suspension during interleave > scan. The interleave scan will be canceled when the system is going to > sleep, and will be restarted after waking up. > > Signed-off-by: Howard Chung > Reviewed-by: Alain Michaud > Reviewed-by: Manish

Re: [PATCH v1 1/5] driver core: platform: Introduce platform_get_mem_or_io_resource()

2020-12-03 Thread Cornelia Huck
On Tue, 27 Oct 2020 19:58:02 +0200 Andy Shevchenko wrote: > There are at least few existing users of the proposed API which > retrieves either MEM or IO resource from platform device. > > Make it common to utilize in the existing and new users. > > Signed-off-by: Andy Shevchenko > Cc: Eric

Re: [PATCH v13 05/15] iommu/smmuv3: Get prepared for nested stage support

2020-12-03 Thread Kunkun Jiang
On 2020/12/3 21:01, Auger Eric wrote: Hi Kunkun, On 12/3/20 1:32 PM, Kunkun Jiang wrote: Hi Eric, On 2020/11/18 19:21, Eric Auger wrote: When nested stage translation is setup, both s1_cfg and s2_cfg are set. We introduce a new smmu domain abort field that will be set upon guest stage1

Re: [PATCH v1 2/5] vfio: platform: Switch to use platform_get_mem_or_io_resource()

2020-12-03 Thread Cornelia Huck
On Tue, 27 Oct 2020 19:58:03 +0200 Andy Shevchenko wrote: > Switch to use new platform_get_mem_or_io_resource() instead of > home grown analogue. > > Cc: Eric Auger > Cc: Alex Williamson > Cc: Cornelia Huck > Cc: k...@vger.kernel.org > Signed-off-by: Andy Shevchenko > --- >

My Greetings

2020-12-03 Thread Mrs. Maya Oliver
My Dear My Name is Mrs. Maya Oliver, from Norway. I know that this message will be a surprise to you. Firstly, I am married to Mr. Patrick Oliver, A gold merchant who owns a small gold Mine in Burkina Faso; He died of Cardiovascular Disease in mid-March 2011. During his life time he deposited the

Re: [PATCH 01/11] drivers: staging: speakup: remove unneeded MODULE_VERSION() call

2020-12-03 Thread Greg KH
On Thu, Dec 03, 2020 at 01:47:53PM +0100, Enrico Weigelt, metux IT consult wrote: > Remove MODULE_VERSION(), as it doesn't seem to serve any practical > purpose. For in-tree drivers, the kernel version matters. > > The drivers have received lots of changes, without the module version > (or the

Re: NULL pointer dereference bug

2020-12-03 Thread Greg KH
On Wed, Dec 02, 2020 at 07:56:08PM -0500, Ertza Warraich wrote: > We report a null ptr deref bug (in linux-5.8.13) found by FuzzUSB (a > modified version of syzkaller). 5.8.y is end-of-life, you should test 5.9.y at the oldest. Anyway, without a reproducer or a patch for this, it's not going to

[PATCH AUTOSEL 5.9 02/39] arm64: dts: rockchip: Remove system-power-controller from pmic on Odroid Go Advance

2020-12-03 Thread Sasha Levin
From: Maciej Matuszczyk [ Upstream commit 01fe332800d0d2f94337b45c1973f4cf28ae6195 ] This fixes a poweroff issue when this is supposed to happen via PSCI. Signed-off-by: Maciej Matuszczyk Link: https://lore.kernel.org/r/20201023181629.119727-1-maccraft12...@gmail.com Signed-off-by: Heiko

[PATCH AUTOSEL 5.9 01/39] phy: usb: Fix incorrect clearing of tca_drv_sel bit in SETUP reg for 7211

2020-12-03 Thread Sasha Levin
From: Al Cooper [ Upstream commit 209c805835b29495cf66cc705b206da8f4a68e6e ] The 7211a0 has a tca_drv_sel bit in the USB SETUP register that should never be enabled. This feature is only used if there is a USB Type-C PHY, and the 7211 does not have one. If the bit is enabled, the VBUS signal

[PATCH AUTOSEL 5.9 04/39] arm64: dts: rockchip: Assign a fixed index to mmc devices on rk3399 boards.

2020-12-03 Thread Sasha Levin
From: Markus Reichl [ Upstream commit 0011c6d182774fc781fb9e115ebe8baa356029ae ] Recently introduced async probe on mmc devices can shuffle block IDs. Pin them to fixed values to ease booting in environments where UUIDs are not practical. Use newly introduced aliases for mmcblk devices from

[PATCH AUTOSEL 5.9 05/39] arm64: dts: rockchip: Reorder LED triggers from mmc devices on rk3399-roc-pc.

2020-12-03 Thread Sasha Levin
From: Markus Reichl [ Upstream commit 7327c8b98e2e14c47021eea14d1ab268086a6408 ] After patch [1] SD-card becomes mmc1 and eMMC becomes mmc2. Correct trigger of LEDs accordingly. [1] https://patchwork.kernel.org/patch/11881427 Signed-off-by: Markus Reichl Link:

[PATCH AUTOSEL 5.9 06/39] iwlwifi: sta: set max HE max A-MPDU according to HE capa

2020-12-03 Thread Sasha Levin
From: Mordechay Goodstein [ Upstream commit c8a2e7a29702fe4626b7aa81149b7b7164e20606 ] Currently, our max tpt is limited to max HT A-MPDU for LB, and max VHT A-MPDU for HB. Configure HE exponent value correctly to achieve HE max A-MPDU, both on LB and HB. Signed-off-by: Mordechay Goodstein

[PATCH AUTOSEL 5.9 03/39] iwlwifi: pcie: limit memory read spin time

2020-12-03 Thread Sasha Levin
From: Johannes Berg [ Upstream commit 04516706bb99889986ddfa3a769ed50d2dc7ac13 ] When we read device memory, we lock a spinlock, write the address we want to read from the device and then spin in a loop reading the data in 32-bit quantities from another register. As the description makes

[PATCH AUTOSEL 5.9 09/39] powerpc: Drop -me200 addition to build flags

2020-12-03 Thread Sasha Levin
From: Michael Ellerman [ Upstream commit e02152ba2810f7c88cb54e71cda096268dfa9241 ] Currently a build with CONFIG_E200=y will fail with: Error: invalid switch -me200 Error: unrecognized option -me200 Upstream binutils has never supported an -me200 option. Presumably it was supported at

[PATCH AUTOSEL 5.9 08/39] iwlwifi: mvm: fix kernel panic in case of assert during CSA

2020-12-03 Thread Sasha Levin
From: Sara Sharon [ Upstream commit fe56d05ee6c87f6a1a8c7267affd92c9438249cc ] During CSA, we briefly nullify the phy context, in __iwl_mvm_unassign_vif_chanctx. In case we have a FW assert right after it, it remains NULL though. We end up running into endless loop due to mac80211 trying

[PATCH AUTOSEL 5.9 14/39] interconnect: qcom: msm8916: Remove rpm-ids from non-RPM nodes

2020-12-03 Thread Sasha Levin
From: Georgi Djakov [ Upstream commit c497f9322af947204c28292be6f20dd2d97483dd ] Some nodes are incorrectly marked as RPM-controlled (they have RPM master and slave ids assigned), but are actually controlled by the application CPU instead. The RPM complains when we send requests for resources

[PATCH AUTOSEL 5.9 17/39] tun: honor IOCB_NOWAIT flag

2020-12-03 Thread Sasha Levin
From: Jens Axboe [ Upstream commit 5aac0390a63b8718237a61dd0d24a29201d1c94a ] tun only checks the file O_NONBLOCK flag, but it should also be checking the iocb IOCB_NOWAIT flag. Any fops using ->read/write_iter() should check both, otherwise it breaks users that correctly expect O_NONBLOCK

[PATCH AUTOSEL 5.9 12/39] scsi: ufs: Fix unexpected values from ufshcd_read_desc_param()

2020-12-03 Thread Sasha Levin
From: Can Guo [ Upstream commit 1699f980d87fb678a669490462cf0b9517c1fb47 ] WB-related sysfs entries can be accessed even when an UFS device does not support the feature. The descriptors which are not supported by the UFS device may be wrongly reported when they are accessed from their

[PATCH AUTOSEL 5.9 15/39] interconnect: qcom: qcs404: Remove GPU and display RPM IDs

2020-12-03 Thread Sasha Levin
From: Georgi Djakov [ Upstream commit 7ab1e9117607485df977bb6e271be5c5ad649a4c ] The following errors are noticed during boot on a QCS404 board: [2.926647] qcom_icc_rpm_smd_send mas 6 error -6 [2.934573] qcom_icc_rpm_smd_send mas 8 error -6 These errors show when we try to configure

[PATCH AUTOSEL 5.9 38/39] can: m_can: m_can_dev_setup(): add support for bosch mcan version 3.3.0

2020-12-03 Thread Sasha Levin
From: Pankaj Sharma [ Upstream commit 5c7d55bded77da6db7c5d249610e3a2eed730b3c ] Add support for mcan bit timing and control mode according to bosch mcan IP version 3.3.0. The mcan version read from the Core Release field of CREL register would be 33. Accordingly the properties are to be set

[PATCH AUTOSEL 5.9 32/39] platform/x86: thinkpad_acpi: Add BAT1 is primary battery quirk for Thinkpad Yoga 11e 4th gen

2020-12-03 Thread Sasha Levin
From: Hans de Goede [ Upstream commit c986a7024916c92a775fc8d853fba3cae1d5fde4 ] The Thinkpad Yoga 11e 4th gen with the N3450 / Celeron CPU only has one battery which is named BAT1 instead of the expected BAT0, add a quirk for this. This fixes not being able to set the charging tresholds on

[PATCH AUTOSEL 5.9 10/39] arm64: dts: broadcom: clear the warnings caused by empty dma-ranges

2020-12-03 Thread Sasha Levin
From: Zhen Lei [ Upstream commit 2013a4b684b6eb614ee5c9a3c07b0ae6f5ca96d9 ] The scripts/dtc/checks.c requires that the node have empty "dma-ranges" property must have the same "#address-cells" and "#size-cells" values as the parent node. Otherwise, the following warnings is reported:

[PATCH AUTOSEL 5.9 29/39] arm64: tegra: Disable the ACONNECT for Jetson TX2

2020-12-03 Thread Sasha Levin
From: Jon Hunter [ Upstream commit fb319496935b7475a863a00c76895e8bb3216704 ] Commit ff4c371d2bc0 ("arm64: defconfig: Build ADMA and ACONNECT driver") enable the Tegra ADMA and ACONNECT drivers and this is causing resume from system suspend to fail on Jetson TX2. Resume is failing because the

[PATCH AUTOSEL 5.9 39/39] can: af_can: can_rx_unregister(): remove WARN() statement from list operation sanity check

2020-12-03 Thread Sasha Levin
From: Oliver Hartkopp [ Upstream commit d73ff9b7c4eacaba0fd956d14882bcae970f8307 ] To detect potential bugs in CAN protocol implementations (double removal of receiver entries) a WARN() statement has been used if no matching list item was found for removal. The fault injection issued by

[PATCH AUTOSEL 5.4 02/23] arm64: dts: rockchip: Assign a fixed index to mmc devices on rk3399 boards.

2020-12-03 Thread Sasha Levin
From: Markus Reichl [ Upstream commit 0011c6d182774fc781fb9e115ebe8baa356029ae ] Recently introduced async probe on mmc devices can shuffle block IDs. Pin them to fixed values to ease booting in environments where UUIDs are not practical. Use newly introduced aliases for mmcblk devices from

[PATCH AUTOSEL 5.9 18/39] ibmvnic: skip tx timeout reset while in resetting

2020-12-03 Thread Sasha Levin
From: Lijun Pan [ Upstream commit 855a631a4c11458a9cef1ab79c1530436aa95fae ] Sometimes it takes longer than 5 seconds (watchdog timeout) to complete failover, migration, and other resets. In stead of scheduling another timeout reset, we wait for the current one to complete. Suggested-by: Brian

[PATCH AUTOSEL 5.4 03/23] iwlwifi: pcie: set LTR to avoid completion timeout

2020-12-03 Thread Sasha Levin
From: Johannes Berg [ Upstream commit edb625208d84aef179e3f16590c1c582fc5fdae6 ] On some platforms, the preset values aren't correct and then we may get a completion timeout in the firmware. Change the LTR configuration to avoid that. The firmware will do some more complex reinit of this later,

[PATCH AUTOSEL 5.4 09/23] interconnect: qcom: qcs404: Remove GPU and display RPM IDs

2020-12-03 Thread Sasha Levin
From: Georgi Djakov [ Upstream commit 7ab1e9117607485df977bb6e271be5c5ad649a4c ] The following errors are noticed during boot on a QCS404 board: [2.926647] qcom_icc_rpm_smd_send mas 6 error -6 [2.934573] qcom_icc_rpm_smd_send mas 8 error -6 These errors show when we try to configure

[PATCH AUTOSEL 5.9 33/39] platform/x86: thinkpad_acpi: Whitelist P15 firmware for dual fan control

2020-12-03 Thread Sasha Levin
From: Matthias Maier [ Upstream commit 80a8c3185f5047dc7438ed226b72385bf93b4071 ] This commit enables dual fan control for the following new Lenovo models: P15, P15v. Signed-off-by: Matthias Maier Link: https://lore.kernel.org/r/20201126000416.2459645-2-tamiko-ibm-acpi-de...@43-1.org

[PATCH AUTOSEL 5.4 11/23] tun: honor IOCB_NOWAIT flag

2020-12-03 Thread Sasha Levin
From: Jens Axboe [ Upstream commit 5aac0390a63b8718237a61dd0d24a29201d1c94a ] tun only checks the file O_NONBLOCK flag, but it should also be checking the iocb IOCB_NOWAIT flag. Any fops using ->read/write_iter() should check both, otherwise it breaks users that correctly expect O_NONBLOCK

[PATCH AUTOSEL 5.4 13/23] irqchip/gic-v3-its: Unconditionally save/restore the ITS state on suspend

2020-12-03 Thread Sasha Levin
From: Xu Qiang [ Upstream commit 74cde1a53368aed4f2b4b54bf7030437f64a534b ] On systems without HW-based collections (i.e. anything except GIC-500), we rely on firmware to perform the ITS save/restore. This doesn't really work, as although FW can properly save everything, it cannot fully restore

[PATCH AUTOSEL 5.4 15/23] soc: fsl: dpio: Get the cpumask through cpumask_of(cpu)

2020-12-03 Thread Sasha Levin
From: Hao Si [ Upstream commit 2663b3388551230cbc4606a40fabf3331ceb59e4 ] The local variable 'cpumask_t mask' is in the stack memory, and its address is assigned to 'desc->affinity' in 'irq_set_affinity_hint()'. But the memory area where this variable is located is at risk of being modified.

[PATCH AUTOSEL 4.19 04/14] powerpc: Drop -me200 addition to build flags

2020-12-03 Thread Sasha Levin
From: Michael Ellerman [ Upstream commit e02152ba2810f7c88cb54e71cda096268dfa9241 ] Currently a build with CONFIG_E200=y will fail with: Error: invalid switch -me200 Error: unrecognized option -me200 Upstream binutils has never supported an -me200 option. Presumably it was supported at

[PATCH AUTOSEL 4.19 08/14] tun: honor IOCB_NOWAIT flag

2020-12-03 Thread Sasha Levin
From: Jens Axboe [ Upstream commit 5aac0390a63b8718237a61dd0d24a29201d1c94a ] tun only checks the file O_NONBLOCK flag, but it should also be checking the iocb IOCB_NOWAIT flag. Any fops using ->read/write_iter() should check both, otherwise it breaks users that correctly expect O_NONBLOCK

[PATCH AUTOSEL 4.19 13/14] platform/x86: acer-wmi: add automatic keyboard background light toggle key as KEY_LIGHTS_TOGGLE

2020-12-03 Thread Sasha Levin
From: Timo Witte [ Upstream commit 9e7a005ad56aa7d6ea5830c5ffcc60bf35de380b ] Got a dmesg message on my AMD Renoir based Acer laptop: "acer_wmi: Unknown key number - 0x84" when toggling keyboard background light Signed-off-by: Timo Witte Reviewed-by: "Lee, Chun-Yi" Link:

[PATCH AUTOSEL 4.19 11/14] platform/x86: thinkpad_acpi: Do not report SW_TABLET_MODE on Yoga 11e

2020-12-03 Thread Sasha Levin
From: Hans de Goede [ Upstream commit f2eae1888cf22590c38764b8fa3c989c0283870e ] The Yoga 11e series has 2 accelerometers described by a BOSC0200 ACPI node. This setup relies on a Windows service which reads both accelerometers and then calculates the angle between the 2 halves to determine

[PATCH AUTOSEL 4.9 2/5] arm64: dts: rockchip: Assign a fixed index to mmc devices on rk3399 boards.

2020-12-03 Thread Sasha Levin
From: Markus Reichl [ Upstream commit 0011c6d182774fc781fb9e115ebe8baa356029ae ] Recently introduced async probe on mmc devices can shuffle block IDs. Pin them to fixed values to ease booting in environments where UUIDs are not practical. Use newly introduced aliases for mmcblk devices from

[PATCH AUTOSEL 4.14 5/9] scsi: ufs: Make sure clk scaling happens only when HBA is runtime ACTIVE

2020-12-03 Thread Sasha Levin
From: Can Guo [ Upstream commit 73cc291c270248567245f084dcdf5078069af6b5 ] If someone plays with the UFS clk scaling devfreq governor through sysfs, ufshcd_devfreq_scale may be called even when HBA is not runtime ACTIVE. This can lead to unexpected error. We cannot just protect it by calling

[PATCH AUTOSEL 4.4 3/3] platform/x86: acer-wmi: add automatic keyboard background light toggle key as KEY_LIGHTS_TOGGLE

2020-12-03 Thread Sasha Levin
From: Timo Witte [ Upstream commit 9e7a005ad56aa7d6ea5830c5ffcc60bf35de380b ] Got a dmesg message on my AMD Renoir based Acer laptop: "acer_wmi: Unknown key number - 0x84" when toggling keyboard background light Signed-off-by: Timo Witte Reviewed-by: "Lee, Chun-Yi" Link:

[PATCH AUTOSEL 4.4 1/3] ARC: stack unwinding: don't assume non-current task is sleeping

2020-12-03 Thread Sasha Levin
From: Vineet Gupta [ Upstream commit e42404fa10fd11fe72d0a0e149a321d10e577715 ] To start stack unwinding (SP, PC and BLINK) are needed. When the explicit execution context (pt_regs etc) is not available, unwinder assumes the task is sleeping (in __switch_to()) and fetches SP and BLINK from

[PATCH AUTOSEL 4.14 4/9] ARC: stack unwinding: don't assume non-current task is sleeping

2020-12-03 Thread Sasha Levin
From: Vineet Gupta [ Upstream commit e42404fa10fd11fe72d0a0e149a321d10e577715 ] To start stack unwinding (SP, PC and BLINK) are needed. When the explicit execution context (pt_regs etc) is not available, unwinder assumes the task is sleeping (in __switch_to()) and fetches SP and BLINK from

[PATCH AUTOSEL 4.4 2/3] usbnet: ipheth: fix connectivity with iOS 14

2020-12-03 Thread Sasha Levin
From: Yves-Alexis Perez [ Upstream commit f33d9e2b48a34e1558b67a473a1fc1d6e793f93c ] Starting with iOS 14 released in September 2020, connectivity using the personal hotspot USB tethering function of iOS devices is broken. Communication between the host and the device (for example ICMP traffic

[PATCH AUTOSEL 5.4 04/23] iwlwifi: mvm: fix kernel panic in case of assert during CSA

2020-12-03 Thread Sasha Levin
From: Sara Sharon [ Upstream commit fe56d05ee6c87f6a1a8c7267affd92c9438249cc ] During CSA, we briefly nullify the phy context, in __iwl_mvm_unassign_vif_chanctx. In case we have a FW assert right after it, it remains NULL though. We end up running into endless loop due to mac80211 trying

[PATCH AUTOSEL 5.4 01/23] iwlwifi: pcie: limit memory read spin time

2020-12-03 Thread Sasha Levin
From: Johannes Berg [ Upstream commit 04516706bb99889986ddfa3a769ed50d2dc7ac13 ] When we read device memory, we lock a spinlock, write the address we want to read from the device and then spin in a loop reading the data in 32-bit quantities from another register. As the description makes

[PATCH AUTOSEL 5.4 05/23] powerpc: Drop -me200 addition to build flags

2020-12-03 Thread Sasha Levin
From: Michael Ellerman [ Upstream commit e02152ba2810f7c88cb54e71cda096268dfa9241 ] Currently a build with CONFIG_E200=y will fail with: Error: invalid switch -me200 Error: unrecognized option -me200 Upstream binutils has never supported an -me200 option. Presumably it was supported at

[PATCH AUTOSEL 5.4 10/23] usbnet: ipheth: fix connectivity with iOS 14

2020-12-03 Thread Sasha Levin
From: Yves-Alexis Perez [ Upstream commit f33d9e2b48a34e1558b67a473a1fc1d6e793f93c ] Starting with iOS 14 released in September 2020, connectivity using the personal hotspot USB tethering function of iOS devices is broken. Communication between the host and the device (for example ICMP traffic

[PATCH AUTOSEL 5.9 35/39] platform/x86: intel-vbtn: Support for tablet mode on HP Pavilion 13 x360 PC

2020-12-03 Thread Sasha Levin
From: Max Verevkin [ Upstream commit 8b205d3e1bf52ab31cdd5c55f87c87a227793d84 ] The Pavilion 13 x360 PC has a chassis-type which does not indicate it is a convertible, while it is actually a convertible. Add it to the dmi_switches_allow_list. Signed-off-by: Max Verevkin Link:

<    3   4   5   6   7   8   9   10   11   12   >