[PATCH v3 1/5] perf/core: add PERF_RECORD_SAMPLE_SKID_IP record type

This patchs adds a new sample record type. The goal is to record the interrupted instruction pointer (IP) as seen by the kernel and reflected in the machine state (pt_regs). On some architectures, it is possible to avoid the IP skid using hardware support. For instance, on Intel x86, the use of

[PATCH v3 1/5] perf/core: add PERF_RECORD_SAMPLE_SKID_IP record type

This patchs adds a new sample record type. The goal is to record the interrupted instruction pointer (IP) as seen by the kernel and reflected in the machine state (pt_regs). On some architectures, it is possible to avoid the IP skid using hardware support. For instance, on Intel x86, the use of

[PATCH v3 2/5] perf/x86: add PERF_SAMPLE_SKID_IP support for X86 PEBS

This patch adds support for SKID_IP for Intel x86 processors when PEBS mode is enabled. Signed-off-by: Stephane Eranian --- arch/x86/events/intel/ds.c | 7 +++ 1 file changed, 7 insertions(+) diff --git a/arch/x86/events/intel/ds.c b/arch/x86/events/intel/ds.c index

[PATCH v3 2/5] perf/x86: add PERF_SAMPLE_SKID_IP support for X86 PEBS

This patch adds support for SKID_IP for Intel x86 processors when PEBS mode is enabled. Signed-off-by: Stephane Eranian --- arch/x86/events/intel/ds.c | 7 +++ 1 file changed, 7 insertions(+) diff --git a/arch/x86/events/intel/ds.c b/arch/x86/events/intel/ds.c index

[PATCH v5 2/2] KVM: MMU: consider host cache mode in MMIO page check

Some reserved pages, such as those from NVDIMM DAX devices, are not for MMIO, and can be mapped with cached memory type for better performance. However, the above check misconceives those pages as MMIO. Because KVM maps MMIO pages with UC memory type, the performance of guest accesses to those

[PATCH v5 2/2] KVM: MMU: consider host cache mode in MMIO page check

Some reserved pages, such as those from NVDIMM DAX devices, are not for MMIO, and can be mapped with cached memory type for better performance. However, the above check misconceives those pages as MMIO. Because KVM maps MMIO pages with UC memory type, the performance of guest accesses to those

[PATCH v3 3/5] perf/tools: add support for PERF_SAMPLE_SKID_IP

This patch adds the support code to handle the PERF_SAMPLE_SKID_IP record type. This is done as an event term and as such can be enabled per event: cpu/event=xxx,skid-ip=1/. This is a boolean term which is false by default. Signed-off-by: Stephane Eranian ---

[PATCH v3 3/5] perf/tools: add support for PERF_SAMPLE_SKID_IP

This patch adds the support code to handle the PERF_SAMPLE_SKID_IP record type. This is done as an event term and as such can be enabled per event: cpu/event=xxx,skid-ip=1/. This is a boolean term which is false by default. Signed-off-by: Stephane Eranian ---

[PATCH v3 4/5] perf/record: add documentation for sampling skid ip

This patch adds documentation to describe how to use the skid ip support with perf record. The sample type can be provided per event as follows: pmu_instance/...,skid-ip=1/ For instance on Intel X86: $ perf record -e cpu/event=0xc5,skid-ip=1/pp does record the precise address of retired

[PATCH v5 1/2] x86/mm: add a function to check if a pfn is UC/UC-

It will be used by KVM to check whether a pfn should be mapped to guest as UC. Signed-off-by: Haozhong Zhang --- arch/x86/include/asm/pat.h | 2 ++ arch/x86/mm/pat.c | 16 2 files changed, 18 insertions(+) diff --git

[PATCH v3 4/5] perf/record: add documentation for sampling skid ip

This patch adds documentation to describe how to use the skid ip support with perf record. The sample type can be provided per event as follows: pmu_instance/...,skid-ip=1/ For instance on Intel X86: $ perf record -e cpu/event=0xc5,skid-ip=1/pp does record the precise address of retired

[PATCH v5 1/2] x86/mm: add a function to check if a pfn is UC/UC-

It will be used by KVM to check whether a pfn should be mapped to guest as UC. Signed-off-by: Haozhong Zhang --- arch/x86/include/asm/pat.h | 2 ++ arch/x86/mm/pat.c | 16 2 files changed, 18 insertions(+) diff --git a/arch/x86/include/asm/pat.h

[PATCH v3 5/5] perf/script: add support for skid ip

This patch adds a skid_ip field to perf script to dump the raw value of the PERF_SAMPLE_SKID_IP field in each sample. $ perf script -F +ip,+skid_ip .. The field is not enabled by default. Signed-off-by: Stephane Eranian --- tools/perf/Documentation/perf-script.txt | 2

[PATCH v3 5/5] perf/script: add support for skid ip

This patch adds a skid_ip field to perf script to dump the raw value of the PERF_SAMPLE_SKID_IP field in each sample. $ perf script -F +ip,+skid_ip .. The field is not enabled by default. Signed-off-by: Stephane Eranian --- tools/perf/Documentation/perf-script.txt | 2 +-

[PATCH v5 0/2] KVM: MMU: fix kvm_is_mmio_pfn()

Some reserved pages, such as those from NVDIMM DAX devices, are not for MMIO, and can be mapped with cached memory type for better performance. However, the above check misconceives those pages as MMIO. Because KVM maps MMIO pages with UC memory type, the performance of guest accesses to those

[PATCH v3 0/5] perf: add support for capturing skid IP

This patchs adds a new sample record type called PERF_SAMPLE_SKID_IP. The goal is to record the unmodified interrupted instruction pointer (IP) as seen by the kernel and reflected in the machine state. On some architectures, it is possible to avoid the IP skid using hardware support. For

[PATCH v5 0/2] KVM: MMU: fix kvm_is_mmio_pfn()

Some reserved pages, such as those from NVDIMM DAX devices, are not for MMIO, and can be mapped with cached memory type for better performance. However, the above check misconceives those pages as MMIO. Because KVM maps MMIO pages with UC memory type, the performance of guest accesses to those

[PATCH v3 0/5] perf: add support for capturing skid IP

This patchs adds a new sample record type called PERF_SAMPLE_SKID_IP. The goal is to record the unmodified interrupted instruction pointer (IP) as seen by the kernel and reflected in the machine state. On some architectures, it is possible to avoid the IP skid using hardware support. For

Re: [PATCH] selftests: futex: fix compilation error

On 2017年11月08日 06:57, Shuah Khan wrote: On 11/06/2017 06:18 PM, lei yang wrote: On 2017年11月07日 07:48, Shuah Khan wrote: On 11/06/2017 04:45 PM, Shuah Khan wrote: On 11/05/2017 09:03 PM, Lei Yang wrote: I run into below error when building futext /bin/sh: -c: line 5: syntax error:

Re: [PATCH] selftests: futex: fix compilation error

On 2017年11月08日 06:57, Shuah Khan wrote: On 11/06/2017 06:18 PM, lei yang wrote: On 2017年11月07日 07:48, Shuah Khan wrote: On 11/06/2017 04:45 PM, Shuah Khan wrote: On 11/05/2017 09:03 PM, Lei Yang wrote: I run into below error when building futext /bin/sh: -c: line 5: syntax error:

Re: [PATCH] mm: page_ext: check if page_ext is not prepared

On Tue, Nov 07, 2017 at 10:47:30AM +0100, Michal Hocko wrote: > [CC Joonsoo] > > On Tue 07-11-17 18:41:31, Jaewon Kim wrote: > > online_page_ext and page_ext_init allocate page_ext for each section, but > > they do not allocate if the first PFN is !pfn_present(pfn) or > > !pfn_valid(pfn). Then

Re: [PATCH] mm: page_ext: check if page_ext is not prepared

On Tue, Nov 07, 2017 at 10:47:30AM +0100, Michal Hocko wrote: > [CC Joonsoo] > > On Tue 07-11-17 18:41:31, Jaewon Kim wrote: > > online_page_ext and page_ext_init allocate page_ext for each section, but > > they do not allocate if the first PFN is !pfn_present(pfn) or > > !pfn_valid(pfn). Then

Re: [PATCH v5 0/9] mtd: sharpslpart partition parser

On Sun, 08 Oct 2017 11:53:11 +0200 Robert Jarzmik wrote: > Robert Jarzmik writes: > > > Boris Brezillon writes: > > > >> Hi Robert, > >> Wait a bit before applying. I think patches 6 to 9 have a dependency

Re: [PATCH v5 0/9] mtd: sharpslpart partition parser

On Sun, 08 Oct 2017 11:53:11 +0200 Robert Jarzmik wrote: > Robert Jarzmik writes: > > > Boris Brezillon writes: > > > >> Hi Robert, > >> Wait a bit before applying. I think patches 6 to 9 have a dependency on > >> patch 1 (it's not a build dependency, but NAND partitioning might be > >>

Re: [PATCH v2 2/3] drivers: phy: broadcom: Add driver for Cygnus USB phy controller

Hi, Adding Chanwoo Choi to review extcon API's. -Raveendra On Wed, Nov 8, 2017 at 1:16 PM, Raveendra Padasalagi wrote: > Add driver for Broadcom's USB phy controller's used in Cygnus > familyof SoC. Cygnus has three USB phy controller's, port 0, > port 1

Re: [PATCH v2 2/3] drivers: phy: broadcom: Add driver for Cygnus USB phy controller

Hi, Adding Chanwoo Choi to review extcon API's. -Raveendra On Wed, Nov 8, 2017 at 1:16 PM, Raveendra Padasalagi wrote: > Add driver for Broadcom's USB phy controller's used in Cygnus > familyof SoC. Cygnus has three USB phy controller's, port 0, > port 1 provides USB host functionality and port

Re: [PATCH 1/2] ARM: sun8i: a83t: add dwmac-sun8i ethernet driver

On Wed, Nov 08, 2017 at 02:27:21PM +0800, Chen-Yu Tsai wrote: > On Wed, Nov 8, 2017 at 4:13 AM, Corentin Labbe > wrote: > > The dwmac-sun8i is an ethernet MAC hardware that support 10/100/1000 speed. > > This patch enable the dwmac-sun8i on the Allwinner a83t SoC

Re: [PATCH 1/2] ARM: sun8i: a83t: add dwmac-sun8i ethernet driver

On Wed, Nov 08, 2017 at 02:27:21PM +0800, Chen-Yu Tsai wrote: > On Wed, Nov 8, 2017 at 4:13 AM, Corentin Labbe > wrote: > > The dwmac-sun8i is an ethernet MAC hardware that support 10/100/1000 speed. > > This patch enable the dwmac-sun8i on the Allwinner a83t SoC Device-tree. > > The subject

Re: [PATCH] mm: page_ext: allocate page extension though first PFN is invalid

On Tue, Nov 07, 2017 at 06:44:47PM +0900, Jaewon Kim wrote: > online_page_ext and page_ext_init allocate page_ext for each section, but > they do not allocate if the first PFN is !pfn_present(pfn) or > !pfn_valid(pfn). > > Though the first page is not valid, page_ext could be useful for other >

Re: [PATCH] mm: page_ext: allocate page extension though first PFN is invalid

On Tue, Nov 07, 2017 at 06:44:47PM +0900, Jaewon Kim wrote: > online_page_ext and page_ext_init allocate page_ext for each section, but > they do not allocate if the first PFN is !pfn_present(pfn) or > !pfn_valid(pfn). > > Though the first page is not valid, page_ext could be useful for other >

[PATCH v2 0/3] Add driver for Broadcom Cygnus USB phy controller

Add driver for Broadcom's USB phy controller's used in Cygnus family of SoC and it's based on 4.14-rc3 tag. The patch set can be fetched from iproc-cyg-usb-v2 branch of https://github.com/Broadcom/arm64-linux.git Changes since v1: - Added "dt-bindings: phy:" subject prefix in dt bindings patch

[PATCH v2 1/3] dt-bindings: phy: Add Cygnus usb phy binding

Add devicetree binding document for broadcom's Cygnus SoC specific usb phy controller driver. Signed-off-by: Raveendra Padasalagi --- .../bindings/phy/brcm,cygnus-usb-phy.txt | 106 + 1 file changed, 106 insertions(+) create mode

[PATCH v2 0/3] Add driver for Broadcom Cygnus USB phy controller

Add driver for Broadcom's USB phy controller's used in Cygnus family of SoC and it's based on 4.14-rc3 tag. The patch set can be fetched from iproc-cyg-usb-v2 branch of https://github.com/Broadcom/arm64-linux.git Changes since v1: - Added "dt-bindings: phy:" subject prefix in dt bindings patch

[PATCH v2 1/3] dt-bindings: phy: Add Cygnus usb phy binding

Add devicetree binding document for broadcom's Cygnus SoC specific usb phy controller driver. Signed-off-by: Raveendra Padasalagi --- .../bindings/phy/brcm,cygnus-usb-phy.txt | 106 + 1 file changed, 106 insertions(+) create mode 100644

[PATCH v2 2/3] drivers: phy: broadcom: Add driver for Cygnus USB phy controller

Add driver for Broadcom's USB phy controller's used in Cygnus familyof SoC. Cygnus has three USB phy controller's, port 0, port 1 provides USB host functionality and port 2 can be configured for host/device role. Configuration of host/device role for port 2 is achieved based on the extcon events,

[PATCH v2 2/3] drivers: phy: broadcom: Add driver for Cygnus USB phy controller

Add driver for Broadcom's USB phy controller's used in Cygnus familyof SoC. Cygnus has three USB phy controller's, port 0, port 1 provides USB host functionality and port 2 can be configured for host/device role. Configuration of host/device role for port 2 is achieved based on the extcon events,

[PATCH v2 3/3] ARM: dts: Add dt node for Broadcom Cygnus USB phy

Add DT node for Broadcom's USB phy controller's used in Cygnus family of SoC. Signed-off-by: Raveendra Padasalagi --- arch/arm/boot/dts/bcm-cygnus.dtsi | 35 +++ 1 file changed, 35 insertions(+) diff --git

[PATCH v2 3/3] ARM: dts: Add dt node for Broadcom Cygnus USB phy

Add DT node for Broadcom's USB phy controller's used in Cygnus family of SoC. Signed-off-by: Raveendra Padasalagi --- arch/arm/boot/dts/bcm-cygnus.dtsi | 35 +++ 1 file changed, 35 insertions(+) diff --git a/arch/arm/boot/dts/bcm-cygnus.dtsi

Re: [PATCH] arm64: dts: msm8916: Add missing #phy-cells

On 11/08/2017 09:15 AM, Bjorn Andersson wrote: Add a missing #phy-cells to the dsi-phy, to silence dtc warning. Reviewed-by: Archit Taneja Thanks, Archit Cc: Archit Taneja Fixes: 305410ffd1b2 ("arm64: dts: msm8916: Add display support")

Re: [PATCH] arm64: dts: msm8916: Add missing #phy-cells

On 11/08/2017 09:15 AM, Bjorn Andersson wrote: Add a missing #phy-cells to the dsi-phy, to silence dtc warning. Reviewed-by: Archit Taneja Thanks, Archit Cc: Archit Taneja Fixes: 305410ffd1b2 ("arm64: dts: msm8916: Add display support") Signed-off-by: Bjorn Andersson ---

Re: [PATCH] mm, vmstat: Make sure mutex is a global static

INFO: trying to register non-static key. > [ 63.259113] the code is fine but needs lockdep annotation. > [ 63.259596] turning off the locking correctness validator. > [ 63.260073] CPU: 1 PID: 4102 Comm: perl Not tainted > 4.14.0-rc8-next-20171107+ #419 > [ 63.260769] Hardware nam

Re: [PATCH] mm, vmstat: Make sure mutex is a global static

INFO: trying to register non-static key. > [ 63.259113] the code is fine but needs lockdep annotation. > [ 63.259596] turning off the locking correctness validator. > [ 63.260073] CPU: 1 PID: 4102 Comm: perl Not tainted > 4.14.0-rc8-next-20171107+ #419 > [ 63.260769] Hardware nam

Re: n900 in next-20170901

On Tue, Nov 07, 2017 at 07:48:42AM -0800, Tony Lindgren wrote: > Hi, > > * Joonsoo Kim [171107 05:30]: > > Could you test follwing updated branch? > > > > https://github.com/JoonsooKim/linux/tree/cma-debug4-next-20180901 > > > > It has three relevant commits on top and

Re: n900 in next-20170901

On Tue, Nov 07, 2017 at 07:48:42AM -0800, Tony Lindgren wrote: > Hi, > > * Joonsoo Kim [171107 05:30]: > > Could you test follwing updated branch? > > > > https://github.com/JoonsooKim/linux/tree/cma-debug4-next-20180901 > > > > It has three relevant commits on top and enables CMA memory use.

Re: Documenting sigaltstack SS_AUTODISRM

Hello Stas, On 6 November 2017 at 23:28, Stas Sergeev wrote: > 07.11.2017 01:26, Michael Kerrisk (man-pages) пишет: >> >> Hello Stas, >> >> Ping on the below? > > Hi, the change with the "not recommended" warning > looks good to me. > Acked-by: Stas Sergeev Thanks.

Re: Documenting sigaltstack SS_AUTODISRM

Hello Stas, On 6 November 2017 at 23:28, Stas Sergeev wrote: > 07.11.2017 01:26, Michael Kerrisk (man-pages) пишет: >> >> Hello Stas, >> >> Ping on the below? > > Hi, the change with the "not recommended" warning > looks good to me. > Acked-by: Stas Sergeev Thanks. I've pushed these changes

Re: [PATCH v2] locking/pvqspinlock: Hybrid PV queued/unfair locks

On 07/11/17 22:18, Waiman Long wrote: > Currently, all the lock waiters entering the slowpath will do one > lock stealing attempt to acquire the lock. That helps performance, > especially in VMs with over-committed vCPUs. However, the current > pvqspinlocks still don't perform as good as unfair

Re: [PATCH v2] locking/pvqspinlock: Hybrid PV queued/unfair locks

On 07/11/17 22:18, Waiman Long wrote: > Currently, all the lock waiters entering the slowpath will do one > lock stealing attempt to acquire the lock. That helps performance, > especially in VMs with over-committed vCPUs. However, the current > pvqspinlocks still don't perform as good as unfair

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

ir original relative > > locations") > > > > If it matters, this is a cross compilation (PowerPC host) using O= . > > > > I have used the tip tree from next-20171107 for today. > > Hi Stephen, > > Does this fix it? > > diff --git a/tools/objtool/M

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

locations") > > > > If it matters, this is a cross compilation (PowerPC host) using O= . > > > > I have used the tip tree from next-20171107 for today. > > Hi Stephen, > > Does this fix it? > > diff --git a/tools/objtool/Makefile b/tools/objtool/Makefil

Re: [PATCH 2/2] backlight: pwm_bl: add configurable delay between re-enabling PWM and switching backlight power on

Hi, On Tue, 7 Nov 2017 18:46:18 -0600 Rob Herring wrote: > On Mon, Oct 30, 2017 at 5:33 AM, Lee Jones wrote: > > On Fri, 27 Oct 2017, Rob Herring wrote: > > > >> On Thu, Oct 26, 2017 at 02:49:46PM +0200, Lothar Waßmann wrote: > >> > When switching the backlight on, the LCD

Re: [PATCH 2/2] backlight: pwm_bl: add configurable delay between re-enabling PWM and switching backlight power on

Hi, On Tue, 7 Nov 2017 18:46:18 -0600 Rob Herring wrote: > On Mon, Oct 30, 2017 at 5:33 AM, Lee Jones wrote: > > On Fri, 27 Oct 2017, Rob Herring wrote: > > > >> On Thu, Oct 26, 2017 at 02:49:46PM +0200, Lothar Waßmann wrote: > >> > When switching the backlight on, the LCD may need some time to

Re: [PATCH] Bluetooth: Use common error handling code in bt_init()

Hi Markus, > * Improve jump targets so that a bit of exception handling can be better > reused at the end of this function. > > * Adjust five condition checks. > > This issue was detected by using the Coccinelle software. > > Signed-off-by: Markus Elfring > ---

Re: [PATCH] Bluetooth: Use common error handling code in bt_init()

Hi Markus, > * Improve jump targets so that a bit of exception handling can be better > reused at the end of this function. > > * Adjust five condition checks. > > This issue was detected by using the Coccinelle software. > > Signed-off-by: Markus Elfring > --- > net/bluetooth/af_bluetooth.c

Re: [interval_tree_test_init] BUG: soft lockup - CPU#0 stuck for 23s! [swapper/0:1]

On Tue, Nov 07, 2017 at 08:58:14AM -0800, Davidlohr Bueso wrote: On Tue, 07 Nov 2017, Fengguang Wu wrote: [ 265.102312] xz_dec_test: module loaded [ 265.111774] xz_dec_test: Create a device node with 'mknod xz_dec_test c 246 0' and write .xz files to it. [ 265.160320] atomic64_test: passed

Re: [interval_tree_test_init] BUG: soft lockup - CPU#0 stuck for 23s! [swapper/0:1]

On Tue, Nov 07, 2017 at 08:58:14AM -0800, Davidlohr Bueso wrote: On Tue, 07 Nov 2017, Fengguang Wu wrote: [ 265.102312] xz_dec_test: module loaded [ 265.111774] xz_dec_test: Create a device node with 'mknod xz_dec_test c 246 0' and write .xz files to it. [ 265.160320] atomic64_test: passed

[PATCH net-next 1/2] net: hns3: fix a bug when getting phy address from NCL_config file

From: Fuyun Liang Driver gets phy address from NCL_config file and uses the phy address to initialize phydev. There are 5 bits for phy address. And C22 phy address has 5 bits. So 0-31 are all valid address for phy. If there is no phy, it will crash. Because driver always

[PATCH v2] af_netlink: give correct bounds to dump skb for NLMSG_DONE

The way people generally use netlink_dump is that they fill in the skb as much as possible, breaking when nla_put returns an error. Then, they get called again and start filling out the next skb, and again, and so forth. The mechanism at work here is the ability for the iterative dumping function

[PATCH net-next 1/2] net: hns3: fix a bug when getting phy address from NCL_config file

From: Fuyun Liang Driver gets phy address from NCL_config file and uses the phy address to initialize phydev. There are 5 bits for phy address. And C22 phy address has 5 bits. So 0-31 are all valid address for phy. If there is no phy, it will crash. Because driver always get a valid phy address.

[PATCH v2] af_netlink: give correct bounds to dump skb for NLMSG_DONE

The way people generally use netlink_dump is that they fill in the skb as much as possible, breaking when nla_put returns an error. Then, they get called again and start filling out the next skb, and again, and so forth. The mechanism at work here is the ability for the iterative dumping function

[PATCH net-next 2/2] net: hns3: cleanup mac auto-negotiation state query in hclge_update_speed_duplex

From: Fuyun Liang When checking whether auto-negotiation is on, driver only needs to check the value of mac.autoneg(SW) directly, and does not need to query it from hardware. Because this value is always synchronized with the auto-negotiation state of hardware. This

[PATCH net-next 2/2] net: hns3: cleanup mac auto-negotiation state query in hclge_update_speed_duplex

From: Fuyun Liang When checking whether auto-negotiation is on, driver only needs to check the value of mac.autoneg(SW) directly, and does not need to query it from hardware. Because this value is always synchronized with the auto-negotiation state of hardware. This patch removes mac

Re: [LKP] [lkp-robot] [fs/locks] 52306e882f: stress-ng.lockofd.ops_per_sec -11% regression

On Thu, Sep 28, 2017 at 04:02:23PM +0800, kernel test robot wrote: > > Greeting, > > FYI, we noticed a -11% regression of stress-ng.lockofd.ops_per_sec due to > commit: > > > commit: 52306e882f77d3fd73f91435c41373d634acc5d2 ("fs/locks: Use allocation > rather than the stack in

Re: [LKP] [lkp-robot] [fs/locks] 52306e882f: stress-ng.lockofd.ops_per_sec -11% regression

On Thu, Sep 28, 2017 at 04:02:23PM +0800, kernel test robot wrote: > > Greeting, > > FYI, we noticed a -11% regression of stress-ng.lockofd.ops_per_sec due to > commit: > > > commit: 52306e882f77d3fd73f91435c41373d634acc5d2 ("fs/locks: Use allocation > rather than the stack in

[PATCH net-next 0/2] net: hns3: Bug fixes & Code improvements in HNS3 driver

This patch-set introduces some bug fixes and code improvements. As [patch 1/2] depends on the patch {5392902 net: hns3: Consistently using GENMASK in hns3 driver}, which exists in net-next, not exists in net, so push this serise to nex-next. Fuyun Liang (2): {topost} net: hns3: fix a bug when

[PATCH net-next 0/2] net: hns3: Bug fixes & Code improvements in HNS3 driver

This patch-set introduces some bug fixes and code improvements. As [patch 1/2] depends on the patch {5392902 net: hns3: Consistently using GENMASK in hns3 driver}, which exists in net-next, not exists in net, so push this serise to nex-next. Fuyun Liang (2): {topost} net: hns3: fix a bug when

Re: [PATCH net-next 0/2] net: hns3: Bug fixes & Code improvements in HNS3 driver

please ignore this patch-set. I should remove "{topost}" from the subject. sorry for that, I will resend the patch-set. On 2017/11/8 15:31, Lipeng wrote: This patch-set introduces some bug fixes and code improvements. As [patch 1/2] depends on the patch {5392902 net: hns3: Consistently

Re: [PATCH net-next 0/2] net: hns3: Bug fixes & Code improvements in HNS3 driver

please ignore this patch-set. I should remove "{topost}" from the subject. sorry for that, I will resend the patch-set. On 2017/11/8 15:31, Lipeng wrote: This patch-set introduces some bug fixes and code improvements. As [patch 1/2] depends on the patch {5392902 net: hns3: Consistently

Re: [PATCH] rtc: omap: Support scratch registers

On 08/11/2017 at 12:38:05 +0530, Keerthy wrote: > > > On Wednesday 08 November 2017 11:57 AM, Alexandre Belloni wrote: > > Hi, > > > > On 08/11/2017 at 11:30:45 +0530, Keerthy wrote: > > +static int omap_rtc_scratch_read(void *priv, unsigned int offset, void > > *_val, > > +

Re: [PATCH] rtc: omap: Support scratch registers

On 08/11/2017 at 12:38:05 +0530, Keerthy wrote: > > > On Wednesday 08 November 2017 11:57 AM, Alexandre Belloni wrote: > > Hi, > > > > On 08/11/2017 at 11:30:45 +0530, Keerthy wrote: > > +static int omap_rtc_scratch_read(void *priv, unsigned int offset, void > > *_val, > > +

[PATCH] Bluetooth: Use common error handling code in bt_init()

From: Markus Elfring Date: Wed, 8 Nov 2017 08:03:04 +0100 * Improve jump targets so that a bit of exception handling can be better reused at the end of this function. * Adjust five condition checks. This issue was detected by using the Coccinelle software.

[PATCH] Bluetooth: Use common error handling code in bt_init()

From: Markus Elfring Date: Wed, 8 Nov 2017 08:03:04 +0100 * Improve jump targets so that a bit of exception handling can be better reused at the end of this function. * Adjust five condition checks. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

Re: [PATCH] watchdog: mpc8xxx: use the core worker function

Le 07/11/2017 à 23:56, Guenter Roeck a écrit : On Tue, Nov 07, 2017 at 05:23:56PM +0100, Christophe Leroy wrote: The watchdog core includes a worker function which pings the watchdog until user app starts pinging it and which also pings it if the HW require more frequent pings. Use that

Re: [PATCH] watchdog: mpc8xxx: use the core worker function

Le 07/11/2017 à 23:56, Guenter Roeck a écrit : On Tue, Nov 07, 2017 at 05:23:56PM +0100, Christophe Leroy wrote: The watchdog core includes a worker function which pings the watchdog until user app starts pinging it and which also pings it if the HW require more frequent pings. Use that

Re: [PATCH net] qmi_wwan: Add missing skb_reset_mac_header-call

From: Kristian Evensen Date: Tue, 7 Nov 2017 13:47:56 +0100 > When we receive a packet on a QMI device in raw IP mode, we should call > skb_reset_mac_header() to ensure that skb->mac_header contains a valid > offset in the packet. While it shouldn't really matter,

Re: [PATCH net] qmi_wwan: Add missing skb_reset_mac_header-call

From: Kristian Evensen Date: Tue, 7 Nov 2017 13:47:56 +0100 > When we receive a packet on a QMI device in raw IP mode, we should call > skb_reset_mac_header() to ensure that skb->mac_header contains a valid > offset in the packet. While it shouldn't really matter, the packets have > no MAC

Re: [PATCH] rtc: omap: Support scratch registers

On Wednesday 08 November 2017 11:57 AM, Alexandre Belloni wrote: > Hi, > > On 08/11/2017 at 11:30:45 +0530, Keerthy wrote: > +static int omap_rtc_scratch_read(void *priv, unsigned int offset, void > *_val, > + size_t bytes) > +{ > + struct omap_rtc

Re: [PATCH] rtc: omap: Support scratch registers

On Wednesday 08 November 2017 11:57 AM, Alexandre Belloni wrote: > Hi, > > On 08/11/2017 at 11:30:45 +0530, Keerthy wrote: > +static int omap_rtc_scratch_read(void *priv, unsigned int offset, void > *_val, > + size_t bytes) > +{ > + struct omap_rtc

Re: [PATCH] af_netlink: give correct bounds to dump skb for NLMSG_DONE

Erf, your patch doesn't handle what happens if len comes back negative, but I'll fix it up and send a v2 using this approach. I think I really prefer v1 though. Jason

Re: [PATCH] af_netlink: give correct bounds to dump skb for NLMSG_DONE

Erf, your patch doesn't handle what happens if len comes back negative, but I'll fix it up and send a v2 using this approach. I think I really prefer v1 though. Jason

[PATCH net-next 1/2] {topost} net: hns3: fix a bug when getting phy address from NCL_config file

From: Fuyun Liang Driver gets phy address from NCL_config file and uses the phy address to initialize phydev. There are 5 bits for phy address. And C22 phy address has 5 bits. So 0-31 are all valid address for phy. If there is no phy, it will crash. Because driver always

[PATCH net-next 1/2] {topost} net: hns3: fix a bug when getting phy address from NCL_config file

From: Fuyun Liang Driver gets phy address from NCL_config file and uses the phy address to initialize phydev. There are 5 bits for phy address. And C22 phy address has 5 bits. So 0-31 are all valid address for phy. If there is no phy, it will crash. Because driver always get a valid phy address.

[PATCH net-next 0/2] net: hns3: Bug fixes & Code improvements in HNS3 driver

This patch-set introduces some bug fixes and code improvements. As [patch 1/2] depends on the patch {5392902 net: hns3: Consistently using GENMASK in hns3 driver}, which exists in net-next, not exists in net, so push this serise to nex-next. Fuyun Liang (2): {topost} net: hns3: fix a bug when

[PATCH net-next 0/2] net: hns3: Bug fixes & Code improvements in HNS3 driver

This patch-set introduces some bug fixes and code improvements. As [patch 1/2] depends on the patch {5392902 net: hns3: Consistently using GENMASK in hns3 driver}, which exists in net-next, not exists in net, so push this serise to nex-next. Fuyun Liang (2): {topost} net: hns3: fix a bug when

[PATCH net-next 2/2] {topost} net: hns3: cleanup mac auto-negotiation state query in hclge_update_speed_duplex

From: Fuyun Liang When checking whether auto-negotiation is on, driver only needs to check the value of mac.autoneg(SW) directly, and does not need to query it from hardware. Because this value is always synchronized with the auto-negotiation state of hardware. This

[PATCH net-next 2/2] {topost} net: hns3: cleanup mac auto-negotiation state query in hclge_update_speed_duplex

From: Fuyun Liang When checking whether auto-negotiation is on, driver only needs to check the value of mac.autoneg(SW) directly, and does not need to query it from hardware. Because this value is always synchronized with the auto-negotiation state of hardware. This patch removes mac

Re: [jump_label_test] WARNING: CPU: 0 PID: 1 at kernel/jump_label.c:761 jump_label_test+0x63/0xab

On Tue, Nov 07, 2017 at 05:17:38PM -0500, Jason Baron wrote: On 11/07/2017 04:27 AM, Fengguang Wu wrote: Hello, FYI this happens in v4.14-rc8 -- it's not necessarily a new bug. Hi, So this looks like the branches aren't getting updated because the WARN_ON()s are all from the second half

Re: [jump_label_test] WARNING: CPU: 0 PID: 1 at kernel/jump_label.c:761 jump_label_test+0x63/0xab

On Tue, Nov 07, 2017 at 05:17:38PM -0500, Jason Baron wrote: On 11/07/2017 04:27 AM, Fengguang Wu wrote: Hello, FYI this happens in v4.14-rc8 -- it's not necessarily a new bug. Hi, So this looks like the branches aren't getting updated because the WARN_ON()s are all from the second half

linux-next: Tree for Nov 8

Hi all, Changes since 20171107: The powerpc tree still had its build failure for which I applied a patch. It also gained a conflict against Linus' tree. The tip tree gained a conflict against the crypto tree and a build failure so I used the version from next-20171107. The drivers-x86 tree

linux-next: Tree for Nov 8

Hi all, Changes since 20171107: The powerpc tree still had its build failure for which I applied a patch. It also gained a conflict against Linus' tree. The tip tree gained a conflict against the crypto tree and a build failure so I used the version from next-20171107. The drivers-x86 tree

Re: [PATCH] pktgen: document 32-bit timestamp overflow

From: Arnd Bergmann Date: Tue, 7 Nov 2017 11:38:32 +0100 > Timestamps in pktgen are currently retrieved using the deprecated > do_gettimeofday() function that wraps its signed 32-bit seconds in 2038 > (on 32-bit architectures) and requires a division operation to calculate >

Re: [PATCH] pktgen: document 32-bit timestamp overflow

From: Arnd Bergmann Date: Tue, 7 Nov 2017 11:38:32 +0100 > Timestamps in pktgen are currently retrieved using the deprecated > do_gettimeofday() function that wraps its signed 32-bit seconds in 2038 > (on 32-bit architectures) and requires a division operation to calculate > microseconds. > >

Re: [PATCH] x86/oprofile/ppro: Do not use __this_cpu* accessors in preemptible context

On Tue, Nov 07, 2017 at 06:53:07PM +0100, Borislav Petkov wrote: On Tue, Nov 07, 2017 at 08:43:40AM -0800, Linus Torvalds wrote: So I'm adding Borislav to the cc just to maybe annoy him into sending in a patch for this thing too.. /me runs away like the wind! This is the famous "you touched

Re: [PATCH] x86/oprofile/ppro: Do not use __this_cpu* accessors in preemptible context

On Tue, Nov 07, 2017 at 06:53:07PM +0100, Borislav Petkov wrote: On Tue, Nov 07, 2017 at 08:43:40AM -0800, Linus Torvalds wrote: So I'm adding Borislav to the cc just to maybe annoy him into sending in a patch for this thing too.. /me runs away like the wind! This is the famous "you touched

Re: [PATCH] net/tcp: track all ipv4/tcp state transition in tcp_set_state

From: Yafang Shao Date: Tue, 7 Nov 2017 18:36:28 +0800 > When I hooked the function tcp_set_state with kprobe to track the ipv4/tcp > state transistion, I found state transition from TCP_LISTEN to TCP_SYN_RECV > is missed. > > I think it is better to use the helper to do

Re: [PATCH] net/tcp: track all ipv4/tcp state transition in tcp_set_state

From: Yafang Shao Date: Tue, 7 Nov 2017 18:36:28 +0800 > When I hooked the function tcp_set_state with kprobe to track the ipv4/tcp > state transistion, I found state transition from TCP_LISTEN to TCP_SYN_RECV > is missed. > > I think it is better to use the helper to do state transition

[PATCH 1/4] documentation: Add compatibles for Amlogic Meson AXG pin controllers

From: Xingyu Chen Add compatibles for Amlogic Meson AXG pin controllers Signed-off-by: Xingyu Chen Signed-off-by: Yixun Lan --- Documentation/devicetree/bindings/pinctrl/meson,pinctrl.txt | 2 ++ 1 file changed, 2

[PATCH 4/4] ARM64: dts: meson-axg: add pinctrl DT info for Meson-AXG SoC

From: Xingyu Chen Add new pinctrl DT info for the Amlogic's Meson-AXG SoC. Signed-off-by: Xingyu Chen Signed-off-by: Yixun Lan --- arch/arm64/boot/dts/amlogic/meson-axg.dtsi | 43 ++ 1 file

[PATCH 1/4] documentation: Add compatibles for Amlogic Meson AXG pin controllers

From: Xingyu Chen Add compatibles for Amlogic Meson AXG pin controllers Signed-off-by: Xingyu Chen Signed-off-by: Yixun Lan --- Documentation/devicetree/bindings/pinctrl/meson,pinctrl.txt | 2 ++ 1 file changed, 2 insertions(+) diff --git

[PATCH 4/4] ARM64: dts: meson-axg: add pinctrl DT info for Meson-AXG SoC

From: Xingyu Chen Add new pinctrl DT info for the Amlogic's Meson-AXG SoC. Signed-off-by: Xingyu Chen Signed-off-by: Yixun Lan --- arch/arm64/boot/dts/amlogic/meson-axg.dtsi | 43 ++ 1 file changed, 43 insertions(+) diff --git

  1   2   3   4   5   6   7   8   9   10   >