Re: CHIPPro NAND issue with 4.12 rc1

Le Sat, 20 May 2017 15:24:06 -0600, Angus Ainslie a écrit : > On 2017-05-20 09:14, Boris Brezillon wrote: > > Le Sat, 20 May 2017 08:49:04 -0600, > > Angus Ainslie a écrit : > > > >> Hi All, > >> > >> I'm trying to boot a CHIPPro with the stock 4.12 rc1

Re: CHIPPro NAND issue with 4.12 rc1

Le Sat, 20 May 2017 15:24:06 -0600, Angus Ainslie a écrit : > On 2017-05-20 09:14, Boris Brezillon wrote: > > Le Sat, 20 May 2017 08:49:04 -0600, > > Angus Ainslie a écrit : > > > >> Hi All, > >> > >> I'm trying to boot a CHIPPro with the stock 4.12 rc1 kernel. If I make > >> no

Re: [PATCH 18/24] thunderbolt: Store Thunderbolt generation in the switch structure

On Sun, May 21, 2017 at 05:29:47AM +, Levy, Amir (Jer) wrote: > On Sun, May 21 2017, 07:47 AM, Lukas Wunner wrote: > > On Thu, May 18, 2017 at 05:39:08PM +0300, Mika Westerberg wrote: > > > + > > > + default: > > > + sw->generation = 1; > > > + break; > > > > If someone adds

Re: [PATCH 18/24] thunderbolt: Store Thunderbolt generation in the switch structure

On Sun, May 21, 2017 at 05:29:47AM +, Levy, Amir (Jer) wrote: > On Sun, May 21 2017, 07:47 AM, Lukas Wunner wrote: > > On Thu, May 18, 2017 at 05:39:08PM +0300, Mika Westerberg wrote: > > > + > > > + default: > > > + sw->generation = 1; > > > + break; > > > > If someone adds

Re: [PATCH 0/8] CaitSith LSM module

On 05/20/2017 09:59 PM, Tetsuo Handa wrote: > John Johansen wrote: >> On 11/22/2016 10:31 PM, Tetsuo Handa wrote: >>> Tetsuo Handa wrote: John Johansen wrote: >> In order to minimize the burden of reviewing, this patchset implements >> only functionality of checking program execution

Re: [PATCH 0/8] CaitSith LSM module

On 05/20/2017 09:59 PM, Tetsuo Handa wrote: > John Johansen wrote: >> On 11/22/2016 10:31 PM, Tetsuo Handa wrote: >>> Tetsuo Handa wrote: John Johansen wrote: >> In order to minimize the burden of reviewing, this patchset implements >> only functionality of checking program execution

Re: [PATCH 10/24] thunderbolt: Read vendor and device name from DROM

On Fri, May 19, 2017 at 01:28:36PM +0300, Mika Westerberg wrote: > On Fri, May 19, 2017 at 12:07:10PM +0200, Lukas Wunner wrote: > > Apple uses 0x30 to store a > > serial number. Is this attribute number assigned by Intel to Apple > > or is it reserved for vendor use or did they arbitrarily

Re: [PATCH 10/24] thunderbolt: Read vendor and device name from DROM

On Fri, May 19, 2017 at 01:28:36PM +0300, Mika Westerberg wrote: > On Fri, May 19, 2017 at 12:07:10PM +0200, Lukas Wunner wrote: > > Apple uses 0x30 to store a > > serial number. Is this attribute number assigned by Intel to Apple > > or is it reserved for vendor use or did they arbitrarily

RE: [PATCH 18/24] thunderbolt: Store Thunderbolt generation in the switch structure

On Sun, May 21 2017, 07:47 AM, Lukas Wunner wrote: > On Thu, May 18, 2017 at 05:39:08PM +0300, Mika Westerberg wrote: > > + > > + default: > > + sw->generation = 1; > > + break; > > If someone adds an entry for, say, a new TB3 controller to nhi_ids[] but > forgets > to

RE: [PATCH 18/24] thunderbolt: Store Thunderbolt generation in the switch structure

On Sun, May 21 2017, 07:47 AM, Lukas Wunner wrote: > On Thu, May 18, 2017 at 05:39:08PM +0300, Mika Westerberg wrote: > > + > > + default: > > + sw->generation = 1; > > + break; > > If someone adds an entry for, say, a new TB3 controller to nhi_ids[] but > forgets > to

Re: linux-next 20170519 - semaphores broken

On Sat, May 20, 2017 at 1:18 PM, wrote: > Seeing problems with programs that use semaphores. The one > that I'm getting bit by is jackd. strace says: > > getuid()= 967 > semget(0x282929, 0, 000)= 229376 > semop(229376,

Re: linux-next 20170519 - semaphores broken

On Sat, May 20, 2017 at 1:18 PM, wrote: > Seeing problems with programs that use semaphores. The one > that I'm getting bit by is jackd. strace says: > > getuid()= 967 > semget(0x282929, 0, 000)= 229376 > semop(229376, [{0, -1, SEM_UNDO}], 1) =

Re: [PATCH 0/8] CaitSith LSM module

John Johansen wrote: > On 11/22/2016 10:31 PM, Tetsuo Handa wrote: > > Tetsuo Handa wrote: > >> John Johansen wrote: > In order to minimize the burden of reviewing, this patchset implements > only functionality of checking program execution requests (i.e. execve() > system call)

Re: [PATCH 0/8] CaitSith LSM module

John Johansen wrote: > On 11/22/2016 10:31 PM, Tetsuo Handa wrote: > > Tetsuo Handa wrote: > >> John Johansen wrote: > In order to minimize the burden of reviewing, this patchset implements > only functionality of checking program execution requests (i.e. execve() > system call)

Re: [PATCH 18/24] thunderbolt: Store Thunderbolt generation in the switch structure

On Thu, May 18, 2017 at 05:39:08PM +0300, Mika Westerberg wrote: > In some cases it is useful to know what is the Thunderbolt generation > the switch supports. This introduces a new field to struct switch that > stores the generation of the switch based on the device ID. > > Signed-off-by: Mika

Re: [PATCH 18/24] thunderbolt: Store Thunderbolt generation in the switch structure

On Thu, May 18, 2017 at 05:39:08PM +0300, Mika Westerberg wrote: > In some cases it is useful to know what is the Thunderbolt generation > the switch supports. This introduces a new field to struct switch that > stores the generation of the switch based on the device ID. > > Signed-off-by: Mika

[PATCH] drm/i915: mark wait_for_engine() __maybe_unused

This solves a warning when compiling the driver with Clang, -Werror enabled, and CONFIG_DRM_I915_DEBUG_GEM unset, since Clang warns that: drivers/gpu/drm/i915/i915_gem.c:3274:12: error: function 'wait_for_engine' is not needed and will not be emitted

[PATCH] drm/i915: mark wait_for_engine() __maybe_unused

This solves a warning when compiling the driver with Clang, -Werror enabled, and CONFIG_DRM_I915_DEBUG_GEM unset, since Clang warns that: drivers/gpu/drm/i915/i915_gem.c:3274:12: error: function 'wait_for_engine' is not needed and will not be emitted

will

-- My previous messages were returned as undelivered. I am making a final attempt to reach you regarding the estate of Late George Brumley, you have made one of the beneficiaries. Please get back to me at your earliest convenience. Regards, Jessica Simpson Board Of Trustees

will

-- My previous messages were returned as undelivered. I am making a final attempt to reach you regarding the estate of Late George Brumley, you have made one of the beneficiaries. Please get back to me at your earliest convenience. Regards, Jessica Simpson Board Of Trustees

[PATCH v2 2/2] dt-bindings: phy: Add documentation for Mediatek PCIe PHY

Add documentation for PCIe PHY available in MT7623 series SoCs. Signed-off-by: Ryder Lee Acked-by: Rob Herring --- .../devicetree/bindings/phy/phy-mt7623-pcie.txt| 63 ++ 1 file changed, 63 insertions(+) create mode 100644

Re: [PATCH 1/2] libsas: Don't process sas events in static works

On Fri, May 19, 2017 at 11:39 PM, Yijing Wang wrote: > Now libsas hotplug work is static, LLDD driver queue > the hotplug work into shost->work_q. If LLDD driver > burst post lots hotplug events to libsas, the hotplug > events may pending in the workqueue like > >

[PATCH v2 2/2] dt-bindings: phy: Add documentation for Mediatek PCIe PHY

Add documentation for PCIe PHY available in MT7623 series SoCs. Signed-off-by: Ryder Lee Acked-by: Rob Herring --- .../devicetree/bindings/phy/phy-mt7623-pcie.txt| 63 ++ 1 file changed, 63 insertions(+) create mode 100644

Re: [PATCH 1/2] libsas: Don't process sas events in static works

On Fri, May 19, 2017 at 11:39 PM, Yijing Wang wrote: > Now libsas hotplug work is static, LLDD driver queue > the hotplug work into shost->work_q. If LLDD driver > burst post lots hotplug events to libsas, the hotplug > events may pending in the workqueue like > > shost->work_q > new

[PATCH v2 1/2] phy: add PCIe PHY driver for mt7623 SoCs families

support PCIe PHY of MT7623 SoCs families Signed-off-by: Ryder Lee --- drivers/phy/Kconfig | 8 ++ drivers/phy/Makefile | 1 + drivers/phy/phy-mt7623-pcie.c | 290 ++ 3 files changed, 299 insertions(+) create

[PATCH v2 1/2] phy: add PCIe PHY driver for mt7623 SoCs families

support PCIe PHY of MT7623 SoCs families Signed-off-by: Ryder Lee --- drivers/phy/Kconfig | 8 ++ drivers/phy/Makefile | 1 + drivers/phy/phy-mt7623-pcie.c | 290 ++ 3 files changed, 299 insertions(+) create mode 100644

[PATCH v2 0/2] Add PCIe phy driver for some Mediatek SoCs

Hi, This patch series add PCIe phy driver and related dt-binding file for Mediatek mt7623 SoCs families. Changes since v2: - rebase to Linux 4.12-rc1 Changes since v1: - revise binding document: drop 'status' properties. add a description to 'phy-switch' property and add vendor prefix.

[PATCH v2 0/2] Add PCIe phy driver for some Mediatek SoCs

Hi, This patch series add PCIe phy driver and related dt-binding file for Mediatek mt7623 SoCs families. Changes since v2: - rebase to Linux 4.12-rc1 Changes since v1: - revise binding document: drop 'status' properties. add a description to 'phy-switch' property and add vendor prefix.

[PATCH v5 2/2] dt-bindings: pcie: Add documentation for Mediatek PCIe

Add documentation for PCIe host driver available in MT7623 series SoCs. Signed-off-by: Ryder Lee Acked-by: Rob Herring --- .../bindings/pci/mediatek,mt7623-pcie.txt | 130 + 1 file changed, 130 insertions(+) create mode

[PATCH v5 2/2] dt-bindings: pcie: Add documentation for Mediatek PCIe

Add documentation for PCIe host driver available in MT7623 series SoCs. Signed-off-by: Ryder Lee Acked-by: Rob Herring --- .../bindings/pci/mediatek,mt7623-pcie.txt | 130 + 1 file changed, 130 insertions(+) create mode 100644

[PATCH v5 0/2] Add PCIe host driver support for Mediatek SoCs

Hi, This patch series add Mediatek Gen2 PCIe host controller driver and dt-binding document. It can be found on MT7623 series SoCs. This driver was validated using Broadcom Tigon3 and Intel(R) 82575/82576 gigabit ethernet card. Changes since v5: - rebase to Linux 4.12-rc1. - remove redundant

[PATCH v5 1/2] PCI: mediatek: Add Mediatek PCIe host controller support

Add support for the Mediatek PCIe Gen2 controller which can be found on MT7623 series SoCs. Signed-off-by: Ryder Lee --- drivers/pci/host/Kconfig | 11 + drivers/pci/host/Makefile| 1 + drivers/pci/host/pcie-mediatek.c | 553

[PATCH v5 0/2] Add PCIe host driver support for Mediatek SoCs

Hi, This patch series add Mediatek Gen2 PCIe host controller driver and dt-binding document. It can be found on MT7623 series SoCs. This driver was validated using Broadcom Tigon3 and Intel(R) 82575/82576 gigabit ethernet card. Changes since v5: - rebase to Linux 4.12-rc1. - remove redundant

[PATCH v5 1/2] PCI: mediatek: Add Mediatek PCIe host controller support

Add support for the Mediatek PCIe Gen2 controller which can be found on MT7623 series SoCs. Signed-off-by: Ryder Lee --- drivers/pci/host/Kconfig | 11 + drivers/pci/host/Makefile| 1 + drivers/pci/host/pcie-mediatek.c | 553 +++ 3 files

[PATCH] initramfs: Fix disabling of initramfs (and its compression)

Commit db2aa7fd15e8 ("initramfs: allow again choice of the embedded initram compression algorithm") introduced the possibility to select the initramfs compression algorithm from Kconfig and while this is a nice feature it broke the use case described below. Here is what my build system does: -

[PATCH] initramfs: Fix disabling of initramfs (and its compression)

Commit db2aa7fd15e8 ("initramfs: allow again choice of the embedded initram compression algorithm") introduced the possibility to select the initramfs compression algorithm from Kconfig and while this is a nice feature it broke the use case described below. Here is what my build system does: -

[PATCH] KVM: X86: Fix preempt the preemption timer cancel

From: Wanpeng Li WARNING: CPU: 3 PID: 1952 at arch/x86/kvm/lapic.c:1529 kvm_lapic_expired_hv_timer+0xb5/0xd0 [kvm] CPU: 3 PID: 1952 Comm: qemu-system-x86 Not tainted 4.12.0-rc1+ #24 RIP: 0010:kvm_lapic_expired_hv_timer+0xb5/0xd0 [kvm] Call Trace:

[PATCH] KVM: X86: Fix preempt the preemption timer cancel

From: Wanpeng Li WARNING: CPU: 3 PID: 1952 at arch/x86/kvm/lapic.c:1529 kvm_lapic_expired_hv_timer+0xb5/0xd0 [kvm] CPU: 3 PID: 1952 Comm: qemu-system-x86 Not tainted 4.12.0-rc1+ #24 RIP: 0010:kvm_lapic_expired_hv_timer+0xb5/0xd0 [kvm] Call Trace: handle_preemption_timer+0xe/0x20

Re: [RFC] KVM: SVM: do not drop VMCB CPL to 0 if SS is not present

On 05/19/2017 09:14 AM, Roman Penyaev wrote: Hi folks, After experiencing guest double faults (sometimes triple faults) on 3.16 guest kernels with the following common pattern: [459395.776124] PANIC: double fault, error_code: 0x0 [459395.776606] CPU: 0 PID: 36565 Comm: fio Not tainted

Re: [RFC] KVM: SVM: do not drop VMCB CPL to 0 if SS is not present

On 05/19/2017 09:14 AM, Roman Penyaev wrote: Hi folks, After experiencing guest double faults (sometimes triple faults) on 3.16 guest kernels with the following common pattern: [459395.776124] PANIC: double fault, error_code: 0x0 [459395.776606] CPU: 0 PID: 36565 Comm: fio Not tainted

Re: [PATCH] usb: gadget: f_fs: use memdup_user

On Sat, May 13, 2017 at 11:05:30AM +0300, Dan Carpenter wrote: > > + data = memdup_user(buf, len); > > + if (unlikely(IS_ERR(data))) > > Don't use likely/unlikely() here. It's not a fast path. More to the point, #define IS_ERR_VALUE(x) unlikely((unsigned long)(void *)(x) >= (unsigned

Re: [PATCH] usb: gadget: f_fs: use memdup_user

On Sat, May 13, 2017 at 11:05:30AM +0300, Dan Carpenter wrote: > > + data = memdup_user(buf, len); > > + if (unlikely(IS_ERR(data))) > > Don't use likely/unlikely() here. It's not a fast path. More to the point, #define IS_ERR_VALUE(x) unlikely((unsigned long)(void *)(x) >= (unsigned

Re: [PATCH v3 08/10] x86/hyper-v: use hypercall for remote TLB flush

On 05/19/2017 07:09 AM, Vitaly Kuznetsov wrote: Hyper-V host can suggest us to use hypercall for doing remote TLB flush, this is supposed to work faster than IPIs. Implementation details: to do HvFlushVirtualAddress{Space,List} hypercalls we need to put the input somewhere in memory and we

Re: [PATCH v3 08/10] x86/hyper-v: use hypercall for remote TLB flush

On 05/19/2017 07:09 AM, Vitaly Kuznetsov wrote: Hyper-V host can suggest us to use hypercall for doing remote TLB flush, this is supposed to work faster than IPIs. Implementation details: to do HvFlushVirtualAddress{Space,List} hypercalls we need to put the input somewhere in memory and we

[GIT PULL] tracing: Fixes for 4.12-rc1

Linus, This fixes a bug caused by not cleaning up the new instance unique triggers when deleting an instance. It also creates a selftest that triggers that bug. Fix the delayed optimization happening after kprobes boot up self tests being removed by freeing of init memory. Comment kprobes on

[GIT PULL] tracing: Fixes for 4.12-rc1

Linus, This fixes a bug caused by not cleaning up the new instance unique triggers when deleting an instance. It also creates a selftest that triggers that bug. Fix the delayed optimization happening after kprobes boot up self tests being removed by freeing of init memory. Comment kprobes on

Re: [PATCH v3 04/10] x86/hyper-v: fast hypercall implementation

On 05/19/2017 07:09 AM, Vitaly Kuznetsov wrote: Hyper-V supports 'fast' hypercalls when all parameters are passed through registers. Implement an inline version of a simpliest of these calls: hypercall with one 8-byte input and no output. Proper hypercall input interface (struct

Re: [PATCH v3 04/10] x86/hyper-v: fast hypercall implementation

On 05/19/2017 07:09 AM, Vitaly Kuznetsov wrote: Hyper-V supports 'fast' hypercalls when all parameters are passed through registers. Implement an inline version of a simpliest of these calls: hypercall with one 8-byte input and no output. Proper hypercall input interface (struct

Re: [PATCH] ext4: keep existing extra fields when inode expands

On Fri, May 19, 2017 at 10:13:39AM +0300, Konstantin Khlebnikov wrote: > ext4_expand_extra_isize() should clear only space between old and new size. > > Signed-off-by: Konstantin Khlebnikov Thanks, applied. - Ted

Re: [PATCH] ext4: keep existing extra fields when inode expands

On Fri, May 19, 2017 at 10:13:39AM +0300, Konstantin Khlebnikov wrote: > ext4_expand_extra_isize() should clear only space between old and new size. > > Signed-off-by: Konstantin Khlebnikov Thanks, applied. - Ted

Re: [v3, 2/2] initramfs: Allow again choice of the embedded initram compression algorithm

On 05/20/2017 03:30 PM, Florian Fainelli wrote: > Hi Francisco, Nicholas, > > Nicholas already fixed part of this commit, but there is more breakage, > see below: > > On 09/27/2016 01:32 PM, klondike wrote: >> Choosing the appropriate compression option when using an embeded initramfs >> can

Re: [v3, 2/2] initramfs: Allow again choice of the embedded initram compression algorithm

On 05/20/2017 03:30 PM, Florian Fainelli wrote: > Hi Francisco, Nicholas, > > Nicholas already fixed part of this commit, but there is more breakage, > see below: > > On 09/27/2016 01:32 PM, klondike wrote: >> Choosing the appropriate compression option when using an embeded initramfs >> can

Re: [PATCH] ext4: handle the rest of ext4_mb_load_buddy() ENOMEM errors

On Fri, May 19, 2017 at 10:09:54AM +0300, Konstantin Khlebnikov wrote: > I've got another report about breaking ext4 by ENOMEM error returned from > ext4_mb_load_buddy() caused by memory shortage in memory cgroup. > This time inside ext4_discard_preallocations(). > > This patch replaces

Re: [PATCH] ext4: handle the rest of ext4_mb_load_buddy() ENOMEM errors

On Fri, May 19, 2017 at 10:09:54AM +0300, Konstantin Khlebnikov wrote: > I've got another report about breaking ext4 by ENOMEM error returned from > ext4_mb_load_buddy() caused by memory shortage in memory cgroup. > This time inside ext4_discard_preallocations(). > > This patch replaces

Re: [PATCH 0/3] arm64: dts: introduce QorIQ DPAA 1.x FMan device tree nodes

On Tue, May 16, 2017 at 03:07:20PM +0300, Madalin Bucur wrote: > This patch set introduces the QorIQ Data Path Acceleration Arhitecture > (DPAA) Frame Manager device tree nodes for the ARM based DPAA 1.x platforms. > > Madalin Bucur (3): > arm64: dts: add DPAA FMan nodes > arm64: dts: add

Re: [PATCH 0/3] arm64: dts: introduce QorIQ DPAA 1.x FMan device tree nodes

On Tue, May 16, 2017 at 03:07:20PM +0300, Madalin Bucur wrote: > This patch set introduces the QorIQ Data Path Acceleration Arhitecture > (DPAA) Frame Manager device tree nodes for the ARM based DPAA 1.x platforms. > > Madalin Bucur (3): > arm64: dts: add DPAA FMan nodes > arm64: dts: add

Re: [v4 1/1] mm: Adaptive hash table scaling

Pavel Tatashin writes: > Allow hash tables to scale with memory but at slower pace, when HASH_ADAPT > is provided every time memory quadruples the sizes of hash tables will only > double instead of quadrupling as well. This algorithm starts working only > when memory

Re: [v4 1/1] mm: Adaptive hash table scaling

Pavel Tatashin writes: > Allow hash tables to scale with memory but at slower pace, when HASH_ADAPT > is provided every time memory quadruples the sizes of hash tables will only > double instead of quadrupling as well. This algorithm starts working only > when memory size reaches a certain

Re: [PATCH] ARM: dts: imx7: use 3 PWM cells

On Tue, May 16, 2017 at 12:40:13AM -0700, Stefan Agner wrote: > The PWM driver has now capability to specify the PWM polarity > which is e.g. for backlight control. Allow to make use of PWM > polarity by specifying pwm-cells to be 3 in the base dt. > > Signed-off-by: Stefan Agner

Re: [PATCH] ARM: dts: imx7: use 3 PWM cells

On Tue, May 16, 2017 at 12:40:13AM -0700, Stefan Agner wrote: > The PWM driver has now capability to specify the PWM polarity > which is e.g. for backlight control. Allow to make use of PWM > polarity by specifying pwm-cells to be 3 in the base dt. > > Signed-off-by: Stefan Agner Applied,

Re: [PATCH v3 0/7] i.MX7 PCIe related device tree changes

On Mon, May 15, 2017 at 07:52:58AM -0700, Andrey Smirnov wrote: > Andrey Smirnov (7): > ARM: dts: imx: Reintroduce 'anatop-enable-bit' where appropriate > ARM: imx: Select GPCv2 for i.MX7 > ARM: dts: imx7s: Add node for GPC > ARM: dts: imx7s: Mark 'gpr' compatible with i.MX6 variant >

Re: [PATCH v3 0/7] i.MX7 PCIe related device tree changes

On Mon, May 15, 2017 at 07:52:58AM -0700, Andrey Smirnov wrote: > Andrey Smirnov (7): > ARM: dts: imx: Reintroduce 'anatop-enable-bit' where appropriate > ARM: imx: Select GPCv2 for i.MX7 > ARM: dts: imx7s: Add node for GPC > ARM: dts: imx7s: Mark 'gpr' compatible with i.MX6 variant >

[PATCH v9] mm: Add memory allocation watchdog kernel thread.

This patch adds a watchdog which periodically reports number of memory allocating tasks, dying tasks and OOM victim tasks when some task is spending too long time inside __alloc_pages_slowpath(). This patch also serves as a hook for obtaining additional information using SystemTap (e.g. examine

[PATCH v9] mm: Add memory allocation watchdog kernel thread.

This patch adds a watchdog which periodically reports number of memory allocating tasks, dying tasks and OOM victim tasks when some task is spending too long time inside __alloc_pages_slowpath(). This patch also serves as a hook for obtaining additional information using SystemTap (e.g. examine

[PATCH -next] drm/vgem: Fix return value check in vgem_init()

From: Wei Yongjun In case of error, the function platform_device_register_simple() returns ERR_PTR() and never returns NULL. The NULL test in the return value check should be replaced with IS_ERR(). Fixes: 315f0242aa2b ("drm/vgem: Convert to a struct drm_device

[PATCH -next] drm/vgem: Fix return value check in vgem_init()

From: Wei Yongjun In case of error, the function platform_device_register_simple() returns ERR_PTR() and never returns NULL. The NULL test in the return value check should be replaced with IS_ERR(). Fixes: 315f0242aa2b ("drm/vgem: Convert to a struct drm_device subclass") Signed-off-by: Wei

[PATCH -next] drm/pl111: Fix return value check in pl111_amba_probe()

From: Wei Yongjun In case of error, the function devm_ioremap_resource() returns ERR_PTR() and never returns NULL. The NULL test in the return value check should be replaced with IS_ERR(). Fixes: bed41005e617 ("drm/pl111: Initial drm/kms driver for pl111") Signed-off-by:

[PATCH -next] drm/pl111: Fix return value check in pl111_amba_probe()

From: Wei Yongjun In case of error, the function devm_ioremap_resource() returns ERR_PTR() and never returns NULL. The NULL test in the return value check should be replaced with IS_ERR(). Fixes: bed41005e617 ("drm/pl111: Initial drm/kms driver for pl111") Signed-off-by: Wei Yongjun ---

[PATCH] goldfish_pipe: use GFP_ATOMIC under spin lock

From: Wei Yongjun The function get_free_pipe_id_locked() is called from goldfish_pipe_open() with a lock is held, so we should use GFP_ATOMIC instead of GFP_KERNEL. Signed-off-by: Wei Yongjun --- drivers/platform/goldfish/goldfish_pipe.c | 2 +-

[PATCH] goldfish_pipe: use GFP_ATOMIC under spin lock

From: Wei Yongjun The function get_free_pipe_id_locked() is called from goldfish_pipe_open() with a lock is held, so we should use GFP_ATOMIC instead of GFP_KERNEL. Signed-off-by: Wei Yongjun --- drivers/platform/goldfish/goldfish_pipe.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

Re: [PATCH] lpfc: nvmet_fc: fix format string

On Sat, 2017-05-20 at 21:10 +0200, Arnd Bergmann wrote: > On Sat, May 20, 2017 at 12:28 PM, Joe Perches wrote: > > On Fri, 2017-05-19 at 10:04 +0200, Arnd Bergmann wrote: > > > The lpfc_nvmeio_data() tracing helper always takes a format string and > > > three additional

Re: [PATCH] lpfc: nvmet_fc: fix format string

On Sat, 2017-05-20 at 21:10 +0200, Arnd Bergmann wrote: > On Sat, May 20, 2017 at 12:28 PM, Joe Perches wrote: > > On Fri, 2017-05-19 at 10:04 +0200, Arnd Bergmann wrote: > > > The lpfc_nvmeio_data() tracing helper always takes a format string and > > > three additional arguments. > > > > No it

linux-next 20170519 - semaphores broken

Seeing problems with programs that use semaphores. The one that I'm getting bit by is jackd. strace says: getuid()= 967 semget(0x282929, 0, 000)= 229376 semop(229376, [{0, -1, SEM_UNDO}], 1) = -1 EIDRM (Identifier removed) write(2, "JACK

linux-next 20170519 - semaphores broken

Seeing problems with programs that use semaphores. The one that I'm getting bit by is jackd. strace says: getuid()= 967 semget(0x282929, 0, 000)= 229376 semop(229376, [{0, -1, SEM_UNDO}], 1) = -1 EIDRM (Identifier removed) write(2, "JACK

[PATCH] x86: fix reference to lockup watchdog documentation

Fixes: 9919cba7ff71147803c988521cc1ceb80e7f0f6d ("watchdog: Update documentation") Signed-off-by: Benjamin Peterson --- arch/x86/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig index cd18994a9555..4ccfacc7232a

[PATCH] x86: fix reference to lockup watchdog documentation

Fixes: 9919cba7ff71147803c988521cc1ceb80e7f0f6d ("watchdog: Update documentation") Signed-off-by: Benjamin Peterson --- arch/x86/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig index cd18994a9555..4ccfacc7232a 100644 ---

Re: [PATCH] PCI: Make SR-IOV capable GPU working on the SR-IOV incapable platform

I'd say the common solution is probably the parameter that allows the user to disable SR-IOV in the kernel on boot. The problem with trying to do this automatically is that there are too many scenarios to know what it was that the BIOS was trying to do. Another alternative would be to look at

Re: [PATCH] PCI: Make SR-IOV capable GPU working on the SR-IOV incapable platform

I'd say the common solution is probably the parameter that allows the user to disable SR-IOV in the kernel on boot. The problem with trying to do this automatically is that there are too many scenarios to know what it was that the BIOS was trying to do. Another alternative would be to look at

Re: [PATCH] drm: remove NULL pointer check for clk_disable_unprepare

On Sat, May 20, 2017 at 3:04 PM, Masahiro Yamada wrote: > 2017-05-21 2:58 GMT+09:00 Masahiro Yamada : >> After long term efforts of fixing non-common clock implementations, >> clk_disable() is a no-op for a NULL pointer input, and this

Re: [PATCH] drm: remove NULL pointer check for clk_disable_unprepare

On Sat, May 20, 2017 at 3:04 PM, Masahiro Yamada wrote: > 2017-05-21 2:58 GMT+09:00 Masahiro Yamada : >> After long term efforts of fixing non-common clock implementations, >> clk_disable() is a no-op for a NULL pointer input, and this is now >> tree-wide consistent. >> >> All clock consumers can

Re: [PATCH] Make x86 use $TARGET-readelf like all the other arches.

On Sat, May 20, 2017 at 1:03 PM, Rob Landley wrote: > From: Rob Landley > > My cross-compile environment doesn't provide an unprefixed > readelf in the $PATH, which works fine on every target but x86, > where you get a bunch of "/bin/sh: 1: readelf: not found"

Re: [PATCH] Make x86 use $TARGET-readelf like all the other arches.

On Sat, May 20, 2017 at 1:03 PM, Rob Landley wrote: > From: Rob Landley > > My cross-compile environment doesn't provide an unprefixed > readelf in the $PATH, which works fine on every target but x86, > where you get a bunch of "/bin/sh: 1: readelf: not found" > messages (but the result still

Re: [PATCH 7/7] DWARF: add the config option

On Sat, May 20, 2017 at 4:00 PM, Linus Torvalds wrote: > > hjl already posted an example of the kinds of horrors glibc does to do > things "right". Side note: we'd hopefully/presumably never need anything _that_ disgusting for the kernel, so hjl's example is

Re: [PATCH 7/7] DWARF: add the config option

On Sat, May 20, 2017 at 4:00 PM, Linus Torvalds wrote: > > hjl already posted an example of the kinds of horrors glibc does to do > things "right". Side note: we'd hopefully/presumably never need anything _that_ disgusting for the kernel, so hjl's example is probably an extreme one. But even

LOAN UPDATE

Hello, Complement of the day to you,Please treat this with the utmost confidentiality and Upon maturity, I sent a routine notification to you days back and never receive a response from you...If you find yourself able to work with me, contact for an update in regards to the latest development

LOAN UPDATE

Hello, Complement of the day to you,Please treat this with the utmost confidentiality and Upon maturity, I sent a routine notification to you days back and never receive a response from you...If you find yourself able to work with me, contact for an update in regards to the latest development

Re: [PATCH 7/7] DWARF: add the config option

On Sat, May 20, 2017 at 2:56 PM, Andy Lutomirski wrote: > On Sat, May 20, 2017 at 1:16 PM, Linus Torvalds > wrote: >> >> The amount of unreadable crap and bugs it requires is not worth the >> pain. Not for *any* amount of gain, and the gain here is

Re: [PATCH 7/7] DWARF: add the config option

On Sat, May 20, 2017 at 2:56 PM, Andy Lutomirski wrote: > On Sat, May 20, 2017 at 1:16 PM, Linus Torvalds > wrote: >> >> The amount of unreadable crap and bugs it requires is not worth the >> pain. Not for *any* amount of gain, and the gain here is basically >> zero. > > But what if objtool

Re: [v3, 2/2] initramfs: Allow again choice of the embedded initram compression algorithm

Hi Francisco, Nicholas, Nicholas already fixed part of this commit, but there is more breakage, see below: On 09/27/2016 01:32 PM, klondike wrote: > Choosing the appropriate compression option when using an embeded initramfs > can result in significant size differences in the resulting data. >

Re: [v3, 2/2] initramfs: Allow again choice of the embedded initram compression algorithm

Hi Francisco, Nicholas, Nicholas already fixed part of this commit, but there is more breakage, see below: On 09/27/2016 01:32 PM, klondike wrote: > Choosing the appropriate compression option when using an embeded initramfs > can result in significant size differences in the resulting data. >

Re: [PATCH 7/7] DWARF: add the config option

On Sat, May 20, 2017 at 2:58 PM, Andy Lutomirski wrote: > On Sat, May 20, 2017 at 1:01 PM, H.J. Lu wrote: >> On Sat, May 20, 2017 at 9:20 AM, Josh Poimboeuf wrote: >> (H.J., could we get a binutils feature that allows is to

Re: [PATCH 7/7] DWARF: add the config option

On Sat, May 20, 2017 at 2:58 PM, Andy Lutomirski wrote: > On Sat, May 20, 2017 at 1:01 PM, H.J. Lu wrote: >> On Sat, May 20, 2017 at 9:20 AM, Josh Poimboeuf wrote: >> (H.J., could we get a binutils feature that allows is to do: pushq %whatever .cfi_adjust_sp -8 ...

[PATCH] ubifs: Wire-up statx() support

statx() can report what flags a file has, expose flags that UBIFS supports. Especially STATX_ATTR_COMPRESSED and STATX_ATTR_ENCRYPTED can be interesting for userspace. Signed-off-by: Richard Weinberger --- fs/ubifs/dir.c | 15 +++ 1 file changed, 15 insertions(+)

[PATCH] ubifs: Wire-up statx() support

statx() can report what flags a file has, expose flags that UBIFS supports. Especially STATX_ATTR_COMPRESSED and STATX_ATTR_ENCRYPTED can be interesting for userspace. Signed-off-by: Richard Weinberger --- fs/ubifs/dir.c | 15 +++ 1 file changed, 15 insertions(+) diff --git

Re: [PATCH 7/7] DWARF: add the config option

On Sat, May 20, 2017 at 1:01 PM, H.J. Lu wrote: > On Sat, May 20, 2017 at 9:20 AM, Josh Poimboeuf wrote: > >>> >>> (H.J., could we get a binutils feature that allows is to do: >>> >>> pushq %whatever >>> .cfi_adjust_sp -8 >>> ... >>> popq %whatever >>>

Re: [PATCH 7/7] DWARF: add the config option

On Sat, May 20, 2017 at 1:01 PM, H.J. Lu wrote: > On Sat, May 20, 2017 at 9:20 AM, Josh Poimboeuf wrote: > >>> >>> (H.J., could we get a binutils feature that allows is to do: >>> >>> pushq %whatever >>> .cfi_adjust_sp -8 >>> ... >>> popq %whatever >>> .cfi_adjust_sp 8 >>> > > Np. Compiler

Re: [PATCH 7/7] DWARF: add the config option

On Sat, May 20, 2017 at 1:16 PM, Linus Torvalds wrote: > On Fri, May 19, 2017 at 10:23 PM, Andy Lutomirski wrote: >> >> I personally like the idea of using real DWARF annotations in the >> entry code because it makes gdb work better (not kgdb --

Re: [PATCH 7/7] DWARF: add the config option

On Sat, May 20, 2017 at 1:16 PM, Linus Torvalds wrote: > On Fri, May 19, 2017 at 10:23 PM, Andy Lutomirski wrote: >> >> I personally like the idea of using real DWARF annotations in the >> entry code because it makes gdb work better (not kgdb -- real gdb >> attached to KVM). I bet that we could

Re: CHIPPro NAND issue with 4.12 rc1

On 2017-05-20 09:14, Boris Brezillon wrote: Le Sat, 20 May 2017 08:49:04 -0600, Angus Ainslie a écrit : Hi All, I'm trying to boot a CHIPPro with the stock 4.12 rc1 kernel. If I make no modifications to the sun5i-gr8-chip-pro.dtb the kernel boots but can't find the root

Re: CHIPPro NAND issue with 4.12 rc1

On 2017-05-20 09:14, Boris Brezillon wrote: Le Sat, 20 May 2017 08:49:04 -0600, Angus Ainslie a écrit : Hi All, I'm trying to boot a CHIPPro with the stock 4.12 rc1 kernel. If I make no modifications to the sun5i-gr8-chip-pro.dtb the kernel boots but can't find the root partition. So I

  1   2   3   4   5   >