OOM killer invoked during btrfs send/recieve on otherwise idle machine

Tonight the OOM killer got invoked during backup of /: [Jul31 01:56] kthreadd invoked oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=2, oom_score_adj=0 [ +0.04] CPU: 3 PID: 2 Comm: kthreadd Not tainted 4.7.0-06816-g797cee982eef-dirty #37 [ +0.00] Hardware

OOM killer invoked during btrfs send/recieve on otherwise idle machine

Tonight the OOM killer got invoked during backup of /: [Jul31 01:56] kthreadd invoked oom-killer: gfp_mask=0x27000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK), order=2, oom_score_adj=0 [ +0.04] CPU: 3 PID: 2 Comm: kthreadd Not tainted 4.7.0-06816-g797cee982eef-dirty #37 [ +0.00] Hardware

[PATCH v2] Bluetooth: Add LED triggers for HCI frames tx and rx

Two LED triggers are added into hci_dev: tx_led and rx_led. Upon ACL/SCO packets available in tx or rx, the LEDs will blink. For each hci registration, two triggers are added into LED subsystem: [hdev->name]-tx and [hdev-name]-rx. Refer to Documentation/leds/leds-class.txt for usage. Verified on

[PATCH v2] Bluetooth: Add LED triggers for HCI frames tx and rx

Two LED triggers are added into hci_dev: tx_led and rx_led. Upon ACL/SCO packets available in tx or rx, the LEDs will blink. For each hci registration, two triggers are added into LED subsystem: [hdev->name]-tx and [hdev-name]-rx. Refer to Documentation/leds/leds-class.txt for usage. Verified on

Re: [PATCH v2 0/4] drivers: net: cpsw: fix driver loading/unloading

From: Grygorii Strashko Date: Thu, 28 Jul 2016 20:50:33 +0300 > This series fixes set of isssues observed when CPSW driver module is > unloaded/loaded: > 1) rmmod: deadlock in cpdma_ctlr_destroy > 2) rmmod: L3 back-trace and crash if all net interfaces are down,

Re: [PATCH v2 0/4] drivers: net: cpsw: fix driver loading/unloading

From: Grygorii Strashko Date: Thu, 28 Jul 2016 20:50:33 +0300 > This series fixes set of isssues observed when CPSW driver module is > unloaded/loaded: > 1) rmmod: deadlock in cpdma_ctlr_destroy > 2) rmmod: L3 back-trace and crash if all net interfaces are down, because CPSW > can be powerred

[PATCH] i2c: Modify error handling

devm_gpiod_get returns an ERR_PTR on error so a null check is incorrect and an IS_ERR check is required. The Coccinelle semantic patch used to make this change is as follows: @@ expression e; statement S; @@ e = devm_gpiod_get(...); if( - !e + IS_ERR(e) ) { ... - return ...; +

[PATCH] i2c: Modify error handling

devm_gpiod_get returns an ERR_PTR on error so a null check is incorrect and an IS_ERR check is required. The Coccinelle semantic patch used to make this change is as follows: @@ expression e; statement S; @@ e = devm_gpiod_get(...); if( - !e + IS_ERR(e) ) { ... - return ...; +

Re: [PATCH] random: Fix crashes with sparse node ids

On Sat, Jul 30, 2016 at 8:27 PM, Michael Ellerman wrote: > > Dropping NOFAIL means we need to handle allocation failures, which makes > the patch a bit bigger, and less of a pure fix. Hmm. If you get allocation failures for something like this at init time, I think you're

Re: [PATCH] random: Fix crashes with sparse node ids

On Sat, Jul 30, 2016 at 8:27 PM, Michael Ellerman wrote: > > Dropping NOFAIL means we need to handle allocation failures, which makes > the patch a bit bigger, and less of a pure fix. Hmm. If you get allocation failures for something like this at init time, I think you're basically screwed

Re: [PATCH net] 8139too:fix system hang when there is a tx timeout event.

From: Chunhao Lin Date: Thu, 28 Jul 2016 02:39:57 +0800 > If tx timeout event occur, kernel will call rtl8139_tx_timeout_task() to reset > hardware. But in this function, driver does not stop tx and rx function before > reset hardware, that will cause system hang. > > In this

Re: [PATCH net] 8139too:fix system hang when there is a tx timeout event.

From: Chunhao Lin Date: Thu, 28 Jul 2016 02:39:57 +0800 > If tx timeout event occur, kernel will call rtl8139_tx_timeout_task() to reset > hardware. But in this function, driver does not stop tx and rx function before > reset hardware, that will cause system hang. > > In this patch, add stop tx

Re: [PATCH] random: Fix crashes with sparse node ids

Linus Torvalds writes: > On Sat, Jul 30, 2016 at 7:23 AM, Michael Ellerman wrote: >> #ifdef CONFIG_NUMA >> - pool = kmalloc(num_nodes * sizeof(void *), >> + pool = kmalloc(nr_node_ids * sizeof(void *), >>

Re: [PATCH] random: Fix crashes with sparse node ids

Linus Torvalds writes: > On Sat, Jul 30, 2016 at 7:23 AM, Michael Ellerman wrote: >> #ifdef CONFIG_NUMA >> - pool = kmalloc(num_nodes * sizeof(void *), >> + pool = kmalloc(nr_node_ids * sizeof(void *), >>GFP_KERNEL|__GFP_NOFAIL|__GFP_ZERO); >>

[GIT PULL] Please pull powerpc/linux.git powerpc-4.8-1 tag

Hi Linus, Please pull powerpc updates for 4.8: The following changes since commit 5edb56491d4812c42175980759da53388e5d86f5:   Linux 4.7-rc3 are available in the git repository at:   git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git tags/powerpc-4.8-1 for you to fetch changes

[GIT PULL] Please pull powerpc/linux.git powerpc-4.8-1 tag

Hi Linus, Please pull powerpc updates for 4.8: The following changes since commit 5edb56491d4812c42175980759da53388e5d86f5:   Linux 4.7-rc3 are available in the git repository at:   git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git tags/powerpc-4.8-1 for you to fetch changes

Linux 3.18.38

I'm announcing the release of the 3.18.38 kernel. All users of the 3.18 kernel series must upgrade. The updated 3.18.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-3.18.y and can be browsed at the normal kernel.org git web browser:

Linux 4.1.29

I'm announcing the release of the 4.1.29 kernel. All users of the 4.1 kernel series must upgrade. The updated 4.1.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.1.y and can be browsed at the normal kernel.org git web browser:

Linux 3.18.38

I'm announcing the release of the 3.18.38 kernel. All users of the 3.18 kernel series must upgrade. The updated 3.18.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-3.18.y and can be browsed at the normal kernel.org git web browser:

Linux 4.1.29

I'm announcing the release of the 4.1.29 kernel. All users of the 4.1 kernel series must upgrade. The updated 4.1.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.1.y and can be browsed at the normal kernel.org git web browser:

drivers/media/v4l2-core/videobuf2-dma-contig.c:484:2: error: implicit declaration of function 'dma_get_cache_alignment'

Hi, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 7f155c702677d057d03b192ce652311de5434697 commit: e1c7e324539ada3b2b13ca2898bcb4948a9ef9db dma-mapping: always provide the dma_map_ops based implementation date:

drivers/media/v4l2-core/videobuf2-dma-contig.c:484:2: error: implicit declaration of function 'dma_get_cache_alignment'

Hi, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 7f155c702677d057d03b192ce652311de5434697 commit: e1c7e324539ada3b2b13ca2898bcb4948a9ef9db dma-mapping: always provide the dma_map_ops based implementation date:

[PATCH] net: thunderx: correct bound check in nic_config_loopback

Off by one in nic_config_loopback would access an invalid arrat variable when vf id == MAX_LMAC. Signed-off-by: Sasha Levin --- drivers/net/ethernet/cavium/thunder/nic_main.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH] net: thunderx: correct bound check in nic_config_loopback

Off by one in nic_config_loopback would access an invalid arrat variable when vf id == MAX_LMAC. Signed-off-by: Sasha Levin --- drivers/net/ethernet/cavium/thunder/nic_main.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/net/ethernet/cavium/thunder/nic_main.c

Re: [RFC PATCH 4/4] KVM: vmx: add support for emulating UMIP

2016-07-14 16:09 GMT+08:00 Paolo Bonzini : [...] > > This is not necessary because this is how KVM computes > CPUID[EAX=7,EBX=0].ECX: > > unsigned f_umip = kvm_x86_ops->umip_emulated() ? F(UMIP) : 0; > ... > const u32 kvm_cpuid_7_0_ecx_x86_features =

Re: [RFC PATCH 4/4] KVM: vmx: add support for emulating UMIP

2016-07-14 16:09 GMT+08:00 Paolo Bonzini : [...] > > This is not necessary because this is how KVM computes > CPUID[EAX=7,EBX=0].ECX: > > unsigned f_umip = kvm_x86_ops->umip_emulated() ? F(UMIP) : 0; > ... > const u32 kvm_cpuid_7_0_ecx_x86_features = F(PKU) | F(UMIP); >

Re: [PATCH v6 3/3] arm: dts: mt2701: Add auxadc node.

Hi, [auto build test ERROR on robh/for-next] [also build test ERROR on v4.7 next-20160729] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v6 3/3] arm: dts: mt2701: Add auxadc node.

Hi, [auto build test ERROR on robh/for-next] [also build test ERROR on v4.7 next-20160729] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH 1/2] Support SD UHS for hikey-mainline-rebase

Hi, [auto build test ERROR on robh/for-next] [also build test ERROR on v4.7 next-20160729] [cannot apply to ulf.hansson-mmc/next] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH 1/2] Support SD UHS for hikey-mainline-rebase

Hi, [auto build test ERROR on robh/for-next] [also build test ERROR on v4.7 next-20160729] [cannot apply to ulf.hansson-mmc/next] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

vgacon.c:undefined reference to `screen_info'

Hi, It's probably a bug fix that unveils the link errors. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: d761f3ed6e71bcca724a6e9e39efcac65b7b4ac1 commit: f69405ce6c0fc9f4a039011007371b31f80b470d openrisc: include: asm: Kbuild: add default "vga.h"

vgacon.c:undefined reference to `screen_info'

Hi, It's probably a bug fix that unveils the link errors. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: d761f3ed6e71bcca724a6e9e39efcac65b7b4ac1 commit: f69405ce6c0fc9f4a039011007371b31f80b470d openrisc: include: asm: Kbuild: add default "vga.h"

Re: [PATCH] qed: Add and use specific logging functions to reduce object size

Hi, [auto build test ERROR on net-next/master] [also build test ERROR on v4.7 next-20160729] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH] qed: Add and use specific logging functions to reduce object size

Hi, [auto build test ERROR on net-next/master] [also build test ERROR on v4.7 next-20160729] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v5] net: sched: convert qdisc linked list to hashtable

Hi, [auto build test ERROR on v4.7-rc7] [also build test ERROR on next-20160729] [cannot apply to net/master net-next/master ipsec-next/master] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v5] net: sched: convert qdisc linked list to hashtable

Hi, [auto build test ERROR on v4.7-rc7] [also build test ERROR on next-20160729] [cannot apply to net/master net-next/master ipsec-next/master] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [GIT PULL] Please pull NFS client updates for 4.8

On Sat, Jul 30, 2016 at 4:32 PM, Linus Torvalds wrote: > > Hmm. That machine is being very very slow. It's responding to pings, > but the whole "git pull" thing is not making any real progress. > > Mind giving it a look/kick, or maybe pushing to kernel.org or

Re: [GIT PULL] Please pull NFS client updates for 4.8

On Sat, Jul 30, 2016 at 4:32 PM, Linus Torvalds wrote: > > Hmm. That machine is being very very slow. It's responding to pings, > but the whole "git pull" thing is not making any real progress. > > Mind giving it a look/kick, or maybe pushing to kernel.org or something? Ahh, it's ok now. Pulled.

Re: [GIT PULL] Please pull NFS client updates for 4.8

On Sat, Jul 30, 2016 at 3:36 PM, Trond Myklebust wrote: > > git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-4.8-1 Hmm. That machine is being very very slow. It's responding to pings, but the whole "git pull" thing is not making any real progress.

Re: [GIT PULL] Please pull NFS client updates for 4.8

On Sat, Jul 30, 2016 at 3:36 PM, Trond Myklebust wrote: > > git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-4.8-1 Hmm. That machine is being very very slow. It's responding to pings, but the whole "git pull" thing is not making any real progress. Mind giving it a

[PATCH 3/5] usb: ulpi: remove "dev" field from struct ulpi_ops

Operations now use ulpi->dev.parent directly instead of via the ulpi_ops struct, making this field unused. Remove it. Signed-off-by: Tal Shorer --- drivers/usb/common/ulpi.c | 1 - include/linux/ulpi/interface.h | 2 +- 2 files changed, 1 insertion(+), 2 deletions(-)

[PATCH 5/5] usb: dwc3: ulpi: make dwc3_ulpi_ops constant

ulpi_register_interface() accepts a const struct ulpi_ops and dwc3 doesn't perform any changes to this struct at runtime, so there's no reason it shouldn't be constant. Signed-off-by: Tal Shorer --- drivers/usb/dwc3/ulpi.c | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH 4/5] usb: ulpi: make ops struct constant

None of the core ulpi functions perform any changes to the operations struct, and logically as a struct that contains function pointers there's no reason it shouldn't be constant. Signed-off-by: Tal Shorer --- drivers/usb/common/ulpi.c | 3 ++-

[PATCH 3/5] usb: ulpi: remove "dev" field from struct ulpi_ops

Operations now use ulpi->dev.parent directly instead of via the ulpi_ops struct, making this field unused. Remove it. Signed-off-by: Tal Shorer --- drivers/usb/common/ulpi.c | 1 - include/linux/ulpi/interface.h | 2 +- 2 files changed, 1 insertion(+), 2 deletions(-) diff --git

[PATCH 5/5] usb: dwc3: ulpi: make dwc3_ulpi_ops constant

ulpi_register_interface() accepts a const struct ulpi_ops and dwc3 doesn't perform any changes to this struct at runtime, so there's no reason it shouldn't be constant. Signed-off-by: Tal Shorer --- drivers/usb/dwc3/ulpi.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 4/5] usb: ulpi: make ops struct constant

None of the core ulpi functions perform any changes to the operations struct, and logically as a struct that contains function pointers there's no reason it shouldn't be constant. Signed-off-by: Tal Shorer --- drivers/usb/common/ulpi.c | 3 ++- include/linux/ulpi/driver.h| 2 +-

[PATCH 1/5] usb: ulpi: move setting of ulpi->dev parent up in ulpi_register()

Once ulpi operations use the parent device directly, this will be needed during the operations used in ulpi_register() itself, so set the parent field before calling any ulpi operations. Signed-off-by: Tal Shorer --- drivers/usb/common/ulpi.c | 3 ++- 1 file changed, 2

[PATCH 1/5] usb: ulpi: move setting of ulpi->dev parent up in ulpi_register()

Once ulpi operations use the parent device directly, this will be needed during the operations used in ulpi_register() itself, so set the parent field before calling any ulpi operations. Signed-off-by: Tal Shorer --- drivers/usb/common/ulpi.c | 3 ++- 1 file changed, 2 insertions(+), 1

[PATCH 2/5] usb: ulpi: change operations api to pass parent device directly

struct ulpi_ops is defined as follows: struct ulpi_ops { struct device *dev; int (*read)(struct ulpi_ops *ops, u8 addr); int (*write)(struct ulpi_ops *ops, u8 addr, u8 val); }; Upon calling ulpi_register_interface(), the struct device argument is put inside the struct

[PATCH 0/5] usb: ulpi: remove "dev" field from struct ulpi_ops

struct ulpi_ops is defined as follows: struct ulpi_ops { struct device *dev; int (*read)(struct ulpi_ops *ops, u8 addr); int (*write)(struct ulpi_ops *ops, u8 addr, u8 val); }; Upon calling ulpi_register_interface(), the struct device argument is put inside the struct

[PATCH 2/5] usb: ulpi: change operations api to pass parent device directly

struct ulpi_ops is defined as follows: struct ulpi_ops { struct device *dev; int (*read)(struct ulpi_ops *ops, u8 addr); int (*write)(struct ulpi_ops *ops, u8 addr, u8 val); }; Upon calling ulpi_register_interface(), the struct device argument is put inside the struct

[PATCH 0/5] usb: ulpi: remove "dev" field from struct ulpi_ops

struct ulpi_ops is defined as follows: struct ulpi_ops { struct device *dev; int (*read)(struct ulpi_ops *ops, u8 addr); int (*write)(struct ulpi_ops *ops, u8 addr, u8 val); }; Upon calling ulpi_register_interface(), the struct device argument is put inside the struct

STRICTLY CONFIDENTIAL .

I have important transaction for you as next of kin to claim US$8.37m Mail me on my private email: chi...@yahoo.com so i can send you more details Thanks Mr.Chim Wai Kim === DISCLAIMER: This email and any

STRICTLY CONFIDENTIAL .

I have important transaction for you as next of kin to claim US$8.37m Mail me on my private email: chi...@yahoo.com so i can send you more details Thanks Mr.Chim Wai Kim === DISCLAIMER: This email and any

[GIT PULL] Please pull NFS client updates for 4.8

Hi Linus, The following changes since commit 92d21ac74a9e3c09b0b01c764e530657e4c85c49: Linux 4.7-rc7 (2016-07-10 20:24:59 -0700) are available in the git repository at: git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-4.8-1 for you to fetch changes up to

[GIT PULL] Please pull NFS client updates for 4.8

Hi Linus, The following changes since commit 92d21ac74a9e3c09b0b01c764e530657e4c85c49: Linux 4.7-rc7 (2016-07-10 20:24:59 -0700) are available in the git repository at: git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-4.8-1 for you to fetch changes up to

Re: [PATCH] Networking: Core: netpoll: Fixed a missing spin_unlock

Salil Kapur : [...] > diff --git a/net/core/netpoll.c b/net/core/netpoll.c > index fc75c9e..9124f76 100644 > --- a/net/core/netpoll.c > +++ b/net/core/netpoll.c > @@ -386,8 +386,10 @@ void netpoll_send_skb_on_dev(struct netpoll *np, struct > sk_buff *skb, >

Re: [PATCH] Networking: Core: netpoll: Fixed a missing spin_unlock

Salil Kapur : [...] > diff --git a/net/core/netpoll.c b/net/core/netpoll.c > index fc75c9e..9124f76 100644 > --- a/net/core/netpoll.c > +++ b/net/core/netpoll.c > @@ -386,8 +386,10 @@ void netpoll_send_skb_on_dev(struct netpoll *np, struct > sk_buff *skb, >

Fixup direct bi_rw modifiers

bi_rw should be using bio_set_op_attrs to set bi_rw. Signed-off-by: Shaun Tancheff Cc: Chris Mason Cc: Josef Bacik Cc: David Sterba Cc: Mike Christie --- Patch is against linux-next tag next-20160729

Fixup direct bi_rw modifiers

bi_rw should be using bio_set_op_attrs to set bi_rw. Signed-off-by: Shaun Tancheff Cc: Chris Mason Cc: Josef Bacik Cc: David Sterba Cc: Mike Christie --- Patch is against linux-next tag next-20160729 NOTE: In 4.7 this was not including the 'WRITE' macro so may have it may not have

Hang in 9p/virtio

Hi, With fault injection triggering an allocation failure for the alloc_indirect() call in virtqueue_add() I'm seeing a hang in p9_virtio_zc_request() -- it seems to be waiting here indefinitely (i.e. at least 120 seconds): err = wait_event_interruptible(*req->wq,

Hang in 9p/virtio

Hi, With fault injection triggering an allocation failure for the alloc_indirect() call in virtqueue_add() I'm seeing a hang in p9_virtio_zc_request() -- it seems to be waiting here indefinitely (i.e. at least 120 seconds): err = wait_event_interruptible(*req->wq,

①Hi

hi this is an electronics shop bike,brand guitar,camera,tv,samsung product free shipping www .slooone .com if you do not want receive our email. please reply to us, we will never send email to you

①Hi

hi this is an electronics shop bike,brand guitar,camera,tv,samsung product free shipping www .slooone .com if you do not want receive our email. please reply to us, we will never send email to you

Re: [PATCH] raid5: fix incorrectly counter of conf->empty_inactive_list_nr

On Thu, Jul 28, 2016 at 02:22:14PM +0800, ZhengYuan Liu wrote: > The counter conf->empty_inactive_list_nr is only used for determine if the > raid5 is congested which is deal with in function raid5_congested(). > It was increased in get_free_stripe() when conf->inactive_list got to be > empty and

Re: [PATCH] raid5: fix incorrectly counter of conf->empty_inactive_list_nr

On Thu, Jul 28, 2016 at 02:22:14PM +0800, ZhengYuan Liu wrote: > The counter conf->empty_inactive_list_nr is only used for determine if the > raid5 is congested which is deal with in function raid5_congested(). > It was increased in get_free_stripe() when conf->inactive_list got to be > empty and

Re: [PATCH] prctl: remove one-shot limitation for changing exe link

On Sat, Jul 30, 2016 at 12:31:40PM -0500, Eric W. Biederman wrote: > So what I am requesting is very simple. That the checks in > prctl_set_mm_exe_file be tightened up to more closely approach what > execve requires. Thus preserving the value of the /proc/[pid]/exe for > the applications that

Re: [PATCH] prctl: remove one-shot limitation for changing exe link

On Sat, Jul 30, 2016 at 12:31:40PM -0500, Eric W. Biederman wrote: > So what I am requesting is very simple. That the checks in > prctl_set_mm_exe_file be tightened up to more closely approach what > execve requires. Thus preserving the value of the /proc/[pid]/exe for > the applications that

Re: [PATCH] random: Fix crashes with sparse node ids

On Sat, Jul 30, 2016 at 7:23 AM, Michael Ellerman wrote: > #ifdef CONFIG_NUMA > - pool = kmalloc(num_nodes * sizeof(void *), > + pool = kmalloc(nr_node_ids * sizeof(void *), >GFP_KERNEL|__GFP_NOFAIL|__GFP_ZERO); >

Re: [PATCH] random: Fix crashes with sparse node ids

On Sat, Jul 30, 2016 at 7:23 AM, Michael Ellerman wrote: > #ifdef CONFIG_NUMA > - pool = kmalloc(num_nodes * sizeof(void *), > + pool = kmalloc(nr_node_ids * sizeof(void *), >GFP_KERNEL|__GFP_NOFAIL|__GFP_ZERO); > for_each_online_node(i) { >

Re: Why do we need reset_control_get_optional() ?

On Friday, July 29, 2016 3:08:15 PM CEST Philipp Zabel wrote: > Hi Masahiro, > > Am Donnerstag, den 28.07.2016, 19:29 +0900 schrieb Masahiro Yamada: > [...] > > However, I think the following makes more sense: > > > > > > menuconfig RESET_CONTROLLER > > bool "Reset Controller Support" >

Re: Why do we need reset_control_get_optional() ?

On Friday, July 29, 2016 3:08:15 PM CEST Philipp Zabel wrote: > Hi Masahiro, > > Am Donnerstag, den 28.07.2016, 19:29 +0900 schrieb Masahiro Yamada: > [...] > > However, I think the following makes more sense: > > > > > > menuconfig RESET_CONTROLLER > > bool "Reset Controller Support" >

Re: [PATCH] KEYS: Sort out big_key initialisation

On Sat, 2016-07-30 at 22:03 +0200, Kirill Marinushkin wrote: > big_key has two separate initialisation functions, one that registers the > key type and one that registers the crypto.  If the key type fails to > register, there's no problem if the crypto registers successfully because > there's no

Re: [PATCH] KEYS: Sort out big_key initialisation

On Sat, 2016-07-30 at 22:03 +0200, Kirill Marinushkin wrote: > big_key has two separate initialisation functions, one that registers the > key type and one that registers the crypto.  If the key type fails to > register, there's no problem if the crypto registers successfully because > there's no

[PATCH 34/34] Staging: comedi: drivers: cd_pcidas: Compression of

This patch compresses two lines in to a single line in file cb_pcidas.c if immediate return statement is found. It also removes variable bytes_written as it is no longer needed. It is done using script Coccinelle. And coccinelle uses following semantic patch for this compression function: @@

[PATCH 34/34] Staging: comedi: drivers: cd_pcidas: Compression of

This patch compresses two lines in to a single line in file cb_pcidas.c if immediate return statement is found. It also removes variable bytes_written as it is no longer needed. It is done using script Coccinelle. And coccinelle uses following semantic patch for this compression function: @@

[PATCH] KEYS: Sort out big_key initialisation

big_key has two separate initialisation functions, one that registers the key type and one that registers the crypto. If the key type fails to register, there's no problem if the crypto registers successfully because there's no way to reach the crypto except through the key type. However, if the

[PATCH] KEYS: Sort out big_key initialisation

big_key has two separate initialisation functions, one that registers the key type and one that registers the crypto. If the key type fails to register, there's no problem if the crypto registers successfully because there's no way to reach the crypto except through the key type. However, if the

Re: [GIT pull] x86 core changes for 4.8

On Sat, Jul 30, 2016 at 12:44 PM, Linus Torvalds wrote: > > For example, when I pull, the diffstat is just > > 10 files changed, 81 insertions(+), 65 deletions(-) > > instead of the claimed > >> 19 files changed, 183 insertions(+), 161 deletions(-) > > and I am

Re: [GIT pull] x86 core changes for 4.8

On Sat, Jul 30, 2016 at 12:44 PM, Linus Torvalds wrote: > > For example, when I pull, the diffstat is just > > 10 files changed, 81 insertions(+), 65 deletions(-) > > instead of the claimed > >> 19 files changed, 183 insertions(+), 161 deletions(-) > > and I am missing all these commits [...]

Re: [GIT pull] x86 core changes for 4.8

On Sat, Jul 30, 2016 at 3:17 AM, Thomas Gleixner wrote: > > please pull the latest x86-cpu-for-linus git tree from: > >git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-cpu-for-linus I don't actually get what you claim I should get. For example, when I pull,

Re: [GIT pull] x86 core changes for 4.8

On Sat, Jul 30, 2016 at 3:17 AM, Thomas Gleixner wrote: > > please pull the latest x86-cpu-for-linus git tree from: > >git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-cpu-for-linus I don't actually get what you claim I should get. For example, when I pull, the diffstat is just

[PATCH] staging: vt6656: Fix block comment style

This patch fixes the checkpatch.pl warnings: WARNING: Block comments use * on subsequent lines WARNING: Block comments use a trailing */ on a separate line Signed-off-by: Edward Lipinsky --- drivers/staging/vt6656/card.c | 7 +-- 1 file changed, 5 insertions(+), 2

[PATCH] staging: vt6656: Fix block comment style

This patch fixes the checkpatch.pl warnings: WARNING: Block comments use * on subsequent lines WARNING: Block comments use a trailing */ on a separate line Signed-off-by: Edward Lipinsky --- drivers/staging/vt6656/card.c | 7 +-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git

sfi_core warnings - and a pointer arithmetic bug

Len, right now my tree finally contains only a couple of remaining warnings, thanks to some objtool fixes and previous warning removal. The two remaining warnings are both from SFI: drivers/sfi/sfi_core.c: In function ‘sfi_map_table’: drivers/sfi/sfi_core.c:175:53: warning: self-comparison

sfi_core warnings - and a pointer arithmetic bug

Len, right now my tree finally contains only a couple of remaining warnings, thanks to some objtool fixes and previous warning removal. The two remaining warnings are both from SFI: drivers/sfi/sfi_core.c: In function ‘sfi_map_table’: drivers/sfi/sfi_core.c:175:53: warning: self-comparison

true love

Greetings, I've just came across that stuff on the web and completely fell in love with it! You've got to see that! Here is the link See you around, Pavel Machek

true love

Greetings, I've just came across that stuff on the web and completely fell in love with it! You've got to see that! Here is the link See you around, Pavel Machek

Re: [PATCH v3 2/3] spi: of: allow instantiating slaves without a driver

On 19 July 2016 at 12:52, Mark Brown wrote: > On Tue, Jul 19, 2016 at 10:31:54AM +0200, Michal Suchanek wrote: >> On 19 July 2016 at 01:02, Mark Brown wrote: >> > On Tue, Jul 19, 2016 at 12:35:41AM +0200, Michal Suchanek wrote: > >> >> SPI slave devices

Re: [PATCH v3 2/3] spi: of: allow instantiating slaves without a driver

On 19 July 2016 at 12:52, Mark Brown wrote: > On Tue, Jul 19, 2016 at 10:31:54AM +0200, Michal Suchanek wrote: >> On 19 July 2016 at 01:02, Mark Brown wrote: >> > On Tue, Jul 19, 2016 at 12:35:41AM +0200, Michal Suchanek wrote: > >> >> SPI slave devices are not created when looking up driver for

Re: [PATCH] prctl: remove one-shot limitation for changing exe link

Cyrill Gorcunov writes: > On Mon, Jul 25, 2016 at 02:56:43PM -0500, Eric W. Biederman wrote: > ... >> >> >> >> Also there is a big fat bug in prctl_set_mm_exe_file. It doesn't >> >> validate that the new file is a actually mmaped executable. We would >> >> definitely need

Re: [PATCH] prctl: remove one-shot limitation for changing exe link

Cyrill Gorcunov writes: > On Mon, Jul 25, 2016 at 02:56:43PM -0500, Eric W. Biederman wrote: > ... >> >> >> >> Also there is a big fat bug in prctl_set_mm_exe_file. It doesn't >> >> validate that the new file is a actually mmaped executable. We would >> >> definitely need that to be fixed

Re: [PATCH 0/3] new feature: monitoring page cache events

On Fri, Jul 29, 2016 at 08:33:34AM -0700, Dave Hansen wrote: > What's to stop you from using tracing to gather and transport data out > of the kernel and then aggregate and present it to apps in an "elegant" > way of your choosing? > > I don't think it's really even worth having an in-depth

Re: [PATCH 0/3] new feature: monitoring page cache events

On Fri, Jul 29, 2016 at 08:33:34AM -0700, Dave Hansen wrote: > What's to stop you from using tracing to gather and transport data out > of the kernel and then aggregate and present it to apps in an "elegant" > way of your choosing? > > I don't think it's really even worth having an in-depth

means a lot to me

Hey, Please read this info, it means so much to me, here is the link Typos courtesy of my iPhone, Tim Chen

Re: [PATCH v3 00/13] sunxi spi fixes

On 29 July 2016 at 22:22, Maxime Ripard wrote: > On Mon, Jul 25, 2016 at 10:03:14AM +0200, Michal Suchanek wrote: >> Hello, >> >> On 25 July 2016 at 09:32, Maxime Ripard >> wrote: >> > On Fri, Jun 17, 2016 at 12:34:44PM +0200,

means a lot to me

Hey, Please read this info, it means so much to me, here is the link Typos courtesy of my iPhone, Tim Chen

Re: [PATCH v3 00/13] sunxi spi fixes

On 29 July 2016 at 22:22, Maxime Ripard wrote: > On Mon, Jul 25, 2016 at 10:03:14AM +0200, Michal Suchanek wrote: >> Hello, >> >> On 25 July 2016 at 09:32, Maxime Ripard >> wrote: >> > On Fri, Jun 17, 2016 at 12:34:44PM +0200, Michal Suchanek wrote: >> >> Hello, >> >> >> >> On 13 June 2016 at

Re: [PATCH] KEYS: Sort out big_key initialisation

On Sat, Jul 30, 2016 at 06:21:41PM +0200, Kirill Marinushkin wrote: > big_key has two separate initialisation functions, one that registers the > key type and one that registers the crypto. If the key type fails to > register, there's no problem if the crypto registers successfully because >

Re: [PATCH] KEYS: Sort out big_key initialisation

On Sat, Jul 30, 2016 at 06:21:41PM +0200, Kirill Marinushkin wrote: > big_key has two separate initialisation functions, one that registers the > key type and one that registers the crypto. If the key type fails to > register, there's no problem if the crypto registers successfully because >

  1   2   3   >