Re: [PATCH 18/18] ARM: mvebu: a395-gp: add support for the Armada 395 GP Board

Hi Grzegorz, On jeu., juil. 21 2016, Grzegorz Jaszczyk wrote: Change the prefix to "ARM: dts: mvebu: armada-395-gp:" > This commit adds description for the following features for this board: > > - Serial port > - PCIe interfaces > - USB2.0 > - USB3.0 > - SDIO > - 1024 MiB

Re: [PATCH 18/18] ARM: mvebu: a395-gp: add support for the Armada 395 GP Board

Hi Grzegorz, On jeu., juil. 21 2016, Grzegorz Jaszczyk wrote: Change the prefix to "ARM: dts: mvebu: armada-395-gp:" > This commit adds description for the following features for this board: > > - Serial port > - PCIe interfaces > - USB2.0 > - USB3.0 > - SDIO > - 1024 MiB NAND-FLASH > - SATA

Re: [PATCH v4 3/6] drm/i915/skl: Only flush pipes when we change the ddb allocation

On Tue, Jul 26, 2016 at 01:34:39PM -0400, Lyude wrote: > Manual pipe flushes are only necessary in order to make sure that we prevent > pipes with changed ddb allocations from overlapping from one another at > any point in time. Additionally, forcing us to wait for the next vblank > every time we

Re: [PATCH v4 3/6] drm/i915/skl: Only flush pipes when we change the ddb allocation

On Tue, Jul 26, 2016 at 01:34:39PM -0400, Lyude wrote: > Manual pipe flushes are only necessary in order to make sure that we prevent > pipes with changed ddb allocations from overlapping from one another at > any point in time. Additionally, forcing us to wait for the next vblank > every time we

Re: [PATCH v4 1/6] drm/i915/skl: Add support for the SAGV, fix underrun hangs

On Tue, Jul 26, 2016 at 01:34:37PM -0400, Lyude wrote: > Since the watermark calculations for Skylake are still broken, we're apt > to hitting underruns very easily under multi-monitor configurations. > While it would be lovely if this was fixed, it's not. Another problem > that's been coming from

Re: [PATCH v4 1/6] drm/i915/skl: Add support for the SAGV, fix underrun hangs

On Tue, Jul 26, 2016 at 01:34:37PM -0400, Lyude wrote: > Since the watermark calculations for Skylake are still broken, we're apt > to hitting underruns very easily under multi-monitor configurations. > While it would be lovely if this was fixed, it's not. Another problem > that's been coming from

Re: [PATCH 0/5 RFC] Add an interface to discover relationships between namespaces

"Michael Kerrisk (man-pages)" writes: > On 07/26/2016 10:39 PM, Andrew Vagin wrote: >> On Tue, Jul 26, 2016 at 09:17:31PM +0200, Michael Kerrisk (man-pages) wrote: >> If we want to compare two file descriptors of the current process, >> it is one of cases for which kcmp

Re: [PATCH 0/2] *** Latency Histogram ***

On Thu, Jul 28, 2016 at 10:22:12AM +0530, Binoy Jayan wrote: > Hi, > > I was looking at these RT kernel patches and was wondering why it has > not been upstreamed yet. I have made a few changes to these patches to > make it compliant with upstream submission process. Also did a minimal > testing

Re: [PATCH 0/5 RFC] Add an interface to discover relationships between namespaces

"Michael Kerrisk (man-pages)" writes: > On 07/26/2016 10:39 PM, Andrew Vagin wrote: >> On Tue, Jul 26, 2016 at 09:17:31PM +0200, Michael Kerrisk (man-pages) wrote: >> If we want to compare two file descriptors of the current process, >> it is one of cases for which kcmp can be used. We can call

Re: [PATCH 0/2] *** Latency Histogram ***

On Thu, Jul 28, 2016 at 10:22:12AM +0530, Binoy Jayan wrote: > Hi, > > I was looking at these RT kernel patches and was wondering why it has > not been upstreamed yet. I have made a few changes to these patches to > make it compliant with upstream submission process. Also did a minimal > testing

Re: [RFC v0 4/8] Input: goodix: use firmware_stat instead of completion

Looking at the API, I really don't like the mixing of namespaces. Either it's fw_ or it's firmware_ but not a mix of both. I agree, that was not really clever. struct fw_loading { ... } __fw_loading_*() fw_loading_*() Would that make more sense? firmware_loading_ as

Re: [RFC v0 4/8] Input: goodix: use firmware_stat instead of completion

Looking at the API, I really don't like the mixing of namespaces. Either it's fw_ or it's firmware_ but not a mix of both. I agree, that was not really clever. struct fw_loading { ... } __fw_loading_*() fw_loading_*() Would that make more sense? firmware_loading_ as

Re: [Qemu-devel] [PATCH 6/7] qemu: Implement virtio-pstore device

On Thu, Jul 28, 2016 at 01:56:07PM +0100, Stefan Hajnoczi wrote: > On Thu, Jul 28, 2016 at 02:39:53PM +0900, Namhyung Kim wrote: > > On Thu, Jul 28, 2016 at 03:02:54AM +0300, Michael S. Tsirkin wrote: > > > On Thu, Jul 28, 2016 at 12:08:30AM +0900, Namhyung Kim wrote: > > > > +static ssize_t

Re: [Qemu-devel] [PATCH 6/7] qemu: Implement virtio-pstore device

On Thu, Jul 28, 2016 at 01:56:07PM +0100, Stefan Hajnoczi wrote: > On Thu, Jul 28, 2016 at 02:39:53PM +0900, Namhyung Kim wrote: > > On Thu, Jul 28, 2016 at 03:02:54AM +0300, Michael S. Tsirkin wrote: > > > On Thu, Jul 28, 2016 at 12:08:30AM +0900, Namhyung Kim wrote: > > > > +static ssize_t

Re: [PATCH 17/18] ARM: mvebu: a390-db: add support for the Armada 390 DB board

Hi Grzegorz, On jeu., juil. 21 2016, Grzegorz Jaszczyk wrote: Change the prefix to "ARM: dts: mvebu: armada-390-db:" > This commit adds description for following features for this board: > > - Serial port > - I2C buses > - 16MB SPI-NOR > - USB2.0 > - USB3.0 > - PCIe

Re: [PATCH 17/18] ARM: mvebu: a390-db: add support for the Armada 390 DB board

Hi Grzegorz, On jeu., juil. 21 2016, Grzegorz Jaszczyk wrote: Change the prefix to "ARM: dts: mvebu: armada-390-db:" > This commit adds description for following features for this board: > > - Serial port > - I2C buses > - 16MB SPI-NOR > - USB2.0 > - USB3.0 > - PCIe interfaces > >

RE: [PATCH net 1/3] r8169:fix kernel log spam when set or get hardware wol setting.

[...] > Nit: you may directly use "struct device *d = >pci_dev->dev;" > I will do that on my next version patch. Thanks. --Please consider the environment before printing this e-mail.

Re: [PATCH 3/3] ntb: Test client drivers for asynchronous NTB devices

Hi, [auto build test WARNING on ntb/ntb-next] [cannot apply to v4.7 next-20160728] [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/Serge-Semin/ntb-Asynchronous-NTB-devices-support/20160727

RE: [PATCH net 1/3] r8169:fix kernel log spam when set or get hardware wol setting.

[...] > Nit: you may directly use "struct device *d = >pci_dev->dev;" > I will do that on my next version patch. Thanks. --Please consider the environment before printing this e-mail.

Re: [PATCH 3/3] ntb: Test client drivers for asynchronous NTB devices

Hi, [auto build test WARNING on ntb/ntb-next] [cannot apply to v4.7 next-20160728] [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/Serge-Semin/ntb-Asynchronous-NTB-devices-support/20160727

RE: [PATCH net 1/3] r8169:fix kernel log spam when set or get hardware wol setting.

[...] > > @@ -1852,12 +1863,17 @@ static int rtl8169_set_wol(struct net_device > *dev, struct ethtool_wolinfo *wol) > > tp->features |= RTL_FEATURE_WOL; > > else > > tp->features &= ~RTL_FEATURE_WOL; > > - __rtl8169_set_wol(tp, wol->wolopts); > > + if

RE: [PATCH net 1/3] r8169:fix kernel log spam when set or get hardware wol setting.

[...] > > @@ -1852,12 +1863,17 @@ static int rtl8169_set_wol(struct net_device > *dev, struct ethtool_wolinfo *wol) > > tp->features |= RTL_FEATURE_WOL; > > else > > tp->features &= ~RTL_FEATURE_WOL; > > - __rtl8169_set_wol(tp, wol->wolopts); > > + if

Re: [PATCH 6/7] qemu: Implement virtio-pstore device

On Thu, Jul 28, 2016 at 02:39:53PM +0900, Namhyung Kim wrote: > On Thu, Jul 28, 2016 at 03:02:54AM +0300, Michael S. Tsirkin wrote: > > On Thu, Jul 28, 2016 at 12:08:30AM +0900, Namhyung Kim wrote: > > > +static ssize_t virtio_pstore_do_write(VirtIOPstore *s, struct iovec > > > *out_sg, > > > +

Re: [PATCH 6/7] qemu: Implement virtio-pstore device

On Thu, Jul 28, 2016 at 02:39:53PM +0900, Namhyung Kim wrote: > On Thu, Jul 28, 2016 at 03:02:54AM +0300, Michael S. Tsirkin wrote: > > On Thu, Jul 28, 2016 at 12:08:30AM +0900, Namhyung Kim wrote: > > > +static ssize_t virtio_pstore_do_write(VirtIOPstore *s, struct iovec > > > *out_sg, > > > +

Re: [PATCH 16/18] ARM: mvebu: a398-db: enable supported usb interfaces

Hi Grzegorz, On jeu., juil. 21 2016, Grzegorz Jaszczyk wrote: Change the prefix to "ARM: dts: mvebu: armada-398-db:" Acked-by: Gregory CLEMENT Thanks, Gregory > Signed-off-by: Grzegorz Jaszczyk > --- >

Re: [PATCH 16/18] ARM: mvebu: a398-db: enable supported usb interfaces

Hi Grzegorz, On jeu., juil. 21 2016, Grzegorz Jaszczyk wrote: Change the prefix to "ARM: dts: mvebu: armada-398-db:" Acked-by: Gregory CLEMENT Thanks, Gregory > Signed-off-by: Grzegorz Jaszczyk > --- > arch/arm/boot/dts/armada-398-db.dts | 8 > 1 file changed, 8 insertions(+) >

Re: [PATCH 15/18] ARM: mvebu: a398: update the dtsi about missing interfaces

Hi Grzegorz, On jeu., juil. 21 2016, Grzegorz Jaszczyk wrote: > Beside interfaces described in the armada-39x.dtsi and armada-395.dtsi, the > Armada 398 SoC family supports 2 additional SATA port (2 ports in one unit) > > Signed-off-by: Grzegorz Jaszczyk

Re: [PATCH 15/18] ARM: mvebu: a398: update the dtsi about missing interfaces

Hi Grzegorz, On jeu., juil. 21 2016, Grzegorz Jaszczyk wrote: > Beside interfaces described in the armada-39x.dtsi and armada-395.dtsi, the > Armada 398 SoC family supports 2 additional SATA port (2 ports in one unit) > > Signed-off-by: Grzegorz Jaszczyk Change the prefix to "ARM: dts:

Re: [PATCH v4] net: sched: convert qdisc linked list to hashtable

On Thu, Jul 28, 2016 at 01:18:27PM +0200, Jiri Kosina wrote: On Thu, 28 Jul 2016, kbuild test robot wrote: [auto build test ERROR on v4.7-rc7] [also build test ERROR on next-20160728] [cannot apply to net/master net-next/master ipsec-next/master] [if your patch is applied to the wrong git tree

Re: [PATCH v4] net: sched: convert qdisc linked list to hashtable

On Thu, Jul 28, 2016 at 01:18:27PM +0200, Jiri Kosina wrote: On Thu, 28 Jul 2016, kbuild test robot wrote: [auto build test ERROR on v4.7-rc7] [also build test ERROR on next-20160728] [cannot apply to net/master net-next/master ipsec-next/master] [if your patch is applied to the wrong git tree

Re: [RFC PATCH v3] net: sched: convert qdisc linked list to hashtable

Hi Jiri, On Thu, Jul 14, 2016 at 04:14:58PM +0200, Jiri Kosina wrote: [ added CCs ] On Tue, 12 Jul 2016, kbuild test robot wrote: Hi, [auto build test ERROR on net/master] [also build test ERROR on v4.7-rc7 next-20160711] [if your patch is applied to the wrong git tree, please drop us a

Re: [RFC PATCH v3] net: sched: convert qdisc linked list to hashtable

Hi Jiri, On Thu, Jul 14, 2016 at 04:14:58PM +0200, Jiri Kosina wrote: [ added CCs ] On Tue, 12 Jul 2016, kbuild test robot wrote: Hi, [auto build test ERROR on net/master] [also build test ERROR on v4.7-rc7 next-20160711] [if your patch is applied to the wrong git tree, please drop us a

Re: [PATCH v2 2/4] iio: cros_ec_sensors: add ChromeOS EC Contiguous Sensors driver

Hi Guenter, Thanks for the review, some answers below, just preparing next version that I'll send asap. 2016-07-25 19:25 GMT+02:00 Guenter Roeck : > On Wed, Jul 20, 2016 at 2:22 AM, Enric Balletbo i Serra > wrote: >> Handle 3d contiguous sensors

Re: [PATCH v2 2/4] iio: cros_ec_sensors: add ChromeOS EC Contiguous Sensors driver

Hi Guenter, Thanks for the review, some answers below, just preparing next version that I'll send asap. 2016-07-25 19:25 GMT+02:00 Guenter Roeck : > On Wed, Jul 20, 2016 at 2:22 AM, Enric Balletbo i Serra > wrote: >> Handle 3d contiguous sensors like Accelerometers, Gyroscope and >>

Re: warning: calling ‘__builtin_return_address’ with a nonzero argument is unsafe

On Wed, Jul 27, 2016 at 08:21:50PM -0700, Linus Torvalds wrote: > The remaining ones are mostly objtool warnings (Josh added to cc: I > get both a "objtool: x86 instruction decoder differs from kernel" > warning Ok, this should be an easy fix. > and several new "sibling call from callable

Re: warning: calling ‘__builtin_return_address’ with a nonzero argument is unsafe

On Wed, Jul 27, 2016 at 08:21:50PM -0700, Linus Torvalds wrote: > The remaining ones are mostly objtool warnings (Josh added to cc: I > get both a "objtool: x86 instruction decoder differs from kernel" > warning Ok, this should be an easy fix. > and several new "sibling call from callable

Re: [e1000_netpoll] BUG: sleeping function called from invalid context at kernel/irq/manage.c:110

On Thu, 28 Jul 2016, Sabrina Dubroca wrote: > 2016-07-28, 07:43:55 +0200, Eric Dumazet wrote: > > I would prefer having a definitive advice from Thomas Gleixner and/or > > others if disable_irq() is forbidden from IRQ path. Yes it is. Before we added threaded interrupt handlers it was not an

Re: [e1000_netpoll] BUG: sleeping function called from invalid context at kernel/irq/manage.c:110

On Thu, 28 Jul 2016, Sabrina Dubroca wrote: > 2016-07-28, 07:43:55 +0200, Eric Dumazet wrote: > > I would prefer having a definitive advice from Thomas Gleixner and/or > > others if disable_irq() is forbidden from IRQ path. Yes it is. Before we added threaded interrupt handlers it was not an

Re: [PATCH] mm: fail prefaulting if page table allocation fails

On Thu, Jul 28, 2016 at 02:15:07PM +0200, Vegard Nossum wrote: > I ran into this: > > BUG: sleeping function called from invalid context at mm/page_alloc.c:3784 > in_atomic(): 0, irqs_disabled(): 0, pid: 1434, name: trinity-c1 > 2 locks held by trinity-c1/1434: > #0:

Re: [RFC v0 4/8] Input: goodix: use firmware_stat instead of completion

On Thu, 2016-07-28 at 13:59 +0200, Daniel Wagner wrote: > On 07/28/2016 01:22 PM, Bastien Nocera wrote: > > On Thu, 2016-07-28 at 09:55 +0200, Daniel Wagner wrote: > > > From: Daniel Wagner > > > > > > Loading firmware is an operation many drivers implement in > > >

Re: [PATCH] mm: fail prefaulting if page table allocation fails

On Thu, Jul 28, 2016 at 02:15:07PM +0200, Vegard Nossum wrote: > I ran into this: > > BUG: sleeping function called from invalid context at mm/page_alloc.c:3784 > in_atomic(): 0, irqs_disabled(): 0, pid: 1434, name: trinity-c1 > 2 locks held by trinity-c1/1434: > #0:

Re: [RFC v0 4/8] Input: goodix: use firmware_stat instead of completion

On Thu, 2016-07-28 at 13:59 +0200, Daniel Wagner wrote: > On 07/28/2016 01:22 PM, Bastien Nocera wrote: > > On Thu, 2016-07-28 at 09:55 +0200, Daniel Wagner wrote: > > > From: Daniel Wagner > > > > > > Loading firmware is an operation many drivers implement in > > > various > > > ways > > >

Re: linux-next - modprobe causes BUG: sleeping function called from invalid context at mm/slab.h:393

Hi Valdis, Valdis Kletnieks writes: > This ring any bells for anybody? > > [ 20.418310] BUG: sleeping function called from invalid context at > mm/slab.h:393 > [ 20.420592] in_atomic(): 1, irqs_disabled(): 0, pid: 679, name: > systemd-udevd > [ 20.423143] no

Re: linux-next - modprobe causes BUG: sleeping function called from invalid context at mm/slab.h:393

Hi Valdis, Valdis Kletnieks writes: > This ring any bells for anybody? > > [ 20.418310] BUG: sleeping function called from invalid context at > mm/slab.h:393 > [ 20.420592] in_atomic(): 1, irqs_disabled(): 0, pid: 679, name: > systemd-udevd > [ 20.423143] no locks held by

Re: debug tip after earlycon is closed?

On Thu, Jul 28, 2016 at 09:44:53AM +0200, Arnd Bergmann wrote: > I think the problem is that you have three consoles: > > - the boot console that stays active until a real console comes up > - the framebuffer console that is initialized early and goes on to > disable the bootconsole > - the

Re: debug tip after earlycon is closed?

On Thu, Jul 28, 2016 at 09:44:53AM +0200, Arnd Bergmann wrote: > I think the problem is that you have three consoles: > > - the boot console that stays active until a real console comes up > - the framebuffer console that is initialized early and goes on to > disable the bootconsole > - the

[PATCH] mm: fail prefaulting if page table allocation fails

I ran into this: BUG: sleeping function called from invalid context at mm/page_alloc.c:3784 in_atomic(): 0, irqs_disabled(): 0, pid: 1434, name: trinity-c1 2 locks held by trinity-c1/1434: #0: (>mmap_sem){..}, at: [] __do_page_fault+0x1ce/0x8f0 #1:

[PATCH] mm: fail prefaulting if page table allocation fails

I ran into this: BUG: sleeping function called from invalid context at mm/page_alloc.c:3784 in_atomic(): 0, irqs_disabled(): 0, pid: 1434, name: trinity-c1 2 locks held by trinity-c1/1434: #0: (>mmap_sem){..}, at: [] __do_page_fault+0x1ce/0x8f0 #1:

LOAN OFFER

DO YOU NEED PERSONAL OR BUSINESS LOAN? IF YES KINDLY REPLY US FOR INSTANT APPROVAL WITH 3% INTEREST RATE!!! NAME--- COUNTRY. AMOUNT-- NUMBER--- GENDER AGE--- ADDRESS--- DURATION---

LOAN OFFER

DO YOU NEED PERSONAL OR BUSINESS LOAN? IF YES KINDLY REPLY US FOR INSTANT APPROVAL WITH 3% INTEREST RATE!!! NAME--- COUNTRY. AMOUNT-- NUMBER--- GENDER AGE--- ADDRESS--- DURATION---

Re: [RFC] can we use vmalloc to alloc thread stack if compaction failed

On 2016/7/28 17:43, Michal Hocko wrote: > On Thu 28-07-16 16:45:06, Xishi Qiu wrote: >> On 2016/7/28 15:58, Michal Hocko wrote: >> >>> On Thu 28-07-16 15:41:53, Xishi Qiu wrote: On 2016/7/28 15:20, Michal Hocko wrote: > On Thu 28-07-16 15:08:26, Xishi Qiu wrote: >> Usually

Re: [RFC] can we use vmalloc to alloc thread stack if compaction failed

On 2016/7/28 17:43, Michal Hocko wrote: > On Thu 28-07-16 16:45:06, Xishi Qiu wrote: >> On 2016/7/28 15:58, Michal Hocko wrote: >> >>> On Thu 28-07-16 15:41:53, Xishi Qiu wrote: On 2016/7/28 15:20, Michal Hocko wrote: > On Thu 28-07-16 15:08:26, Xishi Qiu wrote: >> Usually

Re: [RFC v0 4/8] Input: goodix: use firmware_stat instead of completion

On 07/28/2016 01:22 PM, Bastien Nocera wrote: On Thu, 2016-07-28 at 09:55 +0200, Daniel Wagner wrote: From: Daniel Wagner Loading firmware is an operation many drivers implement in various ways around the completion API. And most of them do it almost in the same

Re: [RFC v0 4/8] Input: goodix: use firmware_stat instead of completion

On 07/28/2016 01:22 PM, Bastien Nocera wrote: On Thu, 2016-07-28 at 09:55 +0200, Daniel Wagner wrote: From: Daniel Wagner Loading firmware is an operation many drivers implement in various ways around the completion API. And most of them do it almost in the same way. Let's reuse the

Re: [PATCH 2/3] staging: wilc1000: One function call less in mac_ioctl() after error detection

Hi Marcus, On Mon, Jul 25, 2016 at 6:22 AM, SF Markus Elfring wrote: > From: Markus Elfring > Date: Sun, 24 Jul 2016 21:15:23 +0200 > > The kfree() function was called in two cases by the mac_ioctl() function > during error handling

Re: [PATCH 2/3] staging: wilc1000: One function call less in mac_ioctl() after error detection

Hi Marcus, On Mon, Jul 25, 2016 at 6:22 AM, SF Markus Elfring wrote: > From: Markus Elfring > Date: Sun, 24 Jul 2016 21:15:23 +0200 > > The kfree() function was called in two cases by the mac_ioctl() function > during error handling even if the passed variable did not contain a pointer > for a

Re: [PATCH v4] net: sched: convert qdisc linked list to hashtable

Hi, [auto build test ERROR on v4.7-rc7] [also build test ERROR on next-20160728] [cannot apply to net/master net-next/master ipsec-next/master] [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

Re: [PATCH v4] net: sched: convert qdisc linked list to hashtable

Hi, [auto build test ERROR on v4.7-rc7] [also build test ERROR on next-20160728] [cannot apply to net/master net-next/master ipsec-next/master] [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

Re: [PATCH 00/10] Add NAND, DMA, USB, and QSPI EDAC

On Thu, Jul 14, 2016 at 11:06:38AM -0500, ttha...@opensource.altera.com wrote: > From: Thor Thayer > > This patch series adds the NAND, DMA, USB and QSPI FIFO EDAC modules. > > Thor Thayer (10): > Documentation: dt: socfpga: Add Arria10 NAND EDAC binding >

Re: [PATCH 00/10] Add NAND, DMA, USB, and QSPI EDAC

On Thu, Jul 14, 2016 at 11:06:38AM -0500, ttha...@opensource.altera.com wrote: > From: Thor Thayer > > This patch series adds the NAND, DMA, USB and QSPI FIFO EDAC modules. > > Thor Thayer (10): > Documentation: dt: socfpga: Add Arria10 NAND EDAC binding > Documentation: dt: socfpga: Add

linux-next - modprobe causes BUG: sleeping function called from invalid context at mm/slab.h:393

I've been seeing this several times per boot since next-20160708 or so, finally had a chance to reproduce it on a linux-next that wasn't horribly hand-hacked. Not every modprobe, maybe 5-8 out of 40 modules usually loaded, with no real rhyme/reason that I've spotted. I keep having a nagging

linux-next - modprobe causes BUG: sleeping function called from invalid context at mm/slab.h:393

I've been seeing this several times per boot since next-20160708 or so, finally had a chance to reproduce it on a linux-next that wasn't horribly hand-hacked. Not every modprobe, maybe 5-8 out of 40 modules usually loaded, with no real rhyme/reason that I've spotted. I keep having a nagging

Aw: Re: staging: wilc1000: Reduce scope for a few variables in mac_ioctl()

> Gesendet: Dienstag, 26. Juli 2016 um 08:25 Uhr > Von: "SF Markus Elfring" > > >> - if (strncasecmp(buff, "RSSI", length) == 0) { > >> + if (strncasecmp(buff, "RSSI", 0) == 0) { > >> + s8 rssi; > >> + >

Aw: Re: staging: wilc1000: Reduce scope for a few variables in mac_ioctl()

> Gesendet: Dienstag, 26. Juli 2016 um 08:25 Uhr > Von: "SF Markus Elfring" > > >> - if (strncasecmp(buff, "RSSI", length) == 0) { > >> + if (strncasecmp(buff, "RSSI", 0) == 0) { > >> + s8 rssi; > >> + > > > > Um, please think a

Re: [linux-sunxi] Re: Changed: sunxi-ng clock code - NKMP clock implementation is wrong

Hi, On Thu, Jul 28, 2016 at 7:27 PM, Ondřej Jirman wrote: > Hi Maxime, > > I don't have your sunxi-ng clock patches in my mailbox, so I'm replying > to this. > > On 26.7.2016 08:32, Maxime Ripard wrote: >> On Thu, Jul 21, 2016 at 11:52:15AM +0200, Ondřej Jirman wrote: >>

Re: [linux-sunxi] Re: Changed: sunxi-ng clock code - NKMP clock implementation is wrong

Hi, On Thu, Jul 28, 2016 at 7:27 PM, Ondřej Jirman wrote: > Hi Maxime, > > I don't have your sunxi-ng clock patches in my mailbox, so I'm replying > to this. > > On 26.7.2016 08:32, Maxime Ripard wrote: >> On Thu, Jul 21, 2016 at 11:52:15AM +0200, Ondřej Jirman wrote: >> If so, then yes,

Re: [PATCH v5 5/8] thunderbolt: Networking state machine

On Thu, Jul 28, 2016 at 11:15:18AM +0300, Amir Levy wrote: > +static void nhi_handle_notification_msg(struct tbt_nhi_ctxt *nhi_ctxt, > + const u8 *msg) > +{ > + struct port_net_dev *port; > + u8 port_num; > + > +#define INTER_DOMAIN_LINK_SHIFT 0 >

Re: [PATCH v5 5/8] thunderbolt: Networking state machine

On Thu, Jul 28, 2016 at 11:15:18AM +0300, Amir Levy wrote: > +static void nhi_handle_notification_msg(struct tbt_nhi_ctxt *nhi_ctxt, > + const u8 *msg) > +{ > + struct port_net_dev *port; > + u8 port_num; > + > +#define INTER_DOMAIN_LINK_SHIFT 0 >

Re: Changed: sunxi-ng clock code - NKMP clock implementation is wrong

Hi Maxime, I don't have your sunxi-ng clock patches in my mailbox, so I'm replying to this. On 26.7.2016 08:32, Maxime Ripard wrote: > On Thu, Jul 21, 2016 at 11:52:15AM +0200, Ondřej Jirman wrote: > If so, then yes, trying to switch to the 24MHz oscillator before > applying the factors,

Re: Changed: sunxi-ng clock code - NKMP clock implementation is wrong

Hi Maxime, I don't have your sunxi-ng clock patches in my mailbox, so I'm replying to this. On 26.7.2016 08:32, Maxime Ripard wrote: > On Thu, Jul 21, 2016 at 11:52:15AM +0200, Ondřej Jirman wrote: > If so, then yes, trying to switch to the 24MHz oscillator before > applying the factors,

Re: [PATCH v4] net: sched: convert qdisc linked list to hashtable

Hi, [auto build test ERROR on v4.7-rc7] [also build test ERROR on next-20160728] [cannot apply to net/master net-next/master ipsec-next/master] [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

Re: [PATCH v4] net: sched: convert qdisc linked list to hashtable

Hi, [auto build test ERROR on v4.7-rc7] [also build test ERROR on next-20160728] [cannot apply to net/master net-next/master ipsec-next/master] [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

Re: [RFC v0 4/8] Input: goodix: use firmware_stat instead of completion

On Thu, 2016-07-28 at 09:55 +0200, Daniel Wagner wrote: > From: Daniel Wagner > > Loading firmware is an operation many drivers implement in various > ways > around the completion API. And most of them do it almost in the same > way. Let's reuse the firmware_stat API

Re: [RFC v0 4/8] Input: goodix: use firmware_stat instead of completion

On Thu, 2016-07-28 at 09:55 +0200, Daniel Wagner wrote: > From: Daniel Wagner > > Loading firmware is an operation many drivers implement in various > ways > around the completion API. And most of them do it almost in the same > way. Let's reuse the firmware_stat API which is used also by the >

Re: [PATCH v2] Coccinelle: Script to replace allocate and memset with zalloc functions

On 2016-07-28 10:29, Amitoj Kaur Chawla wrote: > This script finds instances of allocate and memset which can be > replaced with a direct call to zalloc equivalent of a function. > > Signed-off-by: Amitoj Kaur Chawla > --- > Changes in v2: > -Modified commit message

Re: [PATCH v2] Coccinelle: Script to replace allocate and memset with zalloc functions

On 2016-07-28 10:29, Amitoj Kaur Chawla wrote: > This script finds instances of allocate and memset which can be > replaced with a direct call to zalloc equivalent of a function. > > Signed-off-by: Amitoj Kaur Chawla > --- > Changes in v2: > -Modified commit message and subject There is

Re: [PATCH 2/2] sc16is7xx: add reading CTS

Hello Pascal, If you look at the history of this driver, you'll see that something similar was present in the past, but was removed because it introduced problems. The problem is that you can't just call sc16is7xx_port_read() unsynchronized to the worker thread. And this is related to the device

Re: [PATCH 2/2] sc16is7xx: add reading CTS

Hello Pascal, If you look at the history of this driver, you'll see that something similar was present in the past, but was removed because it introduced problems. The problem is that you can't just call sc16is7xx_port_read() unsynchronized to the worker thread. And this is related to the device

Re: [PATCH 14/18] ARM: mvebu: add support for the Armada 395 SoC family

Hi Rob, On lun., juil. 25 2016, Thomas Petazzoni wrote: > Hello, > > On Mon, 25 Jul 2016 10:12:43 -0500, Rob Herring wrote: > >> Yes, I get that, but that is only meaningful if you want to run an OS >> that is only aware of 395 on a 398 SoC/board (though

Re: [PATCH 14/18] ARM: mvebu: add support for the Armada 395 SoC family

Hi Rob, On lun., juil. 25 2016, Thomas Petazzoni wrote: > Hello, > > On Mon, 25 Jul 2016 10:12:43 -0500, Rob Herring wrote: > >> Yes, I get that, but that is only meaningful if you want to run an OS >> that is only aware of 395 on a 398 SoC/board (though I'd guess the 390 >> compat is enough

Re: [PATCH v4] net: sched: convert qdisc linked list to hashtable

On Thu, 28 Jul 2016, kbuild test robot wrote: > [auto build test ERROR on v4.7-rc7] > [also build test ERROR on next-20160728] > [cannot apply to net/master net-next/master ipsec-next/master] > [if your patch is applied to the wrong git tree, please drop us a note to > help imp

Re: [PATCH v4] net: sched: convert qdisc linked list to hashtable

On Thu, 28 Jul 2016, kbuild test robot wrote: > [auto build test ERROR on v4.7-rc7] > [also build test ERROR on next-20160728] > [cannot apply to net/master net-next/master ipsec-next/master] > [if your patch is applied to the wrong git tree, please drop us a note to > help imp

Re: [PATCH v4] net: sched: convert qdisc linked list to hashtable

Hi, [auto build test ERROR on v4.7-rc7] [also build test ERROR on next-20160728] [cannot apply to net/master net-next/master ipsec-next/master] [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

Re: [PATCH v4] net: sched: convert qdisc linked list to hashtable

Hi, [auto build test ERROR on v4.7-rc7] [also build test ERROR on next-20160728] [cannot apply to net/master net-next/master ipsec-next/master] [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

Re: [GIT PULL] binfmt_misc updates for 4.7+ merge window

On Wed, 2016-07-27 at 20:30 -0700, Joe Perches wrote: > On Wed, 2016-07-27 at 20:26 -0700, Linus Torvalds wrote: > > On Wed, Jul 27, 2016 at 8:21 PM, Joe Perches > > wrote: > > > > > > On Wed, 2016-07-27 at 20:12 -0700, Linus Torvalds wrote: > > > > > > > > Did you actually

Re: [GIT PULL] binfmt_misc updates for 4.7+ merge window

On Wed, 2016-07-27 at 20:30 -0700, Joe Perches wrote: > On Wed, 2016-07-27 at 20:26 -0700, Linus Torvalds wrote: > > On Wed, Jul 27, 2016 at 8:21 PM, Joe Perches > > wrote: > > > > > > On Wed, 2016-07-27 at 20:12 -0700, Linus Torvalds wrote: > > > > > > > > Did you actually try it. > > > yes. >

Re: Why do we need reset_control_get_optional() ?

Am Donnerstag, den 28.07.2016, 19:52 +0900 schrieb Masahiro Yamada: > Hi Arnd, > > > 2016-07-28 19:09 GMT+09:00 Arnd Bergmann : > > On Thursday, July 28, 2016 11:43:00 AM CEST Philipp Zabel wrote: > >> > I want to deprecate _optional variants in the following steps: > >> > > >> >

Re: [PATCH v4 2/5] dma-buf/sync_file: refactor fence storage in struct sync_file

Hi Greg, On 19 July 2016 at 17:51, Sumit Semwal wrote: > (Adding Greg KH) > > Hi Greg, > > On 19 July 2016 at 17:45, Sumit Semwal wrote: >> Hi Greg, >> >> >> On 12 July 2016 at 23:38, Gustavo Padovan wrote: >>> From:

Re: Why do we need reset_control_get_optional() ?

Am Donnerstag, den 28.07.2016, 19:52 +0900 schrieb Masahiro Yamada: > Hi Arnd, > > > 2016-07-28 19:09 GMT+09:00 Arnd Bergmann : > > On Thursday, July 28, 2016 11:43:00 AM CEST Philipp Zabel wrote: > >> > I want to deprecate _optional variants in the following steps: > >> > > >> > [1] Add

Re: [PATCH v4 2/5] dma-buf/sync_file: refactor fence storage in struct sync_file

Hi Greg, On 19 July 2016 at 17:51, Sumit Semwal wrote: > (Adding Greg KH) > > Hi Greg, > > On 19 July 2016 at 17:45, Sumit Semwal wrote: >> Hi Greg, >> >> >> On 12 July 2016 at 23:38, Gustavo Padovan wrote: >>> From: Gustavo Padovan >>> >>> Create sync_file->fence to abstract the type of

Re: [PATCH -next] drm/arm: mali-dp: Fix error return code in malidp_bind()

On Thu, Jul 28, 2016 at 09:22:21AM +0100, Brian Starkey wrote: > Hi Wei, > > On Thu, Jul 28, 2016 at 02:14:26AM +, Wei Yongjun wrote: > > Fix to return error code -EINVAL from the error handling > > case instead of 0, as done elsewhere in this function. > > > > Fixes: 3c31760e760c ('drm/arm:

Re: [PATCH -next] drm/arm: mali-dp: Fix error return code in malidp_bind()

On Thu, Jul 28, 2016 at 09:22:21AM +0100, Brian Starkey wrote: > Hi Wei, > > On Thu, Jul 28, 2016 at 02:14:26AM +, Wei Yongjun wrote: > > Fix to return error code -EINVAL from the error handling > > case instead of 0, as done elsewhere in this function. > > > > Fixes: 3c31760e760c ('drm/arm:

Re: [PATCH -next] drm/arm: mali-dp: Remove redundant dev_err call in malidp_bind()

On Thu, Jul 28, 2016 at 09:11:43AM +0100, Liviu Dudau wrote: > On Thu, Jul 28, 2016 at 02:09:13AM +, Wei Yongjun wrote: > > There is a error message within devm_ioremap_resource > > already, so remove the DRM_ERROR call to avoid redundant > > error message. > > Yeah, good catch! > > > > >

Re: [PATCH -next] drm/arm: mali-dp: Remove redundant dev_err call in malidp_bind()

On Thu, Jul 28, 2016 at 09:11:43AM +0100, Liviu Dudau wrote: > On Thu, Jul 28, 2016 at 02:09:13AM +, Wei Yongjun wrote: > > There is a error message within devm_ioremap_resource > > already, so remove the DRM_ERROR call to avoid redundant > > error message. > > Yeah, good catch! > > > > >

Re: Why do we need reset_control_get_optional() ?

Am Donnerstag, den 28.07.2016, 12:09 +0200 schrieb Arnd Bergmann: > On Thursday, July 28, 2016 11:43:00 AM CEST Philipp Zabel wrote: > > > I want to deprecate _optional variants in the following steps: > > > > > > [1] Add "depends on RESET_CONTROLLER" to drivers > > > for which reset_control

Re: Why do we need reset_control_get_optional() ?

Am Donnerstag, den 28.07.2016, 12:09 +0200 schrieb Arnd Bergmann: > On Thursday, July 28, 2016 11:43:00 AM CEST Philipp Zabel wrote: > > > I want to deprecate _optional variants in the following steps: > > > > > > [1] Add "depends on RESET_CONTROLLER" to drivers > > > for which reset_control

Re: [PATCH 13/18] ARM: mvebu: a39x: enable rtc for all Armada-39x SoCs

Hi Grzegorz, On jeu., juil. 21 2016, Grzegorz Jaszczyk wrote: > Despite that FS states that rtc is present only in A395 and A398 and not in > A390, the rtc is working with A390. > Change the prefix to "ARM: dts: mvebu: armada-39x:" Acked-by: Gregory CLEMENT

Re: [PATCH 13/18] ARM: mvebu: a39x: enable rtc for all Armada-39x SoCs

Hi Grzegorz, On jeu., juil. 21 2016, Grzegorz Jaszczyk wrote: > Despite that FS states that rtc is present only in A395 and A398 and not in > A390, the rtc is working with A390. > Change the prefix to "ARM: dts: mvebu: armada-39x:" Acked-by: Gregory CLEMENT Thanks, Gregory >

Re: Why do we need reset_control_get_optional() ?

Hi Arnd, 2016-07-28 19:09 GMT+09:00 Arnd Bergmann : > On Thursday, July 28, 2016 11:43:00 AM CEST Philipp Zabel wrote: >> > I want to deprecate _optional variants in the following steps: >> > >> > [1] Add "depends on RESET_CONTROLLER" to drivers >> > for which reset_control is

Re: Why do we need reset_control_get_optional() ?

Hi Arnd, 2016-07-28 19:09 GMT+09:00 Arnd Bergmann : > On Thursday, July 28, 2016 11:43:00 AM CEST Philipp Zabel wrote: >> > I want to deprecate _optional variants in the following steps: >> > >> > [1] Add "depends on RESET_CONTROLLER" to drivers >> > for which reset_control is mandatory. >>

<    3   4   5   6   7   8   9   10   11   >