Re: [PATCH v2 0/1] add (un)patch callbacks

On Tue, 8 Aug 2017, Joe Lawrence wrote: > Hi folks, > > This is v2 of the livepatch (un)patch hook/notifier/callback/etc code. > > The documentation is still a little rough, but I wanted to post up the > code for feedback before getting too far in revising it. > > This implements the pre and

Re: [PATCH v2] nvme: Fix nvme reset command timeout handling

Looks good, Reviewed-by: Sagi Grimberg p.s. we'll need also to update the configure timestamp configuration.

[PATCH v2] irq_work: improve the flag definitions

IRQ_WORK_FLAGS is defined simply to 3UL. This is confusing as it says nothing about its purpose. Define IRQ_WORK_FLAGS as a bitwise OR of IRQ_WORK_PENDING and IRQ_WORK_BUSY. While we're at it: use the BIT() macro for all flags. Signed-off-by: Bartosz Golaszewski --- v1 -> v2: -

Re: [PATCH v5 3/3] drm/rockchip: Add support for Rockchip Soc LVDS

Am 15.08.2017 um 05:49 schrieb Sandy Huang: > This adds support for Rockchip soc lvds found on rk3288 > Based on the patches from Mark yao and Heiko Stuebner > > Signed-off-by: Sandy Huang > Signed-off-by: Mark Yao > Signed-off-by: Heiko Stuebner

[PATCH v3 7/9] soc: mediatek: pwrap: add MediaTek MT6380 as one slave of pwrap

From: Sean Wang Add MediaTek MT6380 regulator becoming one of PMIC wrapper slave and also add extra new regmap_config of 32-bit mode for MT6380 since old regmap_config of 16-bit mode can't be fit into the need. Signed-off-by: Chenglin Xu

Re: [PATCH v8 1/3] perf: cavium: Support memory controller PMU counters

On Tue, Aug 08, 2017 at 02:25:10PM +0100, Will Deacon wrote: > On Fri, Jul 28, 2017 at 04:12:33PM -0700, Greg KH wrote: > > On Thu, Jul 27, 2017 at 03:15:15PM +0200, Borislav Petkov wrote: > > > On Thu, Jul 27, 2017 at 11:08:56AM +0200, Jan Glauber wrote: > > > > OK. As fixing the firmware will

Re: drm/mtrr: possible deadlock

On Tue, Aug 15, 2017 at 11:20 AM, Dou Liyang wrote: > Hi Dmitry, > > At 08/15/2017 03:18 PM, Dmitry Vyukov wrote: >> >> Hello, >> >> I am getting the following deadlock report while booting linux-next on >> 91dfed74eabcdae9378131546c446442c29bf769 in qemu. Config is

Re: [PATCH] netfilter: fix indent on in statements

Hello! On 8/15/2017 9:50 AM, Colin King wrote: From: Colin Ian King The returns on some if statements are not indented correctly, s/in/if/ in the subject? add in the missing tab. Signed-off-by: Colin Ian King [...] MBR, Sergei

Re: [PATCH v4 1/6] Documentation: perf: hisi: Documentation for HiSilicon SoC PMU driver

Hi, On Tue, Jul 25, 2017 at 08:10:37PM +0800, Shaokun Zhang wrote: > This patch adds documentation for the uncore PMUs on HiSilicon SoC. > > Reviewed-by: Jonathan Cameron > Signed-off-by: Shaokun Zhang > Signed-off-by: Anurup M

Re: [PATCH] netfilter: fix indent on in statements

On 15/08/17 10:45, Sergei Shtylyov wrote: > Hello! > > On 8/15/2017 9:50 AM, Colin King wrote: > >> From: Colin Ian King >> >> The returns on some if statements are not indented correctly, > >s/in/if/ in the subject? Doh, fix resent. > >> add in the missing

[PATCH][V2] netfilter: fix indent on if statements

From: Colin Ian King The returns on some if statements are not indented correctly, add in the missing tab. Signed-off-by: Colin Ian King --- net/bridge/netfilter/ebt_ip.c | 4 ++-- net/bridge/netfilter/ebt_ip6.c | 2 +- 2 files changed, 3

[patch v3 2/3] drivers: jtag: Add Aspeed SoC 24xx and 25xx families JTAG master driver

Driver adds support of Aspeed 2500/2400 series SOC JTAG master controller. Driver implements the following jtag ops: - freq_get; - freq_set; - status_get; - idle; - xfer; It has been tested on Mellanox system with BMC equipped with Aspeed 2520 SoC for programming CPLD devices. Signed-off-by:

Re: [PATCH 2/3] GHES: Move memory initialisation to ghes_probe()

Hi Boris, Borislav Petkov writes: > On Tue, Aug 01, 2017 at 02:36:07PM +0100, Punit Agrawal wrote: >> During the driver init, the ghes driver initialises some data structures > > Let's stick to "GHES" in capital letters everywhere. > >> which are only used if a GHES platform

Re: [PATCH 2/2] of: Restrict DMA configuration

On 14/08/17 21:08, Rob Herring wrote: > +linuxppc-dev > > On Fri, Aug 11, 2017 at 11:29 AM, Robin Murphy wrote: >> Moving DMA configuration to happen later at driver probe time had the >> unnoticed side-effect that we now perform DMA configuration for *every* >> device

Re: [PATCH 2/3] GHES: Move memory initialisation to ghes_probe()

On Tue, Aug 15, 2017 at 11:10:05AM +0100, Punit Agrawal wrote: > In the absence of any GHES entries these are wasted. I know. This whole APEI init code would need a proper cleanup, like acpi_pci_root_init() calls acpi_hest_init() and it shouldn't have to communicate through a variable with GHES

Re: [PATCH 0/2] Separate NUMA statistics from zone statistics

On Tue, 15 Aug 2017 16:45:34 +0800 Kemi Wang wrote: > Each page allocation updates a set of per-zone statistics with a call to > zone_statistics(). As discussed in 2017 MM submit, these are a substantial ^^ should be "summit"

[RFT 09/13] s390: ctcm: constify ccw_device_id

ccw_device_id are not supposed to change at runtime. All functions working with ccw_device_id provided by work with const ccw_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/s390/net/ctcm_main.c | 2 +- 1 file changed, 1

[RFT 03/13] s390: dasd_fba: constify ccw_device_id

ccw_device_id are not supposed to change at runtime. All functions working with ccw_device_id provided by work with const ccw_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/s390/block/dasd_fba.c | 2 +- 1 file changed, 1

[RFT 12/13] s390: zfcp: constify ccw_device_id

ccw_device_id are not supposed to change at runtime. All functions working with ccw_device_id provided by work with const ccw_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/s390/scsi/zfcp_ccw.c | 2 +- 1 file changed, 1

[RFT 13/13] s390: virtio: constify ccw_device_id

ccw_device_id are not supposed to change at runtime. All functions working with ccw_device_id provided by work with const ccw_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/s390/virtio/virtio_ccw.c | 2 +- 1 file changed, 1

[RFT 06/13] s390: tape_34xx: constify ccw_device_id

ccw_device_id are not supposed to change at runtime. All functions working with ccw_device_id provided by work with const ccw_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/s390/char/tape_34xx.c | 2 +- 1 file changed, 1

Re: [PATCH 4.12 00/65] 4.12.8-stable review

On 08/14/2017 06:18 PM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 4.12.8 release. There are 65 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 v2] acpi: apei: fix the wrongly iterate generic error status block

The revision 0x300 generic error data entry is different from the old version, but currently iterating through the GHES estatus blocks does not take into account this difference. This will lead to failure to get the right data entry if GHES has revision 0x300 error data entry. Update the GHES

special handle of scripts/kconfig/zconf.tab.o

Masahiro-san, I have a question about make *config. In scripts/kconfig/Makefile, there is following statement: $(obj)/zconf.tab.o: $(obj)/zconf.lex.c $(obj)/zconf.hash.c and the $(obj)/zconf.{tab,hash,lex}.c match the rule in Makefile.lib: $(obj)/%: $(src)/%_shipped $(call cmd,shipped)

Re: [PATCH v4 4/6] perf: hisi: Add support for HiSilicon SoC HHA PMU driver

On Tue, Jul 25, 2017 at 08:10:40PM +0800, Shaokun Zhang wrote: > +/* HHA register definition */ > +#define HHA_INT_MASK 0x0804 > +#define HHA_INT_STATUS 0x0808 > +#define HHA_INT_CLEAR0x080C > +#define HHA_PERF_CTRL0x1E00 > +#define

Re: [PATCH 14/14] arm64: add VMAP_STACK overflow detection

On Mon, Aug 07, 2017 at 07:36:05PM +0100, Mark Rutland wrote: > diff --git a/arch/arm64/kernel/entry.S b/arch/arm64/kernel/entry.S > index e5aa866..44a27c3 100644 > --- a/arch/arm64/kernel/entry.S > +++ b/arch/arm64/kernel/entry.S > @@ -72,6 +72,37 @@ > .macro kernel_ventrylabel >

[PATCH v5 2/3] usb: phy: Add USB charger support

This patch introduces the usb charger support based on usb phy that makes an enhancement to a power driver. The basic conception of the usb charger is that, when one usb charger is added or removed by reporting from the extcon device state change, the usb charger will report to power user to set

[tip:x86/urgent] x86/mtrr: Prevent CPU hotplug lock recursion

Commit-ID: 84393817db09bb436e934f8f8cc981cbca9ea4dc Gitweb: http://git.kernel.org/tip/84393817db09bb436e934f8f8cc981cbca9ea4dc Author: Thomas Gleixner AuthorDate: Tue, 15 Aug 2017 13:03:47 +0200 Committer: Thomas Gleixner CommitDate: Tue, 15 Aug

Re: [PATCH v4 0/3] Introduce USB charger support in USB phy

Hi Felipe, On 15 August 2017 at 17:53, Felipe Balbi wrote: > > Hi, > > Baolin Wang writes: >>> Currently the Linux kernel does not provide any standard integration of this >>> feature that integrates the USB subsystem with the system power regulation

Re: [PATCH 14/14] arm64: add VMAP_STACK overflow detection

On Tue, Aug 15, 2017 at 12:10:32PM +0100, Catalin Marinas wrote: > On Mon, Aug 07, 2017 at 07:36:05PM +0100, Mark Rutland wrote: > > diff --git a/arch/arm64/kernel/entry.S b/arch/arm64/kernel/entry.S > > index e5aa866..44a27c3 100644 > > --- a/arch/arm64/kernel/entry.S > > +++

[PATCH 2/3] [media] davinci: constify platform_device_id

platform_device_id are not supposed to change at runtime. All functions working with platform_device_id provided by work with const platform_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/media/platform/davinci/vpbe_osd.c

[PATCH 3/3] [media] omap3isp: constify platform_device_id

platform_device_id are not supposed to change at runtime. All functions working with platform_device_id provided by work with const platform_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/media/platform/omap3isp/isp.c | 2

Re: [RFT 00/13] constify s390 ccw_device_id

On Tue, Aug 15, 2017 at 04:05:31PM +0530, Arvind Yadav wrote: > ccw_device_id are not supposed to change at runtime. All functions > working with ccw_device_id provided by work with > const ccw_device_id. So mark ccw_device_id member of struct ccw driver > as const. And change all driver

pull-request: wireless-drivers 2017-08-15

Hi Dave, more fixes to net tree for 4.13. More info in the signed tag below, please let me know if there are any problems. Kalle The following changes since commit 5f5d03143de5e0c593da4ab18fc6393c2815e108: brcmfmac: fix memleak due to calling brcmf_sdiod_sgtable_alloc() twice (2017-07-27

Re: [PATCH 2/3] [media] rc: constify usb_device_id

On Sun, Aug 13, 2017 at 02:24:44PM +0530, Arvind Yadav wrote: > usb_device_id are not supposed to change at runtime. All functions > working with usb_device_id provided by work with > const usb_device_id. So mark the non-const structs as const. > > Signed-off-by: Arvind Yadav

Re: [PATCH] f2fs: let fill_super handle roll-forward errors

On 2017/8/15 11:22, Jaegeuk Kim wrote: > On 08/15, Chao Yu wrote: >> Hi Jaegeuk, >> >> On 2017/8/11 8:42, Jaegeuk Kim wrote: >>> If we set CP_ERROR_FLAG in roll-forward error, f2fs is no longer to proceed >>> any IOs due to f2fs_cp_error(). But, for example, if some stale data is >>> involved >>>

Re: [PATCH v3 2/9] dt-bindings: regulator: Add document for MediaTek MT6380 regulator

On Tue, Aug 15, 2017 at 05:09:14PM +0800, sean.w...@mediatek.com wrote: > From: Sean Wang > > add dt-binding document for MediaTek MT6380 PMIC Please use subject lines reflecting the style for the subsystem. signature.asc Description: PGP signature

Re: [PATCH] usb: gadget: udc: udc_stop before gadget unbind

Hi, thanks for reviewing. On 2017-08-15 12:03, Felipe Balbi wrote: Hi, Danilo Krummrich writes: udc_stop needs to be called before gadget driver unbind. Otherwise it might happen that udc drivers still call into the gadget driver (e.g. to reset gadget after

Re: [PATCH net-next] bpf/verifier: track liveness for pruning

On 08/14/2017 07:55 PM, Edward Cree wrote: State of a register doesn't matter if it wasn't read in reaching an exit; a write screens off all reads downstream of it from all explored_states upstream of it. This allows us to prune many more branches; here are some processed insn counts for

Re: [PATCH] ASoC: mediatek: Correct the interrupt property

On Tue, Aug 15, 2017 at 04:07:02PM +0800, Ryder Lee wrote: > This patch update interrupt property since we only use ASYS IRQ > in the driver, and this may confuse people. > - interrupts = , > - ; > + interrupts = ; What harm does having the extra

[PATCH 1/5] net/9p: Delete an error message for a failed memory allocation in five functions

From: Markus Elfring Date: Tue, 15 Aug 2017 08:25:41 +0200 Omit an extra message for a memory allocation failure in these functions. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

[PATCH 4/5] net/9p: Adjust a jump target in p9_client_attach()

From: Markus Elfring Date: Tue, 15 Aug 2017 11:17:23 +0200 Adjust jump labels so that the function implementation becomes smaller. Delete an extra variable assignment and a check (at the end of this function). Signed-off-by: Markus Elfring

Re: [PATCH] usb: gadget: udc: udc_stop before gadget unbind

Hi, Danilo Krummrich writes: > thanks for reviewing. np :-) > On 2017-08-15 12:03, Felipe Balbi wrote: >> Hi, >> >> Danilo Krummrich writes: >>> udc_stop needs to be called before gadget driver unbind. Otherwise it >>> might

Re: [PATCH 3/3] ALSA: firewire-motu: constify snd_rawmidi_ops structures

On Tue, 15 Aug 2017 10:09:54 +0200, Julia Lawall wrote: > > These snd_rawmidi_ops structures are only passed as the third > argument of snd_rawmidi_set_ops. This argument is const, so the > snd_rawmidi_ops structures can be const too. > > Done with the help of Coccinelle. > > Signed-off-by:

[PATCH] tty: n_gsm: Add compat_ioctl

To use this driver with 32 bit userspace applications on 64 bit kernels a compat_ioctl is needed. Signed-off-by: Lars Poeschel --- drivers/tty/n_gsm.c | 11 +++ 1 file changed, 11 insertions(+) diff --git a/drivers/tty/n_gsm.c b/drivers/tty/n_gsm.c index

Re: [v5 2/4] mm, oom: cgroup-aware OOM killer

On Mon, Aug 14, 2017 at 03:42:54PM -0700, David Rientjes wrote: > On Mon, 14 Aug 2017, Roman Gushchin wrote: > > + > > +static long oom_evaluate_memcg(struct mem_cgroup *memcg, > > + const nodemask_t *nodemask) > > +{ > > + struct css_task_iter it; > > + struct

Re: [RFC][PATCH 2/2] selftests: timers: freq-step: Fix build warning

On Mon, Aug 14, 2017 at 02:01:36PM -0700, John Stultz wrote: > Fixes the following build warning: > freq-step.c: In function ‘main’: > freq-step.c:271:1: warning: control reaches end of non-void function > [-Wreturn-type] > @@ -268,4 +268,6 @@ int main(int argc, char **argv) >

RE: [PATCH] Coccinelle: add atomic_as_refcounter script

> On Mon, 14 Aug 2017, Elena Reshetova wrote: > > > atomic_as_refcounter.cocci script allows detecting > > cases when refcount_t type and API should be used > > instead of atomic_t. > > > > Signed-off-by: Elena Reshetova > > --- > >

[PATCH v1] mtd: plat-ram: use release_mem_region instead of release_resource

Use api pair of request_mem_region and release_mem_region instead of release_resource. Found by Linux Driver Verification project (linuxtesting. Signed-off-by: Anton Vasilyev --- v1: Fix commit based on Boris Brezillon review --- drivers/mtd/maps/plat-ram.c | 4 ++-- 1 file

Re: [PATCH v4 2/3] mm: introduce MAP_VALIDATE a mechanism for adding new mmap flags

On Mon 14-08-17 23:12:16, Dan Williams wrote: > The mmap syscall suffers from the ABI anti-pattern of not validating > unknown flags. However, proposals like MAP_SYNC and MAP_DIRECT need a > mechanism to define new behavior that is known to fail on older kernels > without the feature. Use the fact

Re: [PATCH 0/2] mm, oom: fix oom_reaper fallouts

On Mon 07-08-17 13:38:37, Michal Hocko wrote: > Hi, > there are two issues this patch series attempts to fix. First one is > something that has been broken since MMF_UNSTABLE flag introduction > and I guess we should backport it stable trees (patch 1). The other > issue has been brought up by

Re: [PATCH 2/3] GHES: Move memory initialisation to ghes_probe()

[ thanks for dropping the bad email! ] Borislav Petkov writes: > On Tue, Aug 15, 2017 at 11:10:05AM +0100, Punit Agrawal wrote: >> In the absence of any GHES entries these are wasted. > > I know. This whole APEI init code would need a proper cleanup, like > acpi_pci_root_init()

[RFT 01/13] s390: ccwdev: constify ccw_device_id

ccw_device_id are not supposed to change at runtime. AlL functions working with ccw_device_id provided by work with const ccw_device_id. So mark ccw_device_id as const. Signed-off-by: Arvind Yadav --- arch/s390/include/asm/ccwdev.h | 2 +- 1 file changed, 1

[RFT 00/13] constify s390 ccw_device_id

ccw_device_id are not supposed to change at runtime. All functions working with ccw_device_id provided by work with const ccw_device_id. So mark ccw_device_id member of struct ccw driver as const. And change all driver relatively. Arvind Yadav (13): [RFT 01/13] s390: ccwdev: constify

[RFT 11/13] s390: qeth: constify ccw_device_id

ccw_device_id are not supposed to change at runtime. All functions working with ccw_device_id provided by work with const ccw_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/s390/net/qeth_core_main.c | 2 +- 1 file changed,

[RFT 07/13] s390: tape_3590: constify ccw_device_id

ccw_device_id are not supposed to change at runtime. All functions working with ccw_device_id provided by work with const ccw_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/s390/char/tape_3590.c | 2 +- 1 file changed, 1

[RFT 08/13] s390: vmur: constify ccw_device_id

ccw_device_id are not supposed to change at runtime. All functions working with ccw_device_id provided by work with const ccw_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/s390/char/vmur.c | 2 +- 1 file changed, 1

[RFT 10/13] s390: lcs: constify ccw_device_id

ccw_device_id are not supposed to change at runtime. All functions working with ccw_device_id provided by work with const ccw_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/s390/net/lcs.c | 2 +- 1 file changed, 1

[RFT 04/13] s390: con3215: constify ccw_device_id

ccw_device_id are not supposed to change at runtime. All functions working with ccw_device_id provided by work with const ccw_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/s390/char/con3215.c | 2 +- 1 file changed, 1

[RFT 05/13] s390: raw3270: constify ccw_device_id

ccw_device_id are not supposed to change at runtime. All functions working with ccw_device_id provided by work with const ccw_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/s390/char/raw3270.c | 2 +- 1 file changed, 1

Re: [PATCH 3.18 00/16] 3.18.66-stable review

On 08/14/2017 06:18 PM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 3.18.66 release. There are 16 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.9 00/41] 4.9.44-stable review

On 08/14/2017 06:18 PM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 4.9.44 release. There are 41 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: early x86 unseeded randomness

On Tue, 15 Aug 2017, Ingo Molnar wrote: > * Willy Tarreau wrote: > > > Nowadays we could use similar methods using RDTSC providing more accurate > > counting. This doesn't provide a lot of entropy of course, given that a > > 2 GHz machine will at most count 31 bits there. But I tend

Re: [PATCH 2/3] GHES: Move memory initialisation to ghes_probe()

On Tue, Aug 15, 2017 at 11:31:57AM +0100, Punit Agrawal wrote: > I'd seen the link between acpi_pci_root_init() and acpi_hest_init() but > didn't want to open another can of worms... :) > > $SUBJECT was my attempt (small) at improving the situation but I guess I > didn't go far enough. Well, one

Re: [RFT 13/13] s390: virtio: constify ccw_device_id

On Tue, 15 Aug 2017 16:05:44 +0530 Arvind Yadav wrote: > ccw_device_id are not supposed to change at runtime. All functions > working with ccw_device_id provided by work with > const ccw_device_id. So mark the non-const structs as const. > > Signed-off-by: Arvind

[PATCH 0/3] constify media platform_device_id

platform_device_id are not supposed to change at runtime. All functions working with platform_device_id provided by work with const platform_device_id. So mark the non-const structs as const. Arvind Yadav (3): [PATCH 1/3] [media] coda: constify platform_device_id [PATCH 2/3] [media] davinci:

[PATCH 1/3] [media] coda: constify platform_device_id

platform_device_id are not supposed to change at runtime. All functions working with platform_device_id provided by work with const platform_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/media/platform/coda/coda-common.c |

[PATCH] signal: don't remove SIGNAL_UNKILLABLE for traced tasks.

When forcing a signal, SIGNAL_UNKILLABLE is removed to prevent recursive faults, but this is undesirable when tracing. For example, debugging an init process (whether global or namespace), hitting a breakpoint and SIGTRAP will force SIGTRAP and then remove SIGNAL_UNKILLABLE. Everything continues

[PATCH 11/12] irqchip/mips-gic: Report that effective affinity is a single target

The MIPS GIC driver only targets a single CPU at a time, even if the notional affinity is wider. Let's inform the core code about this. Signed-off-by: Marc Zyngier --- drivers/irqchip/Kconfig| 1 + drivers/irqchip/irq-mips-gic.c | 2 ++ 2 files changed, 3

[PATCH 12/12] irqchip/xtensa-mx: Report that effective affinity is a single target

The xtensa-mx driver only targets a single CPU at a time, even if the notional affinity is wider. Let's inform the core code about this. Signed-off-by: Marc Zyngier --- drivers/irqchip/Kconfig | 1 + drivers/irqchip/irq-xtensa-mx.c | 6 +- 2 files changed, 6

[PATCH 00/12] genirq/irqchip: Effective affinity fixups

4.13 contains a number of updates to the core IRQ code to deal with things like the effective affinity. This series attempts to fix a number of small things that are now breaking: 1) The core code assumes that CONFIG_GENERIC_IRQ_EFFECTIVE_AFF_MASK being defined implies that *all* interrupts

[PATCH 02/12] genirq/proc: Use the the accessor to report the effective affinity

If CONFIG_GENERIC_IRQ_EFFECTIVE_AFF_MASK is defined, but that the interrupt is not single target, the effective affinity reported in /proc/irq/x/effective_affinity will be empty, which is not the truth. Instead, use the accessor to report the affinity, which will pick the right mask.

[PATCH 05/12] irqchip/gic-v3-its: Report that effective affinity is a single target

The GICv3 ITS driver only targets a single CPU at a time, even if the notional affinity is wider. Let's inform the core code about this. Signed-off-by: Marc Zyngier --- drivers/irqchip/irq-gic-v3-its.c | 7 ++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git

[PATCH 01/12] genirq: Restrict effective affinity to single-target interrupts

Just because CONFIG_GENERIC_IRQ_EFFECTIVE_AFF_MASK is selected doesn't mean that all the interrupts are using the effective affinity mask. For a number of them, this mask is likely to be empty. In order to deal with this, let's restrict the use of the effective affinity mask to these interrupts

Re: [PATCH 1/3] [media] coda: constify platform_device_id

On Tue, 2017-08-15 at 16:53 +0530, Arvind Yadav wrote: > platform_device_id are not supposed to change at runtime. All > functions > working with platform_device_id provided by > work with const platform_device_id. So mark the non-const structs as > const. > > Signed-off-by: Arvind Yadav

[PATCH 03/12] irqchip/gic: Report that effective affinity is a single target

The GIC driver only targets a single CPU at a time, even if the notional affinity is wider. Let's inform the core code about this. Signed-off-by: Marc Zyngier --- drivers/irqchip/Kconfig | 1 + drivers/irqchip/irq-gic.c | 3 +++ 2 files changed, 4 insertions(+) diff

[PATCH 0/5] net/9p: Fine-tuning for some function implementations

From: Markus Elfring Date: Tue, 15 Aug 2017 13:43:21 +0200 Some update suggestions were taken into account from static source code analysis. Markus Elfring (5): Delete an error message for a failed memory allocation in five functions Improve 19 size

[PATCH 2/5] net/9p: Improve 19 size determinations

From: Markus Elfring Date: Tue, 15 Aug 2017 09:36:20 +0200 Replace the specification of data structures by variable references as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style

Re: [RFC][PATCHv5 06/13] printk: register PM notifier

On Tuesday, August 15, 2017 4:56:18 AM CEST Sergey Senozhatsky wrote: > It's not always possible/safe to wake_up() printk kernel > thread. For example, late suspend/early resume may printk() > while timekeeping is not initialized yet, so calling into the > scheduler may result in recursive

Re: [PATCH v4] f2fs: introduce discard_granularity sysfs entry

On 2017/8/15 11:45, Jaegeuk Kim wrote: > On 08/07, Chao Yu wrote: >> From: Chao Yu >> >> Commit d618ebaf0aa8 ("f2fs: enable small discard by default") enables >> f2fs to issue 4K size discard in real-time discard mode. However, issuing >> smaller discard may cost more lifetime

Re: [RFC][PATCHv5 07/13] printk: register syscore notifier

On Tuesday, August 15, 2017 4:56:19 AM CEST Sergey Senozhatsky wrote: > We need to switch to emergency printk mode in kernel_kexec(). One > kernel_kexec() branch calls kernel_restart_prepare(), which updates > `system_state', however, the other one, when user requested to > ->preserve_context,

[PATCH 5/5] net/9p: Delete an unnecessary variable initialisation in p9_client_attach()

From: Markus Elfring Date: Tue, 15 Aug 2017 11:25:31 +0200 The local variable "err" will eventually be set to an appropriate value a bit later. Thus omit the explicit initialisation at the beginning. Signed-off-by: Markus Elfring

Re: [PATCH v2] f2fs-tools: fix the usage message of overprovision option

On 2017/8/15 15:41, Yunlong Song wrote: > The usage message shows a wrong message for ovp option, so fix it. > > Signed-off-by: Yunlong Song > --- > mkfs/f2fs_format_main.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/mkfs/f2fs_format_main.c

Re: [PATCH 3/3] ACPI / scan: Enable GPEs before scanning the namespace

On Tuesday, August 15, 2017 4:12:24 AM CEST Zheng, Lv wrote: > Hi, Rafael > > > From: linux-acpi-ow...@vger.kernel.org > > [mailto:linux-acpi-ow...@vger.kernel.org] On Behalf Of Rafael J. > > Wysocki > > Subject: [PATCH 3/3] ACPI / scan: Enable GPEs before scanning the namespace > > > > From:

Re: [PATCH 07/10] cpufreq: dt: Add support for some new Allwinner SoCs

On Tuesday, August 15, 2017 7:42:19 AM CEST Chen-Yu Tsai wrote: > On Mon, Jul 24, 2017 at 7:46 PM, Rafael J. Wysocki wrote: > > On Monday, July 24, 2017 02:23:49 PM Viresh Kumar wrote: > >> On 23-07-17, 18:27, Icenowy Zheng wrote: > >> > Some new Allwinner SoCs get supported

Re: [PATCH v4 2/6] perf: hisi: Add support for HiSilicon SoC uncore PMU driver

Hi, On Tue, Jul 25, 2017 at 08:10:38PM +0800, Shaokun Zhang wrote: > +/* Read Super CPU cluster and CPU cluster ID from MPIDR_EL1 */ > +void hisi_read_sccl_and_ccl_id(u32 *sccl_id, u32 *ccl_id) > +{ > + u64 mpidr; > + > + mpidr = read_cpuid_mpidr(); > + if (mpidr & MPIDR_MT_BITMASK) {

Re: [PATCH] ACPI/APEI: Add BERT data driver

Hi Tony, "Luck, Tony" writes: > From: Tony Luck > > The ACPI Boot Error Record Table provides a method for platform > firmware to give information to the operating system about error > that occurred prior to boot (of particular interest are problems >

Re: WARNING: CPU: 3 PID: 2952 at drivers/base/firmware_class.c:1225 _request_firmware+0x329/0x890

Hi Richard, > My new Thinkpad T470p regularly triggers this warning. > Seems to happy only after resuming from suspend. > > [147242.220708] PM: Finishing wakeup. > [147242.220711] OOM killer enabled. > [147242.220711] Restarting tasks ... > [147242.221908] Bluetooth: hci0: Bootloader revision

[RFT 02/13] s390: dasd_eckd: constify ccw_device_id

ccw_device_id are not supposed to change at runtime. All functions working with ccw_device_id provided by work with const ccw_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- drivers/s390/block/dasd_eckd.c | 2 +- 1 file changed, 1

Re: [PATCH v4 3/6] perf: hisi: Add support for HiSilicon SoC L3C PMU driver

On Tue, Jul 25, 2017 at 08:10:39PM +0800, Shaokun Zhang wrote: > This patch adds support for L3C PMU driver in HiSilicon SoC chip, Each > L3C has own control, counter and interrupt registers and is an separate > PMU. For each L3C PMU, it has 8-programable counters and supports 0x60 > events, event

RE: [PATCH] New Chapter on CodingStyle .

From: Jonathan Corbet > Sent: 12 August 2017 15:55 ... > > + Chapter 20: Put values on initialisers without exception > > + > > +When declaring variables on functions must put values: > > Thanks for sending a patch for the kernel's documentation. > Unfortunately, I can't accept this

Re: [PATCH 4.4 00/23] 4.4.83-stable review

On 08/14/2017 06:18 PM, Greg Kroah-Hartman wrote: This is the start of the stable review cycle for the 4.4.83 release. There are 23 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 v3 pci] PCI/MSI: pci-xgene-msi: Enable MSI support in ACPI boot for X-Gene v1

On Mon, Aug 14, 2017 at 04:17:35PM -0700, Khuong Dinh wrote: [...] > >> +static acpi_status acpi_create_msi_device(acpi_handle handle, u32 Level, > >> + void *context, void **retval) > >> +{ > >> + struct acpi_device *device = NULL; > >> + int type =

Re: [PATCH 05/11] ASoC: omap: make snd_soc_platform_driver const

 Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki On 2017-08-14 14:38, Bhumika Goyal wrote: > Make this const as it is only passed as the 2nd argument to the > function devm_snd_soc_register_platform, which is of

RE: [PATCH 0/5] cramfs refresh for embedded usage

On Tuesday, August 15, 2017 1, Nicolas Pitre wrote: > I was able to reproduce. The following patch on top should partially fix > it. I'm trying to figure out how to split a vma and link it properly in > the case the vma cannot be mapped entirely. In the mean time shared libs > won't be XIP. > >

[PATCH v5 0/3] Introduce USB charger support in USB phy

Currently the Linux kernel does not provide any standard integration of this feature that integrates the USB subsystem with the system power regulation provided by PMICs meaning that either vendors must add this in their kernels or USB gadget devices based on Linux (such as mobile phones) may not

[PATCH v5 3/3] power: wm831x_power: Support USB charger current limit management

Integrate with the newly added USB charger interface to limit the current we draw from the USB input based on the input device configuration identified by the USB stack, allowing us to charge more quickly from high current inputs without drawing more current than specified from others.

[PATCH v5 1/3] include: uapi: usb: Introduce USB charger type and state definition

Introducing USB charger type and state definition can help to support USB charging which will be added in USB phy core. Signed-off-by: Baolin Wang --- include/uapi/linux/usb/charger.h | 31 +++ 1 file changed, 31 insertions(+) create mode

Re: [PATCH] powerpc: store the intended structure

Julia Lawall writes: > Normally the values in the resource field and the argument to ARRAY_SIZE > in the num_resources are the same. In this case, the value in the reousrce > field is the same as the one in the previous platform_device structure, and > appears to be a

Re: [patch v3 1/3] drivers: jtag: Add JTAG core driver

On Tue, Aug 15, 2017 at 12:00 PM, Oleksandr Shamray wrote: > + case JTAG_IOCXFER: > + if (copy_from_user(, varg, sizeof(struct jtag_xfer))) > + return -EFAULT; > + > + if (xfer.length >= JTAG_MAX_XFER_DATA_LEN) > +

<    3   4   5   6   7   8   9   10   11   12   >