Add PHY voltage supply information fixing the following kernel message:
2188000.ethernet supply phy not found, using dummy regulator
Also add PHY clock information to avoid depending on the bootloader
programming correct values.
The bootloader also sets some reserved registers in the PHY as
advi
Explicitly mark I2C GPIOs as open drain to fix the following
kernel message being printed:
enforced open drain please flag it properly in DT/ACPI DSDT/board file
Signed-off-by: Sebastian Reichel
---
arch/arm/boot/dts/imx6q-bx50v3.dtsi | 12 ++--
1 file changed, 6 insertions(+), 6 deleti
From: Ian Ray
Define GPIO line names for b450v3, b650v3, and b850v3.
Signed-off-by: Ian Ray
Signed-off-by: Sebastian Reichel
---
arch/arm/boot/dts/imx6q-b450v3.dts | 5 +
arch/arm/boot/dts/imx6q-b650v3.dts | 5 +
arch/arm/boot/dts/imx6q-b850v3.dts | 5 +
3 files changed, 15 insert
On Tue, Feb 23, 2021 at 10:05:49AM -0800, Axel Rasmussen wrote:
> On Tue, Feb 23, 2021 at 7:38 AM Peter Xu wrote:
> >
> > On Thu, Feb 18, 2021 at 04:48:22PM -0800, Axel Rasmussen wrote:
> > > @@ -4645,8 +4646,18 @@ int hugetlb_mcopy_atomic_pte(struct mm_struct
> > > *dst_mm,
> > > spinlock_
s-out-of-the-bounds-of-referenced-subobject-feature-with-type-unsigned-char-at-offset
| `--
include-linux-fortify-string.h:warning:__builtin_memcpy-offset-from-the-object-at-flow_keys-is-out-of-the-bounds-of-referenced-subobject-ipv6_src-with-type-__u32-aka-unsigned-int-at-offset
`-- i386-rand
Hi Jonathan,
Thanks for the detailed and careful review of this patch. Good to hear
that v7 is not required. Please find below answers to your
questions. Looking forward to seeing this patch merged in the next
cycle. Thanks for your help in making this happen.
1)
>1) Use of long long to get s64
Hi,
On Sun, Feb 21, 2021 at 06:30:10PM -0800, Randy Dunlap wrote:
> Hi,
>
> one spello in 2 locations:
>
> On 2/21/21 7:49 AM, John Wood wrote:
> [...]
> > these statistics dissapear when the involved tasks finished. In this
>
>disappear
> [...]
> > + * statistics dissapear whe
On Tue, Feb 23, 2021 at 7:42 AM Jessica Yu wrote:
>
> Please pull below to receive modules updates for the v5.12 merge window.
"struct symsearch is only used inside of module.h, so move the definition
out of module.h"
Whaa?
The first module.h should be module.c. Oh well.
Pulled.
On Thu, Feb 18, 2021 at 11:55:48AM -0800, Vipin Sharma
wrote:
> --- a/arch/x86/kvm/svm/sev.c
> +++ b/arch/x86/kvm/svm/sev.c
> [...]
> +#ifndef CONFIG_KVM_AMD_SEV
> +/*
> + * When this config is not defined, SEV feature is not supported and APIs in
> + * this file are not used but this file still
On Fri, 19 Feb 2021 11:13:02 -0500
Daniel Jordan wrote:
> v2:
> - Fixed missing error unwind in patch 3 (Alex). After more thought,
>the ENODEV case is fine, so it stayed the same.
>
> - Rebased on linux-vfio.git/next (no conflicts).
>
> ---
>
> The VFIO type1 driver is calling pin_user
Hello.
On Thu, Feb 18, 2021 at 11:55:47AM -0800, Vipin Sharma
wrote:
> This patch is creating a new misc cgroup controller for allocation and
> tracking of resources which are not abstract like other cgroup
> controllers.
Please don't refer to this as "allocation" anywhere, that has a specific
m
Hi,
On Sun, Feb 21, 2021 at 06:47:16PM -0800, Randy Dunlap wrote:
> Hi--
>
> scripts/kernel-doc does not like these items to be marked
> as being in kernel-doc notation. scripts/kernel-doc does not
> recognize them as one of: struct, union, enum, typedef, so it
> defaults to trying to interpret th
I2S-MCC found on SAMA7G5 includes 2 FIFOs (capture and playback). When
FIFOs are enabled, bits I2SMCC_ISRA.TXLRDYx and I2SMCC_ISRA.TXRRDYx must
not be used. Bits I2SMCC_ISRB.TXFFRDY and I2SMCC_ISRB.RXFFRDY must be used
instead.
Signed-off-by: Codrin Ciubotariu
---
sound/soc/atmel/mchp-i2s-mcc.c
The latest I2S-MCC available in SAMA7G5 supports multi-channel for I2S and
Left-Justified formats. For this, the new version uses 8 (4 * 2) input and
output pins, with each pin being responsible for 2 channels. This sums up
to a total of 8 channels for synchronous capture and playback.
Signed-off-
SAMA7G5's I2S-MCC has 4 pairs of DIN/DOUT pins. Since TDM only uses a
single pair of pins for synchronous capture and playback, the controller
needs to be told which of the pair is connected. This can be mentioned
using the new "microchip,tdm-data-pair" property. The property is optional,
needed on
This patch converts the Microchip I2SMCC bindings to DT schema format
using json-schema.
Signed-off-by: Codrin Ciubotariu
---
.../bindings/sound/mchp,i2s-mcc.yaml | 86 +++
.../bindings/sound/mchp-i2s-mcc.txt | 43 --
2 files changed, 86 insertions(+),
SAMA7G5's I2S-MCC has 4 pairs of DIN/DOUT pins. Since TDM only uses a
single pair of pins for synchronous capture and playback, the controller
needs to be told which of the pair is connected. This can be mentioned
using the "microchip,tdm-data-pair" property from DT. The property is
optional, usefu
Microchip's new SAMA7G5 includes an updated I2S-MCC compatible with the
previous version found on SAM9X60. The new controller includes 8 (4 * 2)
input and output data pins for up to 8 channels for I2S and Left-Justified
formats.
Signed-off-by: Codrin Ciubotariu
---
sound/soc/atmel/Kconfig
SAMA7G5 includes an updated version of I2S-MCC, found previously on
SAM9X60. This controller includes 8 data pins, 4 for playback and 4 for
capture. For I2S and LEFT_J formats, these pins can be used to
send/receive up to 8 audio channels. For DSP_A, with TDM, any pins pair
(DIN/DOUT) from these 4
SAMA7G5 includes an updated version of the I2S-MCC driver, that includes
3 more DIN/DOUT pin pairs for multi-channel.
Signed-off-by: Codrin Ciubotariu
---
Documentation/devicetree/bindings/sound/mchp,i2s-mcc.yaml | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/Documenta
On Tue, Feb 23, 2021 at 07:03:47PM +0100, Heiko Carstens wrote:
> Well, if we would have e.g. RANDCONFIG, then we could probably revert
> 334ef6ed06fa ("init/Kconfig: make COMPILE_TEST depend on !S390") and
> instead let COMPILE_TEST depend on !RANDCONFIG.
> I think this _could_ solve all common pr
Including the generated syscall headers in 'targets' is wrong because they
are not built in $(obj)/ and the Makefile does its own path prefix and
build rules.
Cc: Andy Lutomirski
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: Borislav Petkov
Cc: x...@kernel.org
Cc: "H. Peter Anvin"
Cc: Masahiro Yama
Hi,
On Sun, Feb 21, 2021 at 06:25:51PM -0800, Randy Dunlap wrote:
> Hi--
>
> On 2/21/21 7:49 AM, John Wood wrote:
> >
> > +/**
> > + * print_fork_attack_running() - Warn about a fork brute force attack.
> > + */
> > +static inline void print_fork_attack_running(void)
> > +{
> > + pr_warn("Fork b
If arch code calls the wrong kernel entry helpers, syscall entries and
exits can get out of sync. Add a new field to task_struct to track the
syscall state and validate that it transitions correctly.
Signed-off-by: Andy Lutomirski
---
include/linux/entry-common.h | 11 +++
include/linux
test_syscall_vdso_32 ended up with an executable stacks because the asm was
missing the annotation that says that it is modern and doesn't need an
executable stack. Add the annotation.
This was missed in commit aeaaf005da1d ("selftests/x86: Add missing
.note.GNU-stack sections").
Signed-off-by:
On a 32-bit fast syscall that fails to read its arguments from user
memory, the kernel currently does syscall exit work but not
syscall entry work. This confuses audit and ptrace. For example:
$ ./tools/testing/selftests/x86/syscall_arg_fault_32
...
strace: pid 264258: entering, ptra
The compat syscall argument fixup error path is wrong. Fix it.
This also adds some sanity checks to the kernel that catch the bug
when running selftests.
Changes from v1:
- The fix is actually correct this time, I hope
Andy Lutomirski (3):
entry: Check that syscall entries and syscall exits
Any non-phony targets need to be in gitignore. The normal way to check
this is doing an in-tree build and running git-status which is easy to
miss. Git provides an easy way to check whether a file is ignored with
git-check-ignore. Let's add a build time check using it. If the build is
not in a git
The old-atomics and missing-syscalls targets are not files, so they
should be marked as PHONY.
Cc: Masahiro Yamada
Cc: Michal Marek
Signed-off-by: Rob Herring
---
Kbuild | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Kbuild b/Kbuild
index fa441b98c9f6..032157c3ffd2 100644
--- a/Kbuild
+
On Tue, Feb 23, 2021 at 11:23 AM Alex Riesen
wrote:
>
> Alex Riesen, Tue, Feb 23, 2021 16:51:26 +0100:
> > Ilia Mirkin, Tue, Feb 23, 2021 16:46:52 +0100:
> > > I'd recommend using xf86-video-nouveau in any case, but some distros
> >
> > I would like try this out. Do you know how to force the xorg
On Tue, Feb 23, 2021 at 3:34 PM Marco Elver wrote:
>
> Adds bit perf_event_attr::sigtrap, which can be set to cause events to
> send SIGTRAP (with si_code TRAP_PERF) to the task where the event
> occurred. To distinguish perf events and allow user space to decode
> si_perf (if set), the event type
Linus wasn't happy that I forgot a gitignore entry in my recent PR.
Checking that requires doing in tree build (which is not my usual
workflow) and checking git status afterwards. Given either one I'll
easily forget again, I came up with a build time check which works for
in tree and out of tree bu
From: "Madhavan T. Venkataraman"
Unwinder changes
Termination
===
Currently, the unwinder terminates when both the FP (frame pointer)
and the PC (return address) of a frame are 0. But a frame could get
corrupted and zeroed. There
From: "Madhavan T. Venkataraman"
I have made an attempt to add some enhancements to the stack trace code
so it is a few steps closer to what is required for livepatch.
Unwinder changes
Termination
===
Currently, the unwinder terminates when both
Document the binding for the BCM6345 external interrupt controller.
Signed-off-by: Álvaro Fernández Rojas
Signed-off-by: Jonas Gorski
---
.../brcm,bcm6345-ext-intc.yaml| 61 +++
1 file changed, 61 insertions(+)
create mode 100644
Documentation/devicetree/bindin
This interrupt controller is present on bcm63xx SoCs in order to generate
interrupts based on GPIO status changes.
Signed-off-by: Álvaro Fernández Rojas
Signed-off-by: Jonas Gorski
---
drivers/irqchip/Kconfig | 4 +
drivers/irqchip/Makefile | 1 +
drivers/irqchip/irq-bcm6
This interrupt controller is present on bcm63xx SoCs in order to generate
interrupts based on GPIO status changes.
Álvaro Fernández Rojas (2):
dt-bindings: interrupt-controller: document BCM6345 external interrupt
controller
irqchip: add support for BCM6345 interrupt controller
.../brcm,
On Tue, Feb 23, 2021 at 7:38 AM Peter Xu wrote:
>
> On Thu, Feb 18, 2021 at 04:48:22PM -0800, Axel Rasmussen wrote:
> > @@ -4645,8 +4646,18 @@ int hugetlb_mcopy_atomic_pte(struct mm_struct
> > *dst_mm,
> > spinlock_t *ptl;
> > int ret;
> > struct page *page;
> > + int writab
On 2/23/21 6:57 AM, Gerald Schaefer wrote:
> Hi,
>
> LTP triggered a panic on s390 in hugepage_subpool_put_pages() with
> linux-next 5.12.0-20210222, see below.
>
> It crashes on the spin_lock(&spool->lock) at the beginning, because the
> passed-in *spool points to 004e, which is not
On 2/23/2021 10:47 AM, Mike Rapoport wrote:
Hi George,
On Tue, Feb 23, 2021 at 09:35:32AM -0500, George Kennedy wrote:
On 2/23/2021 5:33 AM, Mike Rapoport wrote:
(re-added CC)
On Mon, Feb 22, 2021 at 08:24:59PM -0500, George Kennedy wrote:
On 2/22/2021 4:55 PM, Mike Rapoport wrote:
On Mo
On Tue, Feb 23, 2021 at 09:41:40AM -0800, Guenter Roeck wrote:
> > I tried to explain why we don't want to set COMPILE_TEST for s390
> > anymore. It overrides architecture dependencies in Kconfig, and lots
> > of drivers do not set dependencies for HAS_IOMEM, HAS_DMA, and friends
> > correctly.
> >
On Tue, Feb 23, 2021 at 3:52 PM Marco Elver wrote:
> Introduces the TRAP_PERF si_code, and associated siginfo_t field
> si_perf. These will be used by the perf event subsystem to send signals
> (if requested) to the task where an event occurred.
>
> Signed-off-by: Marco Elver
> arch/m68k/kernel
Hi Manivannan,
Manivannan Sadhasivam wrote on Tue,
23 Feb 2021 23:15:46 +0530:
> Hi Miquel,
>
> On Tue, Feb 23, 2021 at 05:49:22PM +0100, Miquel Raynal wrote:
> > Hi Manivannan,
> >
> > Manivannan Sadhasivam wrote on Mon,
> > 22 Feb 2021 17:32:58 +0530:
> >
> > > On a typical end product,
Lontium Lt8912 is a DSI to HDMI bridge.
Signed-off-by: Adrien Grassein
---
MAINTAINERS | 1 +
drivers/gpu/drm/bridge/Kconfig | 14 +
drivers/gpu/drm/bridge/Makefile | 1 +
drivers/gpu/drm/bridge/lontium-lt8912.c | 764
4
Lontium LT8912 is a DSI to HDMI bridge.
Signed-off-by: Adrien Grassein
Reviewed-by: Rob Herring
---
.../display/bridge/lontium,lt8912.yaml| 102 ++
MAINTAINERS | 5 +
2 files changed, 107 insertions(+)
create mode 100644
Documentatio
Hi,
this patch set adds the support of the Lontium lt8912 MIPI to HDMI
bridge in the kernel.
It's only support the video part, not the audio part yet
since I don't have the datasheet of this component.
I get the current i2c configuration from Digi and
Boundary drivers.
Developed using the DB_DSIHD
> On Feb 23, 2021, at 5:56 AM, Baoquan He wrote:
>
> On 02/23/21 at 08:01pm, Kairui Song wrote:
>> On Thu, Feb 18, 2021 at 10:03 AM Baoquan He wrote:
>>>
>>> On 02/11/21 at 10:08am, Saeed Mirzamohammadi wrote:
> ...
diff --git a/arch/Kconfig b/arch/Kconfig
index af14a567b493..f87c8
Hello,
syzbot found the following issue on:
HEAD commit:3b9cdafb Merge tag 'pinctrl-v5.12-1' of git://git.kernel.o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=153024bcd0
kernel config: https://syzkaller.appspot.com/x/.config?x=22008533485b2c35
das
On Tue, Feb 23, 2021 at 08:57:38AM -0800, dai@oracle.com wrote:
>
> On 2/23/21 8:47 AM, Amir Goldstein wrote:
> > On Tue, Feb 23, 2021 at 6:02 PM wrote:
> > >
> > > On 2/23/21 7:29 AM, dai@oracle.com wrote:
> > > > On 2/23/21 2:32 AM, Luis Henriques wrote:
> > > > > On Mon, Feb 22, 2021
On Mon, Feb 22, 2021 at 3:11 PM Kees Cook wrote:
>
> While x86 LTO enablement is done[1], it depends on some objtool
> clean-ups[2], though it appears those actually have been in linux-next
> (via tip/objtool/core), so it's possible that if that tree lands [..]
That tree is actually next on my li
On Mon, Feb 22, 2021 at 10:44 PM Jiapeng Chong
wrote:
>
> Fix the following coccicheck warnings:
>
> ./drivers/gpu/drm/amd/amdgpu/athub_v2_1.c:79:40-45: WARNING: conversion
> to bool not needed here.
>
> ./drivers/gpu/drm/amd/amdgpu/athub_v2_1.c:81:40-45: WARNING: conversion
> to bool not needed h
Hi Miquel,
On Tue, Feb 23, 2021 at 05:49:22PM +0100, Miquel Raynal wrote:
> Hi Manivannan,
>
> Manivannan Sadhasivam wrote on Mon,
> 22 Feb 2021 17:32:58 +0530:
>
> > On a typical end product, a vendor may choose to secure some regions in
> > the NAND memory which are supposed to stay intact be
On Mon, Feb 22, 2021 at 3:13 PM Souptick Joarder wrote:
>
> >> drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:9804:38:
> >> warning: variable 'i' is uninitialized when used here
> >> [-Wuninitialized]
>timing = &edid->detailed_timings[i];
>
Hello William,
Here is cooled down technical answer. Excuse me for over reacting.
On Tue, Feb 23, 2021 at 11:06:56AM +0100, Oleksij Rempel wrote:
> On Mon, Feb 22, 2021 at 10:43:00AM +0900, William Breathitt Gray wrote:
> > On Mon, Feb 15, 2021 at 10:17:37AM +0100, Oleksij Rempel wrote:
> > > > >
David Howells wrote:
> This set of patches from Eric Snowberg that add support for
> EFI_CERT_X509_GUID entries in the dbx and mokx UEFI tables (such entries
> cause matching certificates to be rejected). These are currently ignored
> and only the hash entries are made use of.
>
> These patches
Over-current reporting isn't supported on some platforms such as bcm63xx.
These devices will incorrectly report over-current if this flag isn't properly
activated.
Signed-off-by: Álvaro Fernández Rojas
---
v3: no changes.
drivers/usb/host/ehci-platform.c | 3 +++
1 file changed, 3 insertions(+
Over-current reporting isn't supported on some platforms such as bcm63xx.
These devices will incorrectly report over-current if this flag isn't properly
activated.
Signed-off-by: Álvaro Fernández Rojas
---
v3: no changes.
v2: change flag name and improve documentation as suggested by Alan Stern
From: Florian Fainelli
This patch adds an ignore_oc flag which can be set by EHCI controller
not supporting or wanting to disable overcurrent checking. The EHCI
platform data in include/linux/usb/ehci_pdriver.h is also augmented to
take advantage of this new flag.
Signed-off-by: Florian Fainelli
Over-current reporting isn't supported on some platforms such as bcm63xx.
These devices will incorrectly report over-current if this flag isn't properly
activated.
v3: add missing patch from Florian Fainelli.
v2: change flag name and improve documentation as suggested by Alan Stern.
Florian Faine
On Tuesday, February 23rd, 2021 at 6:42 PM, Alex Deucher
wrote:
> yeah, fdo ran out of disk space so I moved to gitlab:
>
> https://gitlab.freedesktop.org/agd5f/linux/-/commits/drm-next
Ah, thanks for the info, my bad!
This adds crashkernel=auto feature to configure reserved memory for
vmcore creation. CONFIG_CRASH_AUTO_STR is defined to be set for
different kernel distributions and different archs based on their
needs.
Signed-off-by: Saeed Mirzamohammadi
Signed-off-by: John Donnelly
Tested-by: John Donnelly
Port enable is not complete until ACK = 0. Change
__afu_port_enable() to guarantee that the enable process
is complete by polling for ACK == 0.
Signed-off-by: Russ Weight
Reviewed-by: Tom Rix
Reviewed-by: Matthew Gerlach
Acked-by: Wu Hao
---
v7:
- Added Acked-by tag from Wu Hao
v6:
- Fixed
yeah, fdo ran out of disk space so I moved to gitlab:
https://gitlab.freedesktop.org/agd5f/linux/-/commits/drm-next
Alex
On Mon, Feb 22, 2021 at 7:26 PM Bas Nieuwenhuizen
wrote:
>
> I think Alex moved to gitlab for his branches
>
> On Tue, Feb 23, 2021, 12:50 AM Simon Ser wrote:
>>
>> On Tuesda
On Tue, Feb 23, 2021 at 12:54:10PM +0100, Heiko Carstens wrote:
> On Mon, Feb 22, 2021 at 08:03:31AM -0800, Guenter Roeck wrote:
> > > Maybe, we can add something like CONFIG_SUPPRESS_NOISY_TESTS,
> > > which is set to y by all{yes,mod}config.
> > >
> > > This is self-documenting, so we do not nee
Hi "Álvaro,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on usb/usb-testing]
[also build test ERROR on v5.11 next-20210223]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' a
Hi Hector,
On Mon, 22 Feb 2021 19:35:03 +,
Hector Martin wrote:
>
> On 16/02/2021 03.09, Marc Zyngier wrote:
> > On Mon, 15 Feb 2021 12:17:03 +,
> > Hector Martin wrote:
> >> This patch introduces basic UP irqchip support, without SMP/IPI support.
> >
> > This last comment seems outdat
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 3b9cdafb5358eb9f3790de2f728f765fef100731
commit: 8bdfc5dae4e3ba4d99dfb430ef43249e5f1b7730 drm/bridge: anx7625: Add
anx7625 MIPI DSI/DPI to DP
date: 4 months ago
config: s390-randconfig-r022-20210223
On Tue, 23 Feb 2021 at 06:41, Li, Aubrey wrote:
>
> Hi Vincent,
>
> Sorry for the delay, I just returned from Chinese New Year holiday.
>
> On 2021/1/25 22:51, Vincent Guittot wrote:
> > On Mon, 25 Jan 2021 at 15:00, Li, Aubrey wrote:
> >>
> >> On 2021/1/25 18:56, Vincent Guittot wrote:
> >>> On
On Tue, Feb 23, 2021 at 7:31 PM wrote:
>
> On 2/23/21 8:57 AM, dai@oracle.com wrote:
>
>
> On 2/23/21 8:47 AM, Amir Goldstein wrote:
>
> On Tue, Feb 23, 2021 at 6:02 PM wrote:
>
>
> On 2/23/21 7:29 AM, dai@oracle.com wrote:
>
> On 2/23/21 2:32 AM, Luis Henriques wrote:
>
> On Mon, Feb 22,
On Tue, 23 Feb 2021 at 09:49, Sami Tolvanen wrote:
>
> On Tue, Feb 23, 2021 at 8:41 AM Mathieu Poirier
> wrote:
> >
> > On Mon, 22 Feb 2021 at 15:48, Sami Tolvanen wrote:
> > >
> > > Hi,
> > >
> > > On Sun, Feb 21, 2021 at 11:18 PM Jindong Yue wrote:
> > > >
> > > > There are four different cal
On Wed, Feb 10, 2021 at 8:14 AM Daniel Vetter wrote:
>
> On Wed, Feb 10, 2021 at 08:45:56AM +0100, Christian König wrote:
> > Reviewed-by: Christian König for the series.
>
> Smash it into -misc?
@Christian Koenig did these ever land? I don't see them in drm-misc.
Alex
> -Daniel
>
> >
> > Am
On Tue, Feb 23, 2021 at 11:29:00AM +0100, Michael Tretter wrote:
> On Tue, 23 Feb 2021 10:02:01 +0100, Geert Uytterhoeven wrote:
> > NORMAL (0x0) and IDLE (0x4) are really two different states. Hence you
> > cannot check for both using a bitmask, as that checks for IDLE only,
> > breaking operatio
On Sun, 14 Feb 2021 12:13:07 +0900, Tetsuo Handa wrote:
> syzbot is hitting WARN_ON(pstore_sb != sb) at pstore_kill_sb() [1], for the
> assumption that pstore_sb != NULL is wrong because pstore_fill_super() will
> not assign pstore_sb = sb when new_inode() for d_make_root() returned NULL
> (due to
On Mon, 22 Feb 2021 at 17:26, Andrey Konovalov
wrote:
>
> Hi Robert,
>
> Thank you for your patch!
>
> On 17.02.2021 14:21, Robert Foss wrote:
> > The CSI-2 spec defines the following types:
> > - Data Type - Often abbreviated DT
> > - Decode Format - Often abbreviated as DF
> > - Encode For
It's better to describe the I²C controller and associated IRQ domain with
fwnode, so they will find their place in the hierarchy in sysfs and also
make easier to debug.
Signed-off-by: Andy Shevchenko
---
Hans, unfortunately I have no device at hand with INT34D3. This is only compile
tested in th
Hello Scott,
El 23/02/2021 a las 18:17, Scott Branden escribió:
On 2021-02-23 8:36 a.m., Florian Fainelli wrote:
On 2/23/2021 8:01 AM, Álvaro Fernández Rojas wrote:
Some devices may need to perform a reset before using the RNG, such as the
BCM6368.
Signed-off-by: Álvaro Fernández Rojas
S
ping
I noticed this was never picked up, can it be landed or are there any
concerns with this patch?
On Tue, Sep 15, 2020 at 06:50:32PM -0500, Bjorn Andersson wrote:
> On Tue 15 Sep 14:31 CDT 2020, Matthias Kaehlcke wrote:
>
> > The dwc3-qcom currently enables wakeup interrupts unconditionally
>
On 23/02/21 18:15, Sean Christopherson wrote:
If event
creation fails in that flow, I would think KVM would do its best to create an
event in future runs without waiting for additional actions from the guest.
Also, this bug suggests there's a big gaping hole in the test coverage. AFAICT,
event
On 21-02-22 17:03:13, Martin Kepplinger wrote:
> On 19.02.21 16:59, Abel Vesa wrote:
> > This has been on my queue for quite some time now. It is more of a
> > proof-of-concept.
> >
> > This rework is done with the compatibility of future i.MX platforms in
> > mind. For example, the i.MX8MP platfo
On 2021-02-23 8:36 a.m., Florian Fainelli wrote:
>
>
> On 2/23/2021 8:01 AM, Álvaro Fernández Rojas wrote:
>> Some devices may need to perform a reset before using the RNG, such as the
>> BCM6368.
>>
>> Signed-off-by: Álvaro Fernández Rojas
>
> Since the reset is unique to the 6368, you may wan
On Tue, 23 Feb 2021 at 16:16, Dmitry Vyukov wrote:
>
> On Tue, Feb 23, 2021 at 4:10 PM 'Marco Elver' via kasan-dev
> wrote:
> > > > Encode information from breakpoint attributes into siginfo_t, which
> > > > helps disambiguate which breakpoint fired.
> > > >
> > > > Note, providing the event fd m
On Tue, Feb 23, 2021, Like Xu wrote:
> If lbr_desc->event is successfully created, the intel_pmu_create_
> guest_lbr_event() will return 0, otherwise it will return -ENOENT,
> and then jump to LBR msrs dummy handling.
>
> Fixes: 1b5ac3226a1a ("KVM: vmx/pmu: Pass-through LBR msrs when the guest LBR
On Tue, Feb 23, 2021 at 7:03 AM David Sterba wrote:
> Ira Weiny (8):
> iov_iter: Remove memzero_page() in favor of zero_user()
Ugh. I absolutely _detest_ this patch.
"zero_user()" is a completely horrendous function, and not at all the
same as memzero_page().
Just look at it.
Yes, it's m
On Tue, Feb 23, 2021 at 11:03 AM wrote:
>
>
> On 2/23/21 7:29 AM, dai@oracle.com wrote:
> >
> > On 2/23/21 2:32 AM, Luis Henriques wrote:
> >> On Mon, Feb 22, 2021 at 08:25:27AM -0800, dai@oracle.com wrote:
> >>> On 2/22/21 2:24 AM, Luis Henriques wrote:
> A regression has been report
Hello,
My name is Tayeb Souami, I am an accountant and native of Little Ferry, New
Jersey, United States. I am a winner of $ 315.3 million jackpot winner in the
USA Powerball™ lottery. Your email was randomly selected from the world email
database among many other emails and you have been se
On 23/02/21 17:38, Sean Christopherson wrote:
On Tue, Feb 23, 2021, Like Xu wrote:
When the processor that support model-specific LBR generates a debug
breakpoint event, it automatically clears the LBR flag. This action
does not clear previously stored LBR stack MSRs. (Intel SDM 17.4.2)
Signed-
On 23/02/21 02:39, Like Xu wrote:
If lbr_desc->event is successfully created, the intel_pmu_create_
guest_lbr_event() will return 0, otherwise it will return -ENOENT,
and then jump to LBR msrs dummy handling.
Fixes: 1b5ac3226a1a ("KVM: vmx/pmu: Pass-through LBR msrs when the guest LBR event
is
On Wed 03-02-21 19:43:51, Sabyrzhan Tasbolatov wrote:
> syzbot found UBSAN: shift-out-of-bounds in ext4_mb_init [1], when
> 1 << sbi->s_es->s_log_groups_per_flex is bigger than UINT_MAX,
> where sbi->s_mb_prefetch is unsigned integer type.
>
> 32 is the maximum allowed power of s_log_groups_per_fl
On Tue, 23 Feb 2021 09:54:22 -0700
Jens Axboe wrote:
> On 2/22/21 4:02 PM, Steven Rostedt wrote:
> >
> > Jens,
> >
> > I guess this goes through your tree.
> >
> > I'm pinging you in case you did what I did, and confused this patch as one
> > of Greg's stable patches (which I almost archived a
BCM6368 devices need to reset the in order to generate true random numbers.
This is what BCM6368 produces without a reset:
root@OpenWrt:/# cat /dev/hwrng | rngtest -c 1000
rngtest 6.10
Copyright (c) 2004 by Henrique de Moraes Holschuh
This is free software; see the source for copying conditions. T
Some devices may need to perform a reset before using the RNG, such as the
BCM6368.
Signed-off-by: Álvaro Fernández Rojas
---
v3: make resets required if brcm,bcm6368-rng.
v2: document reset support.
.../devicetree/bindings/rng/brcm,bcm2835.yaml | 17 +
1 file changed, 17 in
On 2/23/2021 1:05 AM, Álvaro Fernández Rojas wrote:
>
>
>> El 23 feb 2021, a las 9:58, Pavel Machek escribió:
>>
>> Hi!
>>
> This is proven to work in BMIPS BE/LE and ARM BE/LE, as used in
> bcm2835-rng
> and bcmgenet drivers.
> Both should also be inline functions.
Some devices may need to perform a reset before using the RNG, such as the
BCM6368.
v3: make resets required if brcm,bcm6368-rng.
v2: document reset support.
Álvaro Fernández Rojas (2):
dt-bindings: rng: bcm2835: document reset support
hwrng: bcm2835: add reset support
.../devicetree/bindin
On 2/23/21 8:47 AM, Amir Goldstein wrote:
On Tue, Feb 23, 2021 at 6:02 PM wrote:
On 2/23/21 7:29 AM, dai@oracle.com wrote:
On 2/23/21 2:32 AM, Luis Henriques wrote:
On Mon, Feb 22, 2021 at 08:25:27AM -0800, dai@oracle.com wrote:
On 2/22/21 2:24 AM, Luis Henriques wrote:
A regress
On Tue, Feb 23, 2021 at 05:16:44PM +0100, Álvaro Fernández Rojas wrote:
> Over-current reporting isn't supported on some platforms such as bcm63xx.
> These devices will incorrectly report over-current if this flag isn't properly
> activated.
>
> Signed-off-by: Álvaro Fernández Rojas
> ---
> v2:
On 2/22/21 4:02 PM, Steven Rostedt wrote:
>
> Jens,
>
> I guess this goes through your tree.
>
> I'm pinging you in case you did what I did, and confused this patch as one
> of Greg's stable patches (which I almost archived as such)!
>
> No, this is an actual update from Greg, not a patch that
On 2/16/21 8:52 AM, Greg Kroah-Hartman wrote:
> These debugfs dentries do not need to be saved for anything as the whole
> directory and everything in it is properly cleaned up when the parent
> directory is removed. So remove them from struct blk_trace and don't
> save them when created as it's n
Hi Manivannan,
Manivannan Sadhasivam wrote on Mon,
22 Feb 2021 17:32:58 +0530:
> On a typical end product, a vendor may choose to secure some regions in
> the NAND memory which are supposed to stay intact between FW upgrades.
> The access to those regions will be blocked by a secure element like
On Tue, Feb 23, 2021 at 8:41 AM Mathieu Poirier
wrote:
>
> On Mon, 22 Feb 2021 at 15:48, Sami Tolvanen wrote:
> >
> > Hi,
> >
> > On Sun, Feb 21, 2021 at 11:18 PM Jindong Yue wrote:
> > >
> > > There are four different callback functions that are used for the
> > > rproc_handle_resource_t callba
On Tue, Feb 23, 2021 at 6:02 PM wrote:
>
>
> On 2/23/21 7:29 AM, dai@oracle.com wrote:
> >
> > On 2/23/21 2:32 AM, Luis Henriques wrote:
> >> On Mon, Feb 22, 2021 at 08:25:27AM -0800, dai@oracle.com wrote:
> >>> On 2/22/21 2:24 AM, Luis Henriques wrote:
> A regression has been reporte
501 - 600 of 1024 matches
Mail list logo
