[PATCH v2] lightnvm: divide global reverse translation map into per lun

Divide the target's global reverse translation map into per lun, to prepare support for the non-continuous lun target creation. Signed-off-by: Wenwei Tao --- Changes since v1 -fix merge/rebase mistake in rrpc_block_map_update(). -remove variables poffset and lun_offset in

[PATCH v2] lightnvm: divide global reverse translation map into per lun

Divide the target's global reverse translation map into per lun, to prepare support for the non-continuous lun target creation. Signed-off-by: Wenwei Tao --- Changes since v1 -fix merge/rebase mistake in rrpc_block_map_update(). -remove variables poffset and lun_offset in rrpc structure since

arch/xtensa/include/asm/initialize_mmu.h:55: Error: invalid register 'atomctl' for 'wsr' instruction

Hi Max, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 1e75a9f34a5ed5902707fb74b468356c55142b71 commit: ca55b2fef3a9373fcfc30f82fd26bc7fccbda732 xtensa: add de212 core variant date: 5 months ago config:

arch/xtensa/include/asm/initialize_mmu.h:55: Error: invalid register 'atomctl' for 'wsr' instruction

Hi Max, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 1e75a9f34a5ed5902707fb74b468356c55142b71 commit: ca55b2fef3a9373fcfc30f82fd26bc7fccbda732 xtensa: add de212 core variant date: 5 months ago config:

[PATCH] Coccinelle: setup_timer: Add space in front of parentheses

Add space in front of the offending parentheses to silent the parse error for older Coccinelle versions. This makes the rule usable with all Coccinelle versions. Reported-by: Nishanth Menon Signed-off-by: Vaishali Thakkar ---

[PATCH] Coccinelle: setup_timer: Add space in front of parentheses

Add space in front of the offending parentheses to silent the parse error for older Coccinelle versions. This makes the rule usable with all Coccinelle versions. Reported-by: Nishanth Menon Signed-off-by: Vaishali Thakkar --- scripts/coccinelle/api/setup_timer.cocci | 4 ++-- 1 file changed, 2

Re: Nokia N900 - audio TPA6130A2 problems

Hi, On Sat, Mar 19, 2016 at 10:49:57AM +0200, Ivaylo Dimitrov wrote: > On 18.03.2016 17:04, Sebastian Reichel wrote: > >On Fri, Mar 18, 2016 at 03:45:26PM +0200, Ivaylo Dimitrov wrote: > >>On 18.03.2016 15:36, Sebastian Reichel wrote: > >>Regulator is V28_A, which is always-on, so it is enabled

Re: Nokia N900 - audio TPA6130A2 problems

Hi, On Sat, Mar 19, 2016 at 10:49:57AM +0200, Ivaylo Dimitrov wrote: > On 18.03.2016 17:04, Sebastian Reichel wrote: > >On Fri, Mar 18, 2016 at 03:45:26PM +0200, Ivaylo Dimitrov wrote: > >>On 18.03.2016 15:36, Sebastian Reichel wrote: > >>Regulator is V28_A, which is always-on, so it is enabled

[PATCH v20 21/23] vfs: Add richacl permission checking

Hook the richacl permission checking function into the vfs. Signed-off-by: Andreas Gruenbacher --- fs/namei.c | 51 +-- fs/posix_acl.c | 6 +++--- 2 files changed, 52 insertions(+), 5 deletions(-) diff --git a/fs/namei.c

[PATCH v20 21/23] vfs: Add richacl permission checking

Hook the richacl permission checking function into the vfs. Signed-off-by: Andreas Gruenbacher --- fs/namei.c | 51 +-- fs/posix_acl.c | 6 +++--- 2 files changed, 52 insertions(+), 5 deletions(-) diff --git a/fs/namei.c b/fs/namei.c index

Re: Linux 3.14.65

diff --git a/Documentation/filesystems/efivarfs.txt b/Documentation/filesystems/efivarfs.txt index c477af086e65..686a64bba775 100644 --- a/Documentation/filesystems/efivarfs.txt +++ b/Documentation/filesystems/efivarfs.txt @@ -14,3 +14,10 @@ filesystem. efivarfs is typically mounted like this,

Re: Linux 3.14.65

diff --git a/Documentation/filesystems/efivarfs.txt b/Documentation/filesystems/efivarfs.txt index c477af086e65..686a64bba775 100644 --- a/Documentation/filesystems/efivarfs.txt +++ b/Documentation/filesystems/efivarfs.txt @@ -14,3 +14,10 @@ filesystem. efivarfs is typically mounted like this,

Re: [RFC PATCH linux-next] ovs: internal_set_rx_headroom() can be static

From: kbuild test robot Date: Sat, 19 Mar 2016 00:54:50 +0800 > Signed-off-by: Fengguang Wu Looks good, applied, thanks.

Re: [PATCH v4 2/2] auxdisplay: ht16k33: Driver for LED controller

On Wed, Mar 16, 2016 at 04:52:09PM +0100, Robin van der Gracht wrote: > This is a driver for the Holtek HT16K33 RAM mapping LED controller with > keyscan. Wrap your lines to less than 80 chars. > Signed-off-by: Robin van der Gracht > --- > > Changes in v4: > - Removed

Re: [RFC PATCH linux-next] ovs: internal_set_rx_headroom() can be static

From: kbuild test robot Date: Sat, 19 Mar 2016 00:54:50 +0800 > Signed-off-by: Fengguang Wu Looks good, applied, thanks.

Re: [PATCH v4 2/2] auxdisplay: ht16k33: Driver for LED controller

On Wed, Mar 16, 2016 at 04:52:09PM +0100, Robin van der Gracht wrote: > This is a driver for the Holtek HT16K33 RAM mapping LED controller with > keyscan. Wrap your lines to less than 80 chars. > Signed-off-by: Robin van der Gracht > --- > > Changes in v4: > - Removed trailing dot from patch

Re: [PATCH] MAINTAINERS: Update UBIFS entry

On Thu, 2016-03-03 at 14:22 +0100, Richard Weinberger wrote: > ...to represent the status quo. > > Signed-off-by: Richard Weinberger > --- >  MAINTAINERS | 3 ++- >  1 file changed, 2 insertions(+), 1 deletion(-) Acked-by: Artem Bityutskiy

Re: [PATCH v2] ARC: axs10x - add Ethernet PHY description in .dts

On 3/17/2016 12:41 PM, Alexey Brodkin wrote: Following commit broke DW GMAC functionality on AXS10x boards: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=e34d65696d2ef13dc32f2a162556c86c461ed763 Note that scripts/checkpatch.pl now enforces certain format for

Re: [PATCH] MAINTAINERS: Update UBIFS entry

On Thu, 2016-03-03 at 14:22 +0100, Richard Weinberger wrote: > ...to represent the status quo. > > Signed-off-by: Richard Weinberger > --- >  MAINTAINERS | 3 ++- >  1 file changed, 2 insertions(+), 1 deletion(-) Acked-by: Artem Bityutskiy Thanks Richard!

Re: [PATCH v2] ARC: axs10x - add Ethernet PHY description in .dts

On 3/17/2016 12:41 PM, Alexey Brodkin wrote: Following commit broke DW GMAC functionality on AXS10x boards: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=e34d65696d2ef13dc32f2a162556c86c461ed763 Note that scripts/checkpatch.pl now enforces certain format for

[PATCH] ARM: dts: k2*: Rename the k2* files to keystone-k2* files

As reported in [1], rename the k2* dts files to keystone-* files this will force consistency throughout. Script for the same (and hand modified for Makefile and MAINTAINERS files): for i in arch/arm/boot/dts/k2* do b=`basename $i`; git mv $i arch/arm/boot/dts/keystone-$b;

[PATCH] ARM: dts: k2*: Rename the k2* files to keystone-k2* files

As reported in [1], rename the k2* dts files to keystone-* files this will force consistency throughout. Script for the same (and hand modified for Makefile and MAINTAINERS files): for i in arch/arm/boot/dts/k2* do b=`basename $i`; git mv $i arch/arm/boot/dts/keystone-$b;

Re: RFC on fixing mutex spinning on owner

On Wed, 16 Mar 2016 16:38:56 -0700 Joel Fernandes wrote: > I am not sure if the problem is with the i915 driver, because the > mutex spin on owner stuff is mutex related so the mutex design may > potentially need a tweak (I mentioned a proposal of adding mutex > spinning

Re: [PATCH] ARC: build: Turn off -Wmaybe-uninitialized for ARC gcc 4.8

On Friday 18 March 2016 03:59 PM, Arnd Bergmann wrote: > On Friday 18 March 2016 15:50:11 Vineet Gupta wrote: >> Sure, but I prefer this to be only for gcc 4.8 as this warning seems to be >> healthy in small doses At least it keeps the door open for future discussion >> with gcc guys ! > > FWIW,

Re: RFC on fixing mutex spinning on owner

On Wed, 16 Mar 2016 16:38:56 -0700 Joel Fernandes wrote: > I am not sure if the problem is with the i915 driver, because the > mutex spin on owner stuff is mutex related so the mutex design may > potentially need a tweak (I mentioned a proposal of adding mutex > spinning time outs). > Also since

Re: [PATCH] ARC: build: Turn off -Wmaybe-uninitialized for ARC gcc 4.8

On Friday 18 March 2016 03:59 PM, Arnd Bergmann wrote: > On Friday 18 March 2016 15:50:11 Vineet Gupta wrote: >> Sure, but I prefer this to be only for gcc 4.8 as this warning seems to be >> healthy in small doses At least it keeps the door open for future discussion >> with gcc guys ! > > FWIW,

[PATCH 3.19.y-ckt 09/70] ahci: add new Intel device IDs

v3.19.8-ckt17 -stable review patch. If anyone has any objections, please let me know. ---8< From: Alexandra Yates commit 56e74338a535cbcc2f2da08b1ea1a92920194364 upstream. Adding Intel codename

[PATCH 3.19.y-ckt 09/70] ahci: add new Intel device IDs

v3.19.8-ckt17 -stable review patch. If anyone has any objections, please let me know. ---8< From: Alexandra Yates commit 56e74338a535cbcc2f2da08b1ea1a92920194364 upstream. Adding Intel codename Lewisburg platform device IDs for

Re: [PATCH 2/2] bcma: use of_dma_configure() to set initial dma mask

Hi Arnd, [auto build test ERROR on v4.5-rc7] [also build test ERROR on next-20160317] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url:

Re: [PATCH 2/2] bcma: use of_dma_configure() to set initial dma mask

Hi Arnd, [auto build test ERROR on v4.5-rc7] [also build test ERROR on next-20160317] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url:

[PATCH v2 6/6] x86/pat: Document PAT initializations

Update PAT documentation to describe how PAT is initialized under various configurations. Signed-off-by: Toshi Kani Cc: Borislav Petkov Cc: Luis R. Rodriguez Cc: Juergen Gross Cc: Ingo Molnar Cc: H. Peter

[PATCH v2 6/6] x86/pat: Document PAT initializations

Update PAT documentation to describe how PAT is initialized under various configurations. Signed-off-by: Toshi Kani Cc: Borislav Petkov Cc: Luis R. Rodriguez Cc: Juergen Gross Cc: Ingo Molnar Cc: H. Peter Anvin Cc: Thomas Gleixner --- Documentation/x86/pat.txt | 32

[RESEND] [PATCH v11 5/6] add TC G210 platform driver

This patch adds a glue platform driver for the Synopsys G210 Test Chip. Signed-off-by: Joao Pinto --- Changes v10->v11 (Arnd Bergmann): - vops structs are now passed in .data Changes v0->v10: - This patch only appeared in v10

[PATCH 01/15] ARM: tegra: Correct interrupt type for ARM TWD

The ARM TWD interrupt is a private peripheral interrupt (PPI) and per the ARM GIC documentation, whether the type for PPIs can be set is IMPLEMENTATION DEFINED. For Tegra20/30 devices the PPI type cannot be set and so when we attempt to set the type for the ARM TWD interrupt it fails. This has

[PATCH 01/15] ARM: tegra: Correct interrupt type for ARM TWD

The ARM TWD interrupt is a private peripheral interrupt (PPI) and per the ARM GIC documentation, whether the type for PPIs can be set is IMPLEMENTATION DEFINED. For Tegra20/30 devices the PPI type cannot be set and so when we attempt to set the type for the ARM TWD interrupt it fails. This has

[RESEND] [PATCH v11 5/6] add TC G210 platform driver

This patch adds a glue platform driver for the Synopsys G210 Test Chip. Signed-off-by: Joao Pinto --- Changes v10->v11 (Arnd Bergmann): - vops structs are now passed in .data Changes v0->v10: - This patch only appeared in v10 .../devicetree/bindings/ufs/tc-dwc-g210-pltfrm.txt | 26 +

Re: [PATCH 1/2] mm/vmap: Add a notifier for when we run out of vmap address space

On Thu, Mar 17, 2016 at 1:57 PM, Chris Wilson wrote: > On Thu, Mar 17, 2016 at 01:37:06PM +0100, Roman Peniaev wrote: >> > + freed = 0; >> > + blocking_notifier_call_chain(_notify_list, 0, ); >> >> It seems to me that alloc_vmap_area() was designed not to

Re: [PATCH 1/2] mm/vmap: Add a notifier for when we run out of vmap address space

On Thu, Mar 17, 2016 at 1:57 PM, Chris Wilson wrote: > On Thu, Mar 17, 2016 at 01:37:06PM +0100, Roman Peniaev wrote: >> > + freed = 0; >> > + blocking_notifier_call_chain(_notify_list, 0, ); >> >> It seems to me that alloc_vmap_area() was designed not to sleep, >> at least on

[PART1 RFC v3 12/12] svm: Manage vcpu load/unload when enable AVIC

From: Suravee Suthikulpanit When a vcpu is loaded/unloaded to a physical core, we need to update host physical APIC ID information in the Physical APIC-ID table accordingly. Also, when vCPU is blocking/un-blocking (due to halt instruction), we need to make sure

Re: linux-next: manual merge of the rdma tree with the net-next tree

On Tue, Mar 15, 2016 at 5:58 PM, Stephen Rothwell wrote: > > I fixed it up (see below) and can carry the fix as necessary (no action > is required). Side note: can you change this wording for your manual merge script? Last merge window (or was it the one before it?) we had

[PART1 RFC v3 12/12] svm: Manage vcpu load/unload when enable AVIC

From: Suravee Suthikulpanit When a vcpu is loaded/unloaded to a physical core, we need to update host physical APIC ID information in the Physical APIC-ID table accordingly. Also, when vCPU is blocking/un-blocking (due to halt instruction), we need to make sure that the is-running bit in set

Re: linux-next: manual merge of the rdma tree with the net-next tree

On Tue, Mar 15, 2016 at 5:58 PM, Stephen Rothwell wrote: > > I fixed it up (see below) and can carry the fix as necessary (no action > is required). Side note: can you change this wording for your manual merge script? Last merge window (or was it the one before it?) we had confusion with people

[PATCH v2 6/9] efi/arm: libstub: make screen_info accessible to the UEFI stub

In order to hand over the framebuffer described by the GOP protocol and discovered by the UEFI stub, make struct screen_info accessible by the stub. This involves allocating a loader data buffer and passing it to the kernel proper via a UEFI Configuration Table, since the UEFI stub executes in the

[PATCH v2 6/9] efi/arm: libstub: make screen_info accessible to the UEFI stub

In order to hand over the framebuffer described by the GOP protocol and discovered by the UEFI stub, make struct screen_info accessible by the stub. This involves allocating a loader data buffer and passing it to the kernel proper via a UEFI Configuration Table, since the UEFI stub executes in the

Re: [PATCH 1/3] crypto: marvell/cesa - replace dma_to_phys with dma_map_single

On 3/18/2016 9:51 AM, Sinan Kaya wrote: > Another option is I can write > > engine->sram_dma = swiotlb_dma_to_phys(res->start) I realized that I made a mistake in the commit message and the code above. The code is trying to find DMA address from physical address. Not the other way around.

Re: [PATCH 1/3] crypto: marvell/cesa - replace dma_to_phys with dma_map_single

On 3/18/2016 9:51 AM, Sinan Kaya wrote: > Another option is I can write > > engine->sram_dma = swiotlb_dma_to_phys(res->start) I realized that I made a mistake in the commit message and the code above. The code is trying to find DMA address from physical address. Not the other way around.

Re: linux-next: manual merge of the rdma tree with the net-next tree

On 3/16/2016 1:18 PM, Linus Torvalds wrote: > On Tue, Mar 15, 2016 at 5:58 PM, Stephen Rothwell > wrote: >> >> I fixed it up (see below) and can carry the fix as necessary (no action >> is required). > > Side note: can you change this wording for your manual merge script?

Re: linux-next: manual merge of the rdma tree with the net-next tree

On 3/16/2016 1:18 PM, Linus Torvalds wrote: > On Tue, Mar 15, 2016 at 5:58 PM, Stephen Rothwell > wrote: >> >> I fixed it up (see below) and can carry the fix as necessary (no action >> is required). > > Side note: can you change this wording for your manual merge script? > Last merge window

[PATCH v5 4/4] ARM: STM32: Enable Ethernet in stm32_defconfig

Enable basic Ethernet support (IPV4) for stm32 defconfig. Signed-off-by: Alexandre TORGUE diff --git a/arch/arm/configs/stm32_defconfig b/arch/arm/configs/stm32_defconfig index ec52505..8b8abe0 100644 --- a/arch/arm/configs/stm32_defconfig +++

[PATCH v5 4/4] ARM: STM32: Enable Ethernet in stm32_defconfig

Enable basic Ethernet support (IPV4) for stm32 defconfig. Signed-off-by: Alexandre TORGUE diff --git a/arch/arm/configs/stm32_defconfig b/arch/arm/configs/stm32_defconfig index ec52505..8b8abe0 100644 --- a/arch/arm/configs/stm32_defconfig +++ b/arch/arm/configs/stm32_defconfig @@ -33,11 +33,20

Re: [PATCH 1/2] pinctrl: sh-pfc: enable to indicate GPSR/IPSR/MOD_SEL for debug

Hi Laurent, Geert > > struct pinmux_cfg_reg { > > + const char *name; > > This will increase the kernel size, I would remove the name field when > compiling the kernel in non-debug mode. You could use CONFIG_DYNAMIC_DEBUG or > CONFIG_DEBUG_PINCTRL. OK, [1/2] patch is not a big deal. I'm

Re: [PATCH 1/2] pinctrl: sh-pfc: enable to indicate GPSR/IPSR/MOD_SEL for debug

Hi Laurent, Geert > > struct pinmux_cfg_reg { > > + const char *name; > > This will increase the kernel size, I would remove the name field when > compiling the kernel in non-debug mode. You could use CONFIG_DYNAMIC_DEBUG or > CONFIG_DEBUG_PINCTRL. OK, [1/2] patch is not a big deal. I'm

[PATCH v2] net: smc911x: convert pxa dma to dmaengine

Convert the dma transfers to be dmaengine based, now pxa has a dmaengine slave driver. This makes this driver a bit more PXA agnostic. The driver was only compile tested. The risk is quite small as no current PXA platform I'm aware of is using smc911x driver. Signed-off-by: Robert Jarzmik

[PATCH v2] net: smc911x: convert pxa dma to dmaengine

Convert the dma transfers to be dmaengine based, now pxa has a dmaengine slave driver. This makes this driver a bit more PXA agnostic. The driver was only compile tested. The risk is quite small as no current PXA platform I'm aware of is using smc911x driver. Signed-off-by: Robert Jarzmik

Re: [PATCH 2/7] dmaengine: xilinx_vdma: Add quirks support to differentiate differnet IP cores

Hello, On Tuesday 15 March 2016 22:53:07 Kedareswara rao Appana wrote: > This patch adds quirks support in the driver to differentiate differnet IP s/differnet/different/ (and in the subject line too) With this series applied the driver will not be vdma-specific anymore. The xilinx_vdma_

Re: [PATCH 2/7] dmaengine: xilinx_vdma: Add quirks support to differentiate differnet IP cores

Hello, On Tuesday 15 March 2016 22:53:07 Kedareswara rao Appana wrote: > This patch adds quirks support in the driver to differentiate differnet IP s/differnet/different/ (and in the subject line too) With this series applied the driver will not be vdma-specific anymore. The xilinx_vdma_

Re: [GIT PULL] GPIO bulk changes for kernel v4.6

Linus Torvalds writes: > It's literally just the fact that "git merge" does it with no extra > flags or checks. I'd like people to have to be aware of what they are > doing when they merge two different projects, not do it by mistake. > > So making it conditional

Re: divide error: 0000 [#1] SMP in task_numa_migrate - handle_mm_fault vanilla 4.4.6

On Thu, Mar 17, 2016 at 07:38:03PM +0100, Stefan Priebe wrote: > Hi, > > while running qemu 2.5 on a host running 4.4.6 the host system has crashed > (load > 200) 3 times in the last 3 days. > > Always with this stack trace: (copy left here: > http://pastebin.com/raw/bCWTLKyt) > >

Re: [GIT PULL] GPIO bulk changes for kernel v4.6

Linus Torvalds writes: > It's literally just the fact that "git merge" does it with no extra > flags or checks. I'd like people to have to be aware of what they are > doing when they merge two different projects, not do it by mistake. > > So making it conditional on a flag like

Re: divide error: 0000 [#1] SMP in task_numa_migrate - handle_mm_fault vanilla 4.4.6

On Thu, Mar 17, 2016 at 07:38:03PM +0100, Stefan Priebe wrote: > Hi, > > while running qemu 2.5 on a host running 4.4.6 the host system has crashed > (load > 200) 3 times in the last 3 days. > > Always with this stack trace: (copy left here: > http://pastebin.com/raw/bCWTLKyt) > >

Re: [PATCH] Revert "arm64: Increase the max granular size"

On Thu, Mar 17, 2016 at 09:49:51AM -0500, Timur Tabi wrote: > Catalin Marinas wrote: > >>>Yes, that's exactly it. Ours is an ACPI system, and so we have to have our > >>>own defconfig for now. We're holding off on pushing our own defconfig > >>>changes (enabling drivers, etc) until ACPI is

Re: [PATCH] Revert "arm64: Increase the max granular size"

On Thu, Mar 17, 2016 at 09:49:51AM -0500, Timur Tabi wrote: > Catalin Marinas wrote: > >>>Yes, that's exactly it. Ours is an ACPI system, and so we have to have our > >>>own defconfig for now. We're holding off on pushing our own defconfig > >>>changes (enabling drivers, etc) until ACPI is

[RFC v2] Documentation: mmc: Add the introduction for mmc-utils

This patch introduces one mmc test tools called mmc-utils, which is convenient if someone wants to exercise and test MMC/SD devices from userspace. Signed-off-by: Baolin Wang --- Documentation/mmc/00-INDEX |2 ++ Documentation/mmc/mmc-tools.txt | 34

[RFC v2] Documentation: mmc: Add the introduction for mmc-utils

This patch introduces one mmc test tools called mmc-utils, which is convenient if someone wants to exercise and test MMC/SD devices from userspace. Signed-off-by: Baolin Wang --- Documentation/mmc/00-INDEX |2 ++ Documentation/mmc/mmc-tools.txt | 34 ++

Re: [PATCH v2 1/4] nmi_backtrace: add more trigger_*_cpu_backtrace() methods

On Thu, Mar 17, 2016 at 06:41:42PM -0400, Chris Metcalf wrote: > The build bot caught the fact that I missed arch/xtensa since it doesn't use > LOCK_TEXT, so if you're testing on that (ok maybe unlikely) you can add this: Ha!, no. regular boring x86_64.

Re: [PATCH v2 1/4] nmi_backtrace: add more trigger_*_cpu_backtrace() methods

On Thu, Mar 17, 2016 at 06:41:42PM -0400, Chris Metcalf wrote: > The build bot caught the fact that I missed arch/xtensa since it doesn't use > LOCK_TEXT, so if you're testing on that (ok maybe unlikely) you can add this: Ha!, no. regular boring x86_64.

Re: [PATCH v11 3/9] arm64: add copy_to/from_user to kprobes blacklist

Hi Pratyush, On 18/03/16 13:29, Pratyush Anand wrote: > Probably, I can see why does not it work. So, when we are single stepping an > instruction and page fault occurs, we will come to el1_da in entry.S. Here, we > do enable_dbg. As soon as we will do this, we will start receiving single step >

Re: [PATCH v11 3/9] arm64: add copy_to/from_user to kprobes blacklist

Hi Pratyush, On 18/03/16 13:29, Pratyush Anand wrote: > Probably, I can see why does not it work. So, when we are single stepping an > instruction and page fault occurs, we will come to el1_da in entry.S. Here, we > do enable_dbg. As soon as we will do this, we will start receiving single step >

[PATCH 3.19.y-ckt 65/70] ipv6: re-enable fragment header matching in ipv6_find_hdr

v3.19.8-ckt17 -stable review patch. If anyone has any objections, please let me know. ---8< From: Florian Westphal commit 5d150a985520bbe3cb2aa1ceef24a7e32f20c15f upstream. When ipv6_find_hdr is used to find a

[PATCH 3.19.y-ckt 65/70] ipv6: re-enable fragment header matching in ipv6_find_hdr

v3.19.8-ckt17 -stable review patch. If anyone has any objections, please let me know. ---8< From: Florian Westphal commit 5d150a985520bbe3cb2aa1ceef24a7e32f20c15f upstream. When ipv6_find_hdr is used to find a fragment header

[PATCH 3.19.y-ckt 62/70] tcp: convert cached rtt from usec to jiffies when feeding initial rto

v3.19.8-ckt17 -stable review patch. If anyone has any objections, please let me know. ---8< From: Konstantin Khlebnikov commit 9bdfb3b79e61c60e1a3e2dc05ad164528afa6b8a upstream. Currently it's converted

Re: [PATCH 4/5] gpio: of: Add support to have multiple gpios in gpio-hog

On Thursday 17 March 2016 09:16 PM, Rob Herring wrote: On Thu, Mar 10, 2016 at 05:23:55PM +0530, Laxman Dewangan wrote: On this case, we have already property "line-name" and passed the name of the gpio via this property. The property names is "line-name" which is good for one string. We can

[PATCH 3.19.y-ckt 62/70] tcp: convert cached rtt from usec to jiffies when feeding initial rto

v3.19.8-ckt17 -stable review patch. If anyone has any objections, please let me know. ---8< From: Konstantin Khlebnikov commit 9bdfb3b79e61c60e1a3e2dc05ad164528afa6b8a upstream. Currently it's converted into msecs, thus HZ=1000

Re: [PATCH 4/5] gpio: of: Add support to have multiple gpios in gpio-hog

On Thursday 17 March 2016 09:16 PM, Rob Herring wrote: On Thu, Mar 10, 2016 at 05:23:55PM +0530, Laxman Dewangan wrote: On this case, we have already property "line-name" and passed the name of the gpio via this property. The property names is "line-name" which is good for one string. We can

[PATCH v2] misc: mic: Remove return statements from void functions

Return statements at the end of void functions are useless. The Coccinelle semantic patch used to make this change is as follows: // @@ identifier f; expression e; @@ void f(...) { <... - return e; ...> } // Signed-off-by: Amitoj Kaur Chawla --- Changes in v2:

[PATCH v2] misc: mic: Remove return statements from void functions

Return statements at the end of void functions are useless. The Coccinelle semantic patch used to make this change is as follows: // @@ identifier f; expression e; @@ void f(...) { <... - return e; ...> } // Signed-off-by: Amitoj Kaur Chawla --- Changes in v2: -Resend to add Greg's

Re: [RESEND PATCH v4 5/5] clocksource: add memory-mapped timer support in arm_arch_timer.c

On Fri, 18 Mar 2016, fu@linaro.org wrote: > +static u32 __init arch_timer_mem_cnttidr(struct acpi_gtdt_timer_block > *gt_block) > +{ > + phys_addr_t cntctlbase_phy; > + void __iomem *cntctlbase; > + u32 cnttidr; > + > + cntctlbase_phy =

Re: [RESEND PATCH v4 5/5] clocksource: add memory-mapped timer support in arm_arch_timer.c

On Fri, 18 Mar 2016, fu@linaro.org wrote: > +static u32 __init arch_timer_mem_cnttidr(struct acpi_gtdt_timer_block > *gt_block) > +{ > + phys_addr_t cntctlbase_phy; > + void __iomem *cntctlbase; > + u32 cnttidr; > + > + cntctlbase_phy =

Re: [PATCH] usb: chipidea: Configure DMA properties and ops from DT

On Monday 14 March 2016 18:51:08 Peter Chen wrote: > On Wed, Mar 09, 2016 at 05:16:50PM -0600, Li Yang wrote: > > On Tue, Mar 8, 2016 at 9:40 PM, Bjorn Andersson > > wrote: > > > On Tue, Mar 8, 2016 at 11:52 AM, Li Yang wrote: > > >> On Wed, Mar

Re: [PATCH] usb: chipidea: Configure DMA properties and ops from DT

On Monday 14 March 2016 18:51:08 Peter Chen wrote: > On Wed, Mar 09, 2016 at 05:16:50PM -0600, Li Yang wrote: > > On Tue, Mar 8, 2016 at 9:40 PM, Bjorn Andersson > > wrote: > > > On Tue, Mar 8, 2016 at 11:52 AM, Li Yang wrote: > > >> On Wed, Mar 2, 2016 at 4:59 PM, Li Yang wrote: > > >>> On

Re: [PATCH 14/15] dt-bindings: arm-gic: Drop 'clock-names' from binding document

Hi Grygorii, On Fri, Mar 18, 2016 at 1:47 PM, Grygorii Strashko wrote: > On 03/18/2016 02:05 PM, Geert Uytterhoeven wrote: >> On Fri, Mar 18, 2016 at 11:56 AM, Jon Hunter wrote: >>> On 18/03/16 10:52, Geert Uytterhoeven wrote: On Fri, Mar 18,

Re: [PATCH 14/15] dt-bindings: arm-gic: Drop 'clock-names' from binding document

Hi Grygorii, On Fri, Mar 18, 2016 at 1:47 PM, Grygorii Strashko wrote: > On 03/18/2016 02:05 PM, Geert Uytterhoeven wrote: >> On Fri, Mar 18, 2016 at 11:56 AM, Jon Hunter wrote: >>> On 18/03/16 10:52, Geert Uytterhoeven wrote: On Fri, Mar 18, 2016 at 11:13 AM, Jon Hunter wrote: > On

Re: Oops from calibrate_delay_is_known on qemu machine with Linux v4.5-1523-g271ecc5253e2

On Thu, Mar 17, 2016 at 01:54:36PM -0400, Josh Boyer wrote: > Hi Thomas, > > We've had a report [1] of the mainline kernel crashing on a single-cpu > QEMU machine (not kvm) in Fedora. It looks as if the emulated machine > is failing to provide a TSC and the calibrate_delay_is_known function > is

Re: Suspicious error for CMA stress test

2016-03-17 18:24 GMT+09:00 Hanjun Guo : > On 2016/3/17 14:54, Joonsoo Kim wrote: >> On Wed, Mar 16, 2016 at 05:44:28PM +0800, Hanjun Guo wrote: >>> On 2016/3/14 15:18, Joonsoo Kim wrote: On Mon, Mar 14, 2016 at 08:06:16AM +0100, Vlastimil Babka wrote: > On 03/14/2016

Re: Oops from calibrate_delay_is_known on qemu machine with Linux v4.5-1523-g271ecc5253e2

On Thu, Mar 17, 2016 at 01:54:36PM -0400, Josh Boyer wrote: > Hi Thomas, > > We've had a report [1] of the mainline kernel crashing on a single-cpu > QEMU machine (not kvm) in Fedora. It looks as if the emulated machine > is failing to provide a TSC and the calibrate_delay_is_known function > is

Re: Suspicious error for CMA stress test

2016-03-17 18:24 GMT+09:00 Hanjun Guo : > On 2016/3/17 14:54, Joonsoo Kim wrote: >> On Wed, Mar 16, 2016 at 05:44:28PM +0800, Hanjun Guo wrote: >>> On 2016/3/14 15:18, Joonsoo Kim wrote: On Mon, Mar 14, 2016 at 08:06:16AM +0100, Vlastimil Babka wrote: > On 03/14/2016 07:49 AM, Joonsoo Kim

Re: [PATCH v2] staging/comedi/dt282x: avoid integer overflow warning

On Thursday 17 March 2016 15:47:57 Hartley Sweeten wrote: > On Wednesday, March 16, 2016 1:51 PM, Arnd Bergmann wrote: > > Is this a gcc-6 specific issue? Seems line this warning should be showing > up in a lot of drivers. Yes, I did not see this before moving to gcc-6.0, but this is the only

Re: [PATCH v2] staging/comedi/dt282x: avoid integer overflow warning

On Thursday 17 March 2016 15:47:57 Hartley Sweeten wrote: > On Wednesday, March 16, 2016 1:51 PM, Arnd Bergmann wrote: > > Is this a gcc-6 specific issue? Seems line this warning should be showing > up in a lot of drivers. Yes, I did not see this before moving to gcc-6.0, but this is the only

Re: [PATCH v3 7/8] Documentation: devicetree: rockchip: Document Landingship

On Sun, Mar 06, 2016 at 08:53:56PM +0100, Andreas Färber wrote: > Use "geekbuying,geekbox-landingship" compatible string, plus those of > the GeekBox module. > > Signed-off-by: Andreas Färber > --- > v2 -> v3: > * Changed compatible string to include geekbox- (Heiko) >and

Re: [PATCH v3 7/8] Documentation: devicetree: rockchip: Document Landingship

On Sun, Mar 06, 2016 at 08:53:56PM +0100, Andreas Färber wrote: > Use "geekbuying,geekbox-landingship" compatible string, plus those of > the GeekBox module. > > Signed-off-by: Andreas Färber > --- > v2 -> v3: > * Changed compatible string to include geekbox- (Heiko) >and clarify that this

[PATCH BlueZ v5] tools/btattach: add marvell support

From: Ganapathi Bhat User needs to issue below command for Marvell devices btattach -P marvell -B /dev/ttyUSB# --- tools/btattach.c | 1 + tools/hciattach.h | 1 + 2 files changed, 2 insertions(+) diff --git a/tools/btattach.c b/tools/btattach.c index a025bb0..7807e9f

[PATCH BlueZ v5] tools/btattach: add marvell support

From: Ganapathi Bhat User needs to issue below command for Marvell devices btattach -P marvell -B /dev/ttyUSB# --- tools/btattach.c | 1 + tools/hciattach.h | 1 + 2 files changed, 2 insertions(+) diff --git a/tools/btattach.c b/tools/btattach.c index a025bb0..7807e9f 100644 ---

Re: [GIT PULL] Score: Fix the check condition of get_sigframe

On Tue, Mar 15, 2016 at 9:33 AM, Lennox Wu wrote: > > git://github.com/sctscore/linux-off.git sig Please use a signed tag for github pull requests. I don't pull unsigned branches from open hosting sites. Yeah, yeah, I know this is a one-liner, and I could just eyeball the

Re: [GIT PULL] Score: Fix the check condition of get_sigframe

On Tue, Mar 15, 2016 at 9:33 AM, Lennox Wu wrote: > > git://github.com/sctscore/linux-off.git sig Please use a signed tag for github pull requests. I don't pull unsigned branches from open hosting sites. Yeah, yeah, I know this is a one-liner, and I could just eyeball the end result to make

Re: [PATCH 0/2] usb: dwc3: gadget: Fix erratic interrupts and delayed enumeration

Hi, Roger Quadros writes: > The existing workaround (for STAR#9000525659) of forcing > DEVSPD to SUPER_SPEED for HIGH_SPEED ports is causing > another side effect which causes erratic interrupts and delayed gadget > enumeration of upto 2 seconds. right, but the real problem is

Re: [PATCH 0/2] usb: dwc3: gadget: Fix erratic interrupts and delayed enumeration

Hi, Roger Quadros writes: > The existing workaround (for STAR#9000525659) of forcing > DEVSPD to SUPER_SPEED for HIGH_SPEED ports is causing > another side effect which causes erratic interrupts and delayed gadget > enumeration of upto 2 seconds. right, but the real problem is with an SoC

Re: [PATCH 4/4] dma: qcom_hidma: read the channel id from HW

On Fri, Mar 11, 2016 at 04:49:54PM -0500, Sinan Kaya wrote: > Removing the flexibility to choose the event channel as there is no real > use case right now. We have been using the values in ACPI that match the HW > defaults. OS is reading the event-channel from the HW register now. > >

Re: [PATCH 4/4] dma: qcom_hidma: read the channel id from HW

On Fri, Mar 11, 2016 at 04:49:54PM -0500, Sinan Kaya wrote: > Removing the flexibility to choose the event channel as there is no real > use case right now. We have been using the values in ACPI that match the HW > defaults. OS is reading the event-channel from the HW register now. > >

Re: [PATCH 4/5] rtc: jz4740_rtc: Add support for acting as the system power controller

On 05/03/2016 at 23:38:50 +0100, Paul Cercueil wrote : > + if (of_device_is_system_power_controller(pdev->dev.of_node)) { > + if (!pm_power_off) { > + /* Default: 60ms */ > + rtc->reset_pin_assert_time = 60; > +

Re: [PATCH 4/5] rtc: jz4740_rtc: Add support for acting as the system power controller

On 05/03/2016 at 23:38:50 +0100, Paul Cercueil wrote : > + if (of_device_is_system_power_controller(pdev->dev.of_node)) { > + if (!pm_power_off) { > + /* Default: 60ms */ > + rtc->reset_pin_assert_time = 60; > +

  1   2   3   4   5   6   7   8   9   10   >