[PATCH] scsi: libiscsi: Fix an error handling path in 'iscsi_session_setup()'

All error handling paths in this function go through 'iscsi_host_dec_session_cnt()' except this one. Fix it and properly decrement the number of active sessions in such a case. Signed-off-by: Christophe JAILLET --- drivers/scsi/libiscsi.c | 2 +- 1 file changed, 1

[PATCH] scsi: libiscsi: Fix an error handling path in 'iscsi_session_setup()'

All error handling paths in this function go through 'iscsi_host_dec_session_cnt()' except this one. Fix it and properly decrement the number of active sessions in such a case. Signed-off-by: Christophe JAILLET --- drivers/scsi/libiscsi.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

Re: [PATCH 2/9] Implement containers as kernel objects

On 2017-09-06 09:03, Serge E. Hallyn wrote: > Quoting Richard Guy Briggs (r...@redhat.com): > ... > > > I believe we are going to need a container ID to container definition > > > (namespace, etc.) mapping mechanism regardless of if the container ID > > > is provided by userspace or a kernel

Re: [PATCH 2/9] Implement containers as kernel objects

On 2017-09-06 09:03, Serge E. Hallyn wrote: > Quoting Richard Guy Briggs (r...@redhat.com): > ... > > > I believe we are going to need a container ID to container definition > > > (namespace, etc.) mapping mechanism regardless of if the container ID > > > is provided by userspace or a kernel

[PATCH] dmaengine: imx-sdma: Correct addr widths

The driver also supports 2_BYTES and 1_BYTE in sdma_prep_slave_sg(). So this patch just adds them to the lists. Signed-off-by: Nicolin Chen --- drivers/dma/imx-sdma.c | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/drivers/dma/imx-sdma.c

[PATCH] dmaengine: imx-sdma: Correct addr widths

The driver also supports 2_BYTES and 1_BYTE in sdma_prep_slave_sg(). So this patch just adds them to the lists. Signed-off-by: Nicolin Chen --- drivers/dma/imx-sdma.c | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/drivers/dma/imx-sdma.c b/drivers/dma/imx-sdma.c

Re: [PATCH 4.9 00/14] 4.9.50-stable review

On Thu, Sep 14, 2017 at 04:18:03AM +0200, Willy Tarreau wrote: > On Wed, Sep 13, 2017 at 02:30:46PM -0700, Greg Kroah-Hartman wrote: > > > Yes. I don't recall if it is a direct --force or if you would have to > > > remove the original tag first (with git push :refs/tags/). > > > > Ah, but then

Re: [PATCH 4.9 00/14] 4.9.50-stable review

On Thu, Sep 14, 2017 at 04:18:03AM +0200, Willy Tarreau wrote: > On Wed, Sep 13, 2017 at 02:30:46PM -0700, Greg Kroah-Hartman wrote: > > > Yes. I don't recall if it is a direct --force or if you would have to > > > remove the original tag first (with git push :refs/tags/). > > > > Ah, but then

Re: [PATCH] checkpatch: support function pointers for unnamed function definition arguments

On Thu, 2017-09-14 at 11:01 +0800, Miles Chen wrote: > Current unnamed function definition argument does not include function > pointer cases and it reports warnings like: > > WARNING: function definition argument 'void' should also have an identifier > name > > Support function pointers for

Re: [PATCH] checkpatch: support function pointers for unnamed function definition arguments

On Thu, 2017-09-14 at 11:01 +0800, Miles Chen wrote: > Current unnamed function definition argument does not include function > pointer cases and it reports warnings like: > > WARNING: function definition argument 'void' should also have an identifier > name > > Support function pointers for

Re: [PATCH] tools: objtool: fix memory leak in elf_create_rela_section()

* Josh Poimboeuf wrote: > From: Martin Kepplinger > > Let's free the allocated char array relaname before returning > in order to avoid leaking memory. > > Signed-off-by: Martin Kepplinger > Signed-off-by: Josh Poimboeuf

Re: [PATCH] tools: objtool: fix memory leak in elf_create_rela_section()

* Josh Poimboeuf wrote: > From: Martin Kepplinger > > Let's free the allocated char array relaname before returning > in order to avoid leaking memory. > > Signed-off-by: Martin Kepplinger > Signed-off-by: Josh Poimboeuf > --- > tools/objtool/elf.c | 6 +- > 1 file changed, 5

Re: RFC: Audit Kernel Container IDs

On 2017-09-13 14:33, Carlos O'Donell wrote: > On 09/13/2017 12:13 PM, Richard Guy Briggs wrote: > > Containers are a userspace concept. The kernel knows nothing of them. > > I am looking at this RFC from a userspace perspective, particularly from > the loader's point of view and the unshare

Re: RFC: Audit Kernel Container IDs

On 2017-09-13 14:33, Carlos O'Donell wrote: > On 09/13/2017 12:13 PM, Richard Guy Briggs wrote: > > Containers are a userspace concept. The kernel knows nothing of them. > > I am looking at this RFC from a userspace perspective, particularly from > the loader's point of view and the unshare

Re: [patch V2 25/29] lockup_detector: Implement init time detection of perf

* Thomas Gleixner wrote: > On Wed, 13 Sep 2017, Don Zickus wrote: > > > +/* Return 0, if a NMI watchdog is available. Error code otherwise */ > > > +int __weak __init void watchdog_nmi_probe(void) > > > > ^^^ compile error, can't have 'int' and 'void'. Removing 'void'

Re: [patch V2 00/29] lockup_detector: Cure hotplug deadlocks and replace duct tape

* Don Zickus wrote: > On Tue, Sep 12, 2017 at 09:36:54PM +0200, Thomas Gleixner wrote: > > The lockup detector is broken is several ways: > > > > - It's deadlock prone vs. CPU hotplug in various ways. Some of these > > are due to recursive cpus_read_lock() others

Re: [patch V2 25/29] lockup_detector: Implement init time detection of perf

* Thomas Gleixner wrote: > On Wed, 13 Sep 2017, Don Zickus wrote: > > > +/* Return 0, if a NMI watchdog is available. Error code otherwise */ > > > +int __weak __init void watchdog_nmi_probe(void) > > > > ^^^ compile error, can't have 'int' and 'void'. Removing 'void' fixes it. > > Yes, I

Re: [patch V2 00/29] lockup_detector: Cure hotplug deadlocks and replace duct tape

* Don Zickus wrote: > On Tue, Sep 12, 2017 at 09:36:54PM +0200, Thomas Gleixner wrote: > > The lockup detector is broken is several ways: > > > > - It's deadlock prone vs. CPU hotplug in various ways. Some of these > > are due to recursive cpus_read_lock() others are due to > >

[PATCH] iommu/arm-smmu-v3: Avoid ILLEGAL setting of STE.S1STALLD

According to Spec, it is ILLEGAL to set STE.S1STALLD if STALL_MODEL is not 0b00, which means we should not disable stall mode if stall or terminate mode is not configuable. As Jean-Philippe's suggestion, this patch introduce a feature bit ARM_SMMU_FEAT_STALL_FORCE, which means smmu only supports

[PATCH] iommu/arm-smmu-v3: Avoid ILLEGAL setting of STE.S1STALLD

According to Spec, it is ILLEGAL to set STE.S1STALLD if STALL_MODEL is not 0b00, which means we should not disable stall mode if stall or terminate mode is not configuable. As Jean-Philippe's suggestion, this patch introduce a feature bit ARM_SMMU_FEAT_STALL_FORCE, which means smmu only supports

[PATCH 1/1] irqchip/gicv3: iterate over possible CPUs by for_each_possible_cpu()

From: zijun_hu get_cpu_number() doesn't use existing helper to iterate over possible CPUs, so error happens in case of discontinuous @cpu_possible_mask such as 0b0001. fixed by using existing helper for_each_possible_cpu(). Signed-off-by: zijun_hu ---

[PATCH 1/1] irqchip/gicv3: iterate over possible CPUs by for_each_possible_cpu()

From: zijun_hu get_cpu_number() doesn't use existing helper to iterate over possible CPUs, so error happens in case of discontinuous @cpu_possible_mask such as 0b0001. fixed by using existing helper for_each_possible_cpu(). Signed-off-by: zijun_hu --- drivers/irqchip/irq-gic-v3.c | 8

[PATCH v2 3/3] media: ov7670: Add the s_power operation

Add the s_power operation which is responsible for manipulating the power dowm mode through the PWDN pin and the reset operation through the RESET pin. Signed-off-by: Wenyou Yang --- Changes in v2: - Add the patch to support the get_fmt ops. - Remove the redundant

[PATCH v2 3/3] media: ov7670: Add the s_power operation

Add the s_power operation which is responsible for manipulating the power dowm mode through the PWDN pin and the reset operation through the RESET pin. Signed-off-by: Wenyou Yang --- Changes in v2: - Add the patch to support the get_fmt ops. - Remove the redundant invoking ov7670_init_gpio().

[PATCH v2 2/3] media: ov7670: Add the get_fmt callback

Add the get_fmt callback, also enable V4L2_SUBDEV_FL_HAS_DEVNODE flag to make this subdev has device node. Signed-off-by: Wenyou Yang --- Changes in v2: None drivers/media/i2c/ov7670.c | 26 ++ 1 file changed, 26 insertions(+) diff --git

[PATCH v2 2/3] media: ov7670: Add the get_fmt callback

Add the get_fmt callback, also enable V4L2_SUBDEV_FL_HAS_DEVNODE flag to make this subdev has device node. Signed-off-by: Wenyou Yang --- Changes in v2: None drivers/media/i2c/ov7670.c | 26 ++ 1 file changed, 26 insertions(+) diff --git a/drivers/media/i2c/ov7670.c

[PATCH v2 1/3] media: ov7670: Add entity pads initialization

Add the media entity pads initialization. Signed-off-by: Wenyou Yang --- Changes in v2: None drivers/media/i2c/ov7670.c | 13 - 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/drivers/media/i2c/ov7670.c b/drivers/media/i2c/ov7670.c index

[PATCH v2 1/3] media: ov7670: Add entity pads initialization

Add the media entity pads initialization. Signed-off-by: Wenyou Yang --- Changes in v2: None drivers/media/i2c/ov7670.c | 13 - 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/drivers/media/i2c/ov7670.c b/drivers/media/i2c/ov7670.c index e88549f0e704..5c8460ee65c3

[PATCH v2 0/3] media: ov7670: Add entity init and power operation

This patch set is to add the media entity pads initialization, the s_power operation and get_fmt callback support. Changes in v2: - Add the patch to support the get_fmt ops. - Remove the redundant invoking ov7670_init_gpio(). Wenyou Yang (3): media: ov7670: Add entity pads initialization

[PATCH v2 0/3] media: ov7670: Add entity init and power operation

This patch set is to add the media entity pads initialization, the s_power operation and get_fmt callback support. Changes in v2: - Add the patch to support the get_fmt ops. - Remove the redundant invoking ov7670_init_gpio(). Wenyou Yang (3): media: ov7670: Add entity pads initialization

Re: [Outreachy kernel] Re: [PATCH v2 1/2] include: linux: sysfs: Add __ATTR_NAMED macro

On Wed, 13 Sep 2017, Joe Perches wrote: > On Thu, 2017-09-14 at 00:43 +0300, Dan Carpenter wrote: > > He was exagerating a bit to call it a "static checker" warning... > > Not really. > > False positives and false negatives exist in just about > every static > checker. > > > It's just

Re: [Outreachy kernel] Re: [PATCH v2 1/2] include: linux: sysfs: Add __ATTR_NAMED macro

On Wed, 13 Sep 2017, Joe Perches wrote: > On Thu, 2017-09-14 at 00:43 +0300, Dan Carpenter wrote: > > He was exagerating a bit to call it a "static checker" warning... > > Not really. > > False positives and false negatives exist in just about > every static > checker. > > > It's just

Re: [RFC PATCH] can: m_can: Support higher speed CAN-FD bitrates

On Thursday 14 September 2017 03:28 AM, Franklin S Cooper Jr wrote: > > > On 08/18/2017 02:39 PM, Franklin S Cooper Jr wrote: >> During test transmitting using CAN-FD at high bitrates (4 Mbps) only >> resulted in errors. Scoping the signals I noticed that only a single bit >> was being

Re: [RFC PATCH] can: m_can: Support higher speed CAN-FD bitrates

On Thursday 14 September 2017 03:28 AM, Franklin S Cooper Jr wrote: > > > On 08/18/2017 02:39 PM, Franklin S Cooper Jr wrote: >> During test transmitting using CAN-FD at high bitrates (4 Mbps) only >> resulted in errors. Scoping the signals I noticed that only a single bit >> was being

[PATCH] staging: irda: Remove typedef struct

This patch remove typedef from a structure with all its ocurrences since using typedefs for structures is discouraged. Issue found using Coccinelle: @r1@ type T; @@ typedef struct { ... } T; @script:python c1@ T2; T << r1.T; @@ if T[-2:] =="_t" or T[-2:] == "_T": coccinelle.T2 = T[:-2];

[PATCH] staging: irda: Remove typedef struct

This patch remove typedef from a structure with all its ocurrences since using typedefs for structures is discouraged. Issue found using Coccinelle: @r1@ type T; @@ typedef struct { ... } T; @script:python c1@ T2; T << r1.T; @@ if T[-2:] =="_t" or T[-2:] == "_T": coccinelle.T2 = T[:-2];

Re: [PATCH 01/10] arch:powerpc: return -ENOMEM on failed allocation

> I think the changelog for this series of conversions > should show that you've validated the change by > inspecting the return call chain at each modified line. > > Also, it seems you've cc'd the same mailing lists for > all of the patches modified by this series. > > It would be better to

Re: [PATCH 01/10] arch:powerpc: return -ENOMEM on failed allocation

> I think the changelog for this series of conversions > should show that you've validated the change by > inspecting the return call chain at each modified line. > > Also, it seems you've cc'd the same mailing lists for > all of the patches modified by this series. > > It would be better to

[PATCH] Input: add support for HiDeep touchscreen

The HiDeep touchscreen device is a capacitive multi-touch controller mainly for multi-touch supported devices use. It use I2C interface for communication to IC and provide axis X, Y, Z locations for ten finger touch through input event interface to userspace. It support the Crimson and the Lime

[PATCH] Input: add support for HiDeep touchscreen

The HiDeep touchscreen device is a capacitive multi-touch controller mainly for multi-touch supported devices use. It use I2C interface for communication to IC and provide axis X, Y, Z locations for ten finger touch through input event interface to userspace. It support the Crimson and the Lime

[lkp-robot] [kprobes] e1ce3eee7d: BUG:using_smp_processor_id()in_preemptible

IG_PREEMPT/20170913-034557 in testcase: boot on test machine: qemu-system-x86_64 -enable-kvm -cpu Haswell,+smep,+smap -smp 2 -m 512M caused below changes (please refer to attached dmesg/kmsg for entire log

[lkp-robot] [kprobes] e1ce3eee7d: BUG:using_smp_processor_id()in_preemptible

IG_PREEMPT/20170913-034557 in testcase: boot on test machine: qemu-system-x86_64 -enable-kvm -cpu Haswell,+smep,+smap -smp 2 -m 512M caused below changes (please refer to attached dmesg/kmsg for entire log

Re: [RESEND][PATCH] kvm: x86: Do not handle MMIO request in fast_page_fault

On Wed, Sep 13, 2017 at 04:39:56PM +0200, Radim Krčmář wrote: > 2017-09-05 18:37+0800, changbin...@intel.com: > > From: Changbin Du > > > > If it is a MMIO request, it should be handled by slow path. This patch > > actually fixed below warning when mmu debug is enabled. >

Re: [RESEND][PATCH] kvm: x86: Do not handle MMIO request in fast_page_fault

On Wed, Sep 13, 2017 at 04:39:56PM +0200, Radim Krčmář wrote: > 2017-09-05 18:37+0800, changbin...@intel.com: > > From: Changbin Du > > > > If it is a MMIO request, it should be handled by slow path. This patch > > actually fixed below warning when mmu debug is enabled. > > > > WARNING: CPU: 5

[PATCH 2/3] drm/rockchip: Add support for Rockchip Soc RGB output interface

Like rockchip rv1108 crtc can directly output parallel and serial RGB data to panel or conversion chip, so we add this driver to probe encoder and connector. Signed-off-by: Sandy Huang --- drivers/gpu/drm/rockchip/Kconfig| 9 +

[PATCH 1/3] dt-bindings: Add document for rockchip RGB output interface

This path add support rv1108 rgb output interface driver. Signed-off-by: Sandy Huang --- .../bindings/display/rockchip/rockchip-rgb.txt | 80 ++ 1 file changed, 80 insertions(+) create mode 100644

[PATCH 2/3] drm/rockchip: Add support for Rockchip Soc RGB output interface

Like rockchip rv1108 crtc can directly output parallel and serial RGB data to panel or conversion chip, so we add this driver to probe encoder and connector. Signed-off-by: Sandy Huang --- drivers/gpu/drm/rockchip/Kconfig| 9 + drivers/gpu/drm/rockchip/Makefile | 1 +

[PATCH 1/3] dt-bindings: Add document for rockchip RGB output interface

This path add support rv1108 rgb output interface driver. Signed-off-by: Sandy Huang --- .../bindings/display/rockchip/rockchip-rgb.txt | 80 ++ 1 file changed, 80 insertions(+) create mode 100644 Documentation/devicetree/bindings/display/rockchip/rockchip-rgb.txt

[PATCH 0/3] Add support rockchip RGB output interface

This patches add support some rockchip Soc like rv1108, the VOP can directly output parallel and serial RGB data to panel or to conversion chip. So we add this driver to probe encoder and connector to support this case. Sandy Huang (3): dt-bindings: Add document for rockchip RGB output

[PATCH 3/3] drm/rockchip: vop: Add more RGB output interface type

This patch add serial RGB output interface for rockchip vop, the more info about serial RGB output interface described at the following file: Documentation/devicetree/bindings/display/rockchip/rockchip-rgb.txt Signed-off-by: Sandy Huang ---

[PATCH 0/3] Add support rockchip RGB output interface

This patches add support some rockchip Soc like rv1108, the VOP can directly output parallel and serial RGB data to panel or to conversion chip. So we add this driver to probe encoder and connector to support this case. Sandy Huang (3): dt-bindings: Add document for rockchip RGB output

[PATCH 3/3] drm/rockchip: vop: Add more RGB output interface type

This patch add serial RGB output interface for rockchip vop, the more info about serial RGB output interface described at the following file: Documentation/devicetree/bindings/display/rockchip/rockchip-rgb.txt Signed-off-by: Sandy Huang --- drivers/gpu/drm/rockchip/rockchip_drm_vop.h | 2 ++ 1

linux-next: Tree for Sep 14

Hi all, Please do not add any v4.15 related material to your linux-next included branches until after v4.14-rc1 has been released. Changes since 20170913: The vfs tree gained a conflict against the btrfs-kdave tree. Non-merge commits (relative to Linus' tree): 746 1078 files changed, 39588

linux-next: Tree for Sep 14

Hi all, Please do not add any v4.15 related material to your linux-next included branches until after v4.14-rc1 has been released. Changes since 20170913: The vfs tree gained a conflict against the btrfs-kdave tree. Non-merge commits (relative to Linus' tree): 746 1078 files changed, 39588

[PATCH v2] ASoC: fsl_ssi: Caculate bit clock rate using slot number and width

The set_sysclk() now is used to override the output bit clock rate. But this is not a common way to implement a set_dai_sysclk(). And this creates a problem when a general machine driver (simple-card for example) tries to do set_dai_sysclk() by passing an input clock rate for the baud clock

[PATCH v2] ASoC: fsl_ssi: Caculate bit clock rate using slot number and width

The set_sysclk() now is used to override the output bit clock rate. But this is not a common way to implement a set_dai_sysclk(). And this creates a problem when a general machine driver (simple-card for example) tries to do set_dai_sysclk() by passing an input clock rate for the baud clock

[PATCH] checkpatch: support function pointers for unnamed function definition arguments

Current unnamed function definition argument does not include function pointer cases and it reports warnings like: WARNING: function definition argument 'void' should also have an identifier name +unsigned int (*dummy)(void); Support function pointers for unnamed function arguments.

[PATCH] checkpatch: support function pointers for unnamed function definition arguments

Current unnamed function definition argument does not include function pointer cases and it reports warnings like: WARNING: function definition argument 'void' should also have an identifier name +unsigned int (*dummy)(void); Support function pointers for unnamed function arguments.

[PATCH] net/packet: fix race condition between fanout_add and __unregister_prot_hook

If fanout_add is preempted after running po-> fanout = match and before running __fanout_link, it will cause BUG_ON when __unregister_prot_hook call __fanout_unlink so, we need add mutex_lock(_mutex) to __unregister_prot_hook or add spin_lock(>bind_lock) before po-> fanout = match test on linux

[PATCH] net/packet: fix race condition between fanout_add and __unregister_prot_hook

If fanout_add is preempted after running po-> fanout = match and before running __fanout_link, it will cause BUG_ON when __unregister_prot_hook call __fanout_unlink so, we need add mutex_lock(_mutex) to __unregister_prot_hook or add spin_lock(>bind_lock) before po-> fanout = match test on linux

[PATCH] gpio: thunderx: remove unused .map() hook from irq_domain_ops

This driver implements .alloc() hook, so .map() is not used. Signed-off-by: Masahiro Yamada --- drivers/gpio/gpio-thunderx.c | 13 - 1 file changed, 13 deletions(-) diff --git a/drivers/gpio/gpio-thunderx.c b/drivers/gpio/gpio-thunderx.c index

[PATCH] gpio: thunderx: remove unused .map() hook from irq_domain_ops

This driver implements .alloc() hook, so .map() is not used. Signed-off-by: Masahiro Yamada --- drivers/gpio/gpio-thunderx.c | 13 - 1 file changed, 13 deletions(-) diff --git a/drivers/gpio/gpio-thunderx.c b/drivers/gpio/gpio-thunderx.c index 57efb25..b5adb79 100644 ---

[PATCH] net/packet: fix race condition between fanout_add and __unregister_prot_hook

If fanout_add is preempted after running po-> fanout = match and before running __fanout_link, it will cause BUG_ON when __unregister_prot_hook call __fanout_unlink so, we need add mutex_lock(_mutex) to __unregister_prot_hook or add spin_lock(>bind_lock) before po-> fanout = match test on linux

[PATCH] net/packet: fix race condition between fanout_add and __unregister_prot_hook

If fanout_add is preempted after running po-> fanout = match and before running __fanout_link, it will cause BUG_ON when __unregister_prot_hook call __fanout_unlink so, we need add mutex_lock(_mutex) to __unregister_prot_hook or add spin_lock(>bind_lock) before po-> fanout = match test on linux

[PATCH 1/1] Coccinelle: array_size: report even if include is missing

Rule r does not depend on rule i (which is the include of linux/kernel.h) so the output should not depend on i in org and report mode. Signed-off-by: Jérémy Lefaure --- I have tested this patch in report mode on the file

[PATCH 1/1] Coccinelle: array_size: report even if include is missing

Rule r does not depend on rule i (which is the include of linux/kernel.h) so the output should not depend on i in org and report mode. Signed-off-by: Jérémy Lefaure --- I have tested this patch in report mode on the file drivers/staging/rtlwifi/phydm/rtl8822b/halhwimg8822b_rf.c which does not

[PATCH] signal: remove unused variable

Reported-by: Stephen Rothwell Fixes: 9b24ec57688a ("get_compat_sigset()") Signed-off-by: Dmitry V. Levin --- kernel/signal.c | 1 - 1 file changed, 1 deletion(-) diff --git a/kernel/signal.c b/kernel/signal.c index 3198a7d2e5ff..36a523640894 100644 ---

[PATCH] signal: remove unused variable

Reported-by: Stephen Rothwell Fixes: 9b24ec57688a ("get_compat_sigset()") Signed-off-by: Dmitry V. Levin --- kernel/signal.c | 1 - 1 file changed, 1 deletion(-) diff --git a/kernel/signal.c b/kernel/signal.c index 3198a7d2e5ff..36a523640894 100644 --- a/kernel/signal.c +++ b/kernel/signal.c

Re: [PATCH 2/2 v2] sched/wait: Introduce lock breaker in wake_up_page_bit

On Wed, Sep 13, 2017 at 7:12 PM, Tim Chen wrote: > > BTW, will you be merging these 2 patches in 4.14? Yes, and thanks for reminding me. In fact, would you mind sending me the latest versions, rather than me digging them out of the disaster area that is my mailbox

Re: [PATCH 2/2 v2] sched/wait: Introduce lock breaker in wake_up_page_bit

On Wed, Sep 13, 2017 at 7:12 PM, Tim Chen wrote: > > BTW, will you be merging these 2 patches in 4.14? Yes, and thanks for reminding me. In fact, would you mind sending me the latest versions, rather than me digging them out of the disaster area that is my mailbox and possibly picking an older

RE: [Intel-wired-lan] [PATCH] igb: check memory allocation failure

> From: Intel-wired-lan [mailto:intel-wired-lan-boun...@osuosl.org] On Behalf > Of Christophe JAILLET > Sent: Monday, August 28, 2017 10:13 AM > To: Waskiewicz Jr, Peter ; Kirsher, Jeffrey T > > Cc: net...@vger.kernel.org;

Re: [PATCH 4.9 00/14] 4.9.50-stable review

On Wed, Sep 13, 2017 at 02:30:46PM -0700, Greg Kroah-Hartman wrote: > > Yes. I don't recall if it is a direct --force or if you would have to > > remove the original tag first (with git push :refs/tags/). > > Ah, but then if someone had pulled the old tag, they would have to > delete it locally

RE: [Intel-wired-lan] [PATCH] igb: check memory allocation failure

> From: Intel-wired-lan [mailto:intel-wired-lan-boun...@osuosl.org] On Behalf > Of Christophe JAILLET > Sent: Monday, August 28, 2017 10:13 AM > To: Waskiewicz Jr, Peter ; Kirsher, Jeffrey T > > Cc: net...@vger.kernel.org; kernel-janit...@vger.kernel.org; intel-wired- > l...@lists.osuosl.org;

Re: [PATCH 4.9 00/14] 4.9.50-stable review

On Wed, Sep 13, 2017 at 02:30:46PM -0700, Greg Kroah-Hartman wrote: > > Yes. I don't recall if it is a direct --force or if you would have to > > remove the original tag first (with git push :refs/tags/). > > Ah, but then if someone had pulled the old tag, they would have to > delete it locally

[PATCH] f2fs: show flush list status in sysfs

This patch adds to show flush list status in sysfs. Signed-off-by: Chao Yu --- fs/f2fs/debug.c | 5 - fs/f2fs/f2fs.h | 3 ++- 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/fs/f2fs/debug.c b/fs/f2fs/debug.c index 87f449845f5f..00c1d4a9f356 100644 ---

[PATCH] f2fs: show flush list status in sysfs

This patch adds to show flush list status in sysfs. Signed-off-by: Chao Yu --- fs/f2fs/debug.c | 5 - fs/f2fs/f2fs.h | 3 ++- 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/fs/f2fs/debug.c b/fs/f2fs/debug.c index 87f449845f5f..00c1d4a9f356 100644 --- a/fs/f2fs/debug.c +++

Re: [PATCH 2/2 v2] sched/wait: Introduce lock breaker in wake_up_page_bit

On 08/29/2017 09:24 AM, Linus Torvalds wrote: > On Tue, Aug 29, 2017 at 9:13 AM, Tim Chen wrote: >> >> It is affecting not a production use, but the customer's acceptance >> test for their systems. So I suspect it is a stress test. > > Can you gently poke them and

Re: [PATCH v2 1/2] dt-bindings: spi: Add Spreadtrum ADI controller documentation

Hi Rob, On 14 September 2017 at 03:51, Rob Herring wrote: > On Fri, Sep 08, 2017 at 04:33:41PM +0800, Baolin Wang wrote: >> This patch adds the binding documentation for Spreadtrum ADI >> controller device. >> >> Signed-off-by: Baolin Wang >> --- >>

Re: [PATCH 2/2 v2] sched/wait: Introduce lock breaker in wake_up_page_bit

On 08/29/2017 09:24 AM, Linus Torvalds wrote: > On Tue, Aug 29, 2017 at 9:13 AM, Tim Chen wrote: >> >> It is affecting not a production use, but the customer's acceptance >> test for their systems. So I suspect it is a stress test. > > Can you gently poke them and ask if they might make theie

Re: [PATCH v2 1/2] dt-bindings: spi: Add Spreadtrum ADI controller documentation

Hi Rob, On 14 September 2017 at 03:51, Rob Herring wrote: > On Fri, Sep 08, 2017 at 04:33:41PM +0800, Baolin Wang wrote: >> This patch adds the binding documentation for Spreadtrum ADI >> controller device. >> >> Signed-off-by: Baolin Wang >> --- >> Changes since v1: >> - Add more

Re: [PATCH 01/12] mmc: dt-bindings: update Mediatek MMC bindings

On Wed, 2017-09-13 at 09:10 -0500, Rob Herring wrote: > On Tue, Sep 12, 2017 at 05:07:41PM +0800, Chaotian Jing wrote: > > Change the comptiable for support of multi-platform > > Add description for reg > > Add description for source_cg > > Add description for mediatek,latch-ck > > This is at

Re: [PATCH 01/12] mmc: dt-bindings: update Mediatek MMC bindings

On Wed, 2017-09-13 at 09:10 -0500, Rob Herring wrote: > On Tue, Sep 12, 2017 at 05:07:41PM +0800, Chaotian Jing wrote: > > Change the comptiable for support of multi-platform > > Add description for reg > > Add description for source_cg > > Add description for mediatek,latch-ck > > This is at

Re: [PATCH v2 2/2] spi: Add ADI driver for Spreadtrum platform

Hi Rob, On 14 September 2017 at 03:45, Rob Herring wrote: > On Fri, Sep 08, 2017 at 04:33:42PM +0800, Baolin Wang wrote: >> This patch adds ADI driver based on SPI framework for >> Spreadtrum SC9860 platform. >> >> Signed-off-by: Baolin Wang >> --- >

Re: [PATCH v2 2/2] spi: Add ADI driver for Spreadtrum platform

Hi Rob, On 14 September 2017 at 03:45, Rob Herring wrote: > On Fri, Sep 08, 2017 at 04:33:42PM +0800, Baolin Wang wrote: >> This patch adds ADI driver based on SPI framework for >> Spreadtrum SC9860 platform. >> >> Signed-off-by: Baolin Wang >> --- > > [...] > >> +++

Re: linux-next: build warning after merge of the vfs tree

Hi Al, On Fri, 8 Sep 2017 09:25:45 +1000 Stephen Rothwell wrote: > > After merging the vfs tree, today's linux-next build (powerpc > ppc64_defconfig) produced this warning: > > kernel/signal.c: In function 'C_SYSC_rt_sigaction': > kernel/signal.c:3405:19: warning: unused

Re: linux-next: build warning after merge of the vfs tree

Hi Al, On Fri, 8 Sep 2017 09:25:45 +1000 Stephen Rothwell wrote: > > After merging the vfs tree, today's linux-next build (powerpc > ppc64_defconfig) produced this warning: > > kernel/signal.c: In function 'C_SYSC_rt_sigaction': > kernel/signal.c:3405:19: warning: unused variable 'mask'

Re: [PATCH v2 RESEND 0/2] x86/mm/KASLR: Do not adapt the size of the direct mapping section for SGI UV system

Hi all, PING! Do anyone has any suggestion about this issue? This bug blocks SGI system's boot, KASLR has to be disabled on SGI system if they want to run tests. Thanks Baoquan On 09/07/17 at 03:42pm, Baoquan He wrote: > This is v2 post RESEND. Add Mike's Acked-by to patch 2/2 as he suggested

Re: [PATCH v2 RESEND 0/2] x86/mm/KASLR: Do not adapt the size of the direct mapping section for SGI UV system

Hi all, PING! Do anyone has any suggestion about this issue? This bug blocks SGI system's boot, KASLR has to be disabled on SGI system if they want to run tests. Thanks Baoquan On 09/07/17 at 03:42pm, Baoquan He wrote: > This is v2 post RESEND. Add Mike's Acked-by to patch 2/2 as he suggested

Re: [PATCH] vfs: introduce UMOUNT_WAIT which waits for umount completion

On Wed, Sep 13, 2017 at 06:10:48PM -0700, Jaegeuk Kim wrote: > Android triggers umount(2) by init process, which is definitely not a kernel > thread. But, we've seen some kernel panics which say umount(2) was succeeded, > but ext4 triggered a kernel panic due to EIO after then like below. I'm

Re: [PATCH] vfs: introduce UMOUNT_WAIT which waits for umount completion

On Wed, Sep 13, 2017 at 06:10:48PM -0700, Jaegeuk Kim wrote: > Android triggers umount(2) by init process, which is definitely not a kernel > thread. But, we've seen some kernel panics which say umount(2) was succeeded, > but ext4 triggered a kernel panic due to EIO after then like below. I'm

[PATCH v9 2/4] ARM: dts: rockchip: add RGA device node for RK3288

This patch add the RGA dt config of rk3288 SoC. Signed-off-by: Jacob Chen Signed-off-by: Yakir Yang --- arch/arm/boot/dts/rk3288.dtsi | 11 +++ 1 file changed, 11 insertions(+) diff --git a/arch/arm/boot/dts/rk3288.dtsi

[PATCH v9 2/4] ARM: dts: rockchip: add RGA device node for RK3288

This patch add the RGA dt config of rk3288 SoC. Signed-off-by: Jacob Chen Signed-off-by: Yakir Yang --- arch/arm/boot/dts/rk3288.dtsi | 11 +++ 1 file changed, 11 insertions(+) diff --git a/arch/arm/boot/dts/rk3288.dtsi b/arch/arm/boot/dts/rk3288.dtsi index 595d395..ca6c63a 100644 ---

[PATCH v9 1/4] rockchip/rga: v4l2 m2m support

Rockchip RGA is a separate 2D raster graphic acceleration unit. It accelerates 2D graphics operations, such as point/line drawing, image scaling, rotation, BitBLT, alpha blending and image blur/sharpness The drvier is mostly based on s5p-g2d v4l2 m2m driver And supports various operations from

[PATCH v9 1/4] rockchip/rga: v4l2 m2m support

Rockchip RGA is a separate 2D raster graphic acceleration unit. It accelerates 2D graphics operations, such as point/line drawing, image scaling, rotation, BitBLT, alpha blending and image blur/sharpness The drvier is mostly based on s5p-g2d v4l2 m2m driver And supports various operations from

Re: [PATCH v9 0/4] Add Rockchip RGA V4l2 support

Hi all, 2017-09-14 9:19 GMT+08:00 Jacob Chen : > This patch series add a v4l2 m2m drvier for rockchip RGA direct rendering > based 2d graphics acceleration module. > > Recently I tried to add protduff support for gstreamer on rockchip platform, > and i found that API >

Re: [PATCH v9 0/4] Add Rockchip RGA V4l2 support

Hi all, 2017-09-14 9:19 GMT+08:00 Jacob Chen : > This patch series add a v4l2 m2m drvier for rockchip RGA direct rendering > based 2d graphics acceleration module. > > Recently I tried to add protduff support for gstreamer on rockchip platform, > and i found that API > were not very suitable

[PATCH v9 4/4] dt-bindings: Document the Rockchip RGA bindings

Add DT bindings documentation for Rockchip RGA Signed-off-by: Jacob Chen Signed-off-by: Yakir Yang Acked-by: Rob Herring --- .../devicetree/bindings/media/rockchip-rga.txt | 33 ++ 1 file changed, 33

[PATCH v9 4/4] dt-bindings: Document the Rockchip RGA bindings

Add DT bindings documentation for Rockchip RGA Signed-off-by: Jacob Chen Signed-off-by: Yakir Yang Acked-by: Rob Herring --- .../devicetree/bindings/media/rockchip-rga.txt | 33 ++ 1 file changed, 33 insertions(+) create mode 100644

[PATCH v9 0/4] Add Rockchip RGA V4l2 support

This patch series add a v4l2 m2m drvier for rockchip RGA direct rendering based 2d graphics acceleration module. Recently I tried to add protduff support for gstreamer on rockchip platform, and i found that API were not very suitable for my purpose. It shouldn't go upstream until we can

[PATCH v9 0/4] Add Rockchip RGA V4l2 support

This patch series add a v4l2 m2m drvier for rockchip RGA direct rendering based 2d graphics acceleration module. Recently I tried to add protduff support for gstreamer on rockchip platform, and i found that API were not very suitable for my purpose. It shouldn't go upstream until we can

  1   2   3   4   5   6   7   8   9   10   >