[PATCH] checkpatch: don't check c99 types like uint8_t under tools

Tools contains user space code so uintX_t types are just fine. Signed-off-by: Tomas Winkler --- scripts/checkpatch.pl | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl index a8368d1c4348..42c3221be6eb

[PATCH] checkpatch: don't check c99 types like uint8_t under tools

Tools contains user space code so uintX_t types are just fine. Signed-off-by: Tomas Winkler --- scripts/checkpatch.pl | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl index a8368d1c4348..42c3221be6eb 100755 ---

Re: [PATCH] mtd: nand: nandsim: fix error check

On Tuesday 15 November 2016 11:42 PM, Marek Vasut wrote: On 11/16/2016 12:09 AM, Sudip Mukherjee wrote: debugfs_create_dir() and debugfs_create_file() returns NULL on error or a pointer on success. They do not return the error value with ERR_PTR. So we should not check the return with

Re: [PATCH] mtd: nand: nandsim: fix error check

On Tuesday 15 November 2016 11:42 PM, Marek Vasut wrote: On 11/16/2016 12:09 AM, Sudip Mukherjee wrote: debugfs_create_dir() and debugfs_create_file() returns NULL on error or a pointer on success. They do not return the error value with ERR_PTR. So we should not check the return with

Re: [PATCHSET 0/7] perf sched: Introduce timehist command, again (v2)

* Namhyung Kim wrote: > Hello, > > This patchset is a rebased version of David's sched timehist work [1]. > I plan to improve perf sched command more and think that having > timehist command before the work looks good. It seems David is busy > these days, so I'm retrying

Re: [PATCHSET 0/7] perf sched: Introduce timehist command, again (v2)

* Namhyung Kim wrote: > Hello, > > This patchset is a rebased version of David's sched timehist work [1]. > I plan to improve perf sched command more and think that having > timehist command before the work looks good. It seems David is busy > these days, so I'm retrying it by myself. > > *

[PATCH] b: re-queue tx dma request on herror

Some times dma transfer to usb endpoint fails: [ 78.378283] musb-hdrc musb-hdrc.1.auto: Start TX10 dma [ 78.410763] musb-hdrc musb-hdrc.1.auto: OUT/TX10 end, csr 3400, dma [ 78.410896] musb-hdrc musb-hdrc.1.auto: complete dc01eb00 usb_api_blocking_completion+0x0/0x24 [usbcore] (0), dev4 ep1out,

[PATCH] b: re-queue tx dma request on herror

Some times dma transfer to usb endpoint fails: [ 78.378283] musb-hdrc musb-hdrc.1.auto: Start TX10 dma [ 78.410763] musb-hdrc musb-hdrc.1.auto: OUT/TX10 end, csr 3400, dma [ 78.410896] musb-hdrc musb-hdrc.1.auto: complete dc01eb00 usb_api_blocking_completion+0x0/0x24 [usbcore] (0), dev4 ep1out,

[PATCH] mm, rmap: handle anon_vma_prepare() common case inline

The anon_vma_prepare() function is mostly a large "if (unlikely(...))" block, as the expected common case is that an anon_vma already exists. We could turn the condition around and return 0, but it also makes sense to do it inline and avoid a call for the common case. Bloat-o-meter naturally

[PATCH] mm, rmap: handle anon_vma_prepare() common case inline

The anon_vma_prepare() function is mostly a large "if (unlikely(...))" block, as the expected common case is that an anon_vma already exists. We could turn the condition around and return 0, but it also makes sense to do it inline and avoid a call for the common case. Bloat-o-meter naturally

Re: [PATCH net-next 2/5] net: ethoc: Implement ethtool::nway_reset

On 2016-11-15 at 20:19:46 +0100, Florian Fainelli wrote: > Implement ethtool::nway_reset using phy_ethtool_nway_reset. We are > already using dev->phydev all over the place so this comes for free. > > Signed-off-by: Florian Fainelli Reviewed-by:

Re: [PATCH net-next 2/5] net: ethoc: Implement ethtool::nway_reset

On 2016-11-15 at 20:19:46 +0100, Florian Fainelli wrote: > Implement ethtool::nway_reset using phy_ethtool_nway_reset. We are > already using dev->phydev all over the place so this comes for free. > > Signed-off-by: Florian Fainelli Reviewed-by: Tobias Klauser

i2c: undefined option I2C_ALGO_BUSCLEAR

Hi Shardar, your commit c3ca951fe41a ("i2c: Add Tegra BPMP I2C proxy driver") popped up in today's linux-next tree, adding Kconfig option I2C_TEGRA_BPMP, which further selects I2C_ALGO_BUSCLEAR, which is nowhere defined in Kconfig. Is there a patch queued somewhere to add I2C_ALGO_BUSCLEAR to

i2c: undefined option I2C_ALGO_BUSCLEAR

Hi Shardar, your commit c3ca951fe41a ("i2c: Add Tegra BPMP I2C proxy driver") popped up in today's linux-next tree, adding Kconfig option I2C_TEGRA_BPMP, which further selects I2C_ALGO_BUSCLEAR, which is nowhere defined in Kconfig. Is there a patch queued somewhere to add I2C_ALGO_BUSCLEAR to

Re: [PATCH] kasan: support use-after-scope detection

On Wed, Nov 16, 2016 at 12:40 AM, Andrew Morton wrote: > On Tue, 15 Nov 2016 17:07:25 +0100 Dmitry Vyukov wrote: > >> Gcc revision 241896 implements use-after-scope detection. >> Will be available in gcc 7. Support it in KASAN. >> >> Gcc emits 2 new

Re: [PATCH] kasan: support use-after-scope detection

On Wed, Nov 16, 2016 at 12:40 AM, Andrew Morton wrote: > On Tue, 15 Nov 2016 17:07:25 +0100 Dmitry Vyukov wrote: > >> Gcc revision 241896 implements use-after-scope detection. >> Will be available in gcc 7. Support it in KASAN. >> >> Gcc emits 2 new callbacks to poison/unpoison large stack >>

Re: [PATCH] vt: fix Scroll Lock LED trigger name

On Wed, Nov 16, 2016 at 12:55:57AM +0100, Maciej S. Szmigiero wrote: > There is a disagreement between drivers/tty/vt/keyboard.c and > drivers/input/input-leds.c with regard to what is a Scroll Lock LED > trigger name: input calls it "kbd-scrolllock", but vt calls it > "kbd-scrollock" (two l's). >

Re: [PATCH] vt: fix Scroll Lock LED trigger name

On Wed, Nov 16, 2016 at 12:55:57AM +0100, Maciej S. Szmigiero wrote: > There is a disagreement between drivers/tty/vt/keyboard.c and > drivers/input/input-leds.c with regard to what is a Scroll Lock LED > trigger name: input calls it "kbd-scrolllock", but vt calls it > "kbd-scrollock" (two l's). >

Re: [PATCH] mm: don't cap request size based on read-ahead setting

On Wednesday, November 16, 2016 12:31 PM Jens Axboe wrote: > @@ -369,10 +369,25 @@ ondemand_readahead(struct address_space *mapping, > bool hit_readahead_marker, pgoff_t offset, > unsigned long req_size) > { > - unsigned long max = ra->ra_pages; > +

Re: [PATCH] mm: don't cap request size based on read-ahead setting

On Wednesday, November 16, 2016 12:31 PM Jens Axboe wrote: > @@ -369,10 +369,25 @@ ondemand_readahead(struct address_space *mapping, > bool hit_readahead_marker, pgoff_t offset, > unsigned long req_size) > { > - unsigned long max = ra->ra_pages; > +

[PATCH v2] kasan: support use-after-scope detection

Gcc revision 241896 implements use-after-scope detection. Will be available in gcc 7. Support it in KASAN. Gcc emits 2 new callbacks to poison/unpoison large stack objects when they go in/out of scope. Implement the callbacks and add a test. Signed-off-by: Dmitry Vyukov Cc:

[PATCH v2] kasan: support use-after-scope detection

Gcc revision 241896 implements use-after-scope detection. Will be available in gcc 7. Support it in KASAN. Gcc emits 2 new callbacks to poison/unpoison large stack objects when they go in/out of scope. Implement the callbacks and add a test. Signed-off-by: Dmitry Vyukov Cc:

Re: Patch procedure

On Tue, Nov 15, 2016 at 08:55:11AM +, Ioana Ciornei wrote: > > > -Original Message- > > From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel- > > ow...@vger.kernel.org] On Behalf Of feas > > Sent: Monday, November 14, 2016 7:16 PM > > To: de...@driverdev.osuosl.org;

Re: Patch procedure

On Tue, Nov 15, 2016 at 08:55:11AM +, Ioana Ciornei wrote: > > > -Original Message- > > From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel- > > ow...@vger.kernel.org] On Behalf Of feas > > Sent: Monday, November 14, 2016 7:16 PM > > To: de...@driverdev.osuosl.org;

Re: [OpenRISC] [PATCH v2 8/9] openrisc: Updates after openrisc.net has been lost

On Mon, Nov 14, 2016 at 2:30 PM, Stafford Horne wrote: > The openrisc.net domain expired and was taken over by squatters. > These updates point documentation to the new domain, mailing lists > and git repos. > > Also, Jonas is not the main maintainer anylonger, he reviews

Re: [OpenRISC] [PATCH v2 8/9] openrisc: Updates after openrisc.net has been lost

On Mon, Nov 14, 2016 at 2:30 PM, Stafford Horne wrote: > The openrisc.net domain expired and was taken over by squatters. > These updates point documentation to the new domain, mailing lists > and git repos. > > Also, Jonas is not the main maintainer anylonger, he reviews changes > but does not

Re: [PATCH v2] staging: slicoss: fix different address space warnings

On Wed, Nov 16, 2016 at 05:07:37AM +0100, Sergio Paracuellos wrote: > This patch fix the following sparse warnings in slicoss driver: > warning: incorrect type in assignment (different address spaces) > > Changes in v2: > * Remove IOMEM_GET_FIELDADDR macro > * Add ioread64 and iowrite64 defines >

Re: [PATCH v2] staging: slicoss: fix different address space warnings

On Wed, Nov 16, 2016 at 05:07:37AM +0100, Sergio Paracuellos wrote: > This patch fix the following sparse warnings in slicoss driver: > warning: incorrect type in assignment (different address spaces) > > Changes in v2: > * Remove IOMEM_GET_FIELDADDR macro > * Add ioread64 and iowrite64 defines >

Re: [PATCH 1/3] virtio: Basic implementation of virtio pstore driver

Hi, On Tue, Nov 15, 2016 at 11:38 PM, Paolo Bonzini wrote: > > > On 15/11/2016 15:36, Namhyung Kim wrote: >> Hi, >> >> On Tue, Nov 15, 2016 at 10:57:29AM +0100, Paolo Bonzini wrote: >>> >>> >>> On 15/11/2016 06:06, Michael S. Tsirkin wrote: On Tue, Nov 15, 2016 at

Re: [PATCH 1/3] virtio: Basic implementation of virtio pstore driver

Hi, On Tue, Nov 15, 2016 at 11:38 PM, Paolo Bonzini wrote: > > > On 15/11/2016 15:36, Namhyung Kim wrote: >> Hi, >> >> On Tue, Nov 15, 2016 at 10:57:29AM +0100, Paolo Bonzini wrote: >>> >>> >>> On 15/11/2016 06:06, Michael S. Tsirkin wrote: On Tue, Nov 15, 2016 at 01:50:21PM +0900, Namhyung

[RESEND PATCH v7 3/3] clocksource: Add clockevent support to NPS400 driver

From: Noam Camus Till now we used clockevent from generic ARC driver. This was enough as long as we worked with simple multicore SoC. When we are working with multithread SoC each HW thread can be scheduled to receive timer interrupt using timer mask register. This patch

[RESEND PATCH v7 3/3] clocksource: Add clockevent support to NPS400 driver

From: Noam Camus Till now we used clockevent from generic ARC driver. This was enough as long as we worked with simple multicore SoC. When we are working with multithread SoC each HW thread can be scheduled to receive timer interrupt using timer mask register. This patch will provide a way to

Re: [PATCH] clk: qoriq: added ls1012a clock configuration

On Wed, 2016-11-16 at 13:58 +0800, yuantian.t...@nxp.com wrote: > From: Tang Yuantian > > Added ls1012a clock configuation information. Do we really need the same line in the changelog twice? > > Signed-off-by: Tang Yuantian > --- >  

Re: [PATCH] clk: qoriq: added ls1012a clock configuration

On Wed, 2016-11-16 at 13:58 +0800, yuantian.t...@nxp.com wrote: > From: Tang Yuantian > > Added ls1012a clock configuation information. Do we really need the same line in the changelog twice? > > Signed-off-by: Tang Yuantian > --- >  drivers/clk/clk-qoriq.c | 19 +++ >  1 file

[RESEND PATCH v7 1/3] soc: Support for NPS HW scheduling

From: Noam Camus This new header file is for NPS400 SoC (part of ARC architecture). The header file includes macros for save/restore of HW scheduling. The control of HW scheduling is achieved by writing core registers. This code was moved from arc/plat-eznps so it can be

[RESEND PATCH v7 1/3] soc: Support for NPS HW scheduling

From: Noam Camus This new header file is for NPS400 SoC (part of ARC architecture). The header file includes macros for save/restore of HW scheduling. The control of HW scheduling is achieved by writing core registers. This code was moved from arc/plat-eznps so it can be used from

Re: [PATCH v3 0/8] pstore: Improve performance of ftrace backend with ramoops

On Tue, Nov 15, 2016 at 2:14 PM, Kees Cook wrote: > On Tue, Nov 15, 2016 at 2:06 PM, Joel Fernandes wrote: >> Hi Kees, >> >> On Tue, Nov 15, 2016 at 1:36 PM, Kees Cook wrote: >>> On Tue, Nov 15, 2016 at 11:55 AM, Joel Fernandes

Re: [PATCH v3 0/8] pstore: Improve performance of ftrace backend with ramoops

On Tue, Nov 15, 2016 at 2:14 PM, Kees Cook wrote: > On Tue, Nov 15, 2016 at 2:06 PM, Joel Fernandes wrote: >> Hi Kees, >> >> On Tue, Nov 15, 2016 at 1:36 PM, Kees Cook wrote: >>> On Tue, Nov 15, 2016 at 11:55 AM, Joel Fernandes wrote: Hi Kees, On Fri, Nov 11, 2016 at 2:21 PM,

Re: [PATCH v4 4/4] ARM: dts: da850: Add the usb otg device nodeg

On Wednesday 16 November 2016 02:49 AM, Bin Liu wrote: > On Tue, Nov 15, 2016 at 04:16:02PM +0530, Sekhar Nori wrote: >> On Thursday 03 November 2016 09:29 PM, Alexandre Bailon wrote: >>> This adds the device tree node for the usb otg >>> controller present in the da850 family of SoC's. >>> This

Re: [PATCH v4 4/4] ARM: dts: da850: Add the usb otg device nodeg

On Wednesday 16 November 2016 02:49 AM, Bin Liu wrote: > On Tue, Nov 15, 2016 at 04:16:02PM +0530, Sekhar Nori wrote: >> On Thursday 03 November 2016 09:29 PM, Alexandre Bailon wrote: >>> This adds the device tree node for the usb otg >>> controller present in the da850 family of SoC's. >>> This

[RESEND PATCH v7 0/3] Add clockevent for timer-nps driver to NPS400 SoC

From: Noam Camus Change log --- V6 --> V7 Apply several comments made by Daniel Lezcano: 1) Remove CLOCK_EVT_FEAT_PERIODIC support. This way it is pure oneshot driver. This simplifies driver so that: nps_clkevent_add_thread() nps_clkevent_rm_thread() are more clearer

[RESEND PATCH v7 2/3] clocksource: update "fn" at CLOCKSOURCE_OF_DECLARE() of nps400 timer

From: Noam Camus nps_setup_clocksource() should take node as only argument as defined by typedef int (*of_init_fn_1_ret)(struct device_node *) Therefore need to replace: int __init nps_setup_clocksource(struct device_node *node, struct clk *clk) with int __init

[RESEND PATCH v7 0/3] Add clockevent for timer-nps driver to NPS400 SoC

From: Noam Camus Change log --- V6 --> V7 Apply several comments made by Daniel Lezcano: 1) Remove CLOCK_EVT_FEAT_PERIODIC support. This way it is pure oneshot driver. This simplifies driver so that: nps_clkevent_add_thread() nps_clkevent_rm_thread() are more clearer without any vague logic

[RESEND PATCH v7 2/3] clocksource: update "fn" at CLOCKSOURCE_OF_DECLARE() of nps400 timer

From: Noam Camus nps_setup_clocksource() should take node as only argument as defined by typedef int (*of_init_fn_1_ret)(struct device_node *) Therefore need to replace: int __init nps_setup_clocksource(struct device_node *node, struct clk *clk) with int __init nps_setup_clocksource(struct

[PATCH] edac: mpc85xx: implement "remove" for mpc85xx_pci_err_driver

From: Yanjiang Jin Tested on a T4240QDS board. If we execute the below steps without this patch: 1. modprobe mpc85xx_edac [The first insmod, everything is well.] 2. modprobe -r mpc85xx_edac 3. modprobe mpc85xx_edac [insmod again, error happens.] We would get the

[PATCH] edac: mpc85xx: implement "remove" for mpc85xx_pci_err_driver

From: Yanjiang Jin Tested on a T4240QDS board. If we execute the below steps without this patch: 1. modprobe mpc85xx_edac [The first insmod, everything is well.] 2. modprobe -r mpc85xx_edac 3. modprobe mpc85xx_edac [insmod again, error happens.] We would get the below error: BUG: recent

[PATCH v4 2/6] usb: chipidea: use bus->sysdev for DMA configuration

From: Arnd Bergmann Set the dma for chipidea from sysdev. This is inherited from its parent node. Also, do not set dma mask for child as it is not required now. Signed-off-by: Arnd Bergmann Signed-off-by: Sriram Dash Acked-by: Peter Chen

[PATCH v4 2/6] usb: chipidea: use bus->sysdev for DMA configuration

From: Arnd Bergmann Set the dma for chipidea from sysdev. This is inherited from its parent node. Also, do not set dma mask for child as it is not required now. Signed-off-by: Arnd Bergmann Signed-off-by: Sriram Dash Acked-by: Peter Chen --- Changes in v4: - No update Changes in v3: -

[PATCH] clk: qoriq: added ls1012a clock configuration

From: Tang Yuantian Added ls1012a clock configuation information. Signed-off-by: Tang Yuantian --- drivers/clk/clk-qoriq.c | 19 +++ 1 file changed, 19 insertions(+) diff --git a/drivers/clk/clk-qoriq.c b/drivers/clk/clk-qoriq.c

[PATCH] clk: qoriq: added ls1012a clock configuration

From: Tang Yuantian Added ls1012a clock configuation information. Signed-off-by: Tang Yuantian --- drivers/clk/clk-qoriq.c | 19 +++ 1 file changed, 19 insertions(+) diff --git a/drivers/clk/clk-qoriq.c b/drivers/clk/clk-qoriq.c index 1bece0f..563d874 100644 ---

[PATCH v4 4/6] usb: xhci: use bus->sysdev for DMA configuration

From: Arnd Bergmann For xhci-hcd platform device, all the DMA parameters are not configured properly, notably dma ops for dwc3 devices. So, set the dma for xhci from sysdev. sysdev is pointing to device that is known to the system firmware or hardware. Signed-off-by: Arnd

[PATCH v4 4/6] usb: xhci: use bus->sysdev for DMA configuration

From: Arnd Bergmann For xhci-hcd platform device, all the DMA parameters are not configured properly, notably dma ops for dwc3 devices. So, set the dma for xhci from sysdev. sysdev is pointing to device that is known to the system firmware or hardware. Signed-off-by: Arnd Bergmann

[PATCH v4 3/6] usb: ehci: fsl: use bus->sysdev for DMA configuration

From: Arnd Bergmann For the dual role ehci fsl driver, sysdev will handle the dma config. Signed-off-by: Arnd Bergmann Signed-off-by: Sriram Dash --- Changes in v4: - No update Changes in v3: - fix compile errors Changes in v2: - fix

[PATCH v4 3/6] usb: ehci: fsl: use bus->sysdev for DMA configuration

From: Arnd Bergmann For the dual role ehci fsl driver, sysdev will handle the dma config. Signed-off-by: Arnd Bergmann Signed-off-by: Sriram Dash --- Changes in v4: - No update Changes in v3: - fix compile errors Changes in v2: - fix compile warnings drivers/usb/host/ehci-fsl.c | 4

Re: [GIT PULL] fbdev fixes for 4.9

Tomi Valkeinen writes: > [ Unknown signature status ] > On 14/11/16 18:25, Linus Torvalds wrote: >> On Mon, Nov 14, 2016 at 3:44 AM, Tomi Valkeinen >> wrote: >>> >>> Please pull two fbdev fixes for 4.9. >> >> No. >> >> This has obviously never

Re: [GIT PULL] fbdev fixes for 4.9

Tomi Valkeinen writes: > [ Unknown signature status ] > On 14/11/16 18:25, Linus Torvalds wrote: >> On Mon, Nov 14, 2016 at 3:44 AM, Tomi Valkeinen >> wrote: >>> >>> Please pull two fbdev fixes for 4.9. >> >> No. >> >> This has obviously never even been test-compiled. It introduces two >>

[PATCH v2 5/8] perf sched timehist: Add -w/--wakeups option

From: David Ahern The -w option is to show wakeup events with timehist. $ perf sched timehist -w timecpu task name b/n time sch delay run time [tid/pid](msec) (msec) (msec) ---

Re: [RFC PATCH] xen/x86: Increase xen_e820_map to E820_X_MAX possible entries

On 15/11/16 16:22, Alex Thorlton wrote: > On Tue, Nov 15, 2016 at 10:55:49AM +0100, Juergen Gross wrote: >> I'd go with the new error code. What about E2BIG or ENOSPC? >> >> I think the hypervisor should fill in the number of entries required >> in this case. >> >> In case nobody objects I can

Re: [RFC PATCH] xen/x86: Increase xen_e820_map to E820_X_MAX possible entries

On 15/11/16 16:22, Alex Thorlton wrote: > On Tue, Nov 15, 2016 at 10:55:49AM +0100, Juergen Gross wrote: >> I'd go with the new error code. What about E2BIG or ENOSPC? >> >> I think the hypervisor should fill in the number of entries required >> in this case. >> >> In case nobody objects I can

[PATCH v2 5/8] perf sched timehist: Add -w/--wakeups option

From: David Ahern The -w option is to show wakeup events with timehist. $ perf sched timehist -w timecpu task name b/n time sch delay run time [tid/pid](msec) (msec) (msec) --- --

Re: linux-next: unable to fetch the amlogic tree

HI Stephen, On Tue, Nov 15, 2016 at 2:18 PM, Stephen Rothwell wrote: > Hi all, > > Fetching the amlogic tree > (git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-amlogic.git#for-next) > produces this error: > > fatal: Couldn't find remote ref refs/heads/for-next

Re: linux-next: unable to fetch the amlogic tree

HI Stephen, On Tue, Nov 15, 2016 at 2:18 PM, Stephen Rothwell wrote: > Hi all, > > Fetching the amlogic tree > (git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-amlogic.git#for-next) > produces this error: > > fatal: Couldn't find remote ref refs/heads/for-next Hmm, must've been bad

[PATCH v4 5/6] usb: dwc3: use bus->sysdev for DMA configuration

From: Arnd Bergmann The dma ops for dwc3 devices are not set properly. So, use a physical device sysdev, which will be inherited from parent, to set the hardware / firmware parameters like dma. Signed-off-by: Arnd Bergmann Signed-off-by: Sriram Dash

[PATCH v4 5/6] usb: dwc3: use bus->sysdev for DMA configuration

From: Arnd Bergmann The dma ops for dwc3 devices are not set properly. So, use a physical device sysdev, which will be inherited from parent, to set the hardware / firmware parameters like dma. Signed-off-by: Arnd Bergmann Signed-off-by: Sriram Dash Signed-off-by: Felipe Balbi Tested-by:

RE: [PATCH] btusb: fix zero BD address problem during stress test

Hi Marcel, > From: Amitkumar Karwar [mailto:akar...@marvell.com] > Sent: Tuesday, October 18, 2016 6:27 PM > To: linux-blueto...@vger.kernel.org > Cc: mar...@holtmann.org; linux-kernel@vger.kernel.org; Cathy Luo; > Nishant Sarmukadam; Ganapathi Bhat; Amitkumar Karwar > Subject: [PATCH] btusb: fix

[PATCH v4 6/6] usb: dwc3: Do not set dma coherent mask

From: Arnd Bergmann The dma mask is correctly set up by the DT probe function, no need to override it any more. Signed-off-by: Arnd Bergmann Signed-off-by: Sriram Dash --- Changes in v4: - No update Changes in v3: - No update Changes in

RE: [PATCH] btusb: fix zero BD address problem during stress test

Hi Marcel, > From: Amitkumar Karwar [mailto:akar...@marvell.com] > Sent: Tuesday, October 18, 2016 6:27 PM > To: linux-blueto...@vger.kernel.org > Cc: mar...@holtmann.org; linux-kernel@vger.kernel.org; Cathy Luo; > Nishant Sarmukadam; Ganapathi Bhat; Amitkumar Karwar > Subject: [PATCH] btusb: fix

[PATCH v4 6/6] usb: dwc3: Do not set dma coherent mask

From: Arnd Bergmann The dma mask is correctly set up by the DT probe function, no need to override it any more. Signed-off-by: Arnd Bergmann Signed-off-by: Sriram Dash --- Changes in v4: - No update Changes in v3: - No update Changes in v2: - club the cleanup for dma coherent mask for

[PATCH v4 1/6] usb: separate out sysdev pointer from usb_bus

From: Arnd Bergmann For xhci-hcd platform device, all the DMA parameters are not configured properly, notably dma ops for dwc3 devices. The idea here is that you pass in the parent of_node along with the child device pointer, so it would behave exactly like the parent already

[PATCH v4 0/6] inherit dma configuration from parent dev

For xhci-hcd platform device, all the DMA parameters are not configured properly, notably dma ops for dwc3 devices. The idea here is that you pass in the parent of_node along with the child device pointer, so it would behave exactly like the parent already does. The difference is that it also

[PATCH v4 1/6] usb: separate out sysdev pointer from usb_bus

From: Arnd Bergmann For xhci-hcd platform device, all the DMA parameters are not configured properly, notably dma ops for dwc3 devices. The idea here is that you pass in the parent of_node along with the child device pointer, so it would behave exactly like the parent already does. The

[PATCH v4 0/6] inherit dma configuration from parent dev

For xhci-hcd platform device, all the DMA parameters are not configured properly, notably dma ops for dwc3 devices. The idea here is that you pass in the parent of_node along with the child device pointer, so it would behave exactly like the parent already does. The difference is that it also

Re: [PATCH] drm/bridge: analogix_dp: return error if transfer none byte

On 11/15/2016 10:39 PM, Sean Paul wrote: On Thu, Nov 3, 2016 at 3:17 AM, Jianqun Xu wrote: Reference from drm_dp_aux description (about transfer): Upon success, the implementation should return the number of payload bytes that were transferred, or a negative error-code

Re: [PATCH] drm/bridge: analogix_dp: return error if transfer none byte

On 11/15/2016 10:39 PM, Sean Paul wrote: On Thu, Nov 3, 2016 at 3:17 AM, Jianqun Xu wrote: Reference from drm_dp_aux description (about transfer): Upon success, the implementation should return the number of payload bytes that were transferred, or a negative error-code on failure. Helpers

[PATCH v2 2/8] perf tools: Support printing callchains with arrows

The EVSEL__PRINT_CALLCHAIN_ARROW options can be used to print callchains with arrows for readability. It will be used 'sched timehist' command like below: __schedule <- schedule <- schedule_timeout <- rcu_gp_kthread <- kthread <- ret_from_fork __schedule <- schedule <- schedule_timeout

[PATCH v2 1/8] perf symbol: Print symbol offsets conditionally

The __symbol__fprintf_symname_offs() always shows symbol offsets. So there's no difference between 'perf script -F ip,sym' and 'perf script -F ip,sym,symoff'. I don't think it's a desired behavior.. Signed-off-by: Namhyung Kim --- tools/perf/util/evsel_fprintf.c | 6

[PATCH v2 2/8] perf tools: Support printing callchains with arrows

The EVSEL__PRINT_CALLCHAIN_ARROW options can be used to print callchains with arrows for readability. It will be used 'sched timehist' command like below: __schedule <- schedule <- schedule_timeout <- rcu_gp_kthread <- kthread <- ret_from_fork __schedule <- schedule <- schedule_timeout

[PATCH v2 1/8] perf symbol: Print symbol offsets conditionally

The __symbol__fprintf_symname_offs() always shows symbol offsets. So there's no difference between 'perf script -F ip,sym' and 'perf script -F ip,sym,symoff'. I don't think it's a desired behavior.. Signed-off-by: Namhyung Kim --- tools/perf/util/evsel_fprintf.c | 6 --

[PATCH v2 8/8] perf sched: Add documentation for timehist options

From: David Ahern Add entry to perf-sched documentation for timehist command and its options. Signed-off-by: David Ahern Signed-off-by: Namhyung Kim --- tools/perf/Documentation/perf-sched.txt | 46 +++--

[PATCHSET 0/7] perf sched: Introduce timehist command, again (v2)

Hello, This patchset is a rebased version of David's sched timehist work [1]. I plan to improve perf sched command more and think that having timehist command before the work looks good. It seems David is busy these days, so I'm retrying it by myself. * changes in v2) - change name 'b/n

[PATCH v2 8/8] perf sched: Add documentation for timehist options

From: David Ahern Add entry to perf-sched documentation for timehist command and its options. Signed-off-by: David Ahern Signed-off-by: Namhyung Kim --- tools/perf/Documentation/perf-sched.txt | 46 +++-- 1 file changed, 44 insertions(+), 2 deletions(-) diff

[PATCHSET 0/7] perf sched: Introduce timehist command, again (v2)

Hello, This patchset is a rebased version of David's sched timehist work [1]. I plan to improve perf sched command more and think that having timehist command before the work looks good. It seems David is busy these days, so I'm retrying it by myself. * changes in v2) - change name 'b/n

[PATCH v2 7/8] perf sched timehist: Add -V/--cpu-visual option

From: David Ahern The -V option provides a visual aid for sched switches by cpu: $ perf sched timehist -V timecpu 0123456789abc task name b/n time sch delay run time [tid/pid](msec)

[PATCH v2 3/8] perf sched timehist: Introduce timehist command

From: David Ahern 'perf sched timehist' provides an analysis of scheduling events. Example usage: perf sched record -- sleep 1 perf sched timehist By default it shows the individual schedule events, including the wait time (time between sched-out and next sched-in

[PATCH v2 4/8] perf sched timehist: Add summary options

From: David Ahern The -s/--summary option is to show process runtime statistics. And the -S/--with-summary option is to show the stats with the normal output. $ perf sched timehist -s Runtime summary comm parent sched-in run-time

[PATCH v2 7/8] perf sched timehist: Add -V/--cpu-visual option

From: David Ahern The -V option provides a visual aid for sched switches by cpu: $ perf sched timehist -V timecpu 0123456789abc task name b/n time sch delay run time [tid/pid](msec) (msec)

[PATCH v2 3/8] perf sched timehist: Introduce timehist command

From: David Ahern 'perf sched timehist' provides an analysis of scheduling events. Example usage: perf sched record -- sleep 1 perf sched timehist By default it shows the individual schedule events, including the wait time (time between sched-out and next sched-in events for the task),

[PATCH v2 4/8] perf sched timehist: Add summary options

From: David Ahern The -s/--summary option is to show process runtime statistics. And the -S/--with-summary option is to show the stats with the normal output. $ perf sched timehist -s Runtime summary comm parent sched-in run-timemin-run avg-run

[PATCH v2 6/8] perf sched timehist: Add call graph options

From: David Ahern If callchains were recorded they are appended to the line with a default stack depth of 5: 79371.874569 [0011] gcc[31949]0.0140.0001.148 wait_for_completion_killable <- do_fork <- sys_vfork <- stub_vfork <- __vfork

[PATCH v2 6/8] perf sched timehist: Add call graph options

From: David Ahern If callchains were recorded they are appended to the line with a default stack depth of 5: 79371.874569 [0011] gcc[31949]0.0140.0001.148 wait_for_completion_killable <- do_fork <- sys_vfork <- stub_vfork <- __vfork 79371.874591 [0010]

Re: [net] 34fad54c25: kernel BUG at include/linux/skbuff.h:1935!

On 11/16, Duyck, Alexander H wrote: >On Wed, 2016-11-16 at 05:20 +0800, kernel test robot wrote: >From what I can tell it looks like the size of the frame is 0x160 hex, >or 352.  For whatever reason we are only pulling 8 bytes into the >header which is giving us an skb->len of 352 (0x160), and a

Re: [net] 34fad54c25: kernel BUG at include/linux/skbuff.h:1935!

On 11/16, Duyck, Alexander H wrote: >On Wed, 2016-11-16 at 05:20 +0800, kernel test robot wrote: >From what I can tell it looks like the size of the frame is 0x160 hex, >or 352.  For whatever reason we are only pulling 8 bytes into the >header which is giving us an skb->len of 352 (0x160), and a

Re: [PATCH v12 12/22] vfio: Add notifier callback to parent's ops structure of mdev

On 11/15/2016 11:19 PM, Alex Williamson wrote: > On Tue, 15 Nov 2016 14:45:42 +0800 > Jike Song wrote: > >> On 11/14/2016 11:42 PM, Kirti Wankhede wrote: >>> Add a notifier calback to parent's ops structure of mdev device so that per >>> device notifer for vfio module is

Re: [PATCH v12 12/22] vfio: Add notifier callback to parent's ops structure of mdev

On 11/15/2016 11:19 PM, Alex Williamson wrote: > On Tue, 15 Nov 2016 14:45:42 +0800 > Jike Song wrote: > >> On 11/14/2016 11:42 PM, Kirti Wankhede wrote: >>> Add a notifier calback to parent's ops structure of mdev device so that per >>> device notifer for vfio module is registered through

Re: [PATCH 2/3] thermal: hisilicon: fix for dependency

On Tue, Nov 15, 2016 at 08:24:55PM +0800, Zhang Rui wrote: > On Sat, 2016-11-12 at 20:05 +0800, Leo Yan wrote: > > Hi Rui, Eduardo, > > > > On Wed, Aug 31, 2016 at 04:50:16PM +0800, Leo Yan wrote: > > > > > > The thermal driver is standalone driver which is used to enable > > > thermal sensors,

Re: [PATCH 2/3] thermal: hisilicon: fix for dependency

On Tue, Nov 15, 2016 at 08:24:55PM +0800, Zhang Rui wrote: > On Sat, 2016-11-12 at 20:05 +0800, Leo Yan wrote: > > Hi Rui, Eduardo, > > > > On Wed, Aug 31, 2016 at 04:50:16PM +0800, Leo Yan wrote: > > > > > > The thermal driver is standalone driver which is used to enable > > > thermal sensors,

Re: [PATCH] tpm: drop chip->is_open and chip->duration_adjusted

On Mon, Nov 14, 2016 at 09:11:54PM -0800, Jarkko Sakkinen wrote: > How strong is your opposition here? I do not see any exceptional damage > done but see some subtle but still significant benefits. It seems OK, but I never like seeing locking made less clear - this should be manageable, and

Re: [PATCH] tpm: drop chip->is_open and chip->duration_adjusted

On Mon, Nov 14, 2016 at 09:11:54PM -0800, Jarkko Sakkinen wrote: > How strong is your opposition here? I do not see any exceptional damage > done but see some subtle but still significant benefits. It seems OK, but I never like seeing locking made less clear - this should be manageable, and

Re: [PATCH v4 2/2] mailbox: Add Tegra HSP driver

On Tue, Nov 15, 2016 at 9:18 PM, Thierry Reding wrote: > + > +struct tegra_hsp_channel; > +struct tegra_hsp; > + > +struct tegra_hsp_channel_ops { > + int (*send_data)(struct tegra_hsp_channel *channel, void *data); > + int (*startup)(struct

Re: [PATCH v4 2/2] mailbox: Add Tegra HSP driver

On Tue, Nov 15, 2016 at 9:18 PM, Thierry Reding wrote: > + > +struct tegra_hsp_channel; > +struct tegra_hsp; > + > +struct tegra_hsp_channel_ops { > + int (*send_data)(struct tegra_hsp_channel *channel, void *data); > + int (*startup)(struct tegra_hsp_channel *channel); > +

  1   2   3   4   5   6   7   8   9   10   >