Re: [PATCH v3] powerpc/mm: Implemented default_hugepagesz verification for powerpc

Victor Aoqui writes: > Implemented default hugepage size verification (default_hugepagesz=) > in order to allow allocation of defined number of pages (hugepages=) > only for supported hugepage sizes. > > Signed-off-by: Victor Aoqui I am

Re: [PATCH v3] powerpc/mm: Implemented default_hugepagesz verification for powerpc

Victor Aoqui writes: > Implemented default hugepage size verification (default_hugepagesz=) > in order to allow allocation of defined number of pages (hugepages=) > only for supported hugepage sizes. > > Signed-off-by: Victor Aoqui I am still not sure about this. With current upstream we get

Re: [PATCH v2 17/25] mtd: nand: qcom: add BAM DMA descriptor handling

On 07/19/2017 05:18 PM, Abhishek Sahu wrote: 1. prepare_bam_async_desc is the function which will call all the DMA API’s. It will fetch the outstanding scatter gather list for passed channel and will do the DMA descriptor formation. The DMA flag is dependent upon the type of

Re: [PATCH v2 17/25] mtd: nand: qcom: add BAM DMA descriptor handling

On 07/19/2017 05:18 PM, Abhishek Sahu wrote: 1. prepare_bam_async_desc is the function which will call all the DMA API’s. It will fetch the outstanding scatter gather list for passed channel and will do the DMA descriptor formation. The DMA flag is dependent upon the type of

[PATCH v4 1/2] dt-bindings: gpio: davinci: Add keystone-k2g compatible

The patch adds keystone-k2g compatible, specific properties and an example. The patch also adds the details of supported SoCs for each compatible. Signed-off-by: Keerthy Acked-by: Rob Herring --- Changes in v4: * Changed documentation links. * Added

[PATCH v4 2/2] ARM: dts: keystone-k2g: Add gpio nodes

66AK2G has 2 instances of gpio. The first one has all the 144 GPIOs functional. 9 banks with 16 gpios making a total of 144. The second instance has only the GPIO0:GPIO67 functional and rest are marked reserved. Signed-off-by: Keerthy Acked-by: Linus Walleij

[PATCH v4 1/2] dt-bindings: gpio: davinci: Add keystone-k2g compatible

The patch adds keystone-k2g compatible, specific properties and an example. The patch also adds the details of supported SoCs for each compatible. Signed-off-by: Keerthy Acked-by: Rob Herring --- Changes in v4: * Changed documentation links. * Added Rob's Ack. * Replaced keystone-k2g

[PATCH v4 2/2] ARM: dts: keystone-k2g: Add gpio nodes

66AK2G has 2 instances of gpio. The first one has all the 144 GPIOs functional. 9 banks with 16 gpios making a total of 144. The second instance has only the GPIO0:GPIO67 functional and rest are marked reserved. Signed-off-by: Keerthy Acked-by: Linus Walleij --- Changes in v4: * Couple of

Re: [v4 2/2] ARM: dts: keystone-k2g: Add gpio nodes

On Friday 04 August 2017 11:15 AM, Keerthy wrote: > 66AK2G has 2 instances of gpio. The first one has all the 144 GPIOs > functional. 9 banks with 16 gpios making a total of 144. The second > instance has only the GPIO0:GPIO67 functional and rest are marked > reserved. I will send with the

Re: [v4 2/2] ARM: dts: keystone-k2g: Add gpio nodes

On Friday 04 August 2017 11:15 AM, Keerthy wrote: > 66AK2G has 2 instances of gpio. The first one has all the 144 GPIOs > functional. 9 banks with 16 gpios making a total of 144. The second > instance has only the GPIO0:GPIO67 functional and rest are marked > reserved. I will send with the

[v4 2/2] ARM: dts: keystone-k2g: Add gpio nodes

66AK2G has 2 instances of gpio. The first one has all the 144 GPIOs functional. 9 banks with 16 gpios making a total of 144. The second instance has only the GPIO0:GPIO67 functional and rest are marked reserved. Signed-off-by: Keerthy Acked-by: Linus Walleij

[v4 1/2] dt-bindings: gpio: davinci: Add keystone-k2g compatible

The patch adds keystone-k2g compatible, specific properties and an example. The patch also adds the details of supported SoCs for each compatible. Signed-off-by: Keerthy Acked-by: Rob Herring --- Changes in v4: * Changed documentation links. * Added

[v4 2/2] ARM: dts: keystone-k2g: Add gpio nodes

66AK2G has 2 instances of gpio. The first one has all the 144 GPIOs functional. 9 banks with 16 gpios making a total of 144. The second instance has only the GPIO0:GPIO67 functional and rest are marked reserved. Signed-off-by: Keerthy Acked-by: Linus Walleij --- Changes in v4: * Couple of

[v4 1/2] dt-bindings: gpio: davinci: Add keystone-k2g compatible

The patch adds keystone-k2g compatible, specific properties and an example. The patch also adds the details of supported SoCs for each compatible. Signed-off-by: Keerthy Acked-by: Rob Herring --- Changes in v4: * Changed documentation links. * Added Rob's Ack. * Replaced keystone-k2g

Re: [v4 2/2] ARM: dts: keystone-k2g: Add gpio nodes

On Friday 04 August 2017 11:15 AM, Keerthy wrote: > 66AK2G has 2 instances of gpio. The first one has all the 144 GPIOs > functional. 9 banks with 16 gpios making a total of 144. The second > instance has only the GPIO0:GPIO67 functional and rest are marked > reserved. Oops. I will send with

Re: [v4 2/2] ARM: dts: keystone-k2g: Add gpio nodes

On Friday 04 August 2017 11:15 AM, Keerthy wrote: > 66AK2G has 2 instances of gpio. The first one has all the 144 GPIOs > functional. 9 banks with 16 gpios making a total of 144. The second > instance has only the GPIO0:GPIO67 functional and rest are marked > reserved. Oops. I will send with

[PATCH] samples/bpf: Fix cross compiler error with bpf sample

When cross-compiling the bpf sample map_perf_test for aarch64, I find that __NR_getpgrp is undefined. This causes build errors. Fix it by allowing the deprecated syscall in the sample. Signed-off-by: Joel Fernandes --- samples/bpf/map_perf_test_user.c | 2 ++ 1 file changed,

[PATCH] samples/bpf: Fix cross compiler error with bpf sample

When cross-compiling the bpf sample map_perf_test for aarch64, I find that __NR_getpgrp is undefined. This causes build errors. Fix it by allowing the deprecated syscall in the sample. Signed-off-by: Joel Fernandes --- samples/bpf/map_perf_test_user.c | 2 ++ 1 file changed, 2 insertions(+)

Re: Gift-

Good Day, My wife and I have awarded you with a donation of $ 1,000,000.00 Dollars from part of our Jackpot Lottery of 50 Million Dollars, respond with your details for claims. We await your earliest response and God Bless you. Friedrich And Annand Mayrhofer. --- This email has been checked

Re: Gift-

Good Day, My wife and I have awarded you with a donation of $ 1,000,000.00 Dollars from part of our Jackpot Lottery of 50 Million Dollars, respond with your details for claims. We await your earliest response and God Bless you. Friedrich And Annand Mayrhofer. --- This email has been checked

Re: strace-4.18 test suite oopses sparc64 4.12 and 4.13-rc kernels

Hi Davem. On Thu, Aug 03, 2017 at 02:57:48PM -0700, David Miller wrote: > From: Mikael Pettersson > Date: Thu, 3 Aug 2017 22:02:57 +0200 > > > With that in place the kernel booted fine. > > When I then ran the `poll' strace test binary, the OOPS was replaced by: > > > > [

Re: strace-4.18 test suite oopses sparc64 4.12 and 4.13-rc kernels

Hi Davem. On Thu, Aug 03, 2017 at 02:57:48PM -0700, David Miller wrote: > From: Mikael Pettersson > Date: Thu, 3 Aug 2017 22:02:57 +0200 > > > With that in place the kernel booted fine. > > When I then ran the `poll' strace test binary, the OOPS was replaced by: > > > > [ 140.589913]

[PATCH 4/5] scsi/esp_scsi: Avoid sending ABORT TASK SET messages

If an LLD aborts a task set, it should complete the affected commands with the appropriate result code. In a couple of cases esp_scsi doesn't do so. When the initiator receives an unhandled message, just respond by sending a MESSAGE REJECT instead of ABORT TASK SET, and thus avoid the issue.

[PATCH 4/5] scsi/esp_scsi: Avoid sending ABORT TASK SET messages

If an LLD aborts a task set, it should complete the affected commands with the appropriate result code. In a couple of cases esp_scsi doesn't do so. When the initiator receives an unhandled message, just respond by sending a MESSAGE REJECT instead of ABORT TASK SET, and thus avoid the issue.

[PATCH 3/5] scsi/esp_scsi: Clean up control flow and dead code

This patch improves readability. There are no functional changes. Since this touches on a questionable ESP_INTR_DC conditional, add some commentary to help others who may (as I did) find themselves chasing an "Invalid Command" error after the device flags this condition. This cleanup also

[PATCH 3/5] scsi/esp_scsi: Clean up control flow and dead code

This patch improves readability. There are no functional changes. Since this touches on a questionable ESP_INTR_DC conditional, add some commentary to help others who may (as I did) find themselves chasing an "Invalid Command" error after the device flags this condition. This cleanup also

[PATCH 5/5] scsi/esp_scsi: Always clear msg_out_len after MESSAGE OUT phase

After sending a message, always clear esp->msg_out_len. Otherwise, eh_abort_handler may subsequently fail to send an ABORT TASK SET message. Tested-by: Stan Johnson Signed-off-by: Finn Thain --- drivers/scsi/esp_scsi.c | 2 ++ 1 file changed, 2

[PATCH 5/5] scsi/esp_scsi: Always clear msg_out_len after MESSAGE OUT phase

After sending a message, always clear esp->msg_out_len. Otherwise, eh_abort_handler may subsequently fail to send an ABORT TASK SET message. Tested-by: Stan Johnson Signed-off-by: Finn Thain --- drivers/scsi/esp_scsi.c | 2 ++ 1 file changed, 2 insertions(+) diff --git

[PATCH 0/5] esp_scsi, mac_esp: Various fixes and cleanups

This series has been tested on m68k Macs (ESP236 equivalent). Some more testing with different targets and devices (FAS236 etc) might be nice. Being that the esp_scsi fixes are on error paths, more review may actually be more valuable than more testing... Finn Thain (5): scsi/mac_esp: Avoid

[PATCH 0/5] esp_scsi, mac_esp: Various fixes and cleanups

This series has been tested on m68k Macs (ESP236 equivalent). Some more testing with different targets and devices (FAS236 etc) might be nice. Being that the esp_scsi fixes are on error paths, more review may actually be more valuable than more testing... Finn Thain (5): scsi/mac_esp: Avoid

[PATCH 1/5] scsi/mac_esp: Avoid type warning from sparse

Avoid the following warning from "make C=1": CHECK drivers/scsi/mac_esp.c drivers/scsi/mac_esp.c:357:30: warning: incorrect type in initializer (different address spaces) drivers/scsi/mac_esp.c:357:30:expected unsigned char [usertype] *fifo drivers/scsi/mac_esp.c:357:30:got void

[PATCH 1/5] scsi/mac_esp: Avoid type warning from sparse

Avoid the following warning from "make C=1": CHECK drivers/scsi/mac_esp.c drivers/scsi/mac_esp.c:357:30: warning: incorrect type in initializer (different address spaces) drivers/scsi/mac_esp.c:357:30:expected unsigned char [usertype] *fifo drivers/scsi/mac_esp.c:357:30:got void

[PATCH 2/5] scsi/mac_esp: Fix PIO transfers for MESSAGE IN phase

When in MESSAGE IN phase, the ESP device does not automatically acknowledge each byte that is transferred by PIO. The mac_esp driver neglects to explicitly ack them, which causes a timeout during messages larger than one byte (e.g. tag bytes during reconnect). Fix this with an ESP_CMD_MOK command

Re: [PATCH v2 16/25] mtd: nand: qcom: allocate BAM transaction

On 07/19/2017 05:18 PM, Abhishek Sahu wrote: The BAM transaction is the core data structure which will be used for all the data transfers in QPIC NAND. Since the base layer is serializing all the NAND requests so allocating BAM transaction before every transfer will be overhead. The memory for

[PATCH 2/5] scsi/mac_esp: Fix PIO transfers for MESSAGE IN phase

When in MESSAGE IN phase, the ESP device does not automatically acknowledge each byte that is transferred by PIO. The mac_esp driver neglects to explicitly ack them, which causes a timeout during messages larger than one byte (e.g. tag bytes during reconnect). Fix this with an ESP_CMD_MOK command

Re: [PATCH v2 16/25] mtd: nand: qcom: allocate BAM transaction

On 07/19/2017 05:18 PM, Abhishek Sahu wrote: The BAM transaction is the core data structure which will be used for all the data transfers in QPIC NAND. Since the base layer is serializing all the NAND requests so allocating BAM transaction before every transfer will be overhead. The memory for

Re: [v5 09/15] sparc64: optimized struct page zeroing

Hi Pavel. On Thu, Aug 03, 2017 at 05:23:47PM -0400, Pavel Tatashin wrote: > Add an optimized mm_zero_struct_page(), so struct page's are zeroed without > calling memset(). We do eight regular stores, thus avoid cost of membar. The commit message does no longer reflect the implementation, and

Re: [v5 09/15] sparc64: optimized struct page zeroing

Hi Pavel. On Thu, Aug 03, 2017 at 05:23:47PM -0400, Pavel Tatashin wrote: > Add an optimized mm_zero_struct_page(), so struct page's are zeroed without > calling memset(). We do eight regular stores, thus avoid cost of membar. The commit message does no longer reflect the implementation, and

Re: [PATCH net-next] net: dsa: User per-cpu 64-bit statistics

On Thu, 2017-08-03 at 21:33 -0700, Florian Fainelli wrote: > During testing with a background iperf pushing 1Gbit/sec worth of > traffic and having both ifconfig and ethtool collect statistics, we > could see quite frequent deadlocks. Convert the often accessed DSA slave > network devices

Re: [PATCH net-next] net: dsa: User per-cpu 64-bit statistics

On Thu, 2017-08-03 at 21:33 -0700, Florian Fainelli wrote: > During testing with a background iperf pushing 1Gbit/sec worth of > traffic and having both ifconfig and ethtool collect statistics, we > could see quite frequent deadlocks. Convert the often accessed DSA slave > network devices

[PATCH BUGFIX/IMPROVEMENT V2 1/2] block,bfq: refactor device-idling logic

The logic that decides whether to idle the device is scattered across three functions. Almost all of the logic is in the function bfq_bfqq_may_idle, but (1) part of the decision is made in bfq_update_idle_window, and (2) the function bfq_bfqq_must_idle may switch off idling regardless of the

[PATCH BUGFIX/IMPROVEMENT V2 0/2] block, bfq: improve and refactor throughput-boosting logic

Hi, these two patches improve throughput-boosting logic in two aspects. The first patch refactors the parts of the device-idling logic, related to throughput boosting, that are still scattered across the source file bfq-iosched.c. The patch concetrates all the logic in one function. The second

[PATCH BUGFIX/IMPROVEMENT V2 1/2] block,bfq: refactor device-idling logic

The logic that decides whether to idle the device is scattered across three functions. Almost all of the logic is in the function bfq_bfqq_may_idle, but (1) part of the decision is made in bfq_update_idle_window, and (2) the function bfq_bfqq_must_idle may switch off idling regardless of the

[PATCH BUGFIX/IMPROVEMENT V2 0/2] block, bfq: improve and refactor throughput-boosting logic

Hi, these two patches improve throughput-boosting logic in two aspects. The first patch refactors the parts of the device-idling logic, related to throughput boosting, that are still scattered across the source file bfq-iosched.c. The patch concetrates all the logic in one function. The second

[PATCH BUGFIX/IMPROVEMENT V2 2/2] block, bfq: boost throughput with flash-based non-queueing devices

When a queue associated with a process remains empty, there are cases where throughput gets boosted if the device is idled to await the arrival of a new I/O request for that queue. Currently, BFQ assumes that one of these cases is when the device has no internal queueing (regardless of the

[PATCH BUGFIX/IMPROVEMENT V2 2/2] block, bfq: boost throughput with flash-based non-queueing devices

When a queue associated with a process remains empty, there are cases where throughput gets boosted if the device is idled to await the arrival of a new I/O request for that queue. Currently, BFQ assumes that one of these cases is when the device has no internal queueing (regardless of the

Re: [V3 1/2] phy: ralink-usb: add driver for Mediatek/Ralink

On Thursday 03 August 2017 04:02 PM, Harvey Hunt wrote: > From: John Crispin > > Add a driver to setup the USB phy on Mediatek/Ralink SoCs. > The driver is trivial and only sets up power and host mode. > > Signed-off-by: John Crispin > Signed-off-by:

Re: [V3 1/2] phy: ralink-usb: add driver for Mediatek/Ralink

On Thursday 03 August 2017 04:02 PM, Harvey Hunt wrote: > From: John Crispin > > Add a driver to setup the USB phy on Mediatek/Ralink SoCs. > The driver is trivial and only sets up power and host mode. > > Signed-off-by: John Crispin > Signed-off-by: Harvey Hunt > Cc:

Re: [PATCH v2 2/4] phy: add inno-usb2-phy driver for hi3798cv200 SoC

Hi, On Wednesday 26 July 2017 11:36 AM, Jiancheng Xue wrote: > From: Pengcheng Li > > Add inno-usb2-phy driver for hi3798cv200 SoC. > > Signed-off-by: Pengcheng Li > Signed-off-by: Jiancheng Xue > --- >

Re: [PATCH v2 2/4] phy: add inno-usb2-phy driver for hi3798cv200 SoC

Hi, On Wednesday 26 July 2017 11:36 AM, Jiancheng Xue wrote: > From: Pengcheng Li > > Add inno-usb2-phy driver for hi3798cv200 SoC. > > Signed-off-by: Pengcheng Li > Signed-off-by: Jiancheng Xue > --- > drivers/phy/hisilicon/Kconfig | 11 +- > drivers/phy/hisilicon/Makefile

Re: [PATCH v2 15/25] mtd: nand: qcom: DMA mapping support for register read buffer

Hi, On 07/19/2017 05:18 PM, Abhishek Sahu wrote: The EBI2 NAND directly remaps register read buffer with dma_map_sg. The QPIC NAND will give register read buffer in its command descriptor and the command descriptor will be mapped with dma_map_sg instead of register read buffer. This command

Re: [PATCH v2 15/25] mtd: nand: qcom: DMA mapping support for register read buffer

Hi, On 07/19/2017 05:18 PM, Abhishek Sahu wrote: The EBI2 NAND directly remaps register read buffer with dma_map_sg. The QPIC NAND will give register read buffer in its command descriptor and the command descriptor will be mapped with dma_map_sg instead of register read buffer. This command

Re: [PATCH 0/2] PCI: dwc: convert remaining dbi read/writes to dw_pcie_readX_dbi/dw_pcie_writeX_dbi

On Friday 04 August 2017 01:42 AM, Bjorn Helgaas wrote: > Adding Kishon & Pratyush for real this time. > > On Wed, Aug 02, 2017 at 04:32:56PM -0500, Bjorn Helgaas wrote: >> [+cc Kishon, Pratyush] >> >> On Fri, Jul 14, 2017 at 02:07:33PM +0200, Niklas Cassel wrote: >>> Since the introduction of

Re: [PATCH 0/2] PCI: dwc: convert remaining dbi read/writes to dw_pcie_readX_dbi/dw_pcie_writeX_dbi

On Friday 04 August 2017 01:42 AM, Bjorn Helgaas wrote: > Adding Kishon & Pratyush for real this time. > > On Wed, Aug 02, 2017 at 04:32:56PM -0500, Bjorn Helgaas wrote: >> [+cc Kishon, Pratyush] >> >> On Fri, Jul 14, 2017 at 02:07:33PM +0200, Niklas Cassel wrote: >>> Since the introduction of

Re: [PATCH 2/2] fsnotify: use method copy_dname copying filename

On Fri, Aug 04, 2017 at 11:58:41AM +0800, 林守磊 wrote: > Hi all > > I sent this patch two months ago, then I found CVE from this link last night > > http://seclists.org/oss-sec/2017/q3/240 > > which not only references this patch, but also provides a upstream fix > > >

Re: [PATCH 2/2] fsnotify: use method copy_dname copying filename

On Fri, Aug 04, 2017 at 11:58:41AM +0800, 林守磊 wrote: > Hi all > > I sent this patch two months ago, then I found CVE from this link last night > > http://seclists.org/oss-sec/2017/q3/240 > > which not only references this patch, but also provides a upstream fix > > >

Re: [PATCH v5 3/4] sched/deadline: Add support for SD_PREFER_SIBLING on find_later_rq()

On Thu, Aug 03, 2017 at 02:03:34PM +0200, Peter Zijlstra wrote: > This one I'm not sure on.. at the very least we should exclude all of > the prefer sibling domain when we do the next domain, and if there are > multiple prefer sibling levels, we should only pick the first > fallback_cpu -- there

Re: [PATCH v5 3/4] sched/deadline: Add support for SD_PREFER_SIBLING on find_later_rq()

On Thu, Aug 03, 2017 at 02:03:34PM +0200, Peter Zijlstra wrote: > This one I'm not sure on.. at the very least we should exclude all of > the prefer sibling domain when we do the next domain, and if there are > multiple prefer sibling levels, we should only pick the first > fallback_cpu -- there

Re: [PATCH] cpufreq: dt: Add rk3328 compatible to use generic cpufreq driver

On 04-08-17, 09:52, Finley Xiao wrote: > This patch adds the rk3328 compatible string for supporting > the generic cpufreq driver on RK3328. > > Signed-off-by: Finley Xiao > --- > drivers/cpufreq/cpufreq-dt-platdev.c | 1 + > 1 file changed, 1 insertion(+) > > diff

Re: [PATCH] cpufreq: dt: Add rk3328 compatible to use generic cpufreq driver

On 04-08-17, 09:52, Finley Xiao wrote: > This patch adds the rk3328 compatible string for supporting > the generic cpufreq driver on RK3328. > > Signed-off-by: Finley Xiao > --- > drivers/cpufreq/cpufreq-dt-platdev.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git

[PATCH 01/11] drm: i915: i915_oa_kblgt2: constify attribute_group structures.

attribute_group are not supposed to change at runtime. All functions working with attribute_group provided by work with const attribute_group. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/gpu/drm/i915/i915_oa_kblgt2.c | 36

[PATCH 01/11] drm: i915: i915_oa_kblgt2: constify attribute_group structures.

attribute_group are not supposed to change at runtime. All functions working with attribute_group provided by work with const attribute_group. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/gpu/drm/i915/i915_oa_kblgt2.c | 36 +--

[PATCH 02/11] drm: i915: i915_oa_bdw: constify attribute_group structures.

attribute_group are not supposed to change at runtime. All functions working with attribute_group provided by work with const attribute_group. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/gpu/drm/i915/i915_oa_bdw.c | 44

[PATCH 02/11] drm: i915: i915_oa_bdw: constify attribute_group structures.

attribute_group are not supposed to change at runtime. All functions working with attribute_group provided by work with const attribute_group. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/gpu/drm/i915/i915_oa_bdw.c | 44 +++---

[PATCH 05/11] drm: i915: i915_oa_glk: constify attribute_group structures.

attribute_group are not supposed to change at runtime. All functions working with attribute_group provided by work with const attribute_group. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/gpu/drm/i915/i915_oa_glk.c | 30

[PATCH 05/11] drm: i915: i915_oa_glk: constify attribute_group structures.

attribute_group are not supposed to change at runtime. All functions working with attribute_group provided by work with const attribute_group. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/gpu/drm/i915/i915_oa_glk.c | 30 +++--- 1 file

[PATCH 03/11] drm: i915: i915_oa_bxt: constify attribute_group structures.

attribute_group are not supposed to change at runtime. All functions working with attribute_group provided by work with const attribute_group. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/gpu/drm/i915/i915_oa_bxt.c | 30

[PATCH 03/11] drm: i915: i915_oa_bxt: constify attribute_group structures.

attribute_group are not supposed to change at runtime. All functions working with attribute_group provided by work with const attribute_group. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/gpu/drm/i915/i915_oa_bxt.c | 30 +++--- 1 file

[PATCH 07/11] drm: i915: i915_oa_kblgt3: constify attribute_group structures.

attribute_group are not supposed to change at runtime. All functions working with attribute_group provided by work with const attribute_group. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/gpu/drm/i915/i915_oa_kblgt3.c | 36

[PATCH 07/11] drm: i915: i915_oa_kblgt3: constify attribute_group structures.

attribute_group are not supposed to change at runtime. All functions working with attribute_group provided by work with const attribute_group. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/gpu/drm/i915/i915_oa_kblgt3.c | 36 +--

[PATCH 09/11] drm: i915: i915_oa_sklgt3: constify attribute_group structures.

attribute_group are not supposed to change at runtime. All functions working with attribute_group provided by work with const attribute_group. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/gpu/drm/i915/i915_oa_sklgt3.c | 36

[PATCH 11/11] drm: i915: i915_sysfs: constify attribute_group structures.

attribute_group are not supposed to change at runtime. All functions working with attribute_group provided by work with const attribute_group. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/gpu/drm/i915/i915_sysfs.c | 6 +++--- 1 file

[PATCH 10/11] drm: i915: i915_oa_sklgt4: constify attribute_group structures.

attribute_group are not supposed to change at runtime. All functions working with attribute_group provided by work with const attribute_group. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/gpu/drm/i915/i915_oa_sklgt4.c | 36

[PATCH 09/11] drm: i915: i915_oa_sklgt3: constify attribute_group structures.

attribute_group are not supposed to change at runtime. All functions working with attribute_group provided by work with const attribute_group. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/gpu/drm/i915/i915_oa_sklgt3.c | 36 +--

[PATCH 11/11] drm: i915: i915_sysfs: constify attribute_group structures.

attribute_group are not supposed to change at runtime. All functions working with attribute_group provided by work with const attribute_group. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/gpu/drm/i915/i915_sysfs.c | 6 +++--- 1 file changed, 3 insertions(+),

[PATCH 10/11] drm: i915: i915_oa_sklgt4: constify attribute_group structures.

attribute_group are not supposed to change at runtime. All functions working with attribute_group provided by work with const attribute_group. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/gpu/drm/i915/i915_oa_sklgt4.c | 36 +--

[PATCH 06/11] drm: i915: i915_oa_hsw: constify attribute_group structures.

attribute_group are not supposed to change at runtime. All functions working with attribute_group provided by work with const attribute_group. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/gpu/drm/i915/i915_oa_hsw.c | 12 ++--

[PATCH 04/11] drm: i915: i915_oa_chv: constify attribute_group structures.

attribute_group are not supposed to change at runtime. All functions working with attribute_group provided by work with const attribute_group. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/gpu/drm/i915/i915_oa_chv.c | 28

[PATCH 06/11] drm: i915: i915_oa_hsw: constify attribute_group structures.

attribute_group are not supposed to change at runtime. All functions working with attribute_group provided by work with const attribute_group. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/gpu/drm/i915/i915_oa_hsw.c | 12 ++-- 1 file changed, 6

[PATCH 04/11] drm: i915: i915_oa_chv: constify attribute_group structures.

attribute_group are not supposed to change at runtime. All functions working with attribute_group provided by work with const attribute_group. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/gpu/drm/i915/i915_oa_chv.c | 28 ++-- 1 file

[PATCH 08/11] drm: i915: i915_oa_sklgt2: constify attribute_group structures.

attribute_group are not supposed to change at runtime. All functions working with attribute_group provided by work with const attribute_group. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/gpu/drm/i915/i915_oa_sklgt2.c | 36

[PATCH 08/11] drm: i915: i915_oa_sklgt2: constify attribute_group structures.

attribute_group are not supposed to change at runtime. All functions working with attribute_group provided by work with const attribute_group. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/gpu/drm/i915/i915_oa_sklgt2.c | 36 +--

[PATCH 00/11] constify i915 attribute_group structures.

attribute_group are not supposed to change at runtime. All functions working with attribute_group provided by work with const attribute_group. So mark the non-const structs as const. Arvind Yadav (11): [PATCH 01/11] drm: i915: i915_oa_kblgt2: constify attribute_group structures. [PATCH

[PATCH 00/11] constify i915 attribute_group structures.

attribute_group are not supposed to change at runtime. All functions working with attribute_group provided by work with const attribute_group. So mark the non-const structs as const. Arvind Yadav (11): [PATCH 01/11] drm: i915: i915_oa_kblgt2: constify attribute_group structures. [PATCH

Re: [PATCH 4.12 00/31] 4.12.5-stable review

On 08/03/2017 04:17 PM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 4.12.5 release. There are 31 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be

Re: [PATCH 4.12 00/31] 4.12.5-stable review

On 08/03/2017 04:17 PM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 4.12.5 release. There are 31 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be

[PATCH] pinctrl: add __rcu annotations to fix sparse warnings

Sparse reports "warning: incorrect type in assignment (different address spaces)". Signed-off-by: Masahiro Yamada --- drivers/pinctrl/core.c | 2 +- drivers/pinctrl/pinmux.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git

[PATCH] pinctrl: add __rcu annotations to fix sparse warnings

Sparse reports "warning: incorrect type in assignment (different address spaces)". Signed-off-by: Masahiro Yamada --- drivers/pinctrl/core.c | 2 +- drivers/pinctrl/pinmux.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/pinctrl/core.c b/drivers/pinctrl/core.c

[PATCH] pinctrl: nomadik: fix incorrect type in return expression

Sparse reports "warning: incorrect type in return expression (different address spaces)" because nmk_gpio_populate_chip() is supposed to return (struct nmk_gpio_chip *) whereas devm_ioremap_resource() returns (void __iomem *). ERR_CAST() is needed to fix the warning. Signed-off-by: Masahiro

[PATCH] pinctrl: nomadik: fix incorrect type in return expression

Sparse reports "warning: incorrect type in return expression (different address spaces)" because nmk_gpio_populate_chip() is supposed to return (struct nmk_gpio_chip *) whereas devm_ioremap_resource() returns (void __iomem *). ERR_CAST() is needed to fix the warning. Signed-off-by: Masahiro

[PATCH] pinctrl: sirf: add static to local data

Detected by sparse. Signed-off-by: Masahiro Yamada --- drivers/pinctrl/sirf/pinctrl-atlas7.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/pinctrl/sirf/pinctrl-atlas7.c b/drivers/pinctrl/sirf/pinctrl-atlas7.c index

[PATCH] pinctrl: sirf: add static to local data

Detected by sparse. Signed-off-by: Masahiro Yamada --- drivers/pinctrl/sirf/pinctrl-atlas7.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/pinctrl/sirf/pinctrl-atlas7.c b/drivers/pinctrl/sirf/pinctrl-atlas7.c index 1efa315a7dbe..b3de1eb04ec1 100644 ---

[PATCH] pinctrl: armada-37xx: add static to local data

Detected by sparse. Signed-off-by: Masahiro Yamada --- drivers/pinctrl/mvebu/pinctrl-armada-37xx.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/pinctrl/mvebu/pinctrl-armada-37xx.c b/drivers/pinctrl/mvebu/pinctrl-armada-37xx.c

[PATCH] pinctrl: armada-37xx: add static to local data

Detected by sparse. Signed-off-by: Masahiro Yamada --- drivers/pinctrl/mvebu/pinctrl-armada-37xx.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/pinctrl/mvebu/pinctrl-armada-37xx.c b/drivers/pinctrl/mvebu/pinctrl-armada-37xx.c index f024e25787fc..0b263b90a9a8

[PATCH net-next] net: dsa: User per-cpu 64-bit statistics

During testing with a background iperf pushing 1Gbit/sec worth of traffic and having both ifconfig and ethtool collect statistics, we could see quite frequent deadlocks. Convert the often accessed DSA slave network devices statistics to per-cpu 64-bit statistics to remove these deadlocks and

[PATCH net-next] net: dsa: User per-cpu 64-bit statistics

During testing with a background iperf pushing 1Gbit/sec worth of traffic and having both ifconfig and ethtool collect statistics, we could see quite frequent deadlocks. Convert the often accessed DSA slave network devices statistics to per-cpu 64-bit statistics to remove these deadlocks and

Re: [linux-sunxi] [PATCH 10/13] [NOT FOR REVIEW NOW] clk: sunxi: Add CLK_SET_RATE_PARENT flag for H3 HDMI clock

On Fri, Aug 4, 2017 at 12:16 PM, Icenowy Zheng wrote: > > > 于 2017年8月4日 GMT+08:00 下午12:15:27, Chen-Yu Tsai 写到: >>Hi, >> >>On Tue, Aug 1, 2017 at 9:13 PM, Icenowy Zheng wrote: >>> From: Jernej Skrabec >>> >>> When setting

Re: [linux-sunxi] [PATCH 10/13] [NOT FOR REVIEW NOW] clk: sunxi: Add CLK_SET_RATE_PARENT flag for H3 HDMI clock

On Fri, Aug 4, 2017 at 12:16 PM, Icenowy Zheng wrote: > > > 于 2017年8月4日 GMT+08:00 下午12:15:27, Chen-Yu Tsai 写到: >>Hi, >> >>On Tue, Aug 1, 2017 at 9:13 PM, Icenowy Zheng wrote: >>> From: Jernej Skrabec >>> >>> When setting the HDMI clock of H3, the PLL_VIDEO clock needs to be >>set. >>> >>> Add

Re: [linux-sunxi] [PATCH] drm/panel: simple: Fix width and height for Olimex LCD-OLinuXino-4.3TS

On Thu, Jul 20, 2017 at 6:29 PM, Jonathan Liu wrote: > The physical size of the panel is 105.5 (W) x 67.2 (H) x 4.05 (D) mm > but the active display area is 95.04 (W) x 53.856 (H) mm. > > The width and height should be set to the active display area. > > Signed-off-by: Jonathan

Re: [linux-sunxi] [PATCH] drm/panel: simple: Fix width and height for Olimex LCD-OLinuXino-4.3TS

On Thu, Jul 20, 2017 at 6:29 PM, Jonathan Liu wrote: > The physical size of the panel is 105.5 (W) x 67.2 (H) x 4.05 (D) mm > but the active display area is 95.04 (W) x 53.856 (H) mm. > > The width and height should be set to the active display area. > > Signed-off-by: Jonathan Liu You probably

  1   2   3   4   5   6   7   8   9   10   >