Re: [PATCH] btrfs: Remove some dead code

On 2016-11-01 at 11:26:06 +0100, Christophe JAILLET wrote: > 'btrfs_iget()' can not return an error pointer, so this test can be > removed. This descrption does not match what the patch actually does. Shouldn't it say "...can not return NULL, so this test can be

Re: [PATCH] btrfs: Remove some dead code

On 2016-11-01 at 11:26:06 +0100, Christophe JAILLET wrote: > 'btrfs_iget()' can not return an error pointer, so this test can be > removed. This descrption does not match what the patch actually does. Shouldn't it say "...can not return NULL, so this test can be removed."? > Signed-off-by:

[PATCH 5/6] ARM: add low level debug uart for rk1108

RK1108 UARTs are Synopsis DesignWare 8250 compatible. Only with different register addresses. Signed-off-by: Andy Yan --- arch/arm/Kconfig.debug | 30 ++ 1 file changed, 30 insertions(+) diff --git a/arch/arm/Kconfig.debug

[PATCH 5/6] ARM: add low level debug uart for rk1108

RK1108 UARTs are Synopsis DesignWare 8250 compatible. Only with different register addresses. Signed-off-by: Andy Yan --- arch/arm/Kconfig.debug | 30 ++ 1 file changed, 30 insertions(+) diff --git a/arch/arm/Kconfig.debug b/arch/arm/Kconfig.debug index

[PATCH 4/6] ARM: dts: add basic support for Rockchip RK1108 SOC

RK1108 is embedded with an ARM Cortex-A7 single core and a DSP core. It is designed for varies application scenario such as car DVR, sports DV, secure camera and UAV camera. This patch add basic support for it with DMAC / UART / CRU / pinctrl enabled. Signed-off-by: Andy Yan

[PATCH 4/6] ARM: dts: add basic support for Rockchip RK1108 SOC

RK1108 is embedded with an ARM Cortex-A7 single core and a DSP core. It is designed for varies application scenario such as car DVR, sports DV, secure camera and UAV camera. This patch add basic support for it with DMAC / UART / CRU / pinctrl enabled. Signed-off-by: Andy Yan ---

Re: [PATCH 3/3] [media] au0828-video: Move two assignments in au0828_init_isoc()

On 24/10/16 23:01, SF Markus Elfring wrote: From: Markus Elfring Date: Mon, 24 Oct 2016 22:44:02 +0200 Move the assignment for the data structure members "isoc_copy" and "num_bufs" behind the source code for memory allocations by this function. I don't see the

Re: [PATCH 3/3] [media] au0828-video: Move two assignments in au0828_init_isoc()

On 24/10/16 23:01, SF Markus Elfring wrote: From: Markus Elfring Date: Mon, 24 Oct 2016 22:44:02 +0200 Move the assignment for the data structure members "isoc_copy" and "num_bufs" behind the source code for memory allocations by this function. I don't see the point, dropping this patch.

[PATCH 3/6] clk: rockchip: add clock controller for rk1108

From: Shawn Lin Add the clock tree definition and driver for rk1108 SoC. Signed-off-by: Shawn Lin Signed-off-by: Andy Yan --- drivers/clk/rockchip/Makefile | 1 + drivers/clk/rockchip/clk-rk1108.c |

[PATCH 3/6] clk: rockchip: add clock controller for rk1108

From: Shawn Lin Add the clock tree definition and driver for rk1108 SoC. Signed-off-by: Shawn Lin Signed-off-by: Andy Yan --- drivers/clk/rockchip/Makefile | 1 + drivers/clk/rockchip/clk-rk1108.c | 463 + drivers/clk/rockchip/clk.h

[PATCH] dmaengine: mmp_tdma: Select GENERIC_ALLOCATOR

From: Borislav Petkov as the driver needs it. Build error caught with a randconfig build: drivers/built-in.o: In function `mmp_tdma_prep_dma_cyclic': mmp_tdma.c:(.text+0x1612d9): undefined reference to `gen_pool_dma_alloc' drivers/built-in.o: In function

[PATCH] dmaengine: mmp_tdma: Select GENERIC_ALLOCATOR

From: Borislav Petkov as the driver needs it. Build error caught with a randconfig build: drivers/built-in.o: In function `mmp_tdma_prep_dma_cyclic': mmp_tdma.c:(.text+0x1612d9): undefined reference to `gen_pool_dma_alloc' drivers/built-in.o: In function `mmp_tdma_free_chan_resources':

[PATCH 2/6] pinctrl: rockchip: add support for rk1108

Add basic support for rk1108 soc Signed-off-by: Andy Yan --- drivers/pinctrl/pinctrl-rockchip.c | 27 ++- 1 file changed, 26 insertions(+), 1 deletion(-) diff --git a/drivers/pinctrl/pinctrl-rockchip.c b/drivers/pinctrl/pinctrl-rockchip.c

[PATCH 2/6] pinctrl: rockchip: add support for rk1108

Add basic support for rk1108 soc Signed-off-by: Andy Yan --- drivers/pinctrl/pinctrl-rockchip.c | 27 ++- 1 file changed, 26 insertions(+), 1 deletion(-) diff --git a/drivers/pinctrl/pinctrl-rockchip.c b/drivers/pinctrl/pinctrl-rockchip.c index 49bf7dc..9f324b1 100644

[PATCH 1/6] dt-bindings: rockchip-dw-mshc: add RK1108 dw-mshc description

From: Shawn Lin Add "rockchip,rk1108-dw-mshc", "rockchip,rk3288-dw-mshc" for dwmmc on rk1108 platform. Signed-off-by: Shawn Lin Signed-off-by: Andy Yan ---

[PATCH 1/6] dt-bindings: rockchip-dw-mshc: add RK1108 dw-mshc description

From: Shawn Lin Add "rockchip,rk1108-dw-mshc", "rockchip,rk3288-dw-mshc" for dwmmc on rk1108 platform. Signed-off-by: Shawn Lin Signed-off-by: Andy Yan --- Documentation/devicetree/bindings/mmc/rockchip-dw-mshc.txt | 1 + 1 file changed, 1 insertion(+) diff --git

Re: [PATCH V3 1/6] clk: tegra: add TEGRA20_CLK_NOR to init table

2016-11-03 13:26 GMT+01:00 Mirza Krak : > 2016-11-03 11:06 GMT+01:00 Jon Hunter : >> Hi Mirza, >> >> On 27/10/16 15:01, Mirza Krak wrote: >>> >>> From: Mirza Krak >>> >>> Add TEGRA20_CLK_NOR to init table and set default rate to 92

Re: [PATCH V3 1/6] clk: tegra: add TEGRA20_CLK_NOR to init table

2016-11-03 13:26 GMT+01:00 Mirza Krak : > 2016-11-03 11:06 GMT+01:00 Jon Hunter : >> Hi Mirza, >> >> On 27/10/16 15:01, Mirza Krak wrote: >>> >>> From: Mirza Krak >>> >>> Add TEGRA20_CLK_NOR to init table and set default rate to 92 MHz which >>> is max rate. >>> >>> The maximum rate value of 92

[PATCH 0/6] Add basic support for support for Rockchip RK1108 SOC

RK1108 is embedded with an ARM Cortex-A7 single core and a DSP core. It is designed for varies application scenario such as car DVR, sports DV, secure camera and UAV camera. This patch series add basic support for it, which can boot a board with initramfs into shell. More new feathers will come

[PATCH 0/6] Add basic support for support for Rockchip RK1108 SOC

RK1108 is embedded with an ARM Cortex-A7 single core and a DSP core. It is designed for varies application scenario such as car DVR, sports DV, secure camera and UAV camera. This patch series add basic support for it, which can boot a board with initramfs into shell. More new feathers will come

Re: [PATCH V3 1/6] clk: tegra: add TEGRA20_CLK_NOR to init table

2016-11-03 11:06 GMT+01:00 Jon Hunter : > Hi Mirza, > > On 27/10/16 15:01, Mirza Krak wrote: >> >> From: Mirza Krak >> >> Add TEGRA20_CLK_NOR to init table and set default rate to 92 MHz which >> is max rate. >> >> The maximum rate value of 92 MHz is

Re: [PATCH V3 1/6] clk: tegra: add TEGRA20_CLK_NOR to init table

2016-11-03 11:06 GMT+01:00 Jon Hunter : > Hi Mirza, > > On 27/10/16 15:01, Mirza Krak wrote: >> >> From: Mirza Krak >> >> Add TEGRA20_CLK_NOR to init table and set default rate to 92 MHz which >> is max rate. >> >> The maximum rate value of 92 MHz is pulled from the downstream L4T >> kernel. > >

Re: [PATCH v3 5/5] arm64: dts: exynos: Add dts file for Exynos5433-based TM2E board

Hi Chanwoo, Tested-by: Andi Shyti Andi On Thu, Nov 03, 2016 at 03:39:09PM +0900, Chanwoo Choi wrote: > This patch adds the Device Tree source for Exynos5433-based Samsung TM2E > board. TM2E board is the most similar with TM2 board. The exynos5433-tm2e.dts > include the

Re: [PATCH v3 4/5] arm64: dts: exynos: Add dts file for Exynos5433-based TM2 board

Hi Chanwoo, Tested-by: Andi Shyti Andi On Thu, Nov 03, 2016 at 03:39:08PM +0900, Chanwoo Choi wrote: > This patch adds the Device Tree source for Exynos5433-based Samsung TM2 board. > This board fully support the all things for mobile target. > > This patch supports

Re: [PATCH v3 5/5] arm64: dts: exynos: Add dts file for Exynos5433-based TM2E board

Hi Chanwoo, Tested-by: Andi Shyti Andi On Thu, Nov 03, 2016 at 03:39:09PM +0900, Chanwoo Choi wrote: > This patch adds the Device Tree source for Exynos5433-based Samsung TM2E > board. TM2E board is the most similar with TM2 board. The exynos5433-tm2e.dts > include the difference between TM2

Re: [PATCH v3 4/5] arm64: dts: exynos: Add dts file for Exynos5433-based TM2 board

Hi Chanwoo, Tested-by: Andi Shyti Andi On Thu, Nov 03, 2016 at 03:39:08PM +0900, Chanwoo Choi wrote: > This patch adds the Device Tree source for Exynos5433-based Samsung TM2 board. > This board fully support the all things for mobile target. > > This patch supports the following devices: >

Re: [PATCH 3/4] blk-mq: implement hybrid poll mode for sync O_DIRECT

On Wed, Nov 2, 2016 at 5:05 AM, Jens Axboe wrote: > This patch enables a hybrid polling mode. Instead of polling after IO > submission, we can induce an artificial delay, and then poll after that. > For example, if the IO is presumed to complete in 8 usecs from now, we > can sleep

Re: [PATCH 3/4] blk-mq: implement hybrid poll mode for sync O_DIRECT

On Wed, Nov 2, 2016 at 5:05 AM, Jens Axboe wrote: > This patch enables a hybrid polling mode. Instead of polling after IO > submission, we can induce an artificial delay, and then poll after that. > For example, if the IO is presumed to complete in 8 usecs from now, we > can sleep for 4 usecs,

Re: [PATCH v3 3/5] arm64: dts: exynos: Add dts files for Samsung Exynos5433 64bit SoC

Hi Chanwoo, Tested-by: Andi Shyti Andi On Thu, Nov 03, 2016 at 03:39:07PM +0900, Chanwoo Choi wrote: > This patch adds new Exynos5433 dtsi to support 64-bit Exynos5433 SoC based on > Octa-core CPUs (quad Cortex-A57 and quad Cortex-A53). And Exynos5433 supports > PSCI

Re: [PATCH v3 3/5] arm64: dts: exynos: Add dts files for Samsung Exynos5433 64bit SoC

Hi Chanwoo, Tested-by: Andi Shyti Andi On Thu, Nov 03, 2016 at 03:39:07PM +0900, Chanwoo Choi wrote: > This patch adds new Exynos5433 dtsi to support 64-bit Exynos5433 SoC based on > Octa-core CPUs (quad Cortex-A57 and quad Cortex-A53). And Exynos5433 supports > PSCI (Power State Coordination

[PATCH v3 1/3] ARC: SMP: Register IPI handler using virq but not hwirq

smp_ipi_irq_setup takes a cpu number and a hwirq number for the per core local interrupt line in the root interrupt controller and registers an appropriate IPI handler per cpu. However this function tries to bind a handler to the hwirq as virtual IRQ number and it is a wrong behavior. It is

[PATCH v3 1/3] ARC: SMP: Register IPI handler using virq but not hwirq

smp_ipi_irq_setup takes a cpu number and a hwirq number for the per core local interrupt line in the root interrupt controller and registers an appropriate IPI handler per cpu. However this function tries to bind a handler to the hwirq as virtual IRQ number and it is a wrong behavior. It is

[PATCH v3 0/3] ARC: Set of patches for IRQ subsystem

First 2 patches fix misuse of IRQ numbers. In some places of the Linux kernel for ARC hardware IRQ numbers are used as virtual IRQ numbers and obviously it is wrong. The third patch forces the kernel to set a simple distribution mode for common interrupts in cases when such interrupts are routed

[PATCH v3 3/3] ARCv2: MCIP: Use IDU_M_DISTRI_DEST mode if there is only 1 destination core

ARC linux uses 2 distribution modes for common interrupts: round robin mode (IDU_M_DISTRI_RR) and a simple destination mode (IDU_M_DISTRI_DEST). The first one is used when more than 1 cores may handle a common interrupt and the second one is used when only 1 core may handle a common interrupt.

[PATCH v3 2/3] ARCv2: MCIP: Use hwirq instead of virq for resolution of IDU IRQ handlers

Multicore ARC configurations use IDU (Interrupt Distribution Unit) for distributing of common interrupts. In fact IDU is a interrupt controller on top of main per core interrupt controller. All common IRQs are physically and linearly mapped to per core interrupts. E.g. <0, 1, 2, 3> common IDU

[PATCH v3 0/3] ARC: Set of patches for IRQ subsystem

First 2 patches fix misuse of IRQ numbers. In some places of the Linux kernel for ARC hardware IRQ numbers are used as virtual IRQ numbers and obviously it is wrong. The third patch forces the kernel to set a simple distribution mode for common interrupts in cases when such interrupts are routed

[PATCH v3 3/3] ARCv2: MCIP: Use IDU_M_DISTRI_DEST mode if there is only 1 destination core

ARC linux uses 2 distribution modes for common interrupts: round robin mode (IDU_M_DISTRI_RR) and a simple destination mode (IDU_M_DISTRI_DEST). The first one is used when more than 1 cores may handle a common interrupt and the second one is used when only 1 core may handle a common interrupt.

[PATCH v3 2/3] ARCv2: MCIP: Use hwirq instead of virq for resolution of IDU IRQ handlers

Multicore ARC configurations use IDU (Interrupt Distribution Unit) for distributing of common interrupts. In fact IDU is a interrupt controller on top of main per core interrupt controller. All common IRQs are physically and linearly mapped to per core interrupts. E.g. <0, 1, 2, 3> common IDU

Re: [PATCH 17/34] [media] DaVinci-VPFE-Capture: Improve another size determination in vpfe_enum_input()

On 12/10/16 16:55, SF Markus Elfring wrote: From: Markus Elfring Date: Wed, 12 Oct 2016 10:33:42 +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

Re: [PATCH 17/34] [media] DaVinci-VPFE-Capture: Improve another size determination in vpfe_enum_input()

On 12/10/16 16:55, SF Markus Elfring wrote: From: Markus Elfring Date: Wed, 12 Oct 2016 10:33:42 +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. Signed-off-by:

Re: [PATCH 10/34] [media] DaVinci-VPBE: Check return value of a setup_if_config() call in vpbe_set_output()

On 12/10/16 16:47, SF Markus Elfring wrote: From: Markus Elfring Date: Wed, 12 Oct 2016 09:56:56 +0200 * A function was called over the pointer "setup_if_config" in the data structure "venc_platform_data". But the return value was not used so far. Thus assign

Re: [PATCH 10/34] [media] DaVinci-VPBE: Check return value of a setup_if_config() call in vpbe_set_output()

On 12/10/16 16:47, SF Markus Elfring wrote: From: Markus Elfring Date: Wed, 12 Oct 2016 09:56:56 +0200 * A function was called over the pointer "setup_if_config" in the data structure "venc_platform_data". But the return value was not used so far. Thus assign it to the local variable "ret"

Re: [PATCH 3/3] usb: ohci-da8xx: rename driver to ohci-da8xx

Hi Sekhar, The baseline used was the branch usb-next, in Greg's tree: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git Linux next is missing this patch[1] which was applied last week, but not yet pulled into linux-next. it will be there soon. Sorry, i did not mention it, i thought

Re: [PATCH 3/3] usb: ohci-da8xx: rename driver to ohci-da8xx

Hi Sekhar, The baseline used was the branch usb-next, in Greg's tree: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git Linux next is missing this patch[1] which was applied last week, but not yet pulled into linux-next. it will be there soon. Sorry, i did not mention it, i thought

ko

i am Duncan Vargas From USA, i get you through web book i need a good interest my email, duncanvarg...@yahoo.com,

ko

i am Duncan Vargas From USA, i get you through web book i need a good interest my email, duncanvarg...@yahoo.com,

Re: [PATCH 0/3] fix ohci phy name

On Thursday 03 November 2016 01:54 PM, Axel Haslam wrote: > Hi Sekhar, David, > > It might make sense to have this patch series, > squashed into a single patch, would you agree, > or do you prefer it as is: one-per-subsystem? Patches in the current form are okay. Some coordination is required in

Re: [PATCH 0/3] fix ohci phy name

On Thursday 03 November 2016 01:54 PM, Axel Haslam wrote: > Hi Sekhar, David, > > It might make sense to have this patch series, > squashed into a single patch, would you agree, > or do you prefer it as is: one-per-subsystem? Patches in the current form are okay. Some coordination is required in

Re: [PATCH 3/3] usb: ohci-da8xx: rename driver to ohci-da8xx

On Wednesday 02 November 2016 06:14 PM, Axel Haslam wrote: > To be consistent on the usb driver for the davinci > platform follow the example of musb, and add the > "-da8xx" postfix to the driver name. > > Signed-off-by: Axel Haslam > --- > drivers/usb/host/ohci-da8xx.c |

Re: [PATCH 3/3] usb: ohci-da8xx: rename driver to ohci-da8xx

On Wednesday 02 November 2016 06:14 PM, Axel Haslam wrote: > To be consistent on the usb driver for the davinci > platform follow the example of musb, and add the > "-da8xx" postfix to the driver name. > > Signed-off-by: Axel Haslam > --- > drivers/usb/host/ohci-da8xx.c | 2 +- > 1 file

Re: Kernel regression introduced by "e1000e: Do not write lsc to ics in msi-x mode" and/or "e1000e: Do not read ICR in Other interrupt"

> > Reverting these two commits resolves the Link is Down/Link is Up > > messages. This has been tested on about six servers so far and all have > > stopped reporting these link flaps. > > Are you able to revert either of the patches independently, I don't > recall if they were stand alone or

Re: Kernel regression introduced by "e1000e: Do not write lsc to ics in msi-x mode" and/or "e1000e: Do not read ICR in Other interrupt"

> > Reverting these two commits resolves the Link is Down/Link is Up > > messages. This has been tested on about six servers so far and all have > > stopped reporting these link flaps. > > Are you able to revert either of the patches independently, I don't > recall if they were stand alone or

Re: [PATCH net] r8152: Fix broken RX checksums.

On 16-11-03 04:56 AM, Hayes Wang wrote: > Mark Lord [mailto:ml...@pobox.com] >> Sent: Thursday, November 03, 2016 2:30 AM >> To: Hayes Wang; David Miller > [...] >> I have poked at it some more, and thus far it appears that it is >> only necessary to disable TCP rx checksums. The system doesn't

Re: [PATCH net] r8152: Fix broken RX checksums.

On 16-11-03 04:56 AM, Hayes Wang wrote: > Mark Lord [mailto:ml...@pobox.com] >> Sent: Thursday, November 03, 2016 2:30 AM >> To: Hayes Wang; David Miller > [...] >> I have poked at it some more, and thus far it appears that it is >> only necessary to disable TCP rx checksums. The system doesn't

Re: [PATCH v1 1/2] mtd: m25p80: lock module while used

Dear Maintainers, Requesting for your attention for patch review/merge. Thanks & Regards, Sandeep Jain On Thu, Aug 04, 2016 at 07:46:33PM +0530, Sandeep Jain wrote: > From: Vladimir Zapolskiy > > The change controls module users counter, which prevents to

Re: [PATCH v1 1/2] mtd: m25p80: lock module while used

Dear Maintainers, Requesting for your attention for patch review/merge. Thanks & Regards, Sandeep Jain On Thu, Aug 04, 2016 at 07:46:33PM +0530, Sandeep Jain wrote: > From: Vladimir Zapolskiy > > The change controls module users counter, which prevents to get > accidental oops on

Re: [PATCH 1/1] usb: xhci: cleanup cmd_completion in xhci_virt_device

On 03.11.2016 12:22, Sergei Shtylyov wrote: On 11/3/2016 9:48 AM, Lu Baolu wrote: cmd_completion in struct xhci_virt_device is legacy. With command strutcture and command queue introduced in xhci, cmd_completion is Structure. I'll fix that while applying the patch, no need to resend

Re: [PATCH 1/1] usb: xhci: cleanup cmd_completion in xhci_virt_device

On 03.11.2016 12:22, Sergei Shtylyov wrote: On 11/3/2016 9:48 AM, Lu Baolu wrote: cmd_completion in struct xhci_virt_device is legacy. With command strutcture and command queue introduced in xhci, cmd_completion is Structure. I'll fix that while applying the patch, no need to resend

Re: [PATCH 1/1] usb: xhci: cleanup cmd_completion in xhci_virt_device

On 03.11.2016 08:48, Lu Baolu wrote: cmd_completion in struct xhci_virt_device is legacy. With command strutcture and command queue introduced in xhci, cmd_completion is not used any more. This patch removes it. Signed-off-by: Lu Baolu ---

Re: [PATCH 1/1] usb: xhci: cleanup cmd_completion in xhci_virt_device

On 03.11.2016 08:48, Lu Baolu wrote: cmd_completion in struct xhci_virt_device is legacy. With command strutcture and command queue introduced in xhci, cmd_completion is not used any more. This patch removes it. Signed-off-by: Lu Baolu --- drivers/usb/host/xhci-mem.c | 1 -

Re: [PATCH] mtd: Allocate bdi objects dynamically

Dear Maintainers, This patch is reviewed by Richard. Requesting for Maintainer's attention for patch merge. Thanks & Regards, Sandeep Jain On Sat, Sep 17, 2016 at 04:41:47PM +0200, Richard Weinberger wrote: > On Thu, Aug 4, 2016 at 4:01 PM, Sandeep Jain wrote: > >

Re: [PATCH] mtd: Allocate bdi objects dynamically

Dear Maintainers, This patch is reviewed by Richard. Requesting for Maintainer's attention for patch merge. Thanks & Regards, Sandeep Jain On Sat, Sep 17, 2016 at 04:41:47PM +0200, Richard Weinberger wrote: > On Thu, Aug 4, 2016 at 4:01 PM, Sandeep Jain wrote: > > From: Steve Longerbeam > >

[PATCH] gpio: davinci: Use unique labels for each gpio chip

The gpiod framework uses the chip label to match a specific chip. The davinci gpio driver, creates several chips using always the same label, which is not compatible with gpiod. To allow platform data to declare gpio lookup tables, and for drivers to use the gpiod framework, allocate unique label

[PATCH] gpio: davinci: Use unique labels for each gpio chip

The gpiod framework uses the chip label to match a specific chip. The davinci gpio driver, creates several chips using always the same label, which is not compatible with gpiod. To allow platform data to declare gpio lookup tables, and for drivers to use the gpiod framework, allocate unique label

Re: [PATCH 28/60] block: introduce QUEUE_FLAG_SPLIT_MP

On Thu, Nov 03, 2016 at 07:26:52PM +0800, Ming Lei wrote: > On Thu, Nov 3, 2016 at 7:20 PM, Kent Overstreet > wrote: > > On Thu, Nov 03, 2016 at 06:38:57PM +0800, Ming Lei wrote: > >> On Wed, Nov 2, 2016 at 11:08 AM, Kent Overstreet > >>

Re: [PATCH 28/60] block: introduce QUEUE_FLAG_SPLIT_MP

On Thu, Nov 03, 2016 at 07:26:52PM +0800, Ming Lei wrote: > On Thu, Nov 3, 2016 at 7:20 PM, Kent Overstreet > wrote: > > On Thu, Nov 03, 2016 at 06:38:57PM +0800, Ming Lei wrote: > >> On Wed, Nov 2, 2016 at 11:08 AM, Kent Overstreet > >> wrote: > >> > On Mon, Oct 31, 2016 at 08:39:15AM -0700,

Re: [PATCH 28/60] block: introduce QUEUE_FLAG_SPLIT_MP

On Thu, Nov 3, 2016 at 7:20 PM, Kent Overstreet wrote: > On Thu, Nov 03, 2016 at 06:38:57PM +0800, Ming Lei wrote: >> On Wed, Nov 2, 2016 at 11:08 AM, Kent Overstreet >> wrote: >> > On Mon, Oct 31, 2016 at 08:39:15AM -0700, Christoph Hellwig

Re: [PATCH 28/60] block: introduce QUEUE_FLAG_SPLIT_MP

On Thu, Nov 3, 2016 at 7:20 PM, Kent Overstreet wrote: > On Thu, Nov 03, 2016 at 06:38:57PM +0800, Ming Lei wrote: >> On Wed, Nov 2, 2016 at 11:08 AM, Kent Overstreet >> wrote: >> > On Mon, Oct 31, 2016 at 08:39:15AM -0700, Christoph Hellwig wrote: >> >> On Sat, Oct 29, 2016 at 04:08:27PM +0800,

Re: [PATCH] x86/entry64: move comment about informing of context tracking in right place

On Mon, Oct 24, 2016 at 05:22:34PM +0600, Alexander Kuleshov wrote: > We are switching to kernel gsbase if an IRQ come from usermode with swpags. "... if an IRQ comes from ..." Also, you mean SWAPGS. Instruction names in allcaps please and spelled correctly please. > Now there is comment which

Re: [PATCH] x86/entry64: move comment about informing of context tracking in right place

On Mon, Oct 24, 2016 at 05:22:34PM +0600, Alexander Kuleshov wrote: > We are switching to kernel gsbase if an IRQ come from usermode with swpags. "... if an IRQ comes from ..." Also, you mean SWAPGS. Instruction names in allcaps please and spelled correctly please. > Now there is comment which

Re: [PATCH 28/60] block: introduce QUEUE_FLAG_SPLIT_MP

On Thu, Nov 03, 2016 at 06:38:57PM +0800, Ming Lei wrote: > On Wed, Nov 2, 2016 at 11:08 AM, Kent Overstreet > wrote: > > On Mon, Oct 31, 2016 at 08:39:15AM -0700, Christoph Hellwig wrote: > >> On Sat, Oct 29, 2016 at 04:08:27PM +0800, Ming Lei wrote: > >> > Some

Re: [PATCH 28/60] block: introduce QUEUE_FLAG_SPLIT_MP

On Thu, Nov 03, 2016 at 06:38:57PM +0800, Ming Lei wrote: > On Wed, Nov 2, 2016 at 11:08 AM, Kent Overstreet > wrote: > > On Mon, Oct 31, 2016 at 08:39:15AM -0700, Christoph Hellwig wrote: > >> On Sat, Oct 29, 2016 at 04:08:27PM +0800, Ming Lei wrote: > >> > Some drivers(such as dm) should be

Re: [PATCH 1/4] block: add scalable completion tracking of requests

On Wed, Nov 2, 2016 at 5:05 AM, Jens Axboe wrote: > For legacy block, we simply track them in the request queue. For > blk-mq, we track them on a per-sw queue basis, which we can then > sum up through the hardware queues and finally to a per device > state. > > The stats are tracked

Re: [PATCH 1/4] block: add scalable completion tracking of requests

On Wed, Nov 2, 2016 at 5:05 AM, Jens Axboe wrote: > For legacy block, we simply track them in the request queue. For > blk-mq, we track them on a per-sw queue basis, which we can then > sum up through the hardware queues and finally to a per device > state. > > The stats are tracked in, roughly,

Re: arm64 build failure with CONFIG_ARM64_LSE_ATOMICS=y

On Thu, Nov 03, 2016 at 10:39:43AM +, Suzuki K Poulose wrote: > On 02/11/16 23:28, Will Deacon wrote: > > Hi Artem, > > > > On Wed, Nov 02, 2016 at 05:44:27PM +0100, Artem Savkov wrote: > > > Hello Catalin, > > > > > > Looks like your patch "efd9e03 arm64: Use static keys for CPU features" >

Re: arm64 build failure with CONFIG_ARM64_LSE_ATOMICS=y

On Thu, Nov 03, 2016 at 10:39:43AM +, Suzuki K Poulose wrote: > On 02/11/16 23:28, Will Deacon wrote: > > Hi Artem, > > > > On Wed, Nov 02, 2016 at 05:44:27PM +0100, Artem Savkov wrote: > > > Hello Catalin, > > > > > > Looks like your patch "efd9e03 arm64: Use static keys for CPU features" >

Re: [PATCH 01/10] Documentation: dt-bindings: Document STM32 ADC DT bindings

On 10/31/2016 04:02 AM, Rob Herring wrote: On Tue, Oct 25, 2016 at 06:25:13PM +0200, Fabrice Gasnier wrote: This patch adds documentation of device tree bindings for the STM32 ADC. Signed-off-by: Fabrice Gasnier --- .../devicetree/bindings/iio/adc/st,stm32-adc.txt

[PATCH/RFC v2 1/3] regulator: core: Add new API to poll for error conditions

Regulator consumers can receive event notifications when errors are reported to the driver, but currently, there is no way for a regulator consumer to know when the error is over. To allow a regulator consumer to poll for error conditions add a new API: regulator_get_error_flags. Signed-off-by:

[PATCH/RFC v2 2/3] regulator: fixed: dt: Allow an optional over current pin

Add support for an optional over current input pin which can be used to send an over current event to the regulator consumer. Cc: devicet...@vger.kernel.org Signed-off-by: Axel Haslam --- Documentation/devicetree/bindings/regulator/fixed-regulator.txt | 2 ++ 1 file

Re: [PATCH 01/10] Documentation: dt-bindings: Document STM32 ADC DT bindings

On 10/31/2016 04:02 AM, Rob Herring wrote: On Tue, Oct 25, 2016 at 06:25:13PM +0200, Fabrice Gasnier wrote: This patch adds documentation of device tree bindings for the STM32 ADC. Signed-off-by: Fabrice Gasnier --- .../devicetree/bindings/iio/adc/st,stm32-adc.txt | 78

[PATCH/RFC v2 1/3] regulator: core: Add new API to poll for error conditions

Regulator consumers can receive event notifications when errors are reported to the driver, but currently, there is no way for a regulator consumer to know when the error is over. To allow a regulator consumer to poll for error conditions add a new API: regulator_get_error_flags. Signed-off-by:

[PATCH/RFC v2 2/3] regulator: fixed: dt: Allow an optional over current pin

Add support for an optional over current input pin which can be used to send an over current event to the regulator consumer. Cc: devicet...@vger.kernel.org Signed-off-by: Axel Haslam --- Documentation/devicetree/bindings/regulator/fixed-regulator.txt | 2 ++ 1 file changed, 2 insertions(+)

[PATCH/RFC v2 0/3] regulator: handling of error conditions for usb drivers

Some usb drivers rely on external power switches/regulators to for the port vbus. Some of these drivers are using a plain gpio for the enable pin and also the over current indicator pin. To make these drivers more generic, we can use a regulator to handle vbus, and send and over current event,

[PATCH/RFC v2 3/3] regulator: fixed: Handle optional overcurrent pin

Fixed regulators (ex. TPS2087D) may have a over current pin that is activated on over current. Consumers may be interested to know about over current events to take appropriate actions. Allow the fix regulator to take in an optional gpio pin for over current and send the respective event to the

[PATCH/RFC v2 0/3] regulator: handling of error conditions for usb drivers

Some usb drivers rely on external power switches/regulators to for the port vbus. Some of these drivers are using a plain gpio for the enable pin and also the over current indicator pin. To make these drivers more generic, we can use a regulator to handle vbus, and send and over current event,

[PATCH/RFC v2 3/3] regulator: fixed: Handle optional overcurrent pin

Fixed regulators (ex. TPS2087D) may have a over current pin that is activated on over current. Consumers may be interested to know about over current events to take appropriate actions. Allow the fix regulator to take in an optional gpio pin for over current and send the respective event to the

Re: [PATCH 1/2] arm64: defconfig: enable I2C and DW MMC controller on rockchip platform

Ping On 2016年09月07日 19:46, Andy Yan wrote: I2C and MMC are very basic modules for a board to bootup, as I2C always used to configure PMIC and MMC devices often used to store filesytem. So enable them here to let the rockchip based arm64 boards can bootup. Signed-off-by: Andy Yan

Re: [PATCH 1/2] arm64: defconfig: enable I2C and DW MMC controller on rockchip platform

Ping On 2016年09月07日 19:46, Andy Yan wrote: I2C and MMC are very basic modules for a board to bootup, as I2C always used to configure PMIC and MMC devices often used to store filesytem. So enable them here to let the rockchip based arm64 boards can bootup. Signed-off-by: Andy Yan ---

[PATCH] hid: sensor: fix input and feature attributes in HID sensor custom sysfs interface

User is unable to access to input-X-yyy and feature-X-yyy where X is a hex value and more than 9 (e.g. input-a-yyy, feature-b-yyy) in HID sensor custom sysfs interface. This is because when creating the attribute, the attribute index is written to using %x (hex). However, when reading and writing

[PATCH] hid: sensor: fix input and feature attributes in HID sensor custom sysfs interface

User is unable to access to input-X-yyy and feature-X-yyy where X is a hex value and more than 9 (e.g. input-a-yyy, feature-b-yyy) in HID sensor custom sysfs interface. This is because when creating the attribute, the attribute index is written to using %x (hex). However, when reading and writing

Re: [PATCH v2 3/8] media: vidc: decoder: add video decoder files

On 03/11/16 11:45, Stanimir Varbanov wrote: Hi Hans, On 09/19/2016 01:04 PM, Hans Verkuil wrote: On 09/07/2016 01:37 PM, Stanimir Varbanov wrote: This consists of video decoder implementation plus decoder controls. Signed-off-by: Stanimir Varbanov ---

Re: [PATCH v2 3/8] media: vidc: decoder: add video decoder files

On 03/11/16 11:45, Stanimir Varbanov wrote: Hi Hans, On 09/19/2016 01:04 PM, Hans Verkuil wrote: On 09/07/2016 01:37 PM, Stanimir Varbanov wrote: This consists of video decoder implementation plus decoder controls. Signed-off-by: Stanimir Varbanov ---

Re: [PATCH V3 6/6] bus: Add support for Tegra Generic Memory Interface

On 27/10/16 15:01, Mirza Krak wrote: From: Mirza Krak The Generic Memory Interface bus can be used to connect high-speed devices such as NOR flash, FPGAs, DSPs... Signed-off-by: Mirza Krak Tested-by: Marcel Ziswiler

Re: [PATCH V3 6/6] bus: Add support for Tegra Generic Memory Interface

On 27/10/16 15:01, Mirza Krak wrote: From: Mirza Krak The Generic Memory Interface bus can be used to connect high-speed devices such as NOR flash, FPGAs, DSPs... Signed-off-by: Mirza Krak Tested-by: Marcel Ziswiler Tested-on: Colibri T20/T30 on EvalBoard V3.x and GMI-Memory Board ---

Re: [PATCH v2 3/8] media: vidc: decoder: add video decoder files

Hi Hans, On 09/19/2016 01:04 PM, Hans Verkuil wrote: > On 09/07/2016 01:37 PM, Stanimir Varbanov wrote: >> This consists of video decoder implementation plus decoder >> controls. >> >> Signed-off-by: Stanimir Varbanov >> --- >>

Re: [PATCH v2 3/8] media: vidc: decoder: add video decoder files

Hi Hans, On 09/19/2016 01:04 PM, Hans Verkuil wrote: > On 09/07/2016 01:37 PM, Stanimir Varbanov wrote: >> This consists of video decoder implementation plus decoder >> controls. >> >> Signed-off-by: Stanimir Varbanov >> --- >> drivers/media/platform/qcom/vidc/vdec.c | 1091 >>

[PATCH] iio: light and pressure: change data fields for ambient light and pressure sensor

Sensitivity Percent Relative is added for ambient light sensor as it is used based on HID Sensor Usages specifications. Other changes include adding HID_USAGE_SENSOR_LIGHT_ILLUM and HID_USAGE_SENSOR_ATMOSPHERIC_PRESSURE for ambient light and pressure sensor respectively to be in sync with HID

[PATCH] iio: light and pressure: change data fields for ambient light and pressure sensor

Sensitivity Percent Relative is added for ambient light sensor as it is used based on HID Sensor Usages specifications. Other changes include adding HID_USAGE_SENSOR_LIGHT_ILLUM and HID_USAGE_SENSOR_ATMOSPHERIC_PRESSURE for ambient light and pressure sensor respectively to be in sync with HID

Re: [PATCH] mm: cma: improve utilization of cma pages

st ERROR on v4.9-rc3 next-20161028] > [if your patch is applied to the wrong git tree, please drop us a note to > help improve the system] > > url: > https://github.com/0day-ci/linux/commits/Chen-Feng/mm-cma-improve-utilization-of-cma-pages/20161103-173624 > base: git

Re: [PATCH] mm: cma: improve utilization of cma pages

st ERROR on v4.9-rc3 next-20161028] > [if your patch is applied to the wrong git tree, please drop us a note to > help improve the system] > > url: > https://github.com/0day-ci/linux/commits/Chen-Feng/mm-cma-improve-utilization-of-cma-pages/20161103-173624 > base: git

<    7   8   9   10   11   12   13   14   15   >