Re: [PATCH] lib/zstd: use div_u64() to let it build on 32-bit

On Tue, Jun 27, 2017 at 05:27:51AM +, Nick Terrell wrote: > Adam, I’ve applied the same patch in my tree. I’ll send out the update [1] > once it's reviewed, since I also reduced the stack usage of functions > using over 1 KB of stack space. > > I have userland tests set up mocking the linux

Re: [PATCH] futex: avoid undefined behaviour when shift exponent is negative

Hi, Thomas Thank you for clarification. On 2017/6/29 6:13, Thomas Gleixner wrote: > On Wed, 28 Jun 2017, zhong jiang wrote: >> On 2017/6/22 0:40, Ingo Molnar wrote: >>> * zhong jiang wrote: >>> when shift expoment is negative, left shift alway zero. therefore, we

Re: [PATCH] char: ipmi: constify bmc_dev_attr_group and bmc_device_type

Applied, thanks. -corey On 06/23/2017 12:13 AM, Arvind Yadav wrote: File size before: text data bss dec hex filename 25678 1024 92 2679468aa drivers/char/ipmi/ipmi_msghandler.o File size After adding 'const': text data bss

Re: [PATCH] fs: ext4: inode->i_generation not assigned 0.

On Jun 28, 2017, at 4:06 PM, Kyungchan Koh wrote: > > In fs/ext4/super.c, the function ext4_nfs_get_inode takes as input > "generation" that can be used to specify the generation of the inode to > be returned. When 0 is given as input, then inodes of any generation can > be

Re: [PATCH v7] drm/sun4i: hdmi: Implement I2C adapter for A10s DDC bus

Hi, On Wed, Jun 28, 2017 at 6:52 PM, Jonathan Liu wrote: > The documentation for drm_do_get_edid in drivers/gpu/drm/drm_edid.c states: > "As in the general case the DDC bus is accessible by the kernel at the I2C > level, drivers must make all reasonable efforts to expose it as

[PATCH v7 3/4] KVM: async_pf: Force a nested vmexit if the injected #PF is async_pf

From: Wanpeng Li Add an nested_apf field to vcpu->arch.exception to identify an async page fault, and constructs the expected vm-exit information fields. Force a nested VM exit from nested_vmx_check_exception() if the injected #PF is async page fault. Cc: Paolo

[PATCH v7 4/4] KVM: async_pf: Let host know whether the guest support delivery async_pf as #PF vmexit

From: Wanpeng Li Adds another flag bit (bit 2) to MSR_KVM_ASYNC_PF_EN. If bit 2 is 1, async page faults are delivered to L1 as #PF vmexits; if bit 2 is 0, kvm_can_do_async_pf returns 0 if in guest mode. Cc: Paolo Bonzini Cc: Radim Krčmář

[PATCH v7 2/4] KVM: async_pf: Add L1 guest async_pf #PF vmexit handler

From: Wanpeng Li This patch adds the L1 guest async page fault #PF vmexit handler, such #PF is converted into vmexit from L2 to L1 on #PF which is then handled by L1 similar to ordinary async page fault. Cc: Paolo Bonzini Cc: Radim Krčmář

[PATCH] btrfs: Keep one more workspace around

> Is there a version I should be testing? Not yet, I'm working on v2 of the patch set, which will be ready soon. > I got a bunch of those: > [10170.448783] kworker/u8:6: page allocation stalls for 60720ms, order:0, > mode:0x14000c2(GFP_KERNEL|__GFP_HIGHMEM), nodemask=(null) > [10170.448819]

[PATCH v7 0/4] KVM: async_pf: Fix async pf exception injection

INFO: task gnome-terminal-:1734 blocked for more than 120 seconds. Not tainted 4.12.0-rc4+ #8 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. gnome-terminal- D0 1734 1015 0x Call Trace: __schedule+0x3cd/0xb30 schedule+0x40/0x90

[PATCH v7 1/4] KVM: x86: Simple kvm_x86_ops->queue_exception parameter

From: Wanpeng Li This patch removes all arguments except the first in kvm_x86_ops->queue_exception since they can extract the arguments from vcpu->arch.exception themselves, do the same in nested_{vmx,svm}_check_exception. Cc: Paolo Bonzini Cc:

linux-next: manual merge of the kvm-arm tree with the iommu tree

Hi all, Today's linux-next merge of the kvm-arm tree got a conflict in: Documentation/arm64/silicon-errata.txt between commits: e5b829de053d ("iommu/arm-smmu-v3: Add workaround for Cavium ThunderX2 erratum #74") f935448acf46 ("iommu/arm-smmu-v3: Add workaround for Cavium ThunderX2

[PATCH 10/16] switchtec_ntb: initialize hardware for doorbells and messages

This patch sets up some hardware registers and creates interrupt service routines for the doorbells and messages. There are 64 doorbells in the switch that are shared between all partitions. The upper 4 doorbells are also shared with the messages and are there for not used. Thus, this code

[PATCH 11/16] switchtec_ntb: add skeleton ntb driver

This patch simply adds a skeleton NTB driver which will be filled out in subsequent patches. Signed-off-by: Logan Gunthorpe Reviewed-by: Stephen Bates Reviewed-by: Kurt Schwemmer --- drivers/ntb/hw/mscc/switchtec_ntb.c |

Re: [PATCH v7] drm/sun4i: hdmi: Implement I2C adapter for A10s DDC bus

Hi Chen-Yu, On 29 June 2017 at 12:47, Chen-Yu Tsai wrote: > Hi, > > On Wed, Jun 28, 2017 at 6:52 PM, Jonathan Liu wrote: >> The documentation for drm_do_get_edid in drivers/gpu/drm/drm_edid.c states: >> "As in the general case the DDC bus is accessible by the

Re: [PATCH] fs: ext4: inode->i_generation not assigned 0.

On 6/28/17, 7:32 PM, "Andreas Dilger" wrote: On Jun 28, 2017, at 4:06 PM, Kyungchan Koh wrote: > > In fs/ext4/super.c, the function ext4_nfs_get_inode takes as input > "generation" that can be used to specify the generation of the inode to

linux-next: manual merge of the usb tree with the uuid tree

Hi Greg, Today's linux-next merge of the usb tree got a conflict in: drivers/usb/misc/ucsi.c between commit: 94116f8126de ("ACPI: Switch to use generic guid_t in acpi_evaluate_dsm()") from the uuid tree and commit: 8243edf44152 ("usb: typec: ucsi: Add ACPI driver") from the usb tree.

[PATCH v5 2/6] g_NCR5380: End PDMA transfer correctly on target disconnection

From: Ondrej Zary When an IRQ arrives during PDMA transfer, pread() and pwrite() return without waiting for the 53C80 registers to be ready and this ends up messing up the chip state. This was observed with SONY CDU-55S which is slow enough to disconnect during

[PATCH v5 6/6] g_NCR5380: Use unambiguous terminology for PDMA send and receive

The word "read" may be used to mean "DMA read operation" or "SCSI READ command", though a READ command implies writing to memory. Signed-off-by: Finn Thain --- drivers/scsi/g_NCR5380.c | 14 +++--- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git

[linux-next][PATCH] usb: dwc3: core: Call dwc3_core_get_phy() before initializing phys

commit f54edb539c116 ("usb: dwc3: core: initialize ULPI before trying to get the PHY") moved call to dwc3_core_get_phy() from dwc3_probe() to dwc3_core_init() after dwc3_core_soft_reset(). But dwc3_core_soft_reset() calls phy_init(), therefore dwc3_core_get_phy() needs to be called before

Re: [PATCH] ib_isert: prevent NULL pointer dereference in isert_login_recv_done()

Just tested this patch, I wasn't able to reproduce the NULL pointer dereference or any other bugs, so this fix seems safe enough to me. Tested-by: Andrea Righi Can you test just the one liner fix below? @@ -1452,7 +1452,7 @@ isert_login_recv_done(struct ib_cq

[PATCH] net: ibm: ibmveth: constify dev_pm_ops structures.

dev_pm_ops are not supposed to change at runtime. All functions working with dev_pm_ops provided by work with const dev_pm_ops. So mark the non-const structs as const. File size before: textdata bss dec hex filename 154261256 0 16682412a

[PATCH] net: freescale: gianfar : constify dev_pm_ops structures.

dev_pm_ops are not supposed to change at runtime. All functions working with dev_pm_ops provided by work with const dev_pm_ops. So mark the non-const structs as const. File size before: textdata bss dec hex filename 19057 392 0 194494bf9

Re: [PATCH] thermal/intel_powerclamp: add const to thermal_cooling_device_ops structure

On Thu, Jun 29, 2017 at 11:02 AM, Zhang Rui wrote: > On Thu, 2017-06-29 at 10:41 +0530, Bhumika Goyal wrote: >> On Thu, Jun 29, 2017 at 8:30 AM, Zhang Rui >> wrote: >> > >> > On Wed, 2017-06-21 at 12:39 +0530, Bhumika Goyal wrote: >> > > >> > > Declare

Re: [PATCH] futex: avoid undefined behaviour when shift exponent is negative

On 2017/6/29 12:29, h...@zytor.com wrote: > On June 28, 2017 7:12:04 PM PDT, zhong jiang wrote: >> On 2017/6/29 5:43, h...@zytor.com wrote: >>> On June 27, 2017 9:35:10 PM PDT, zhong jiang >> wrote: Hi, Ingo Thank you for the comment.

[PATCH 15/15] mm/migrate: allow migrate_vma() to alloc new page on empty entry v3

This allow caller of migrate_vma() to allocate new page for empty CPU page table entry. It only support anoymous memory and it won't allow new page to be instance if userfaultfd is armed. This is useful to device driver that want to migrate a range of virtual address and would rather allocate new

[PATCH 09/15] mm/hmm/devmem: device memory hotplug using ZONE_DEVICE v6

This introduce a simple struct and associated helpers for device driver to use when hotpluging un-addressable device memory as ZONE_DEVICE. It will find a unuse physical address range and trigger memory hotplug for it which allocates and initialize struct page for the device memory. Changed since

[PATCH 14/15] mm/migrate: support un-addressable ZONE_DEVICE page in migration v2

Allow to unmap and restore special swap entry of un-addressable ZONE_DEVICE memory. Changed since v1: - s/device unaddressable/device private/ Signed-off-by: Jérôme Glisse Cc: Kirill A. Shutemov --- include/linux/migrate.h | 10 +++-

[PATCH 13/15] mm/migrate: migrate_vma() unmap page from vma while collecting pages

Common case for migration of virtual address range is page are map only once inside the vma in which migration is taking place. Because we already walk the CPU page table for that range we can directly do the unmap there and setup special migration swap entry. Signed-off-by: Jérôme Glisse

Re: [PATCH v4 1/6] clk: sunxi-ng: div: Add support for fixed post-divider

On Tue, Jun 27, 2017 at 11:46:07AM +0200, Maxime Ripard wrote: > Hi! > > On Sun, Jun 25, 2017 at 11:45:42PM +0300, Priit Laes wrote: > > SATA clock on sun4i/sun7i is of type (parent) / M / 6 where > > 6 is fixed post-divider. > > > > Signed-off-by: Priit Laes > > --- > >

[PATCH 08/15] mm/ZONE_DEVICE: special case put_page() for device private pages v2

A ZONE_DEVICE page that reach a refcount of 1 is free ie no longer have any user. For device private pages this is important to catch and thus we need to special case put_page() for this. Changed since v1: - use static key to disable special code path in put_page() by default - uninline

[PATCH 05/15] mm/hmm/mirror: device page fault handler

This handle page fault on behalf of device driver, unlike handle_mm_fault() it does not trigger migration back to system memory for device memory. Signed-off-by: Jérôme Glisse Signed-off-by: Evgeny Baskakov Signed-off-by: John Hubbard

[PATCH 10/15] mm/hmm/devmem: dummy HMM device for ZONE_DEVICE memory v3

This introduce a dummy HMM device class so device driver can use it to create hmm_device for the sole purpose of registering device memory. It is useful to device driver that want to manage multiple physical device memory under same struct device umbrella. Changed since v2: - use

[PATCH 11/15] mm/migrate: new migrate mode MIGRATE_SYNC_NO_COPY

Introduce a new migration mode that allow to offload the copy to a device DMA engine. This changes the workflow of migration and not all address_space migratepage callback can support this. So it needs to be tested in those cases. This is intended to be use by migrate_vma() which itself is use

Re: [lttng-dev] Clarification on SCHED_FIFO support

On Wed, 28 Jun 2017 18:22:38 + (UTC) Mathieu Desnoyers wrote: > - On Jun 27, 2017, at 7:36 PM, Sukanya Sekar sse...@andrew.cmu.edu wrote: > > > Greetings! > > We are exploring the LTTng Kernel Tracer (version 2.9) on Ubuntu 16.04. We > > are > >

Re: [PATCH v3 net-next 03/12] nfp: change bpf verifier hooks to match new verifier data structures

On 06/27/2017 02:57 PM, Edward Cree wrote: Signed-off-by: Edward Cree Acked-by: Daniel Borkmann

Re: [PATCH 1/2] irqchip: RISC-V Local Interrupt Controller Driver

On Mon, 26 Jun 2017, Palmer Dabbelt wrote: > +DEFINE_PER_CPU(struct riscv_irq_data, riscv_irq_data); > +DEFINE_PER_CPU(atomic_long_t, riscv_early_sie); > + > +static void riscv_software_interrupt(void) > +{ > +#ifdef CONFIG_SMP > + irqreturn_t ret; > + > + ret = handle_ipi(); > + if

[tip:x86/platform] x86/PCI: Remove duplicate defines

Commit-ID: 9304d1621e6019c63497f8a4aad09d003916dbe9 Gitweb: http://git.kernel.org/tip/9304d1621e6019c63497f8a4aad09d003916dbe9 Author: Thomas Gleixner AuthorDate: Thu, 16 Mar 2017 22:50:03 +0100 Committer: Thomas Gleixner CommitDate: Wed, 28 Jun

[tip:irq/core] blk-mq: Include all present CPUs in the default queue mapping

Commit-ID: 5f042e7cbd9ebd3580077dcdc21f35e68c2adf5f Gitweb: http://git.kernel.org/tip/5f042e7cbd9ebd3580077dcdc21f35e68c2adf5f Author: Christoph Hellwig AuthorDate: Mon, 26 Jun 2017 12:20:56 +0200 Committer: Thomas Gleixner CommitDate: Wed, 28 Jun 2017

[tip:irq/core] blk-mq: Create hctx for each present CPU

Commit-ID: 4b855ad37194f7bdbb200ce7a1c7051fecb56a08 Gitweb: http://git.kernel.org/tip/4b855ad37194f7bdbb200ce7a1c7051fecb56a08 Author: Christoph Hellwig AuthorDate: Mon, 26 Jun 2017 12:20:57 +0200 Committer: Thomas Gleixner CommitDate: Wed, 28 Jun 2017

[PATCH v5 2/2]Input: Add driver for Goodix GTx5 series touchscreen

This driver is for Goodix GTx5 series touchscreen controllers such as GT8589, GT7589. This driver designed with hierarchical structure, for that can be modified to support subsequent controllers easily. Some zones of the touchscreen can be set to buttons(according to the hardware). That is why it

[PATCH] mm: convert three more cases to kvmalloc

Hi I'm submitting this for the next merge window. Mikulas From: Mikulas Patocka The patch a7c3e901 ("mm: introduce kv[mz]alloc helpers") converted a lot of kernel code to kvmalloc. This patch converts three more forgotten cases. Signed-off-by: Mikulas Patocka

[PATCH v4 2/2] fs/dcache.c: fix spin lockup issue on nlru->lock

__list_lru_walk_one() acquires nlru spin lock (nlru->lock) for longer duration if there are more number of items in the lru list. As per the current code, it can hold the spin lock for upto maximum UINT_MAX entries at a time. So if there are more number of items in the lru list, then "BUG:

[PATCH v4 1/2] mm/list_lru.c: fix list_lru_count_node() to be race free

list_lru_count_node() iterates over all memcgs to get the total number of entries on the node but it can race with memcg_drain_all_list_lrus(), which migrates the entries from a dead cgroup to another. This can return incorrect number of entries from list_lru_count_node(). Fix this by keeping

Re: [PATCH] [net-next] net/mlx5e: select CONFIG_MLXFW

On Wed, Jun 28, 2017 at 11:10 PM, Arnd Bergmann wrote: > With the introduction of mlx5 firmware flash support, we get a link > error with CONFIG_MLXFW=m and CONFIG_MLX5_CORE=y: > > drivers/net/ethernet/mellanox/mlx5/core/fw.o: In function > `mlx5_firmware_flash': >

Re: [PATCH v3 net-next 03/12] nfp: change bpf verifier hooks to match new verifier data structures

On Tue, 27 Jun 2017 13:57:34 +0100, Edward Cree wrote: > Signed-off-by: Edward Cree Acked-by: Jakub Kicinski Sorry about the delay.

Re: [PATCH v3 2/3] dt-bindings: input: Add R_LRADC support for A83T

2017-06-28 1:31 GMT+08:00 Maxime Ripard : > On Tue, Jun 27, 2017 at 11:18:17PM +0800, Ziping Chen wrote: >> 2017-06-27 1:15 GMT+08:00 Maxime Ripard : >> > Hi, >> > >> > On Sat, Jun 24, 2017 at 10:45:14AM +0800, Ziping Chen wrote:

Re: [PATCH] futex: avoid undefined behaviour when shift exponent is negative

On June 28, 2017 7:12:04 PM PDT, zhong jiang wrote: >On 2017/6/29 5:43, h...@zytor.com wrote: >> On June 27, 2017 9:35:10 PM PDT, zhong jiang >wrote: >>> Hi, Ingo >>> >>> Thank you for the comment. >>> On 2017/6/22 0:40, Ingo Molnar wrote: *

Re: [linux-sunxi] Re: [PATCH v3 2/3] dt-bindings: input: Add R_LRADC support for A83T

2017-06-28 1:36 GMT+08:00 Maxime Ripard : > Hi, > > On Tue, Jun 27, 2017 at 11:29:10PM +0800, icen...@aosc.io wrote: >> Maxime, here's another problem: if we have already a GP LRADC driver, >> how can we tell the kernel to use it as IIO ADC rather than keys? > >

Re: [kernel-sched-cputime] question about probable bug in cputime_adjust()

On 29 June 2017 01:57:19 CEST, "Gustavo A. R. Silva" wrote: --- a/kernel/sched/cputime.c +++ b/kernel/sched/cputime.c @@ -637,9 +637,10 @@ static void cputime_adjust(struct task_cputime >*curr, *= (rtime_i+1 - rtime_i) + utime_i

Re: [PATCH] fs: ext4: inode->i_generation not assigned 0.

[add linux-xfs to cc] On Thu, Jun 29, 2017 at 04:37:14AM +, William Koh wrote: > On 6/28/17, 7:32 PM, "Andreas Dilger" wrote: > > On Jun 28, 2017, at 4:06 PM, Kyungchan Koh wrote: > > > > In fs/ext4/super.c, the function ext4_nfs_get_inode

[PATCH] net: smc91x: constify dev_pm_ops structures.

dev_pm_ops are not supposed to change at runtime. All functions working with dev_pm_ops provided by work with const dev_pm_ops. So mark the non-const structs as const. File size before: textdata bss dec hex filename 18709 401 0 191104aa6

Re: [PATCH v1] xen/input: add multi-touch support

ping On 06/23/2017 09:09 AM, Oleksandr Andrushchenko wrote: From: Oleksandr Andrushchenko Extend xen_kbdfront to provide multi-touch support to unprivileged domains. Signed-off-by: Oleksandr Andrushchenko --- Changes since

Re: [PATCH v4 0/5] Add support for the ARMv8.2 Statistical Profiling Extension

On Wed, 28 Jun 2017 12:26:02 +0100 Mark Rutland wrote: > On Tue, Jun 27, 2017 at 04:07:58PM -0500, Kim Phillips wrote: > > I'm close to finishing the bts version of userspace, and have been > > testing a bit more thoroughly, so now I consistently see the excessive > >

[PATCH] perf tools: Add ARM Statistical Profiling Extensions (SPE) support

'perf record' and 'perf report --dump-raw-trace' supported in this release. Example usage: taskset -c 2 ./perf record -C 2 -c 1024 -e arm_spe_0/ts_enable=1,pa_enable=1/ \ dd if=/dev/zero of=/dev/null count=1 perf report --dump-raw-trace Note that the perf.data file is

RE: linux-next: build failure after merge of the sound-asoc tree

ote: (near initialization for > 'soc_codec_dev_rt5670.set_sysclk') > cc1: some warnings being treated as errors > > Caused by commit > > 6c28ce3c425e ("ASoC: rt5670: move set_sysclk to codec level") > > I have used the sound-asoc tree from next-20170628 for today. S

Re: [PATCH v5 1/2] PCI: mediatek: Add Mediatek PCIe host controller support

On Wed, 2017-06-28 at 14:53 -0500, Bjorn Helgaas wrote: > On Sun, May 21, 2017 at 11:42:24AM +0800, Ryder Lee wrote: > > Add support for the Mediatek PCIe Gen2 controller which can > > be found on MT7623 series SoCs. > > > > Signed-off-by: Ryder Lee > > --- > >

[PATCH] iommu/vt-d: Don't free parent pagetable of the PTE we're adding

When adding a large scatterlist entry that covers more than the L3 superpage size (1GB) but has an alignment such that we must use L2 superpages (2MB) , we give dma_pte_free_level() a range that causes it to free the L3 pagetable we're about to populate. We fix this by telling

[PATCH v2] ext4: have ext4_xattr_set_handle() allocate journal credits

Currently, callers of ext4_xattr_set_handle() are expected to allocate journal credits for setting extended attributes. ext4_xattr_set_credits() helps them figure out necessary credits. ext4_xattr_set_handle() performs a sufficient credits check before starting data updates. This model works fine

[PATCH 00/16]

Changes since the rfc: - Rebased on ntb-next - Switched ntb_part_op to use sleep instead of delay - Dropped a number of useless dbg __func__ prints - Went back to the dynamic instead of the static class - Swapped the notifier block for a simple callback - Modified the new ntb api so that a couple

[PATCH 04/16] switchtec: add link event notifier callback

In order for the switchtec NTB code to handle link change events we create a notifier callback in the switchtec code which gets called whenever an appropriate event interrupt occurs. In order to preserve userspace's ability to follow these events, we compare the event count with a stored copy

[PATCH 02/16] switchtec: export class symbol for use in upper layer driver

We export the class pointer symbol and add an extern define in the switchtec header file. Signed-off-by: Logan Gunthorpe Reviewed-by: Stephen Bates Reviewed-by: Kurt Schwemmer --- drivers/pci/switch/switchtec.c | 4 +++-

[PATCH 01/16] switchtec: move structure definitions into a common header

Create the switchtec.h header in include/linux with hardware defines and the switchtec_dev structure moved directly from switchtec.c. This is a prep patch for created an NTB driver for switchtec. Signed-off-by: Logan Gunthorpe Reviewed-by: Stephen Bates

[PATCH 05/16] ntb: ensure ntb_mw_get_align is only called when the link is up

With switchtec hardware it's impossible to get the alignment parameters for a peer's memory window until the peer's driver has configured it's windows. Strictly speaking, the link doesn't have to be up for this, but the link being up is the only way the client can tell that the otherside has been

[PATCH 12/16] switchtec_ntb: add link management

switchtec_ntb checks for a link by looking at the shared memory window. If the magic number is correct and the otherside indicates their link is enabled then we take the link to be up. Whenever we change our local link status we send a msg to the otherside to check whether it's up and change

[PATCH 07/16] ntb: ntb_test: ensure the link is up before trying to configure the mws

After the link tests, there is a race on one side of the test for the link coming up. It's possible, in some cases, for the test script to write to the peer_trans files before the link has come up. To fix this we simply use the link event file to ensure both sides see the link as up before

[PATCH 15/16] switchtec_ntb: add memory window support

The switchtec hardware has two types of memory windows: LUTs and Direct. The first area in each BAR is for LUT windows and the remaining area is for the direct region. The total number of LUT entries is set by a configuration setting in hardware and they all must be the same size. (This is fixed

Re: [PATCH v3] KVM: LAPIC: Fix lapic timer injection delay

2017-06-28 22:30 GMT+08:00 Paolo Bonzini : > > > On 28/06/2017 16:27, Wanpeng Li wrote: >> 2017-06-28 20:10 GMT+08:00 Paolo Bonzini : >>> >>> >>> On 28/06/2017 03:29, Wanpeng Li wrote: u64 tscdeadline = apic->lapic_timer.tscdeadline; +

Re: A udev rule to serve the change event of ACPI container?

Hi YASUAKI, Thanks for your response. On Wed, Jun 28, 2017 at 03:53:16PM -0400, YASUAKI ISHIMATSU wrote: > > On 06/26/2017 02:26 AM, joeyli wrote: > > Hi all, > > > > If ACPI received ejection request for a ACPI container, kernel > > emits KOBJ_CHANGE uevent when it found online children

[PATCH] aic7xxx: fix firmware build with O=path

Building firmware with O=path was apparently broken in aic7 for ever. Message of the previous commit to the Makefile (from 2008) mentions this unfortunate state of affairs already. Fix this, mostly to make randconfig builds more reliable. Signed-off-by: Jakub Kicinski

Re: [kernel-hardening] [PATCH v5 3/3] x86/refcount: Implement fast refcount overflow protection

Hi Kees, 在 2017/5/31 5:39, Kees Cook 写道: This protection is a modified version of the x86 PAX_REFCOUNT defense from PaX/grsecurity. This speeds up the refcount_t API by duplicating the existing atomic_t implementation with a single instruction added to detect if the refcount has wrapped past

Re: [PATCH 1/2] drm/msm: gpu: don't abuse dma_alloc for non-DMA allocations

On Tue 20 Jun 13:16 PDT 2017, Arnd Bergmann wrote: > In zap_shader_load_mdt(), we pass a pointer to a phys_addr_t > into dmam_alloc_coherent, which the compiler warns about: > > drivers/gpu/drm/msm/adreno/a5xx_gpu.c: In function 'zap_shader_load_mdt': >

Re: linux-next: build warnings after merge of the scsi-mkp tree

Hi James, This has now migrated to the scsi tree. On Wed, 28 Jun 2017 15:55:10 +1000 Stephen Rothwell wrote: > > After merging the scsi-mkp tree, today's linux-next build > (powerpc_ppc64_defconfig) produced these warnings: > > In file included from

Re: [PATCH] acpi: thermal: honor "mode" sysfs file setting

On Thu, 2017-06-29 at 00:14 +0200, Rafael J. Wysocki wrote: > On Thursday, June 22, 2017 02:45:42 PM Enric Balletbo i Serra wrote: > > > > From: Sameer Nanda > > > > Under each thermal zone there is a file called "mode". Writing > > enabled > > or disabled to this file

Re: [PATCH v4 0/5] g_NCR5380: PDMA fixes and cleanup

On Wed, 28 Jun 2017, Ondrej Zary wrote: > > Now read seems to work on non-DTC chips. Writes continue in PDMA after > disconnect but there's a corruption - one 128 B block missing on > disconnect. > > On DTC, the log is spammed with errors like this: > sd 2:0:1:0: [sdb] tag#0

[PATCH V2 0/4] sched: cpufreq: Allow remote callbacks

Hi, Here is the second version of this series. The first [1] version was sent several months back. With Android UI and benchmarks the latency of cpufreq response to certain scheduling events can become very critical. Currently, callbacks into schedutil are only made from the scheduler if the

[PATCH] module: make the modinfo name const

This can be accomplished by makine blacklisted() also accept const. Signed-off-by: Luis R. Rodriguez --- kernel/module.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/kernel/module.c b/kernel/module.c index 5ebe3ae2519a..7d679f3bb892 100644 ---

Re: [PATCH] module: make the modinfo name const

On Wed, Jun 28, 2017 at 6:32 PM, Luis R. Rodriguez wrote: > This can be accomplished by makine blacklisted() also accept const. Typo "making" > Signed-off-by: Luis R. Rodriguez But otherwise: Acked-by: Kees Cook -Kees > --- >

[PATCH V2 1/2] dmaengine: qcom_hidma: introduce memset support

HIDMA HW supports memset operation in addition to memcpy. Since the memset API is present on the kernel now, bring the memset feature into life. The descriptor format is the same for both memcpy and memset. Type of the descriptor is 4 when memset is requested. The lowest 8 bits of the source DMA

Re: [PATCH 2/2] dmaengine: dmatest: add support for memset test

Hi Andy, On 6/28/2017 4:58 AM, Andy Shevchenko wrote: > On Wed, Jun 28, 2017 at 3:46 AM, Sinan Kaya wrote: >> >> echo dma0chan0 > /sys/module/dmatest/parameters/channel >> echo 2 > /sys/module/dmatest/parameters/dmatest >> echo 2000 >

Re: [PATCH] thermal/intel_powerclamp: add const to thermal_cooling_device_ops structure

On Wed, 2017-06-21 at 12:39 +0530, Bhumika Goyal wrote: > Declare thermal_cooling_device_ops structure as const as it is only > passed > as an argument to the function thermal_cooling_device_register and > this > argument is of type const. So, declare the structure as const. > I checked the

RE: BUG: unable to handle kernel NULL pointer dereference at 0000000000000038 !//RE: kernel BUG at kernel/locking/rtmutex.c:1027

Thanks Julia, I will try it Thanks Feng >-Original Message- >From: Julia Cartwright [mailto:ju...@ni.com] >Sent: Tuesday, June 27, 2017 10:28 PM >To: Feng Feng24 Liu >Cc: Sebastian Andrzej Siewior; Steven Rostedt; Mike Galbraith; >linux-kernel@vger.kernel.org;

Re: [PATCH] dma: fsl_raid: make of_device_ids const.

On Tue, Jun 27, 2017 at 05:38:27PM +0530, Arvind Yadav wrote: > of_device_ids are not supposed to change at runtime. All functions > working with of_device_ids provided by work with const > of_device_ids. So mark the non-const structs as const. Please ensure you use the right subsystem tags for

Re: [RFC 1/5] drivers: Add boot constraints core

On 28-06-17, 08:55, Randy Dunlap wrote: > On 06/28/2017 03:26 AM, Viresh Kumar wrote: > > +config BOOT_CONSTRAINTS > > + bool "Boot constraints for devices" > > + default y > > Why default y? > > As Linus just wrote yesterday: > > No. We've tried. The only sensible default (and that I try

Re: [RFC 4/5] drivers: boot_constraint: Add debugfs support

On 28-06-17, 08:46, Randy Dunlap wrote: > On 06/28/2017 03:26 AM, Viresh Kumar wrote: > > This patch adds debugfs support for boot constraints. This is how it > > looks for a "vmmc-supply" constraint for the MMC device. > > > > Hi, > Does this build OK when DEBUG_FS is not enabled in kernel

Re: [PATCH v6 1/6] pinctrl: qcom: Add ipq8074 pinctrl driver

On Fri 09 Jun 02:41 PDT 2017, Varadarajan Narayanan wrote: > Add initial pinctrl driver to support pin configuration with > pinctrl framework for ipq8074. > > Acked-by: Rob Herring (bindings) > Signed-off-by: Manoharan Vijaya Raghavan > Signed-off-by:

Re: [PATCH v6 5/6] arm64: dts: Add ipq8074 SoC and HK01 board support

On Fri 09 Jun 02:41 PDT 2017, Varadarajan Narayanan wrote: > diff --git a/arch/arm64/boot/dts/qcom/ipq8074-hk01.dts > b/arch/arm64/boot/dts/qcom/ipq8074-hk01.dts [..] > + > + chosen { > + bootargs = "root=/dev/ram0 rw init=/init"; As far as I know you can omit both root= and

Re: [ANNOUNCE] v4.11.7-rt3

On Thu, 2017-06-29 at 04:55 +0200, Mike Galbraith wrote: > > cpus_allowed became cpus_mask.  Anything (crash.. hohum, yet again) > that rummages around in the kernels gizzard will have to adapt. (wrt crash: nope, it doesn't care for a change)

[PATCH V2 3/4] intel_pstate: Ignore scheduler cpufreq callbacks on remote CPUs

From: Steve Muckle In preparation for the scheduler cpufreq callback happening on remote CPUs, check for this case in intel_pstate which currently requires the callback run on the local CPU. Such callbacks are ignored for now. Signed-off-by: Steve Muckle

[PATCH V2 1/4] cpufreq: schedutil: Process remote callback for shared policies

This patch updates the schedutil governor to process cpufreq utilization update hooks called for remote CPUs (i.e. For updates to the runqueue of other non-local CPUs). For now, we only support remote callbacks for CPUs which share their cpufreq policy with the local CPU. It may not be worth

[PATCH V2 2/4] cpufreq: governor: Process remote callback for shared policies

This patch updates the legacy governors (ondemand/conservative) to process cpufreq utilization update hooks to be called for remote CPUs (i.e. For updates to the runqueue of other non-local CPUs). Based on initial work from Steve Muckle. Signed-off-by: Viresh Kumar ---

[PATCH V2 4/4] sched: cpufreq: Enable remote sched cpufreq callbacks

Now that all clients properly support (or ignore) remote scheduler cpufreq callbacks, remove the restriction that such callbacks only be made on the local CPU. Also remove cpufreq_update_this_cpu() as all its users are migrated to use cpufreq_update_util() instead. Based on initial work from

[PATCH] usb: dwc3: pci: constify dev_pm_ops structures.

dev_pm_ops are not supposed to change at runtime. All functions working with dev_pm_ops provided by work with const dev_pm_ops. So mark the non-const structs as const. File size before: textdata bss dec hex filename 2707 456 03163 c5b

Re: [PATCH v6 0/3] Add new PCI_DEV_FLAGS_NO_RELAXED_ORDERING flag

ping On 2017/6/22 20:15, Ding Tianhong wrote: > Some devices have problems with Transaction Layer Packets with the Relaxed > Ordering Attribute set. This patch set adds a new PCIe Device Flag, > PCI_DEV_FLAGS_NO_RELAXED_ORDERING, a set of PCI Quirks to catch some known > devices with Relaxed

Re: [PATCH 2/2] selftests/ftrace: Update multiple kprobes test for powerpc

On Thu, 29 Jun 2017 00:13:24 +0530 "Naveen N. Rao" wrote: > On 2017/06/28 11:16PM, Masami Hiramatsu wrote: > > > > diff --git > > > > a/tools/testing/selftests/ftrace/test.d/kprobe/kprobe_eventname.tc > > > >

Re: [PATCH] fs: ext4: inode->i_generation not assigned 0.

On 6/28/17, 5:48 PM, "Darrick J. Wong" wrote: On Wed, Jun 28, 2017 at 03:06:42PM -0700, Kyungchan Koh wrote: > In fs/ext4/super.c, the function ext4_nfs_get_inode takes as input > "generation" that can be used to specify the generation of the inode to >

Re: [PATCH NET V7 1/2] net: phy: Add phy loopback support in net phy framework

Hi, Andrew On 2017/6/28 21:27, Andrew Lunn wrote: > On Wed, Jun 28, 2017 at 05:13:10PM +0800, Lin Yun Sheng wrote: >> This patch add set_loopback in phy_driver, which is used by MAC >> driver to enable or disable phy loopback. it also add a generic >> genphy_loopback function, which use BMCR

Re: [PATCH v2 11/51] md: raid1: initialize bvec table via bio_add_page()

On 06/28/2017 12:22 AM, Ming Lei wrote: Seems above section is similar as reset_bvec_table introduced in next patch, why there is difference between raid1 and raid10? Maybe add reset_bvec_table into md.c, then call it in raid1 or raid10 is better, just my 2 cents. Hi Guoqing, I think it is

[PATCH V2 2/2] dmaengine: dmatest: add support for memset test

Introducing memset test into dmatest. It allows us to test memset capable HW using the dmatest suite. The new dmatest value is 2 and it is changeable through sysfs. Memset shares the same code path as the other dmatest code. The only difference is that the first value inside the source buffer is

linux-next: build failure after merge of the sound-asoc tree

by commit 6c28ce3c425e ("ASoC: rt5670: move set_sysclk to codec level") I have used the sound-asoc tree from next-20170628 for today. -- Cheers, Stephen Rothwell

  1   2   3   4   5   6   7   8   9   10   >