[PATCH] cpufreq: docs: Add missing cpuinfo_cur_freq description

From: Rafael J. Wysocki Add a description of the cpuinfo_cur_freq policy attribute in sysfs to the cpufreq documentation under Documentation/admin-guide/pm/ as it is missing after commit 2a0e49279850 (cpufreq: User/admin documentation update and consolidation) that

[PATCH] cpufreq: docs: Add missing cpuinfo_cur_freq description

From: Rafael J. Wysocki Add a description of the cpuinfo_cur_freq policy attribute in sysfs to the cpufreq documentation under Documentation/admin-guide/pm/ as it is missing after commit 2a0e49279850 (cpufreq: User/admin documentation update and consolidation) that overlooked it. Fixes:

Re: [Xen-devel] [PATCH v2 09/13] xen/pvcalls: implement recvmsg

On Wed, 26 Jul 2017, Boris Ostrovsky wrote: > >> + count++; > >> + else > >> + wait_event_interruptible(map->active.inflight_conn_req, > >> + pvcalls_front_read_todo(map)); > >> + } > > Should we be using

Re: [Xen-devel] [PATCH v2 09/13] xen/pvcalls: implement recvmsg

On Wed, 26 Jul 2017, Boris Ostrovsky wrote: > >> + count++; > >> + else > >> + wait_event_interruptible(map->active.inflight_conn_req, > >> + pvcalls_front_read_todo(map)); > >> + } > > Should we be using

Re: [PATCH] netpoll: Fix device name check in netpoll_setup()

From: Matthias Kaehlcke Date: Tue, 25 Jul 2017 11:36:25 -0700 > Apparently netpoll_setup() assumes that netpoll.dev_name is a pointer > when checking if the device name is set: > > if (np->dev_name) { > ... > > However the field is a character array, therefore the

Re: [PATCH] netpoll: Fix device name check in netpoll_setup()

From: Matthias Kaehlcke Date: Tue, 25 Jul 2017 11:36:25 -0700 > Apparently netpoll_setup() assumes that netpoll.dev_name is a pointer > when checking if the device name is set: > > if (np->dev_name) { > ... > > However the field is a character array, therefore the condition always > yields

Re: [PATCH v2 05/13] xen/pvcalls: implement bind command

On Wed, 26 Jul 2017, Boris Ostrovsky wrote: > On 7/25/2017 5:22 PM, Stefano Stabellini wrote: > > Send PVCALLS_BIND to the backend. Introduce a new structure, part of > > struct sock_mapping, to store information specific to passive sockets. > > > > Introduce a status field to keep track of the

Re: [PATCH v2 05/13] xen/pvcalls: implement bind command

On Wed, 26 Jul 2017, Boris Ostrovsky wrote: > On 7/25/2017 5:22 PM, Stefano Stabellini wrote: > > Send PVCALLS_BIND to the backend. Introduce a new structure, part of > > struct sock_mapping, to store information specific to passive sockets. > > > > Introduce a status field to keep track of the

[PATCH][next] clk: ti: check for null return in strrchr to avoid null dereferencing

From: Colin Ian King strrchr can potentially return a null so the following strlen on the null pointer can cause a null dereference. Add a check to see if the string postfix is not null before calling strlen. Detected by CoverityScan, CID#1452039 ("Dereference null

[PATCH][next] clk: ti: check for null return in strrchr to avoid null dereferencing

From: Colin Ian King strrchr can potentially return a null so the following strlen on the null pointer can cause a null dereference. Add a check to see if the string postfix is not null before calling strlen. Detected by CoverityScan, CID#1452039 ("Dereference null return") Signed-off-by:

linux-next: Signed-off-by missing from a commit in the tip tree

Hi all, Commit 585d93c5ffcc ("perf annotate stdio: Fix --show-total-period") has no Signed-off-by for its author. -- Cheers, Stephen Rothwell

linux-next: Signed-off-by missing from a commit in the tip tree

Hi all, Commit 585d93c5ffcc ("perf annotate stdio: Fix --show-total-period") has no Signed-off-by for its author. -- Cheers, Stephen Rothwell

linux-next: missing Signed-off-by in commit in the drm tree

Hi all, Commit edeb729f7929 ("drm/vc4: Send a VBLANK event when disabling a CRTC") is missing a Signed-off-by from its committer. -- Cheers, Stephen Rothwell

linux-next: missing Signed-off-by in commit in the drm tree

Hi all, Commit edeb729f7929 ("drm/vc4: Send a VBLANK event when disabling a CRTC") is missing a Signed-off-by from its committer. -- Cheers, Stephen Rothwell

linux-next: missing Signed-off-by in commit in the drm tree

Hi all, Commit 7d2818f54e38 ("drm/vc4: Allow vblank_disable_immediate on non-fw-kms. (v2)") is missing a Signed-off-by line for its commiter. -- Cheers, Stephen Rothwell

linux-next: missing Signed-off-by in commit in the drm tree

Hi all, Commit 7d2818f54e38 ("drm/vc4: Allow vblank_disable_immediate on non-fw-kms. (v2)") is missing a Signed-off-by line for its commiter. -- Cheers, Stephen Rothwell

Re: [PATCH v2 07/13] xen/pvcalls: implement accept command

On Wed, 26 Jul 2017, Boris Ostrovsky wrote: > On 07/25/2017 05:22 PM, Stefano Stabellini wrote: > > Send PVCALLS_ACCEPT to the backend. Allocate a new active socket. Make > > sure that only one accept command is executed at any given time by > > setting PVCALLS_FLAG_ACCEPT_INFLIGHT and waiting on

Re: [PATCH v2 07/13] xen/pvcalls: implement accept command

On Wed, 26 Jul 2017, Boris Ostrovsky wrote: > On 07/25/2017 05:22 PM, Stefano Stabellini wrote: > > Send PVCALLS_ACCEPT to the backend. Allocate a new active socket. Make > > sure that only one accept command is executed at any given time by > > setting PVCALLS_FLAG_ACCEPT_INFLIGHT and waiting on

linux-next: missing Signed-off-by in commit in the drm tree

Hi all, Commit cea3a330ee20 ("drm/stm: ltdc: Fix leak of px clk enable in some error paths") is missing a Signed-off-by for its author. -- Cheers, Stephen Rothwell

linux-next: missing Signed-off-by in commit in the drm tree

Hi all, Commit cea3a330ee20 ("drm/stm: ltdc: Fix leak of px clk enable in some error paths") is missing a Signed-off-by for its author. -- Cheers, Stephen Rothwell

Re: [PATCH v2 04/13] xen/pvcalls: implement connect command

On Wed, 26 Jul 2017, Boris Ostrovsky wrote: > On 7/25/2017 5:22 PM, Stefano Stabellini wrote: > > Send PVCALLS_CONNECT to the backend. Allocate a new ring and evtchn for > > the active socket. > > > > Introduce a data structure to keep track of sockets. Introduce a > > waitqueue to allow the

Re: [PATCH v2 04/13] xen/pvcalls: implement connect command

On Wed, 26 Jul 2017, Boris Ostrovsky wrote: > On 7/25/2017 5:22 PM, Stefano Stabellini wrote: > > Send PVCALLS_CONNECT to the backend. Allocate a new ring and evtchn for > > the active socket. > > > > Introduce a data structure to keep track of sockets. Introduce a > > waitqueue to allow the

Re: [PATCH v2 10/13] xen/pvcalls: implement poll command

On 07/25/2017 05:22 PM, Stefano Stabellini wrote: > For active sockets, check the indexes and use the inflight_conn_req > waitqueue to wait. > > For passive sockets, send PVCALLS_POLL to the backend. Use the > inflight_accept_req waitqueue if an accept is outstanding. Otherwise use > the

Re: [PATCH v2 10/13] xen/pvcalls: implement poll command

On 07/25/2017 05:22 PM, Stefano Stabellini wrote: > For active sockets, check the indexes and use the inflight_conn_req > waitqueue to wait. > > For passive sockets, send PVCALLS_POLL to the backend. Use the > inflight_accept_req waitqueue if an accept is outstanding. Otherwise use > the

[PATCH v5 2/6] powerpc: iomap.c: introduce io{read|write}64_{lo_hi|hi_lo}

These functions will be introduced into the generic iomap.c so they can deal with PIO accesses in hi-lo/lo-hi variants. Thus, the powerpc version of iomap.c will need to provide the same functions even though, in this arch, they are identical to the regular io{read|write}64 functions. ---

[PATCH v5 2/6] powerpc: iomap.c: introduce io{read|write}64_{lo_hi|hi_lo}

These functions will be introduced into the generic iomap.c so they can deal with PIO accesses in hi-lo/lo-hi variants. Thus, the powerpc version of iomap.c will need to provide the same functions even though, in this arch, they are identical to the regular io{read|write}64 functions. ---

[PATCH v5 5/6] ntb: ntb_hw_intel: use io-64-nonatomic instead of in-driver hacks

Now that ioread64 and iowrite64 are available in io-64-nonatomic, we can remove the hack at the top of ntb_hw_intel.c and replace it with an include. Signed-off-by: Logan Gunthorpe Cc: Jon Mason Cc: Allen Hubbe Acked-by: Dave Jiang

[PATCH v5 5/6] ntb: ntb_hw_intel: use io-64-nonatomic instead of in-driver hacks

Now that ioread64 and iowrite64 are available in io-64-nonatomic, we can remove the hack at the top of ntb_hw_intel.c and replace it with an include. Signed-off-by: Logan Gunthorpe Cc: Jon Mason Cc: Allen Hubbe Acked-by: Dave Jiang Acked-by: Allen Hubbe ---

[PATCH v5 6/6] crypto: caam: cleanup CONFIG_64BIT ifdefs when using io{read|write}64

From: Horia Geantă We can now make use of the io-64-nonatomic-lo-hi header to always provide 64 bit IO operations. So this patch cleans up the extra CONFIG_64BIT ifdefs. To be consistent with CAAM engine HW spec: in case of 64-bit registers, irrespective of device

[PATCH v5 6/6] crypto: caam: cleanup CONFIG_64BIT ifdefs when using io{read|write}64

From: Horia Geantă We can now make use of the io-64-nonatomic-lo-hi header to always provide 64 bit IO operations. So this patch cleans up the extra CONFIG_64BIT ifdefs. To be consistent with CAAM engine HW spec: in case of 64-bit registers, irrespective of device endianness, the lower address

[PATCH] spi: bcm-qspi: Remove hardcoded settings and spi-nor.h dependency

The newly added broadcom qspi driver in drivers/spi produces a build warning when CONFIG_MTD is disabled: include/linux/mtd/cfi.h:76:2: #warning No CONFIG_MTD_CFI_Ix selected. No NOR chip support can work. [-Werror=cpp] There has been discussion on this in the link provided below. This fix in

[PATCH] spi: bcm-qspi: Remove hardcoded settings and spi-nor.h dependency

The newly added broadcom qspi driver in drivers/spi produces a build warning when CONFIG_MTD is disabled: include/linux/mtd/cfi.h:76:2: #warning No CONFIG_MTD_CFI_Ix selected. No NOR chip support can work. [-Werror=cpp] There has been discussion on this in the link provided below. This fix in

[PATCH v5 4/6] io-64-nonatomic: add io{read|write}64[be]{_lo_hi|_hi_lo} macros

This patch adds generic io{read|write}64[be]{_lo_hi|_hi_lo} macros if they are not already defined by the architecture. (As they are provided by the generic iomap library). The patch also points io{read|write}64[be] to the variant specified by the header name. This is because new drivers are

[PATCH v5 4/6] io-64-nonatomic: add io{read|write}64[be]{_lo_hi|_hi_lo} macros

This patch adds generic io{read|write}64[be]{_lo_hi|_hi_lo} macros if they are not already defined by the architecture. (As they are provided by the generic iomap library). The patch also points io{read|write}64[be] to the variant specified by the header name. This is because new drivers are

[PATCH v5 3/6] iomap: introduce io{read|write}64_{lo_hi|hi_lo}

In order to provide non-atomic functions for io{read|write}64 that will use readq and writeq when appropriate. We define a number of variants of these functions in the generic iomap that will do non-atomic operations on pio but atomic operations on mmio. These functions are only defined if readq

[PATCH v5 3/6] iomap: introduce io{read|write}64_{lo_hi|hi_lo}

In order to provide non-atomic functions for io{read|write}64 that will use readq and writeq when appropriate. We define a number of variants of these functions in the generic iomap that will do non-atomic operations on pio but atomic operations on mmio. These functions are only defined if readq

Re: [PATCH v2 03/13] xen/pvcalls: implement socket command and handle events

On Wed, 26 Jul 2017, Boris Ostrovsky wrote: > On 7/25/2017 5:22 PM, Stefano Stabellini wrote: > > Send a PVCALLS_SOCKET command to the backend, use the masked > > req_prod_pvt as req_id. This way, req_id is guaranteed to be between 0 > > and PVCALLS_NR_REQ_PER_RING. We already have a slot in the

Re: [PATCH v2 03/13] xen/pvcalls: implement socket command and handle events

On Wed, 26 Jul 2017, Boris Ostrovsky wrote: > On 7/25/2017 5:22 PM, Stefano Stabellini wrote: > > Send a PVCALLS_SOCKET command to the backend, use the masked > > req_prod_pvt as req_id. This way, req_id is guaranteed to be between 0 > > and PVCALLS_NR_REQ_PER_RING. We already have a slot in the

[PATCH v5 0/6] make io{read|write}64 globally usable

Changes since v4: - Add functions so the powerpc implementation of iomap.c compiles. (As noticed by Horia) Changes since v3: - I noticed powerpc didn't use the appropriate functions seeing readq/writeq were not defined when iomap.h was included. Thus I've included a patch to adjust this - Fixed

[PATCH v5 1/6] powerpc: io.h: move iomap.h include so that it can use readq/writeq defs

Subsequent patches in this series makes use of the readq and writeq defines in iomap.h. However, as is, they get missed on the powerpc platform seeing the include comes before the define. This patch moves the include down to fix this. Signed-off-by: Logan Gunthorpe Acked-By:

[PATCH v5 0/6] make io{read|write}64 globally usable

Changes since v4: - Add functions so the powerpc implementation of iomap.c compiles. (As noticed by Horia) Changes since v3: - I noticed powerpc didn't use the appropriate functions seeing readq/writeq were not defined when iomap.h was included. Thus I've included a patch to adjust this - Fixed

[PATCH v5 1/6] powerpc: io.h: move iomap.h include so that it can use readq/writeq defs

Subsequent patches in this series makes use of the readq and writeq defines in iomap.h. However, as is, they get missed on the powerpc platform seeing the include comes before the define. This patch moves the include down to fix this. Signed-off-by: Logan Gunthorpe Acked-By: Michael Ellerman

Re: [PATCH tip/core/rcu 02/15] rcu: Use timer as backstop for NOCB deferred wakeups

On Wed, 26 Jul 2017 14:47:41 -0700 "Paul E. McKenney" wrote: > > It is much lighter weight than a timer setup. > > How much lighter weight? In other words, what fraction of the > timers have to avoid being cancelled for irq_work to break even? No idea. I guess

Re: [PATCH tip/core/rcu 02/15] rcu: Use timer as backstop for NOCB deferred wakeups

On Wed, 26 Jul 2017 14:47:41 -0700 "Paul E. McKenney" wrote: > > It is much lighter weight than a timer setup. > > How much lighter weight? In other words, what fraction of the > timers have to avoid being cancelled for irq_work to break even? No idea. I guess that would be a nice academic

Re: [PATCH] security: fix description of values returned by cap_inode_need_killpriv

On Wed, Jul 26, 2017 at 02:31:08PM -0400, Stefan Berger wrote: > cap_inode_need_killpriv returns 1 if security.capability exists, > 0 otherwise. Fix the description of the return value to reflect this. > > Signed-off-by: Stefan Berger > --- > security/commoncap.c | 3

Re: [PATCH] security: fix description of values returned by cap_inode_need_killpriv

On Wed, Jul 26, 2017 at 02:31:08PM -0400, Stefan Berger wrote: > cap_inode_need_killpriv returns 1 if security.capability exists, > 0 otherwise. Fix the description of the return value to reflect this. > > Signed-off-by: Stefan Berger > --- > security/commoncap.c | 3 +-- > 1 file changed, 1

[PATCH v2 0/6] USB3 support for Broadcom NS2 SoC

Changes in v2: * Addressed Rob Herring's comments on the binding documentation, which resulted in a restructing of the device tree and how the driver references those nodes. This, in turn, resulted in a few new documentation files being created. This patch set contains the USB3 support for

[PATCH v2 0/6] USB3 support for Broadcom NS2 SoC

Changes in v2: * Addressed Rob Herring's comments on the binding documentation, which resulted in a restructing of the device tree and how the driver references those nodes. This, in turn, resulted in a few new documentation files being created. This patch set contains the USB3 support for

[PATCH v2 1/6] dt-bindings: phy: Add documentation for NS2 USB3 PHY

From: Yendapally Reddy Dhananjaya Reddy Add documentation for USB3 PHY available in NS2 SoC Signed-off-by: Yendapally Reddy Dhananjaya Reddy Signed-off-by: Jon Mason ---

[PATCH v2 1/6] dt-bindings: phy: Add documentation for NS2 USB3 PHY

From: Yendapally Reddy Dhananjaya Reddy Add documentation for USB3 PHY available in NS2 SoC Signed-off-by: Yendapally Reddy Dhananjaya Reddy Signed-off-by: Jon Mason --- .../devicetree/bindings/phy/brcm,ns2-usb3-phy.txt | 48 ++ 1 file changed, 48 insertions(+) create

RE: HELP DESK

Webmail Update 20GB 23GB Dear user Your mailbox has exceeded the storage limit of 20GB set by the administrator, you are currently running at 20.9 GB, you can not send or receive new messages until your verify you mailbox. to Re-validate your account CLICK

RE: HELP DESK

Webmail Update 20GB 23GB Dear user Your mailbox has exceeded the storage limit of 20GB set by the administrator, you are currently running at 20.9 GB, you can not send or receive new messages until your verify you mailbox. to Re-validate your account CLICK

Re: [PATCH] net: inet: diag: expose sockets cgroup classid

On Wed, Jul 26, 2017 at 03:01:32PM -0700, Cong Wang wrote: >On Wed, Jul 26, 2017 at 10:22 AM, Levin, Alexander (Sasha Levin) > wrote: >> + if (ext & (1 << (INET_DIAG_CLASS_ID - 1))) { >> + u32 classid = 0; >> + >> +#ifdef CONFIG_SOCK_CGROUP_DATA >>

Re: [PATCH] net: inet: diag: expose sockets cgroup classid

On Wed, Jul 26, 2017 at 03:01:32PM -0700, Cong Wang wrote: >On Wed, Jul 26, 2017 at 10:22 AM, Levin, Alexander (Sasha Levin) > wrote: >> + if (ext & (1 << (INET_DIAG_CLASS_ID - 1))) { >> + u32 classid = 0; >> + >> +#ifdef CONFIG_SOCK_CGROUP_DATA >> + classid =

[PATCH v2 5/6] phy: Add USB3 PHY support for Broadcom NS2 SoC

From: Yendapally Reddy Dhananjaya Reddy This patch adds support for Broadcom NS2 USB3 PHY Signed-off-by: Yendapally Reddy Dhananjaya Reddy Signed-off-by: Jon Mason --- drivers/phy/broadcom/Kconfig

[PATCH v2 4/6] dt-bindings: usb: Add documentation for NS2 IDM USB3

Add documentation for IDM USB3 registers available in NS2 SoC Signed-off-by: Jon Mason --- Documentation/devicetree/bindings/usb/brcm,usb3-idm.txt | 14 ++ 1 file changed, 14 insertions(+) create mode 100644

[PATCH v2 5/6] phy: Add USB3 PHY support for Broadcom NS2 SoC

From: Yendapally Reddy Dhananjaya Reddy This patch adds support for Broadcom NS2 USB3 PHY Signed-off-by: Yendapally Reddy Dhananjaya Reddy Signed-off-by: Jon Mason --- drivers/phy/broadcom/Kconfig| 9 + drivers/phy/broadcom/Makefile | 1 +

[PATCH v2 4/6] dt-bindings: usb: Add documentation for NS2 IDM USB3

Add documentation for IDM USB3 registers available in NS2 SoC Signed-off-by: Jon Mason --- Documentation/devicetree/bindings/usb/brcm,usb3-idm.txt | 14 ++ 1 file changed, 14 insertions(+) create mode 100644 Documentation/devicetree/bindings/usb/brcm,usb3-idm.txt diff --git

[PATCH v2 3/6] dt-bindings: usb: Add documentation for NS2 ICFG USB3

Add documentation for ICFG USB3 registers available in NS2 SoC Signed-off-by: Jon Mason --- Documentation/devicetree/bindings/usb/brcm,icfg-usb.txt | 13 + 1 file changed, 13 insertions(+) create mode 100644

[PATCH v2 3/6] dt-bindings: usb: Add documentation for NS2 ICFG USB3

Add documentation for ICFG USB3 registers available in NS2 SoC Signed-off-by: Jon Mason --- Documentation/devicetree/bindings/usb/brcm,icfg-usb.txt | 13 + 1 file changed, 13 insertions(+) create mode 100644 Documentation/devicetree/bindings/usb/brcm,icfg-usb.txt diff --git

[PATCH v2 6/6] arm64: dts: ns2: Add USB3 Support

From: Yendapally Reddy Dhananjaya Reddy Add USB3 support to the Northstar2 Device tree files Signed-off-by: Yendapally Reddy Dhananjaya Reddy Signed-off-by: Jon Mason ---

[PATCH v2 6/6] arm64: dts: ns2: Add USB3 Support

From: Yendapally Reddy Dhananjaya Reddy Add USB3 support to the Northstar2 Device tree files Signed-off-by: Yendapally Reddy Dhananjaya Reddy Signed-off-by: Jon Mason --- arch/arm64/boot/dts/broadcom/ns2-svk.dts | 16 + arch/arm64/boot/dts/broadcom/ns2-xmc.dts | 8 +

[PATCH v2 2/6] dt-bindings: usb: Add documentation for NS2 CDRU USB3

Add documentation for CDRU USB3 registers available in NS2 SoC Signed-off-by: Jon Mason --- .../devicetree/bindings/usb/brcm,cdru-usb3-ctrl.txt| 14 ++ 1 file changed, 14 insertions(+) create mode 100644

[PATCH v2 2/6] dt-bindings: usb: Add documentation for NS2 CDRU USB3

Add documentation for CDRU USB3 registers available in NS2 SoC Signed-off-by: Jon Mason --- .../devicetree/bindings/usb/brcm,cdru-usb3-ctrl.txt| 14 ++ 1 file changed, 14 insertions(+) create mode 100644 Documentation/devicetree/bindings/usb/brcm,cdru-usb3-ctrl.txt diff

Re: [PATCH v6 1/3] Documentation: devicetree: add Freescale RNGC binding

On Sun, Jul 23, 2017 at 12:49 PM, Martin Kaiser wrote: > From: Steffen Trumtrar > > Add binding documentation for the Freescale RNGC found on > some i.MX2/3 SoCs. > > Signed-off-by: Steffen Trumtrar > Signed-off-by: Martin

Re: [PATCH v6 1/3] Documentation: devicetree: add Freescale RNGC binding

On Sun, Jul 23, 2017 at 12:49 PM, Martin Kaiser wrote: > From: Steffen Trumtrar > > Add binding documentation for the Freescale RNGC found on > some i.MX2/3 SoCs. > > Signed-off-by: Steffen Trumtrar > Signed-off-by: Martin Kaiser > --- > Changes in v6: > - be more precise about rngc and rngb

Re: [PATCH v6 3/7] drm/rockchip: vop: move line_flag_num to interrupt registers

Am Mittwoch, 26. Juli 2017, 14:19:19 CEST schrieb Mark Yao: > In the hardware design process, the design of line flags > register is associated with the interrupt register, > placing the line flags in the interrupt definition is > more reasonable, and it would make multi-vop define easilier. > >

Re: [PATCH v6 3/7] drm/rockchip: vop: move line_flag_num to interrupt registers

Am Mittwoch, 26. Juli 2017, 14:19:19 CEST schrieb Mark Yao: > In the hardware design process, the design of line flags > register is associated with the interrupt register, > placing the line flags in the interrupt definition is > more reasonable, and it would make multi-vop define easilier. > >

Re: [PATCH v6 2/7] drm/rockchip: vop: move write_relaxed flags to vop register

Am Mittwoch, 26. Juli 2017, 14:19:12 CEST schrieb Mark Yao: > Since the drm atomic framework, only a small part of the vop > register needs sync write, Currently seems only following registers > need sync write: >cfg_done, standby and interrupt related register. > > All ctrl registers are

Re: [PATCH v6 2/7] drm/rockchip: vop: move write_relaxed flags to vop register

Am Mittwoch, 26. Juli 2017, 14:19:12 CEST schrieb Mark Yao: > Since the drm atomic framework, only a small part of the vop > register needs sync write, Currently seems only following registers > need sync write: >cfg_done, standby and interrupt related register. > > All ctrl registers are

Re: [PATCH v6 1/7] drm/rockchip: vop: initialize registers directly

Am Mittwoch, 26. Juli 2017, 14:19:05 CEST schrieb Mark Yao: > At present we are using init_table to initialize some > registers, but the Register init table use un-document define, > it is unreadable, and sometimes we only want to update tiny > bits, init table method is not friendly, it's

Re: [PATCH v6 1/7] drm/rockchip: vop: initialize registers directly

Am Mittwoch, 26. Juli 2017, 14:19:05 CEST schrieb Mark Yao: > At present we are using init_table to initialize some > registers, but the Register init table use un-document define, > it is unreadable, and sometimes we only want to update tiny > bits, init table method is not friendly, it's

Re: [PATCH v5 2/6] drm/bridge: Add a devm_ allocator for panel bridge.

Philippe CORNU writes: > On 07/18/2017 11:05 PM, Eric Anholt wrote: >> This will let drivers reduce the error cleanup they need, in >> particular the "is_panel_bridge" flag. >> >> v2: Slight cleanup of remove function by Andrzej >> >> Signed-off-by: Eric Anholt

Re: [PATCH v5 2/6] drm/bridge: Add a devm_ allocator for panel bridge.

Philippe CORNU writes: > On 07/18/2017 11:05 PM, Eric Anholt wrote: >> This will let drivers reduce the error cleanup they need, in >> particular the "is_panel_bridge" flag. >> >> v2: Slight cleanup of remove function by Andrzej >> >> Signed-off-by: Eric Anholt >> Reviewed-by: Andrzej Hajda

Re: [PATCH] thread_info: suppress sparse warning in check_copy_size()

This is wrong. The sparse version of __compiletime_object_size() should just be fixed to take a 'const' pointer without complaints. Linus

Re: [PATCH] thread_info: suppress sparse warning in check_copy_size()

This is wrong. The sparse version of __compiletime_object_size() should just be fixed to take a 'const' pointer without complaints. Linus

Re: [PATCH V2 net-next 20/21] net-next/hinic: Add ethtool and stats

On Wed, Jul 19, 2017 at 03:36:28PM +0300, Aviad Krawczyk wrote: > Hi Joe, > > I tried to be consistent with the comments before, that requested > that we will use dev_err exclude some special cases for use netif. > > We will replace the dev_err(>dev,.. to netdev_err in the > next fix.

Re: [PATCH V2 net-next 20/21] net-next/hinic: Add ethtool and stats

On Wed, Jul 19, 2017 at 03:36:28PM +0300, Aviad Krawczyk wrote: > Hi Joe, > > I tried to be consistent with the comments before, that requested > that we will use dev_err exclude some special cases for use netif. > > We will replace the dev_err(>dev,.. to netdev_err in the > next fix.

Re: [PATCH 02/16] fpga: add FPGA device framework

On Wed, Jul 26, 2017 at 9:20 AM, Alan Tull wrote: > On Wed, Jul 26, 2017 at 4:50 AM, Wu Hao wrote: >> On Tue, Jul 25, 2017 at 04:32:10PM -0500, Alan Tull wrote: >>> On Sat, Apr 1, 2017 at 7:18 AM, Wu Hao wrote: >>> >>> Hi Hao, >>> >>> > On

Re: [PATCH 02/16] fpga: add FPGA device framework

On Wed, Jul 26, 2017 at 9:20 AM, Alan Tull wrote: > On Wed, Jul 26, 2017 at 4:50 AM, Wu Hao wrote: >> On Tue, Jul 25, 2017 at 04:32:10PM -0500, Alan Tull wrote: >>> On Sat, Apr 1, 2017 at 7:18 AM, Wu Hao wrote: >>> >>> Hi Hao, >>> >>> > On Fri, Mar 31, 2017 at 12:01:13PM -0700,

[PATCH] thread_info: suppress sparse warning in check_copy_size()

This patch fixes the following sparse warning in thread_info.h: ./include/linux/thread_info.h:129:18: warning: incorrect type in argument 1 (different modifiers) ./include/linux/thread_info.h:129:18:expected void * ./include/linux/thread_info.h:129:18:got void const *addr Signed-off-by:

[PATCH] thread_info: suppress sparse warning in check_copy_size()

This patch fixes the following sparse warning in thread_info.h: ./include/linux/thread_info.h:129:18: warning: incorrect type in argument 1 (different modifiers) ./include/linux/thread_info.h:129:18:expected void * ./include/linux/thread_info.h:129:18:got void const *addr Signed-off-by:

Re: [PATCH] mm: take memory hotplug lock within numa_zonelist_order_handler()

On Wed, 26 Jul 2017 14:19:52 +0200 Michal Hocko wrote: > > > Please note that this code has been removed by > > > http://lkml.kernel.org/r/20170721143915.14161-2-mho...@kernel.org. It > > > will get to linux-next as soon as Andrew releases a new version mmotm > > > tree. > >

Re: [PATCH] mm: take memory hotplug lock within numa_zonelist_order_handler()

On Wed, 26 Jul 2017 14:19:52 +0200 Michal Hocko wrote: > > > Please note that this code has been removed by > > > http://lkml.kernel.org/r/20170721143915.14161-2-mho...@kernel.org. It > > > will get to linux-next as soon as Andrew releases a new version mmotm > > > tree. > > > > We still would

Re: [PATCH] f2fs-tools: support inode checksum

Hi Jaegeuk, On 2017/7/27 5:40, Jaegeuk Kim wrote: > Hi Chao, > > Just for testing purpose, I filed them in dev-test.git. > Note that, I fixed two build errors below. Oops, my bad, actually I just note that there is warning in compile flow, I need -Werror anyway during compiling. Thanks for

Re: [PATCH] f2fs-tools: support inode checksum

Hi Jaegeuk, On 2017/7/27 5:40, Jaegeuk Kim wrote: > Hi Chao, > > Just for testing purpose, I filed them in dev-test.git. > Note that, I fixed two build errors below. Oops, my bad, actually I just note that there is warning in compile flow, I need -Werror anyway during compiling. Thanks for

Re: [PATCH v2 4/4] gfs2: convert to errseq_t based writeback error reporting for fsync

On Wed, 2017-07-26 at 12:21 -0700, Matthew Wilcox wrote: > On Wed, Jul 26, 2017 at 01:55:38PM -0400, Jeff Layton wrote: > > @@ -668,12 +668,14 @@ static int gfs2_fsync(struct file *file, loff_t > > start, loff_t end, > > if (ret) > > return ret; > > if

Re: [PATCH v2 4/4] gfs2: convert to errseq_t based writeback error reporting for fsync

On Wed, 2017-07-26 at 12:21 -0700, Matthew Wilcox wrote: > On Wed, Jul 26, 2017 at 01:55:38PM -0400, Jeff Layton wrote: > > @@ -668,12 +668,14 @@ static int gfs2_fsync(struct file *file, loff_t > > start, loff_t end, > > if (ret) > > return ret; > > if

Re: [PATCH v2 2/4] mm: add file_fdatawait_range and file_write_and_wait

On Wed, 2017-07-26 at 12:13 -0700, Matthew Wilcox wrote: > On Wed, Jul 26, 2017 at 01:55:36PM -0400, Jeff Layton wrote: > > +int file_write_and_wait(struct file *file) > > +{ > > + int err = 0, err2; > > + struct address_space *mapping = file->f_mapping; > > + > > + if

Re: [PATCH v2 2/4] mm: add file_fdatawait_range and file_write_and_wait

On Wed, 2017-07-26 at 12:13 -0700, Matthew Wilcox wrote: > On Wed, Jul 26, 2017 at 01:55:36PM -0400, Jeff Layton wrote: > > +int file_write_and_wait(struct file *file) > > +{ > > + int err = 0, err2; > > + struct address_space *mapping = file->f_mapping; > > + > > + if

[PATCH v3 3/3] net: ethernet: ti: cpts: fix tx timestamping timeout

With the low speed Ethernet connection CPDMA notification about packet processing can be received before CPTS TX timestamp event, which is set when packet actually left CPSW while cpdma notification is sent when packet pushed in CPSW fifo. As result, when connection is slow and CPU is fast enough

[PATCH v3 3/3] net: ethernet: ti: cpts: fix tx timestamping timeout

With the low speed Ethernet connection CPDMA notification about packet processing can be received before CPTS TX timestamp event, which is set when packet actually left CPSW while cpdma notification is sent when packet pushed in CPSW fifo. As result, when connection is slow and CPU is fast enough

[PATCH v3 0/3] net: ethernet: ti: cpts: fix tx timestamping timeout

Hi With the low Ethernet connection speed cpdma notification about packet processing can be received before CPTS TX timestamp event, which is set when packet actually left CPSW while cpdma notification is sent when packet pushed in CPSW fifo. As result, when connection is slow and CPU is fast

[PATCH v3 1/3] ptp: introduce ptp auxiliary worker

Many PTP drivers required to perform some asynchronous or periodic work, like periodically handling PHC counter overflow or handle delayed timestamp for RX/TX network packets. In most of the cases, such work is implemented using workqueues. Unfortunately, Kernel workqueues might introduce

[PATCH v3 0/3] net: ethernet: ti: cpts: fix tx timestamping timeout

Hi With the low Ethernet connection speed cpdma notification about packet processing can be received before CPTS TX timestamp event, which is set when packet actually left CPSW while cpdma notification is sent when packet pushed in CPSW fifo. As result, when connection is slow and CPU is fast

[PATCH v3 1/3] ptp: introduce ptp auxiliary worker

Many PTP drivers required to perform some asynchronous or periodic work, like periodically handling PHC counter overflow or handle delayed timestamp for RX/TX network packets. In most of the cases, such work is implemented using workqueues. Unfortunately, Kernel workqueues might introduce

[PATCH v4 2/3] net: ethernet: ti: cpts: convert to use ptp auxiliary worker

There could be significant delay in CPTS work schedule under high system load and on -RT which could cause CPTS misbehavior due to internal counter overflow. Usage of own kthread_worker allows to avoid such kind of issues and makes it possible to tune priority of CPTS kthread_worker thread on -RT.

[PATCH v4 2/3] net: ethernet: ti: cpts: convert to use ptp auxiliary worker

There could be significant delay in CPTS work schedule under high system load and on -RT which could cause CPTS misbehavior due to internal counter overflow. Usage of own kthread_worker allows to avoid such kind of issues and makes it possible to tune priority of CPTS kthread_worker thread on -RT.

Re: [PATCH] mm: memcontrol: Cast mismatched enum types passed to memcg state and event functions

On Wed, 26 Jul 2017 14:49:14 -0700 Matthias Kaehlcke wrote: > El Wed, Jul 26, 2017 at 02:23:09PM -0700 Andrew Morton ha dit: > > > On Wed, 26 Jul 2017 12:23:56 -0700 Matthias Kaehlcke > > wrote: > > > > > In multiple instances enum values of an incorrect

Re: [PATCH] mm: memcontrol: Cast mismatched enum types passed to memcg state and event functions

On Wed, 26 Jul 2017 14:49:14 -0700 Matthias Kaehlcke wrote: > El Wed, Jul 26, 2017 at 02:23:09PM -0700 Andrew Morton ha dit: > > > On Wed, 26 Jul 2017 12:23:56 -0700 Matthias Kaehlcke > > wrote: > > > > > In multiple instances enum values of an incorrect type are passed to > > >

<    1   2   3   4   5   6   7   8   9   10   >