[tip:x86/urgent] x86/PCI: Remove unused HyperTransport interrupt support

Commit-ID: fd2fa6c18b729e19c51240453a521f76c766247e Gitweb: https://git.kernel.org/tip/fd2fa6c18b729e19c51240453a521f76c766247e Author: Bjorn Helgaas AuthorDate: Wed, 22 Nov 2017 16:13:37 -0600 Committer: Thomas Gleixner CommitDate: Thu, 23 Nov

[tip:x86/urgent] x86/PCI: Remove unused HyperTransport interrupt support

Commit-ID: fd2fa6c18b729e19c51240453a521f76c766247e Gitweb: https://git.kernel.org/tip/fd2fa6c18b729e19c51240453a521f76c766247e Author: Bjorn Helgaas AuthorDate: Wed, 22 Nov 2017 16:13:37 -0600 Committer: Thomas Gleixner CommitDate: Thu, 23 Nov 2017 20:18:18 +0100 x86/PCI: Remove

[tip:x86/urgent] x86/boot/KASLR: Remove unused variable

Commit-ID: 69550d41ff9c884c6d996fca41037974b2255852 Gitweb: https://git.kernel.org/tip/69550d41ff9c884c6d996fca41037974b2255852 Author: Chao Fan AuthorDate: Thu, 23 Nov 2017 17:08:47 +0800 Committer: Thomas Gleixner CommitDate: Thu, 23 Nov

[tip:x86/urgent] x86/boot/KASLR: Remove unused variable

Commit-ID: 69550d41ff9c884c6d996fca41037974b2255852 Gitweb: https://git.kernel.org/tip/69550d41ff9c884c6d996fca41037974b2255852 Author: Chao Fan AuthorDate: Thu, 23 Nov 2017 17:08:47 +0800 Committer: Thomas Gleixner CommitDate: Thu, 23 Nov 2017 20:17:59 +0100 x86/boot/KASLR: Remove

Re: [PATCH v2 05/18] x86/fixmap: Generalize the GDT fixmap mechanism

On Tue, 21 Nov 2017, Andy Lutomirski wrote: > Currently, the GDT is an ad-hoc array of pages, one per CPU, in the > fixmap. Generalize it to be an array of a new struct cpu_entry_area > so that we can cleanly add new things to it. > > Signed-off-by: Andy Lutomirski > +/* > +

Re: [PATCH v2 05/18] x86/fixmap: Generalize the GDT fixmap mechanism

On Tue, 21 Nov 2017, Andy Lutomirski wrote: > Currently, the GDT is an ad-hoc array of pages, one per CPU, in the > fixmap. Generalize it to be an array of a new struct cpu_entry_area > so that we can cleanly add new things to it. > > Signed-off-by: Andy Lutomirski > +/* > + * cpu_entry_area

[tip:irq/urgent] genirq/matrix: Make - vs ?: Precedence explicit

Commit-ID: 75f1133873d6a1276d3c19918b7c94975840f990 Gitweb: https://git.kernel.org/tip/75f1133873d6a1276d3c19918b7c94975840f990 Author: Kees Cook AuthorDate: Wed, 22 Nov 2017 12:56:45 -0800 Committer: Thomas Gleixner CommitDate: Thu, 23 Nov

[tip:irq/urgent] genirq/matrix: Make - vs ?: Precedence explicit

Commit-ID: 75f1133873d6a1276d3c19918b7c94975840f990 Gitweb: https://git.kernel.org/tip/75f1133873d6a1276d3c19918b7c94975840f990 Author: Kees Cook AuthorDate: Wed, 22 Nov 2017 12:56:45 -0800 Committer: Thomas Gleixner CommitDate: Thu, 23 Nov 2017 20:09:31 +0100 genirq/matrix: Make - vs

[tip:irq/urgent] irqchip/imgpdc: Use resource_size function on resource object

Commit-ID: 328bf1b29c3741de3c55f2b2e5179d18f16ba9c1 Gitweb: https://git.kernel.org/tip/328bf1b29c3741de3c55f2b2e5179d18f16ba9c1 Author: Vasyl Gomonovych AuthorDate: Mon, 20 Nov 2017 23:02:41 +0100 Committer: Thomas Gleixner CommitDate: Thu, 23

[tip:irq/urgent] irqchip/imgpdc: Use resource_size function on resource object

Commit-ID: 328bf1b29c3741de3c55f2b2e5179d18f16ba9c1 Gitweb: https://git.kernel.org/tip/328bf1b29c3741de3c55f2b2e5179d18f16ba9c1 Author: Vasyl Gomonovych AuthorDate: Mon, 20 Nov 2017 23:02:41 +0100 Committer: Thomas Gleixner CommitDate: Thu, 23 Nov 2017 20:09:12 +0100 irqchip/imgpdc:

[tip:irq/urgent] irqchoip/imgpdc: Use resource_size function on resource object

Commit-ID: a994988d73db142fbe842ce08bbda62b12456577 Gitweb: https://git.kernel.org/tip/a994988d73db142fbe842ce08bbda62b12456577 Author: Vasyl Gomonovych AuthorDate: Mon, 20 Nov 2017 23:02:41 +0100 Committer: Thomas Gleixner CommitDate: Thu, 23

[tip:irq/urgent] irqchoip/imgpdc: Use resource_size function on resource object

Commit-ID: a994988d73db142fbe842ce08bbda62b12456577 Gitweb: https://git.kernel.org/tip/a994988d73db142fbe842ce08bbda62b12456577 Author: Vasyl Gomonovych AuthorDate: Mon, 20 Nov 2017 23:02:41 +0100 Committer: Thomas Gleixner CommitDate: Thu, 23 Nov 2017 20:04:55 +0100 irqchoip/imgpdc:

[tip:irq/urgent] irqchip/qcom: Fix u32 comparison with value less than zero

Commit-ID: e9990d70e8a063a7b894c5cbb99f630a0f41200d Gitweb: https://git.kernel.org/tip/e9990d70e8a063a7b894c5cbb99f630a0f41200d Author: Colin Ian King AuthorDate: Fri, 17 Nov 2017 18:35:53 + Committer: Thomas Gleixner CommitDate: Thu,

[tip:irq/urgent] irqchip/qcom: Fix u32 comparison with value less than zero

Commit-ID: e9990d70e8a063a7b894c5cbb99f630a0f41200d Gitweb: https://git.kernel.org/tip/e9990d70e8a063a7b894c5cbb99f630a0f41200d Author: Colin Ian King AuthorDate: Fri, 17 Nov 2017 18:35:53 + Committer: Thomas Gleixner CommitDate: Thu, 23 Nov 2017 20:03:58 +0100 irqchip/qcom: Fix

[no subject]

subscribe linux-arm-kerne

[no subject]

subscribe linux-arm-kerne

Re: 4.14: WARNING: CPU: 4 PID: 2895 at block/blk-mq.c:1144 with virtio-blk (also 4.12 stable)

On 11/23/2017 07:32 PM, Christoph Hellwig wrote: > On Thu, Nov 23, 2017 at 07:28:31PM +0100, Christian Borntraeger wrote: >> zfcp on s390. > > Ok, so it can't be the interrupt code, but probably is the blk-mq-cpumap.c > changes. Can you try to revert just those for a quick test? Hmm, I get

Re: 4.14: WARNING: CPU: 4 PID: 2895 at block/blk-mq.c:1144 with virtio-blk (also 4.12 stable)

On 11/23/2017 07:32 PM, Christoph Hellwig wrote: > On Thu, Nov 23, 2017 at 07:28:31PM +0100, Christian Borntraeger wrote: >> zfcp on s390. > > Ok, so it can't be the interrupt code, but probably is the blk-mq-cpumap.c > changes. Can you try to revert just those for a quick test? Hmm, I get

Re: Creating cyclecounter and lock member in timecounter structure [ Was Re: [RFC 1/4] drm/i915/perf: Add support to correlate GPU timestamp with system time]

On Thu, 23 Nov 2017, Sagar Arun Kamble wrote: > We needed inputs on possible optimization that can be done to > timecounter/cyclecounter structures/usage. > This mail is in response to review of patch > https://patchwork.freedesktop.org/patch/188448/. > > As Chris's observation below, about dozen

Re: Creating cyclecounter and lock member in timecounter structure [ Was Re: [RFC 1/4] drm/i915/perf: Add support to correlate GPU timestamp with system time]

On Thu, 23 Nov 2017, Sagar Arun Kamble wrote: > We needed inputs on possible optimization that can be done to > timecounter/cyclecounter structures/usage. > This mail is in response to review of patch > https://patchwork.freedesktop.org/patch/188448/. > > As Chris's observation below, about dozen

Re: [PATCH 2/3] hwrng: exynos - add Samsung Exynos True RNG driver

It was <2017-11-23 czw 17:31>, when Krzysztof Kozlowski wrote: > On Thu, Nov 23, 2017 at 4:09 PM, Łukasz Stelmach > wrote: >> Add support for True Random Number Generator found in Samsung Exynos >> 5250+ SoCs. >> >> Signed-off-by: Łukasz Stelmach

Re: [PATCH 2/3] hwrng: exynos - add Samsung Exynos True RNG driver

It was <2017-11-23 czw 17:31>, when Krzysztof Kozlowski wrote: > On Thu, Nov 23, 2017 at 4:09 PM, Łukasz Stelmach > wrote: >> Add support for True Random Number Generator found in Samsung Exynos >> 5250+ SoCs. >> >> Signed-off-by: Łukasz Stelmach >> --- >> MAINTAINERS

Re: [PATCH 1/2] perf intel-pt: Improve build messages for files that differ from the kernel

Em Tue, Nov 21, 2017 at 09:41:11AM +0100, Ingo Molnar escreveu: > * Adrian Hunter wrote: > > + ((diff -B -I'^#include' util/intel-pt-decoder/inat_types.h > > ../../arch/x86/include/asm/inat_types.h >/dev/null) || \ > > + (echo "Warning: Intel PT: x86 instruction

Re: [PATCH 1/2] perf intel-pt: Improve build messages for files that differ from the kernel

Em Tue, Nov 21, 2017 at 09:41:11AM +0100, Ingo Molnar escreveu: > * Adrian Hunter wrote: > > + ((diff -B -I'^#include' util/intel-pt-decoder/inat_types.h > > ../../arch/x86/include/asm/inat_types.h >/dev/null) || \ > > + (echo "Warning: Intel PT: x86 instruction decoder header at > >

Re: [PATCH net v2] net: thunderx: Fix TCP/UDP checksum offload for IPv6 pkts

From: Aleksey Makarov Date: Thu, 23 Nov 2017 17:41:56 +0300 > From: Sunil Goutham > > Don't offload IP header checksum to NIC. > > This fixes a previous patch which enabled checksum offloading > for both IPv4 and IPv6 packets. So L3 checksum

Re: [PATCH net v2] net: thunderx: Fix TCP/UDP checksum offload for IPv6 pkts

From: Aleksey Makarov Date: Thu, 23 Nov 2017 17:41:56 +0300 > From: Sunil Goutham > > Don't offload IP header checksum to NIC. > > This fixes a previous patch which enabled checksum offloading > for both IPv4 and IPv6 packets. So L3 checksum offload was > getting enabled for IPv6 pkts. And

Re: [PATCH v2] MIPS: ralink: Fix platform_get_irq's error checking

On 11/23/2017 06:45 PM, Arvind Yadav wrote: The platform_get_irq() function returns negative if an error occurs. zero or positive number on success. platform_get_irq() error checking for zero is not correct. Signed-off-by: Arvind Yadav --- changes in v2: Subject

Re: [PATCH v2] MIPS: ralink: Fix platform_get_irq's error checking

On 11/23/2017 06:45 PM, Arvind Yadav wrote: The platform_get_irq() function returns negative if an error occurs. zero or positive number on success. platform_get_irq() error checking for zero is not correct. Signed-off-by: Arvind Yadav --- changes in v2: Subject spelling was not correct.

Review of "[PATCH v2 0/3] virt: Add vboxguest driver for Virtual Box Guest integration"

Hi Arnd, Greg, It seems that since there are no obvious glaring issues with v2 of my vboxguest driver series it is now stuck waiting for review. Larry Finger (in the Cc) is willing to review this series, would Larry's Reviewed-by (once he is happy with the series) be enough to get this merged

Review of "[PATCH v2 0/3] virt: Add vboxguest driver for Virtual Box Guest integration"

Hi Arnd, Greg, It seems that since there are no obvious glaring issues with v2 of my vboxguest driver series it is now stuck waiting for review. Larry Finger (in the Cc) is willing to review this series, would Larry's Reviewed-by (once he is happy with the series) be enough to get this merged

Re: [PATCH 2/8] mfd: mtk-mmsys: Add mmsys driver

On 11/23/2017 10:04 AM, CK Hu wrote: >> +static const struct of_device_id of_match_mmsys[] = { >> +{ .compatible = "mediatek,mt2701-mmsys", > > Because this driver replace the original "mediatek,mt2701-mmsys" driver, > could you modify the binding document of "mediatek,mt2701-mmsys" [1]? >

Re: [PATCH 2/8] mfd: mtk-mmsys: Add mmsys driver

On 11/23/2017 10:04 AM, CK Hu wrote: >> +static const struct of_device_id of_match_mmsys[] = { >> +{ .compatible = "mediatek,mt2701-mmsys", > > Because this driver replace the original "mediatek,mt2701-mmsys" driver, > could you modify the binding document of "mediatek,mt2701-mmsys" [1]? >

Re: [PATCH 05/10] x86: jailhouse: Set up timekeeping

On Mon, 20 Nov 2017, Jan Kiszka wrote: > On 2017-11-20 12:24, Thomas Gleixner wrote: > > On Sat, 18 Nov 2017, Jan Kiszka wrote: > >> On 2017-11-17 23:49, Thomas Gleixner wrote: > >>> On Thu, 16 Nov 2017, Jan Kiszka wrote: > Calibrate the TSC and, where necessary, the APIC timer against the >

Re: [PATCH 05/10] x86: jailhouse: Set up timekeeping

On Mon, 20 Nov 2017, Jan Kiszka wrote: > On 2017-11-20 12:24, Thomas Gleixner wrote: > > On Sat, 18 Nov 2017, Jan Kiszka wrote: > >> On 2017-11-17 23:49, Thomas Gleixner wrote: > >>> On Thu, 16 Nov 2017, Jan Kiszka wrote: > Calibrate the TSC and, where necessary, the APIC timer against the >

Re: 4.14: WARNING: CPU: 4 PID: 2895 at block/blk-mq.c:1144 with virtio-blk (also 4.12 stable)

On Thu, Nov 23, 2017 at 07:28:31PM +0100, Christian Borntraeger wrote: > zfcp on s390. Ok, so it can't be the interrupt code, but probably is the blk-mq-cpumap.c changes. Can you try to revert just those for a quick test?

Re: 4.14: WARNING: CPU: 4 PID: 2895 at block/blk-mq.c:1144 with virtio-blk (also 4.12 stable)

On Thu, Nov 23, 2017 at 07:28:31PM +0100, Christian Borntraeger wrote: > zfcp on s390. Ok, so it can't be the interrupt code, but probably is the blk-mq-cpumap.c changes. Can you try to revert just those for a quick test?

Re: 4.14: WARNING: CPU: 4 PID: 2895 at block/blk-mq.c:1144 with virtio-blk (also 4.12 stable)

zfcp on s390. On 11/23/2017 07:25 PM, Christoph Hellwig wrote: > What HBA driver do you use in the host? >

Re: 4.14: WARNING: CPU: 4 PID: 2895 at block/blk-mq.c:1144 with virtio-blk (also 4.12 stable)

zfcp on s390. On 11/23/2017 07:25 PM, Christoph Hellwig wrote: > What HBA driver do you use in the host? >

Re: 4.14: WARNING: CPU: 4 PID: 2895 at block/blk-mq.c:1144 with virtio-blk (also 4.12 stable)

What HBA driver do you use in the host?

Re: 4.14: WARNING: CPU: 4 PID: 2895 at block/blk-mq.c:1144 with virtio-blk (also 4.12 stable)

What HBA driver do you use in the host?

Re: [PATCH v2 1/4] mm: fix device-dax pud write-faults triggered by get_user_pages()

On Sat, 11 Nov 2017, Dan Williams wrote: > Currently only get_user_pages_fast() can safely handle the writable gup > case due to its use of pud_access_permitted() to check whether the pud > entry is writable. In the gup slow path pud_write() is used instead of > pud_access_permitted() and to

Re: [PATCH v2 1/4] mm: fix device-dax pud write-faults triggered by get_user_pages()

On Sat, 11 Nov 2017, Dan Williams wrote: > Currently only get_user_pages_fast() can safely handle the writable gup > case due to its use of pud_access_permitted() to check whether the pud > entry is writable. In the gup slow path pud_write() is used instead of > pud_access_permitted() and to

Re: 4.14: WARNING: CPU: 4 PID: 2895 at block/blk-mq.c:1144 with virtio-blk (also 4.12 stable)

On 11/23/2017 03:34 PM, Christoph Hellwig wrote: > FYI, the patch below changes both the irq and block mappings to > always use the cpu possible map (should be split in two in due time). > > I think this is the right way forward. For every normal machine > those two are the same, but for VMs

Re: 4.14: WARNING: CPU: 4 PID: 2895 at block/blk-mq.c:1144 with virtio-blk (also 4.12 stable)

On 11/23/2017 03:34 PM, Christoph Hellwig wrote: > FYI, the patch below changes both the irq and block mappings to > always use the cpu possible map (should be split in two in due time). > > I think this is the right way forward. For every normal machine > those two are the same, but for VMs

Re: [PATCH 00/18] arm64: Unmap the kernel whilst running in userspace (KAISER)

On 23 November 2017 at 17:54, Pavel Machek wrote: > On Thu 2017-11-23 11:38:52, Ard Biesheuvel wrote: >> On 23 November 2017 at 10:46, Pavel Machek wrote: >> > On Thu 2017-11-23 09:23:02, Ard Biesheuvel wrote: >> >> On 23 November 2017 at 09:07, Pavel Machek

Re: [PATCH 00/18] arm64: Unmap the kernel whilst running in userspace (KAISER)

On 23 November 2017 at 17:54, Pavel Machek wrote: > On Thu 2017-11-23 11:38:52, Ard Biesheuvel wrote: >> On 23 November 2017 at 10:46, Pavel Machek wrote: >> > On Thu 2017-11-23 09:23:02, Ard Biesheuvel wrote: >> >> On 23 November 2017 at 09:07, Pavel Machek wrote: >> >> > Hi! >> >> > >> >> >>

Re: [PATCH v2] mmc: sdhci-msm: Optionally wait for signal level changes

On 20 November 2017 at 20:56, Bjorn Andersson wrote: > Not all instances of the SDCC core supports changing signal voltage and > as such will not generate a power interrupt when the software attempts > to change the voltage. This results in probing the eMMC on some

Re: [PATCH V14 04/24] mmc: block: Ensure that debugfs files are removed

On 21 November 2017 at 14:42, Adrian Hunter wrote: > The card is not necessarily being removed, but the debugfs files must be > removed when the driver is removed, otherwise they will continue to exist > after unbinding the card from the driver. e.g. > > # echo

Re: [PATCH V14 01/24] mmc: block: Fix missing blk_put_request()

On 21 November 2017 at 14:42, Adrian Hunter wrote: > Ensure blk_get_request() is paired with blk_put_request(). > > Fixes: 0493f6fe5bde ("mmc: block: Move boot partition locking into a driver > op") > Fixes: 627c3ccfb46a ("mmc: debugfs: Move block debugfs into block

Re: [PATCH v2] mmc: sdhci-msm: Optionally wait for signal level changes

On 20 November 2017 at 20:56, Bjorn Andersson wrote: > Not all instances of the SDCC core supports changing signal voltage and > as such will not generate a power interrupt when the software attempts > to change the voltage. This results in probing the eMMC on some devices > to take over 2

Re: [PATCH V14 04/24] mmc: block: Ensure that debugfs files are removed

On 21 November 2017 at 14:42, Adrian Hunter wrote: > The card is not necessarily being removed, but the debugfs files must be > removed when the driver is removed, otherwise they will continue to exist > after unbinding the card from the driver. e.g. > > # echo "mmc1:0001" >

Re: [PATCH V14 01/24] mmc: block: Fix missing blk_put_request()

On 21 November 2017 at 14:42, Adrian Hunter wrote: > Ensure blk_get_request() is paired with blk_put_request(). > > Fixes: 0493f6fe5bde ("mmc: block: Move boot partition locking into a driver > op") > Fixes: 627c3ccfb46a ("mmc: debugfs: Move block debugfs into block module") > Signed-off-by:

Re: [PATCH V14 02/24] mmc: block: Check return value of blk_get_request()

On 21 November 2017 at 14:42, Adrian Hunter wrote: > blk_get_request() can fail, always check the return value. > > Fixes: 0493f6fe5bde ("mmc: block: Move boot partition locking into a driver > op") > Fixes: 3ecd8cf23f88 ("mmc: block: move multi-ioctl() to use block

Re: [PATCH V14 03/24] mmc: core: Do not leave the block driver in a suspended state

On 21 November 2017 at 14:42, Adrian Hunter wrote: > The block driver must be resumed if the mmc bus fails to suspend the card. > > Signed-off-by: Adrian Hunter Thanks, applied for fixes and added a stable tag (I think v3.19+ is the first one we

Re: [PATCH V14 02/24] mmc: block: Check return value of blk_get_request()

On 21 November 2017 at 14:42, Adrian Hunter wrote: > blk_get_request() can fail, always check the return value. > > Fixes: 0493f6fe5bde ("mmc: block: Move boot partition locking into a driver > op") > Fixes: 3ecd8cf23f88 ("mmc: block: move multi-ioctl() to use block layer") > Fixes: 614f0388f580

Re: [PATCH V14 03/24] mmc: core: Do not leave the block driver in a suspended state

On 21 November 2017 at 14:42, Adrian Hunter wrote: > The block driver must be resumed if the mmc bus fails to suspend the card. > > Signed-off-by: Adrian Hunter Thanks, applied for fixes and added a stable tag (I think v3.19+ is the first one we can pick, else some other manual back porting is

Re: [PATCH 00/11] net: ethernet: ti: cpsw/ale clean up and optimization

From: Grygorii Strashko Date: Wed, 22 Nov 2017 15:25:46 -0600 > This is set of non critical clean ups and optimizations for TI > CPSW and ALE drivers. The net-next tree is closed, please resubmit this when the net-next tree opens back up. Thank you.

Re: [PATCH 00/11] net: ethernet: ti: cpsw/ale clean up and optimization

From: Grygorii Strashko Date: Wed, 22 Nov 2017 15:25:46 -0600 > This is set of non critical clean ups and optimizations for TI > CPSW and ALE drivers. The net-next tree is closed, please resubmit this when the net-next tree opens back up. Thank you.

Re: Stack switching plan of attack (Re: [PATCH v2 00/18] Entry stack switching)

On Thu, Nov 23, 2017 at 07:50:59AM -0800, Andy Lutomirski wrote: > 1. There needs to be a way to turn it off to get the performance hit > under control. I'm leaning toward a boot-time switch, and we can turn > it into a runtime switch later on. Thoughts? Yes, we need a runtime switch off for

Re: [PATCH net v2] net: thunderx: Fix TCP/UDP checksum offload for IPv6 pkts

On Thu, 2017-11-23 at 17:41 +0300, Aleksey Makarov wrote: > From: Sunil Goutham > > Don't offload IP header checksum to NIC. > > This fixes a previous patch which enabled checksum offloading > for both IPv4 and IPv6 packets.  So L3 checksum offload was > getting enabled for

Re: Stack switching plan of attack (Re: [PATCH v2 00/18] Entry stack switching)

On Thu, Nov 23, 2017 at 07:50:59AM -0800, Andy Lutomirski wrote: > 1. There needs to be a way to turn it off to get the performance hit > under control. I'm leaning toward a boot-time switch, and we can turn > it into a runtime switch later on. Thoughts? Yes, we need a runtime switch off for

Re: [PATCH net v2] net: thunderx: Fix TCP/UDP checksum offload for IPv6 pkts

On Thu, 2017-11-23 at 17:41 +0300, Aleksey Makarov wrote: > From: Sunil Goutham > > Don't offload IP header checksum to NIC. > > This fixes a previous patch which enabled checksum offloading > for both IPv4 and IPv6 packets.  So L3 checksum offload was > getting enabled for IPv6 pkts.  And HW

Re: pull-request: wireless-drivers 2017-11-22

From: Kalle Valo Date: Wed, 22 Nov 2017 17:27:22 +0200 > here's the first pull request to net tree for 4.15. Please let me know > if there are any problems. Pulled, thanks Kalle!

Re: pull-request: wireless-drivers 2017-11-22

From: Kalle Valo Date: Wed, 22 Nov 2017 17:27:22 +0200 > here's the first pull request to net tree for 4.15. Please let me know > if there are any problems. Pulled, thanks Kalle!

Re: [PATCH 00/18] arm64: Unmap the kernel whilst running in userspace (KAISER)

On Thu 2017-11-23 11:38:52, Ard Biesheuvel wrote: > On 23 November 2017 at 10:46, Pavel Machek wrote: > > On Thu 2017-11-23 09:23:02, Ard Biesheuvel wrote: > >> On 23 November 2017 at 09:07, Pavel Machek wrote: > >> > Hi! > >> > > >> >> > On 22 Nov 2017, at 23:37,

Re: [PATCH 00/18] arm64: Unmap the kernel whilst running in userspace (KAISER)

On Thu 2017-11-23 11:38:52, Ard Biesheuvel wrote: > On 23 November 2017 at 10:46, Pavel Machek wrote: > > On Thu 2017-11-23 09:23:02, Ard Biesheuvel wrote: > >> On 23 November 2017 at 09:07, Pavel Machek wrote: > >> > Hi! > >> > > >> >> > On 22 Nov 2017, at 23:37, Pavel Machek wrote: > >> >> >

Re: [PATCH] perf buildid-cache: Document for Node.js USDT

Em Fri, Nov 24, 2017 at 01:05:46AM +0900, Hansuk Hong escreveu: > Add a tip for Node.js USDT(User-Level Statically > Defined Tracing) probes in tips.txt Thanks, applid. - Arnaldo > Cc: Jiri Olsa > Cc: Namhyung Kim > > Signed-off-by: Hansuk Hong

Re: [PATCH] perf buildid-cache: Document for Node.js USDT

Em Fri, Nov 24, 2017 at 01:05:46AM +0900, Hansuk Hong escreveu: > Add a tip for Node.js USDT(User-Level Statically > Defined Tracing) probes in tips.txt Thanks, applid. - Arnaldo > Cc: Jiri Olsa > Cc: Namhyung Kim > > Signed-off-by: Hansuk Hong > --- > tools/perf/Documentation/tips.txt |

Re: kernel BUG at crypto/asymmetric_keys/public_key.c:80

On 11/23/2017 06:24 AM, Johannes Berg wrote: > On Wed, 2017-11-22 at 15:07 -0800, Florian Fainelli wrote: >> On 11/22/2017 10:42 AM, Johannes Berg wrote: >>> On Wed, 2017-11-22 at 19:29 +0100, Arend van Spriel wrote: + Johannes >>> BUG_ON(!sig->digest);

Re: kernel BUG at crypto/asymmetric_keys/public_key.c:80

On 11/23/2017 06:24 AM, Johannes Berg wrote: > On Wed, 2017-11-22 at 15:07 -0800, Florian Fainelli wrote: >> On 11/22/2017 10:42 AM, Johannes Berg wrote: >>> On Wed, 2017-11-22 at 19:29 +0100, Arend van Spriel wrote: + Johannes >>> BUG_ON(!sig->digest);

Re: Add fine grained sampled metrics for perf script

Em Thu, Nov 23, 2017 at 08:47:42AM +0100, Jiri Olsa escreveu: > On Fri, Nov 17, 2017 at 01:42:57PM -0800, Andi Kleen wrote: > > SNIP > > > TopDown: > > > > Note TopDown requires disabling SMT if you have it enabled (e.g. by > > offlining > > the extra CPUs), because SMT would require sampling

Re: Add fine grained sampled metrics for perf script

Em Thu, Nov 23, 2017 at 08:47:42AM +0100, Jiri Olsa escreveu: > On Fri, Nov 17, 2017 at 01:42:57PM -0800, Andi Kleen wrote: > > SNIP > > > TopDown: > > > > Note TopDown requires disabling SMT if you have it enabled (e.g. by > > offlining > > the extra CPUs), because SMT would require sampling

[PATCH 2/2] ASoC: da7213: Improve a size determination in da7213_i2c_probe()

From: Markus Elfring Date: Thu, 23 Nov 2017 18:15:30 +0100 Replace the specification of a data structure by a pointer dereference as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style

[PATCH 2/2] ASoC: da7213: Improve a size determination in da7213_i2c_probe()

From: Markus Elfring Date: Thu, 23 Nov 2017 18:15:30 +0100 Replace the specification of a data structure by a pointer dereference as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style convention. This issue was

[PATCH 1/2] ASoC: da7213: Delete an error message for a failed memory allocation in da7213_fw_to_pdata()

From: Markus Elfring Date: Thu, 23 Nov 2017 17:56:54 +0100 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

[PATCH 1/2] ASoC: da7213: Delete an error message for a failed memory allocation in da7213_fw_to_pdata()

From: Markus Elfring Date: Thu, 23 Nov 2017 17:56:54 +0100 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring --- sound/soc/codecs/da7213.c | 4 +--- 1 file changed, 1 insertion(+), 3

[PATCH 0/2] ASoC: da7213: Adjustments for two function implementations

From: Markus Elfring Date: Thu, 23 Nov 2017 18:28:38 +0100 Two update suggestions were taken into account from static source code analysis. Markus Elfring (2): Delete an error message for a failed memory allocation in da7213_fw_to_pdata() Improve a size

[PATCH 0/2] ASoC: da7213: Adjustments for two function implementations

From: Markus Elfring Date: Thu, 23 Nov 2017 18:28:38 +0100 Two update suggestions were taken into account from static source code analysis. Markus Elfring (2): Delete an error message for a failed memory allocation in da7213_fw_to_pdata() Improve a size determination in da7213_i2c_probe()

[PATCH] arm64: allwinner: a64: Enable AXP803 for Orangepi Win

Enable AXP803 PMIC and regulators for Orangepi Win. Signed-off-by: Jagan Teki --- .../boot/dts/allwinner/sun50i-a64-orangepi-win.dts | 125 +++-- 1 file changed, 117 insertions(+), 8 deletions(-) diff --git

[PATCH] arm64: allwinner: a64: Enable AXP803 for Orangepi Win

Enable AXP803 PMIC and regulators for Orangepi Win. Signed-off-by: Jagan Teki --- .../boot/dts/allwinner/sun50i-a64-orangepi-win.dts | 125 +++-- 1 file changed, 117 insertions(+), 8 deletions(-) diff --git a/arch/arm64/boot/dts/allwinner/sun50i-a64-orangepi-win.dts

Re: [PATCH RFC 1/2] sched: Minimize the idle cpu selection race window.

On Thu, 2017-11-23 at 11:00 -0500, Josef Bacik wrote: > > And on this thanksgiving I'm thankful for Mike, and his entertaining early > morning emails. Read it again tomorrow. -Mike

Re: [PATCH RFC 1/2] sched: Minimize the idle cpu selection race window.

On Thu, 2017-11-23 at 11:00 -0500, Josef Bacik wrote: > > And on this thanksgiving I'm thankful for Mike, and his entertaining early > morning emails. Read it again tomorrow. -Mike

Re: [PATCH v2 0/5] Memory hotplug support for arm64 - complete patchset v2

On Thu 23 Nov 2017, 17:02, Michal Hocko wrote: Hi Michal, > I will try to have a look but I do not expect to understand any of arm64 > specific changes so I will focus on the generic code but it would help a > _lot_ if the cover letter provided some overview of what has been done > from a higher

Re: [PATCH v2 0/5] Memory hotplug support for arm64 - complete patchset v2

On Thu 23 Nov 2017, 17:02, Michal Hocko wrote: Hi Michal, > I will try to have a look but I do not expect to understand any of arm64 > specific changes so I will focus on the generic code but it would help a > _lot_ if the cover letter provided some overview of what has been done > from a higher

Re: [PATCH] bnxt_en: Fix an error handling path in 'bnxt_get_module_eeprom()'

From: Christophe JAILLET Date: Tue, 21 Nov 2017 20:46:49 +0100 > Error code returned by 'bnxt_read_sfp_module_eeprom_info()' is handled a > few lines above when reading the A0 portion of the EEPROM. > The same should be done when reading the A2 portion of the

Re: [PATCH] bnxt_en: Fix an error handling path in 'bnxt_get_module_eeprom()'

From: Christophe JAILLET Date: Tue, 21 Nov 2017 20:46:49 +0100 > Error code returned by 'bnxt_read_sfp_module_eeprom_info()' is handled a > few lines above when reading the A0 portion of the EEPROM. > The same should be done when reading the A2 portion of the EEPROM. > > In order to correctly

Re: [PATCH] ASoC: amd: added error checks in dma driver

On Thu, Nov 23, 2017 at 08:59:43AM -0800, Guenter Roeck wrote: > On Thu, Nov 23, 2017 at 8:30 AM, Vijendar Mukunda > wrote: > > added error checks in acp dma driver > > Signed-off-by: Vijendar Mukunda > > Signed-off-by: Akshu Agrawal

Re: [PATCH] ASoC: amd: added error checks in dma driver

On Thu, Nov 23, 2017 at 08:59:43AM -0800, Guenter Roeck wrote: > On Thu, Nov 23, 2017 at 8:30 AM, Vijendar Mukunda > wrote: > > added error checks in acp dma driver > > Signed-off-by: Vijendar Mukunda > > Signed-off-by: Akshu Agrawal > > Signed-off-by: Guenter Roeck > This is inappropriate.

[PATCH] ARC: Reverse logic of enabled dual-issue detection

As per PRM bit #0 ("D") in EXEC_CTRL enables dual-issue if set to 0, otherwise if set to 1 all instructions are executed one at a time, i.e. dual-issue is disabled. Signed-off-by: Alexey Brodkin --- arch/arc/kernel/setup.c | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH] ARC: Reverse logic of enabled dual-issue detection

As per PRM bit #0 ("D") in EXEC_CTRL enables dual-issue if set to 0, otherwise if set to 1 all instructions are executed one at a time, i.e. dual-issue is disabled. Signed-off-by: Alexey Brodkin --- arch/arc/kernel/setup.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [PATCH RT] fix IPI balancing for 4.14-rt

On 2017-11-21 10:24:36 [-0500], Steven Rostedt wrote: > On Tue, 21 Nov 2017 09:14:25 -0600 > Clark Williams wrote: > > > I was testing 4.14-rt1 on a large system (cores == 96) and saw that > > we were getting into an rt balancing storm, so I tried applying Steven's > > patch

Re: [PATCH RT] fix IPI balancing for 4.14-rt

On 2017-11-21 10:24:36 [-0500], Steven Rostedt wrote: > On Tue, 21 Nov 2017 09:14:25 -0600 > Clark Williams wrote: > > > I was testing 4.14-rt1 on a large system (cores == 96) and saw that > > we were getting into an rt balancing storm, so I tried applying Steven's > > patch (not upstream yet):

[PATCH v1] bloat-o-meter: Don't fail with division by 0

Under some circumstances it's possible to get a divider 0 which crashes the script. Traceback (most recent call last): File "linux/scripts/bloat-o-meter", line 98, in print_result("Function", "tTdDbBrR", 2) File "linux/scripts/bloat-o-meter", line 87, in print_result (otot, ntot,

[PATCH v6 02/17] mfd: madera: Add DT bindings for Cirrus Logic Madera codecs

Specification of the bindings for the parent MFD driver component of the Cirrus Logic Madera codec drivers. Note that although the interrupt controller and GPIO are child drivers their required bindings are trivial, mandatory, and exist within the parent MFD node so are documented here.

[PATCH v6 11/17] pinctrl: madera: Add driver for Cirrus Logic Madera codecs

These codecs have a variable number of I/O lines each of which is individually selectable to a wide range of possible functions. The functionality is slightly different from the traditional muxed GPIO since most of the functions can be mapped to any pin (and even the same function to multiple

[PATCH v1] bloat-o-meter: Don't fail with division by 0

Under some circumstances it's possible to get a divider 0 which crashes the script. Traceback (most recent call last): File "linux/scripts/bloat-o-meter", line 98, in print_result("Function", "tTdDbBrR", 2) File "linux/scripts/bloat-o-meter", line 87, in print_result (otot, ntot,

[PATCH v6 02/17] mfd: madera: Add DT bindings for Cirrus Logic Madera codecs

Specification of the bindings for the parent MFD driver component of the Cirrus Logic Madera codec drivers. Note that although the interrupt controller and GPIO are child drivers their required bindings are trivial, mandatory, and exist within the parent MFD node so are documented here.

[PATCH v6 11/17] pinctrl: madera: Add driver for Cirrus Logic Madera codecs

These codecs have a variable number of I/O lines each of which is individually selectable to a wide range of possible functions. The functionality is slightly different from the traditional muxed GPIO since most of the functions can be mapped to any pin (and even the same function to multiple

[PATCH v6 12/17] gpio: madera: Support Cirrus Logic Madera class codecs

This adds support for the GPIOs on Cirrus Logic Madera class codecs. Any pins not used for special functions (see the pinctrl driver) can be used as general single-bit input or output lines. The number of available GPIOs varies between codecs. Signed-off-by: Nariman Poushin

[PATCH v6 12/17] gpio: madera: Support Cirrus Logic Madera class codecs

This adds support for the GPIOs on Cirrus Logic Madera class codecs. Any pins not used for special functions (see the pinctrl driver) can be used as general single-bit input or output lines. The number of available GPIOs varies between codecs. Signed-off-by: Nariman Poushin Signed-off-by:

<    1   2   3   4   5   6   7   8   9   10   >