[PATCH] staging: atomisp: constify v4l2_subdev_sensor_ops

v4l2_subdev_sensor_ops are not supposed to change at runtime. v4l2_subdev_sensor_ops are working with const 'sensor' field of sturct v4l2_subdev_ops. So mark the non-const v4l2_subdev_sensor_ops structs as const. Signed-off-by: Arvind Yadav ---

[PATCH] staging: atomisp: constify v4l2_subdev_sensor_ops

v4l2_subdev_sensor_ops are not supposed to change at runtime. v4l2_subdev_sensor_ops are working with const 'sensor' field of sturct v4l2_subdev_ops. So mark the non-const v4l2_subdev_sensor_ops structs as const. Signed-off-by: Arvind Yadav --- drivers/staging/media/atomisp/i2c/mt9m114.c | 2 +-

[stable 4.4 0/2 V2] missing mei device ids

Device ids that are missing in 4.4 stable Tomas Winkler (2): mei: me: add broxton pci device ids mei: me: add lewisburg device ids drivers/misc/mei/hw-me-regs.h | 8 drivers/misc/mei/pci-me.c | 4 2 files changed, 12 insertions(+) -- 2.9.5

[stable 4.4 0/2 V2] missing mei device ids

Device ids that are missing in 4.4 stable Tomas Winkler (2): mei: me: add broxton pci device ids mei: me: add lewisburg device ids drivers/misc/mei/hw-me-regs.h | 8 drivers/misc/mei/pci-me.c | 4 2 files changed, 12 insertions(+) -- 2.9.5

[stable 4.4 1/2 V2] mei: me: add broxton pci device ids

commit dd16f6cdeb4e02a728863d3cf99aaab352f0d761 upstream Add device ids for Broxton SoC based devices. Cc: sta...@kernel.com #4.4.x Signed-off-by: Tomas Winkler Signed-off-by: Greg Kroah-Hartman --- Add upstream commit id

[stable 4.4 2/2 V2] mei: me: add lewisburg device ids

commit 9ff2007bea1f1bfc53ac0bc7ccf8200bb275fd52 upstream Add MEI Lewisburg PCH IDs for Purley based workstations. Cc: # 4.4.x Signed-off-by: Alexander Usyskin Signed-off-by: Tomas Winkler Signed-off-by: Greg

[stable 4.4 1/2 V2] mei: me: add broxton pci device ids

commit dd16f6cdeb4e02a728863d3cf99aaab352f0d761 upstream Add device ids for Broxton SoC based devices. Cc: sta...@kernel.com #4.4.x Signed-off-by: Tomas Winkler Signed-off-by: Greg Kroah-Hartman --- Add upstream commit id drivers/misc/mei/hw-me-regs.h | 3 +++ drivers/misc/mei/pci-me.c |

[stable 4.4 2/2 V2] mei: me: add lewisburg device ids

commit 9ff2007bea1f1bfc53ac0bc7ccf8200bb275fd52 upstream Add MEI Lewisburg PCH IDs for Purley based workstations. Cc: # 4.4.x Signed-off-by: Alexander Usyskin Signed-off-by: Tomas Winkler Signed-off-by: Greg Kroah-Hartman --- Add upstream commit id drivers/misc/mei/hw-me-regs.h | 5 +

Re: [PATCH RFC/RFT] sched/fair: Improve the behavior of sync flag

On Sat, 2017-08-26 at 18:02 -0700, Joel Fernandes wrote: > Binder (Android's IPC mechanism) which uses sync wake ups during synchronous > transactions to the scheduler to indicate that the waker is about to sleep > soon. The current wake up path can improved when the sync flag is passed >

Re: [PATCH RFC/RFT] sched/fair: Improve the behavior of sync flag

On Sat, 2017-08-26 at 18:02 -0700, Joel Fernandes wrote: > Binder (Android's IPC mechanism) which uses sync wake ups during synchronous > transactions to the scheduler to indicate that the waker is about to sleep > soon. The current wake up path can improved when the sync flag is passed >

★lingwangbrass--“JEC world 2018 世界复合材料展览及会议”将于“3月06-08日”在“法国巴黎”举行 （地右P1-L-Me）

尊敬的 lingwangbr...@hotmail.com 企业领导/公司负责人/业界专家，您好： 　　 　　 新材料为21世纪三大共性关键技术之一，已成为全球经济迅速增长的源动力和提升核心竞争力的战略焦点。材料作为制造业的基础，特别是新材料研究和产业发展的水平与规模，已经成为衡量一个国家科技进步和综合实力的重要标志。在新材料发展与应用中，复合材料占有相当重要的地位，特别广泛的应用在汽车、交通、风能、航空、航天、兵器、船舶、国防、机械、电子、化工、建筑、农业、渔业、纺织、运动器材等领域，一直是世界各国优先发展和竞争激烈的重要行业。 　　 　　“JEC世界复合材料展览及会议”（JEC

★lingwangbrass--“JEC world 2018 世界复合材料展览及会议”将于“3月06-08日”在“法国巴黎”举行 （地右P1-L-Me）

尊敬的 lingwangbr...@hotmail.com 企业领导/公司负责人/业界专家，您好： 　　 　　 新材料为21世纪三大共性关键技术之一，已成为全球经济迅速增长的源动力和提升核心竞争力的战略焦点。材料作为制造业的基础，特别是新材料研究和产业发展的水平与规模，已经成为衡量一个国家科技进步和综合实力的重要标志。在新材料发展与应用中，复合材料占有相当重要的地位，特别广泛的应用在汽车、交通、风能、航空、航天、兵器、船舶、国防、机械、电子、化工、建筑、农业、渔业、纺织、运动器材等领域，一直是世界各国优先发展和竞争激烈的重要行业。 　　 　　“JEC世界复合材料展览及会议”（JEC

[PATCH 6/6] staging: usb: tcpm: Comply with TryWait.SNK State

According to the spec: "4.5.2.2.10.2 Exiting from TryWait.SNK State The port shall transition to Attached.SNK after tCCDebounce if or when VBUS is detected. Note the Source may initiate USB PD communications which will cause brief periods of the SNK.Open state on both the CC1 and CC2 pins, but

[PATCH 6/6] staging: usb: tcpm: Comply with TryWait.SNK State

According to the spec: "4.5.2.2.10.2 Exiting from TryWait.SNK State The port shall transition to Attached.SNK after tCCDebounce if or when VBUS is detected. Note the Source may initiate USB PD communications which will cause brief periods of the SNK.Open state on both the CC1 and CC2 pins, but

[PATCH 4/6] staging: usb: tcpm: usb: type-c: tcpm: Check for Rp for tPDDebounce

According the spec, the following is the conditions for exiting Try.SNK state: "The port shall wait for tDRPTry and only then begin monitoring the CC1 and CC2 pins for the SNK.Rp state. The port shall then transition to Attached.SNK when the SNK.Rp state is detected on exactly one of the CC1 or

[PATCH 5/6] staging: usb: tcpm: usb: typec: tcpm: Follow Try.SRC exit requirements

According to spec: " 4.5.2.2.9.2 Exiting from Try.SRC State: The port shall transition to Attached.SRC when the SRC.Rd state is detected on exactly one of the CC1 or CC2 pins for at least tPDDebounce. The port shall transition to TryWait.SNK after tDRPTry and the SRC.Rd state has not been

[PATCH 4/6] staging: usb: tcpm: usb: type-c: tcpm: Check for Rp for tPDDebounce

According the spec, the following is the conditions for exiting Try.SNK state: "The port shall wait for tDRPTry and only then begin monitoring the CC1 and CC2 pins for the SNK.Rp state. The port shall then transition to Attached.SNK when the SNK.Rp state is detected on exactly one of the CC1 or

[PATCH 5/6] staging: usb: tcpm: usb: typec: tcpm: Follow Try.SRC exit requirements

According to spec: " 4.5.2.2.9.2 Exiting from Try.SRC State: The port shall transition to Attached.SRC when the SRC.Rd state is detected on exactly one of the CC1 or CC2 pins for at least tPDDebounce. The port shall transition to TryWait.SNK after tDRPTry and the SRC.Rd state has not been

[PATCH 3/6] staging: usb: tcpm: usb: typec: tcpm: Prevent TCPM from looping in SRC_TRYWAIT

According to the spec the following is the condition for exiting TryWait.SRC: "The port shall transition to Attached.SRC when V BUS is at vSafe0V and the SRC.Rd state is detected on exactly one of the CC pins for at least tCCDebounce. The port shall transition to Unattached.SNK after tDRPTry if

[PATCH 1/6] staging: usb: typec: tcpm set port type callback

The port type callback call enquires the tcpc_dev if the requested port type is supported. If supported, then performs a tcpm reset if required after setting the tcpm internal port_type variable. Check against the tcpm port_type instead of checking against caps.type as port_type reflects the

[PATCH 3/6] staging: usb: tcpm: usb: typec: tcpm: Prevent TCPM from looping in SRC_TRYWAIT

According to the spec the following is the condition for exiting TryWait.SRC: "The port shall transition to Attached.SRC when V BUS is at vSafe0V and the SRC.Rd state is detected on exactly one of the CC pins for at least tCCDebounce. The port shall transition to Unattached.SNK after tDRPTry if

[PATCH 1/6] staging: usb: typec: tcpm set port type callback

The port type callback call enquires the tcpc_dev if the requested port type is supported. If supported, then performs a tcpm reset if required after setting the tcpm internal port_type variable. Check against the tcpm port_type instead of checking against caps.type as port_type reflects the

[PATCH 2/6] staging: usb: typec: Check for port type for Try.SRC/Try.SNK

Enable Try.SRC or Try.SNK only when port_type is DRP. Try.SRC or Try.SNK state machines are not valid for SRC only or SNK only ports. Signed-off-by: Badhri Jagan Sridharan --- drivers/staging/typec/tcpm.c | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git

[PATCH 2/6] staging: usb: typec: Check for port type for Try.SRC/Try.SNK

Enable Try.SRC or Try.SNK only when port_type is DRP. Try.SRC or Try.SNK state machines are not valid for SRC only or SNK only ports. Signed-off-by: Badhri Jagan Sridharan --- drivers/staging/typec/tcpm.c | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git

[GIT PULL] NTB bug fixes for v4.13

Hello Linus, Here are a few NTB bug fixes for 4.13. Please consider pulling them. Thanks, Jon The following changes since commit 5771a8c08880cdca3bfb4a3fc6d309d6bba20877: Linux v4.13-rc1 (2017-07-15 15:22:10 -0700) are available in the git repository at: git://github.com/jonmason/ntb

[GIT PULL] NTB bug fixes for v4.13

Hello Linus, Here are a few NTB bug fixes for 4.13. Please consider pulling them. Thanks, Jon The following changes since commit 5771a8c08880cdca3bfb4a3fc6d309d6bba20877: Linux v4.13-rc1 (2017-07-15 15:22:10 -0700) are available in the git repository at: git://github.com/jonmason/ntb

[PATCH] alpha: Fix section mismatches

Signed-off-by: Matt Turner --- arch/alpha/kernel/core_marvel.c | 4 ++-- arch/alpha/kernel/smp.c | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/arch/alpha/kernel/core_marvel.c b/arch/alpha/kernel/core_marvel.c index db72356714c1..03ff832b1cb4

[PATCH] alpha: Fix build error without CONFIG_VGA_HOSE.

pci_vga_hose is #defined to 0 in include/asm/vga.h if CONFIG_VGA_HOSE is not set. Signed-off-by: Matt Turner --- arch/alpha/kernel/core_marvel.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/alpha/kernel/core_marvel.c b/arch/alpha/kernel/core_marvel.c index

[PATCH] alpha: Fix section mismatches

Signed-off-by: Matt Turner --- arch/alpha/kernel/core_marvel.c | 4 ++-- arch/alpha/kernel/smp.c | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/arch/alpha/kernel/core_marvel.c b/arch/alpha/kernel/core_marvel.c index db72356714c1..03ff832b1cb4 100644 ---

[PATCH] alpha: Fix build error without CONFIG_VGA_HOSE.

pci_vga_hose is #defined to 0 in include/asm/vga.h if CONFIG_VGA_HOSE is not set. Signed-off-by: Matt Turner --- arch/alpha/kernel/core_marvel.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/alpha/kernel/core_marvel.c b/arch/alpha/kernel/core_marvel.c index

Re: [RESEND PATCH 1/1] arm64: dts: Add Variscite DART-SD410 Evaluation board dts

On Fri, Aug 25, 2017 at 01:44:18PM +0300, Baruch Siach wrote: > Hi Leonid, > > On Wed, Aug 23, 2017 at 08:44:56PM +0300, Leonid Segal wrote: > > Thank you very much for the tips. > > I have updated the documentation and schematics of our web site. > > I also tried to implement all other fixes,

Re: [RESEND PATCH 1/1] arm64: dts: Add Variscite DART-SD410 Evaluation board dts

On Fri, Aug 25, 2017 at 01:44:18PM +0300, Baruch Siach wrote: > Hi Leonid, > > On Wed, Aug 23, 2017 at 08:44:56PM +0300, Leonid Segal wrote: > > Thank you very much for the tips. > > I have updated the documentation and schematics of our web site. > > I also tried to implement all other fixes,

Re: [PATCH v2 2/3] rtc: Add Realtek RTD1295

On Sun, Aug 27, 2017 at 04:30:08AM +0200, Andreas Färber wrote: > Am 27.08.2017 um 04:05 schrieb Andrew Lunn: > > n Sun, Aug 27, 2017 at 02:33:27AM +0200, Andreas Färber wrote: > >> +struct rtd119x_rtc { > >> + void __iomem *base; > >> + struct clk *clk; > >> + struct rtc_device *rtcdev; > >> +

Re: [PATCH v2 2/3] rtc: Add Realtek RTD1295

On Sun, Aug 27, 2017 at 04:30:08AM +0200, Andreas Färber wrote: > Am 27.08.2017 um 04:05 schrieb Andrew Lunn: > > n Sun, Aug 27, 2017 at 02:33:27AM +0200, Andreas Färber wrote: > >> +struct rtd119x_rtc { > >> + void __iomem *base; > >> + struct clk *clk; > >> + struct rtc_device *rtcdev; > >> +

Re: [PATCH v2 2/3] rtc: Add Realtek RTD1295

Am 27.08.2017 um 04:05 schrieb Andrew Lunn: > n Sun, Aug 27, 2017 at 02:33:27AM +0200, Andreas Färber wrote: >> +struct rtd119x_rtc { >> +void __iomem *base; >> +struct clk *clk; >> +struct rtc_device *rtcdev; >> +unsigned base_year; >> +spinlock_t lock; > > Where is this lock

Re: [PATCH v2 2/3] rtc: Add Realtek RTD1295

Am 27.08.2017 um 04:05 schrieb Andrew Lunn: > n Sun, Aug 27, 2017 at 02:33:27AM +0200, Andreas Färber wrote: >> +struct rtd119x_rtc { >> +void __iomem *base; >> +struct clk *clk; >> +struct rtc_device *rtcdev; >> +unsigned base_year; >> +spinlock_t lock; > > Where is this lock

[PATCH] hugetlbfs: change put_page/unlock_page order in hugetlbfs_fallocate()

hugetlfs_fallocate() currently performs put_page() before unlock_page(). This scenario opens a small time window, from the time the page is added to the page cache, until it is unlocked, in which the page might be removed from the page-cache by another core. If the page is removed during this time

[PATCH] hugetlbfs: change put_page/unlock_page order in hugetlbfs_fallocate()

hugetlfs_fallocate() currently performs put_page() before unlock_page(). This scenario opens a small time window, from the time the page is added to the page cache, until it is unlocked, in which the page might be removed from the page-cache by another core. If the page is removed during this time

Re: [PATCH v2 2/3] rtc: Add Realtek RTD1295

n Sun, Aug 27, 2017 at 02:33:27AM +0200, Andreas Färber wrote: > Based on QNAP's arch/arm/mach-rtk119x/driver/rtk_rtc_drv.c code and > mach-rtk119x/driver/dc2vo/fpga/include/mis_reg.h register definitions. > > The base year 2014 was observed on all of Zidoo X9S, ProBox2 Ava and > Beelink Lake I.

Re: [PATCH v2 2/3] rtc: Add Realtek RTD1295

n Sun, Aug 27, 2017 at 02:33:27AM +0200, Andreas Färber wrote: > Based on QNAP's arch/arm/mach-rtk119x/driver/rtk_rtc_drv.c code and > mach-rtk119x/driver/dc2vo/fpga/include/mis_reg.h register definitions. > > The base year 2014 was observed on all of Zidoo X9S, ProBox2 Ava and > Beelink Lake I.

Re: [PATCH v2] sched/deadline: make it configurable

Ping. On Thu, 17 Aug 2017, Nicolas Pitre wrote: > Ping. > > On Thu, 3 Aug 2017, Nicolas Pitre wrote: > > > On most small systems, the deadline scheduler class is a luxury that > > rarely gets used if at all. It is preferable to have the ability to > > configure it out to reduce the kernel size

Re: [PATCH v2] sched/deadline: make it configurable

Ping. On Thu, 17 Aug 2017, Nicolas Pitre wrote: > Ping. > > On Thu, 3 Aug 2017, Nicolas Pitre wrote: > > > On most small systems, the deadline scheduler class is a luxury that > > rarely gets used if at all. It is preferable to have the ability to > > configure it out to reduce the kernel size

Re: [PATCH 1/2] crypto: n2 - remove null check before kfree

From: Himanshu Jha Date: Sun, 27 Aug 2017 02:45:29 +0530 > kfree on NULL pointer is a no-op and therefore checking it is redundant. > > Signed-off-by: Himanshu Jha Acked-by: David S. Miller

Re: [PATCH 1/2] crypto: n2 - remove null check before kfree

From: Himanshu Jha Date: Sun, 27 Aug 2017 02:45:29 +0530 > kfree on NULL pointer is a no-op and therefore checking it is redundant. > > Signed-off-by: Himanshu Jha Acked-by: David S. Miller

Loan

UNSECURED BUSINESS/PERSONAL LOAN BY LOAN CAPITAL FINANCE - NO COLLATERAL - MINIMUM DOCUMENTATION - BUSINESS LOAN UP TO FIVE(5) MILLION US DOLLARS CONTACT US TODAY VIA EMAIL: finance.incapi...@hotmail.com

Loan

UNSECURED BUSINESS/PERSONAL LOAN BY LOAN CAPITAL FINANCE - NO COLLATERAL - MINIMUM DOCUMENTATION - BUSINESS LOAN UP TO FIVE(5) MILLION US DOLLARS CONTACT US TODAY VIA EMAIL: finance.incapi...@hotmail.com

[PATCH RFC/RFT] sched/fair: Improve the behavior of sync flag

Binder (Android's IPC mechanism) which uses sync wake ups during synchronous transactions to the scheduler to indicate that the waker is about to sleep soon. The current wake up path can improved when the sync flag is passed resulting in higher binder performance. In this patch we more strongly

[PATCH RFC/RFT] sched/fair: Improve the behavior of sync flag

Binder (Android's IPC mechanism) which uses sync wake ups during synchronous transactions to the scheduler to indicate that the waker is about to sleep soon. The current wake up path can improved when the sync flag is passed resulting in higher binder performance. In this patch we more strongly

[PATCH v2 2/3] rtc: Add Realtek RTD1295

Based on QNAP's arch/arm/mach-rtk119x/driver/rtk_rtc_drv.c code and mach-rtk119x/driver/dc2vo/fpga/include/mis_reg.h register definitions. The base year 2014 was observed on all of Zidoo X9S, ProBox2 Ava and Beelink Lake I. Signed-off-by: Andreas Färber --- v1 -> v2: *

[PATCH v2 2/3] rtc: Add Realtek RTD1295

Based on QNAP's arch/arm/mach-rtk119x/driver/rtk_rtc_drv.c code and mach-rtk119x/driver/dc2vo/fpga/include/mis_reg.h register definitions. The base year 2014 was observed on all of Zidoo X9S, ProBox2 Ava and Beelink Lake I. Signed-off-by: Andreas Färber --- v1 -> v2: * Dropped open/release in

[PATCH v2 0/3] arm64: Realtek RTD1295 RTC

Hello, This series adds the RTC for the Realtek RTD1295 SoC. Based on my RTD1295 clk series. There being no public source code for RTD1295, the implementation is based on register offsets seen in the vendor DT, as well as older mach-rtk119x code published by QNAP. The base year is still

[PATCH v2 0/3] arm64: Realtek RTD1295 RTC

Hello, This series adds the RTC for the Realtek RTD1295 SoC. Based on my RTD1295 clk series. There being no public source code for RTD1295, the implementation is based on register offsets seen in the vendor DT, as well as older mach-rtk119x code published by QNAP. The base year is still

[PATCH v2 1/3] dt-bindings: rtc: Add Realtek RTD1295

Add a binding for the RTC on the Realtek RTD119x/RTD129x SoC families. Acked-by: Rob Herring Signed-off-by: Andreas Färber --- v1 -> v2: Unchanged .../devicetree/bindings/rtc/realtek,rtd119x.txt | 16 1 file changed, 16

[PATCH v2 1/3] dt-bindings: rtc: Add Realtek RTD1295

Add a binding for the RTC on the Realtek RTD119x/RTD129x SoC families. Acked-by: Rob Herring Signed-off-by: Andreas Färber --- v1 -> v2: Unchanged .../devicetree/bindings/rtc/realtek,rtd119x.txt | 16 1 file changed, 16 insertions(+) create mode 100644

[PATCH v2 3/3] arm64: dts: realtek: Add RTD1295 RTC node

Add RTC node to the Realtek RTD1295 Device Tree. Signed-off-by: Andreas Färber --- v1 -> v2: Unchanged Depends on the pending clock bindings. arch/arm64/boot/dts/realtek/rtd1295.dtsi | 6 ++ 1 file changed, 6 insertions(+) diff --git

[PATCH v2 3/3] arm64: dts: realtek: Add RTD1295 RTC node

Add RTC node to the Realtek RTD1295 Device Tree. Signed-off-by: Andreas Färber --- v1 -> v2: Unchanged Depends on the pending clock bindings. arch/arm64/boot/dts/realtek/rtd1295.dtsi | 6 ++ 1 file changed, 6 insertions(+) diff --git a/arch/arm64/boot/dts/realtek/rtd1295.dtsi

Re: [PATCH v2 14/20] mm: Provide speculative fault infrastructure

On Fri, Aug 18, 2017 at 12:05:13AM +0200, Laurent Dufour wrote: > +/* > + * vm_normal_page() adds some processing which should be done while > + * hodling the mmap_sem. > + */ > +int handle_speculative_fault(struct mm_struct *mm, unsigned long address, > + unsigned int

Re: [PATCH v2 14/20] mm: Provide speculative fault infrastructure

On Fri, Aug 18, 2017 at 12:05:13AM +0200, Laurent Dufour wrote: > +/* > + * vm_normal_page() adds some processing which should be done while > + * hodling the mmap_sem. > + */ > +int handle_speculative_fault(struct mm_struct *mm, unsigned long address, > + unsigned int

Re: [PATCH v6 3/5] mm: introduce mmap3 for safely defining new mmap flags

On Sat, Aug 26, 2017 at 03:46:22PM -0700, Dan Williams wrote: > On Sat, Aug 26, 2017 at 12:50 PM, Helge Deller wrote: > > On 26.08.2017 17:15, Dan Williams wrote: > [..] > >> I have not seen any patches for parisc pmem+dax enabling so it seems > >> too early to worry about these

Re: [PATCH v6 3/5] mm: introduce mmap3 for safely defining new mmap flags

On Sat, Aug 26, 2017 at 03:46:22PM -0700, Dan Williams wrote: > On Sat, Aug 26, 2017 at 12:50 PM, Helge Deller wrote: > > On 26.08.2017 17:15, Dan Williams wrote: > [..] > >> I have not seen any patches for parisc pmem+dax enabling so it seems > >> too early to worry about these "last mile"

Re: [PATCH] Input: synaptics - fix device info appearing different on reconnect

Any comments on this patch? Thanks, Anthony

Re: [PATCH] Input: synaptics - fix device info appearing different on reconnect

Any comments on this patch? Thanks, Anthony

Re: [PATCH v6 3/5] mm: introduce mmap3 for safely defining new mmap flags

On Sat, Aug 26, 2017 at 12:50 PM, Helge Deller wrote: > On 26.08.2017 17:15, Dan Williams wrote: [..] >> I have not seen any patches for parisc pmem+dax enabling so it seems >> too early to worry about these "last mile" enabling features of >> MAP_DIRECT and MAP_SYNC. In particular

Re: [PATCH v6 3/5] mm: introduce mmap3 for safely defining new mmap flags

On Sat, Aug 26, 2017 at 12:50 PM, Helge Deller wrote: > On 26.08.2017 17:15, Dan Williams wrote: [..] >> I have not seen any patches for parisc pmem+dax enabling so it seems >> too early to worry about these "last mile" enabling features of >> MAP_DIRECT and MAP_SYNC. In particular parisc doesn't

Re: [PATCH] swap: Remove obsolete sentence

On Fri, 25 Aug 2017 14:29:00 +0300 Nikolay Borisov wrote: > Currently there are no ->swap_{in,out} method in address_space_operations > sructure definition, so the statement that anything is going to be proxied > through them is wrong. > > Signed-off-by: Nikolay Borisov

Re: [PATCH] swap: Remove obsolete sentence

On Fri, 25 Aug 2017 14:29:00 +0300 Nikolay Borisov wrote: > Currently there are no ->swap_{in,out} method in address_space_operations > sructure definition, so the statement that anything is going to be proxied > through them is wrong. > > Signed-off-by: Nikolay Borisov > --- >

Re: [PATCH 0/4] Fix problems on building documentation with Sphinx 1.6

On Sat, 26 Aug 2017 06:28:24 -0300 Mauro Carvalho Chehab wrote: > IMHO, the best is if I apply patch 2 on my trees. Please apply > patches 1 and 3 on your tree. > > Patch 4 can only be applied after patch 2 gets merged, but it > is just a cleanup patch that can be

Re: [PATCH 0/4] Fix problems on building documentation with Sphinx 1.6

On Sat, 26 Aug 2017 06:28:24 -0300 Mauro Carvalho Chehab wrote: > IMHO, the best is if I apply patch 2 on my trees. Please apply > patches 1 and 3 on your tree. > > Patch 4 can only be applied after patch 2 gets merged, but it > is just a cleanup patch that can be applied any time later. OK,

Loan Offer

Do you need a loan @ 3% interest rates? If yes reply now by contacting us via: thomasmarklo...@gmail.com

Loan Offer

Do you need a loan @ 3% interest rates? If yes reply now by contacting us via: thomasmarklo...@gmail.com

Re: [PATCH v4 4/5] net: stmmac: dwmac-sun8i: choose internal PHY via phy-is-integrated

Hi Corentin I think we have now all agreed this is an mdio-mux, plus it is also an MII mux. We should represent that in device tree. This patchset does this. However, as it is now, the mux structure in DT is ignored. All it does is search for the phy-is-integrated flags and goes on that. I made

Re: [PATCH v4 4/5] net: stmmac: dwmac-sun8i: choose internal PHY via phy-is-integrated

Hi Corentin I think we have now all agreed this is an mdio-mux, plus it is also an MII mux. We should represent that in device tree. This patchset does this. However, as it is now, the mux structure in DT is ignored. All it does is search for the phy-is-integrated flags and goes on that. I made

[PATCH 1/2] crypto: n2 - remove null check before kfree

kfree on NULL pointer is a no-op and therefore checking it is redundant. Signed-off-by: Himanshu Jha --- drivers/crypto/n2_core.c | 12 1 file changed, 4 insertions(+), 8 deletions(-) diff --git a/drivers/crypto/n2_core.c b/drivers/crypto/n2_core.c

[PATCH 1/2] crypto: n2 - remove null check before kfree

kfree on NULL pointer is a no-op and therefore checking it is redundant. Signed-off-by: Himanshu Jha --- drivers/crypto/n2_core.c | 12 1 file changed, 4 insertions(+), 8 deletions(-) diff --git a/drivers/crypto/n2_core.c b/drivers/crypto/n2_core.c index a9fd8b9..48de52c 100644

[PATCH 2/2] crypto: inside-secure - remove null check before kfree

Kfree on NULL pointer is a no-op and therefore checking is redundant. Signed-off-by: Himanshu Jha --- drivers/crypto/inside-secure/safexcel_hash.c | 6 ++ 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/drivers/crypto/inside-secure/safexcel_hash.c

[PATCH 0/2] remove NULL check before kfree

*** BLURB HERE *** Himanshu Jha (2): crypto: n2 - remove null check before kfree crypto: inside-secure - remove null check before kfree drivers/crypto/inside-secure/safexcel_hash.c | 6 ++ drivers/crypto/n2_core.c | 12 2 files changed, 6 insertions(+),

[PATCH 2/2] crypto: inside-secure - remove null check before kfree

Kfree on NULL pointer is a no-op and therefore checking is redundant. Signed-off-by: Himanshu Jha --- drivers/crypto/inside-secure/safexcel_hash.c | 6 ++ 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/drivers/crypto/inside-secure/safexcel_hash.c

[PATCH 0/2] remove NULL check before kfree

*** BLURB HERE *** Himanshu Jha (2): crypto: n2 - remove null check before kfree crypto: inside-secure - remove null check before kfree drivers/crypto/inside-secure/safexcel_hash.c | 6 ++ drivers/crypto/n2_core.c | 12 2 files changed, 6 insertions(+),

Re: + mm-madvise-fix-freeing-of-locked-page-with-madv_free.patch added to -mm tree

On Fri, Aug 25, 2017 at 04:41:36PM -0700, Mike Kravetz wrote: > > > > If madvise(..., MADV_FREE) split a transparent hugepage, it called > > put_page() before unlock_page(). This was wrong because put_page() can > > free the page, e.g. if a concurrent madvise(..., MADV_DONTNEED)

Re: + mm-madvise-fix-freeing-of-locked-page-with-madv_free.patch added to -mm tree

On Fri, Aug 25, 2017 at 04:41:36PM -0700, Mike Kravetz wrote: > > > > If madvise(..., MADV_FREE) split a transparent hugepage, it called > > put_page() before unlock_page(). This was wrong because put_page() can > > free the page, e.g. if a concurrent madvise(..., MADV_DONTNEED)

[PATCH 3/3] [media] usbvision: Improve a size determination in usbvision_alloc()

From: Markus Elfring Date: Sat, 26 Aug 2017 22:22:13 +0200 Replace the specification of a data structure by a pointer dereference as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style

[PATCH 3/3] [media] usbvision: Improve a size determination in usbvision_alloc()

From: Markus Elfring Date: Sat, 26 Aug 2017 22:22:13 +0200 Replace the specification of a data structure by a pointer dereference as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style convention. This issue was

[PATCH] [media] atomisp2: Remove null check before kfree

Kfree on NULL pointer is a no-op and therefore checking is redundant. Signed-off-by: Himanshu Jha --- .../staging/media/atomisp/pci/atomisp2/css2400/sh_css_firmware.c| 6 ++ 1 file changed, 2 insertions(+), 4 deletions(-) diff --git

[PATCH] [media] atomisp2: Remove null check before kfree

Kfree on NULL pointer is a no-op and therefore checking is redundant. Signed-off-by: Himanshu Jha --- .../staging/media/atomisp/pci/atomisp2/css2400/sh_css_firmware.c| 6 ++ 1 file changed, 2 insertions(+), 4 deletions(-) diff --git

[PATCH 2/3] [media] usbvision: Adjust eight checks for null pointers

From: Markus Elfring Date: Sat, 26 Aug 2017 22:16:52 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The script “checkpatch.pl” pointed information out like the following. Comparison to NULL could be written !… Thus

[PATCH 2/3] [media] usbvision: Adjust eight checks for null pointers

From: Markus Elfring Date: Sat, 26 Aug 2017 22:16:52 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The script “checkpatch.pl” pointed information out like the following. Comparison to NULL could be written !… Thus fix the affected source code

[PATCH 1/3] [media] usbvision: Delete an error message for a failed memory allocation in usbvision_probe()

From: Markus Elfring Date: Sat, 26 Aug 2017 22:06:05 +0200 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

[PATCH 1/3] [media] usbvision: Delete an error message for a failed memory allocation in usbvision_probe()

From: Markus Elfring Date: Sat, 26 Aug 2017 22:06:05 +0200 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring --- drivers/media/usb/usbvision/usbvision-video.c | 1 - 1 file changed,

[PATCH 0/3] [media] usbvision: Adjustments for six function implementations

From: Markus Elfring Date: Sat, 26 Aug 2017 22:36:54 +0200 A few update suggestions were taken into account from static source code analysis. Markus Elfring (3): Delete an error message for a failed memory allocation in usbvision_probe() Adjust eight checks

[PATCH 0/3] [media] usbvision: Adjustments for six function implementations

From: Markus Elfring Date: Sat, 26 Aug 2017 22:36:54 +0200 A few update suggestions were taken into account from static source code analysis. Markus Elfring (3): Delete an error message for a failed memory allocation in usbvision_probe() Adjust eight checks for null pointers Improve a

Re: [PATCHv3] uapi libc compat: add fallback for unsupported libcs

On 07/29/2017 04:02 PM, Felix Janda wrote: > libc-compat.h aims to prevent symbol collisions between uapi and libc > headers for each supported libc. This requires continuous coordination > between them. > > The goal of this commit is to improve the situation for libcs (such as > musl) which are

Re: [PATCHv3] uapi libc compat: add fallback for unsupported libcs

On 07/29/2017 04:02 PM, Felix Janda wrote: > libc-compat.h aims to prevent symbol collisions between uapi and libc > headers for each supported libc. This requires continuous coordination > between them. > > The goal of this commit is to improve the situation for libcs (such as > musl) which are

[PATCH] net: ethernet: broadcom: Remove null check before kfree

Kfree on NULL pointer is a no-op and therefore checking is redundant. Signed-off-by: Himanshu Jha --- drivers/net/ethernet/broadcom/sb1250-mac.c | 12 1 file changed, 4 insertions(+), 8 deletions(-) diff --git

[PATCH] net: ethernet: broadcom: Remove null check before kfree

Kfree on NULL pointer is a no-op and therefore checking is redundant. Signed-off-by: Himanshu Jha --- drivers/net/ethernet/broadcom/sb1250-mac.c | 12 1 file changed, 4 insertions(+), 8 deletions(-) diff --git a/drivers/net/ethernet/broadcom/sb1250-mac.c

Re: [PATCH v6 3/5] mm: introduce mmap3 for safely defining new mmap flags

On 26.08.2017 17:15, Dan Williams wrote: > On Sat, Aug 26, 2017 at 12:40 AM, Helge Deller wrote: >> * Dan Williams : >>> On Fri, Aug 25, 2017 at 9:19 AM, Helge Deller wrote: On 25.08.2017 18:16, Kirill A. Shutemov wrote: > On Fri,

Re: [PATCH v6 3/5] mm: introduce mmap3 for safely defining new mmap flags

On 26.08.2017 17:15, Dan Williams wrote: > On Sat, Aug 26, 2017 at 12:40 AM, Helge Deller wrote: >> * Dan Williams : >>> On Fri, Aug 25, 2017 at 9:19 AM, Helge Deller wrote: On 25.08.2017 18:16, Kirill A. Shutemov wrote: > On Fri, Aug 25, 2017 at 09:02:36AM -0700, Christoph Hellwig

Re: [PATCH v3 36/59] KVM: arm: Select ARM_GIC_V3 and ARM_GIC_V3_ITS

On Mon, Jul 31, 2017 at 06:26:14PM +0100, Marc Zyngier wrote: > The GICv4 support introduces a hard dependency between the KVM > core and the ITS infrastructure. arm64 already selects it at > the architecture level, but 32bit doesn't. In order to avoid > littering the kernel with #ifdefs, let's

Re: [PATCH v3 36/59] KVM: arm: Select ARM_GIC_V3 and ARM_GIC_V3_ITS

On Mon, Jul 31, 2017 at 06:26:14PM +0100, Marc Zyngier wrote: > The GICv4 support introduces a hard dependency between the KVM > core and the ITS infrastructure. arm64 already selects it at > the architecture level, but 32bit doesn't. In order to avoid > littering the kernel with #ifdefs, let's

Re: [PATCH v3 39/59] KVM: arm/arm64: GICv4: Add property field and per-VM predicate

On Mon, Jul 31, 2017 at 06:26:17PM +0100, Marc Zyngier wrote: > Add a new has_gicv4 field in the global VGIC state that indicates > whether the HW is GICv4 capable, as a per-VM predicate indicating > if there is a possibility for a VM to support direct injection > (the above being true and the VM

Re: [PATCH v3 39/59] KVM: arm/arm64: GICv4: Add property field and per-VM predicate

On Mon, Jul 31, 2017 at 06:26:17PM +0100, Marc Zyngier wrote: > Add a new has_gicv4 field in the global VGIC state that indicates > whether the HW is GICv4 capable, as a per-VM predicate indicating > if there is a possibility for a VM to support direct injection > (the above being true and the VM

  1   2   3   4   5   >