[PATCH v2 4/4] cgroup: Make debug controller report new controller masks

The newly added cgroup controller masks (subtree_bypass and enable_ss_mask) are now being reported in the debug.masks controller file. Signed-off-by: Waiman Long --- kernel/cgroup/debug.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/kernel/cgroup/debug.c

[PATCH v2 4/4] cgroup: Make debug controller report new controller masks

The newly added cgroup controller masks (subtree_bypass and enable_ss_mask) are now being reported in the debug.masks controller file. Signed-off-by: Waiman Long --- kernel/cgroup/debug.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/kernel/cgroup/debug.c b/kernel/cgroup/debug.c index

[PATCH v2 3/4] cgroup: Allow reenabling of controller in bypass mode

Controllers set to bypass mode in the parent's "cgroup.subtree_control" can now be optionally enabled by writing the controller name with the '+' prefix to "cgroup.controllers". Using the '#' prefix will reset it back to the bypass state. This capability increases the flexibility each controller

[PATCH v2 1/4] cgroup: Child cgroup creation not allowed on invalid domain

When thread mode is used, it is possible that some cgroups may be in an invalid state. Currently users may not be aware that they are invalid until they try to migrate tasks over. This patch disallows child cgroup creation on invalid domain. This adds one more failure point in reminding users that

[PATCH v2 3/4] cgroup: Allow reenabling of controller in bypass mode

Controllers set to bypass mode in the parent's "cgroup.subtree_control" can now be optionally enabled by writing the controller name with the '+' prefix to "cgroup.controllers". Using the '#' prefix will reset it back to the bypass state. This capability increases the flexibility each controller

[PATCH v2 1/4] cgroup: Child cgroup creation not allowed on invalid domain

When thread mode is used, it is possible that some cgroups may be in an invalid state. Currently users may not be aware that they are invalid until they try to migrate tasks over. This patch disallows child cgroup creation on invalid domain. This adds one more failure point in reminding users that

[PATCH Y.A. RESEND] MAINTAINERS: fix alpha. ordering

From: Randy Dunlap Fix major alphabetic errors. No attempt to fix items that all begin with the same word (like ARM, BROADCOM, DRM, EDAC, FREESCALE, INTEL, OMAP, PCI, SAMSUNG, TI, USB, etc.). (diffstat +/- is different by one line because TI KEYSTONE MULTICORE had 2 blank

[PATCH Y.A. RESEND] MAINTAINERS: fix alpha. ordering

From: Randy Dunlap Fix major alphabetic errors. No attempt to fix items that all begin with the same word (like ARM, BROADCOM, DRM, EDAC, FREESCALE, INTEL, OMAP, PCI, SAMSUNG, TI, USB, etc.). (diffstat +/- is different by one line because TI KEYSTONE MULTICORE had 2 blank lines after it.)

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

Hi Abhishek, [auto build test ERROR on mtd/nand/fixes] [also build test ERROR on v4.13-rc1 next-20170721] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Abhishek-Sahu/Add-QCOM-QPIC-NAND-support

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

Hi Abhishek, [auto build test ERROR on mtd/nand/fixes] [also build test ERROR on v4.13-rc1 next-20170721] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Abhishek-Sahu/Add-QCOM-QPIC-NAND-support

[PATCH] [RESEND] mtd: only use __xipram annotation when XIP_KERNEL is set

When XIP_KERNEL is enabled, some functions are defined in the .data ELF section because we require them to be in RAM whenever we communicate with the flash chip. However this causes problems when FTRACE is enabled and gcc emits calls to __gnu_mcount_nc in the function prolog: drivers/built-in.o:

[PATCH] [RESEND] mtd: only use __xipram annotation when XIP_KERNEL is set

When XIP_KERNEL is enabled, some functions are defined in the .data ELF section because we require them to be in RAM whenever we communicate with the flash chip. However this causes problems when FTRACE is enabled and gcc emits calls to __gnu_mcount_nc in the function prolog: drivers/built-in.o:

Re: MAINTAINERS: F: file patterns without matches

On 07/21/2017 12:04 PM, Joe Perches wrote: > On Fri, 2017-07-21 at 10:10 -0700, Randy Dunlap wrote: >> On 07/21/2017 10:02 AM, Joe Perches wrote: >>> There are a number of file patterns in MAINTAINERS that >>> don't have an actual matching file in the kernel tree. >>> >>> Some of those are due to

Re: MAINTAINERS: F: file patterns without matches

On 07/21/2017 12:04 PM, Joe Perches wrote: > On Fri, 2017-07-21 at 10:10 -0700, Randy Dunlap wrote: >> On 07/21/2017 10:02 AM, Joe Perches wrote: >>> There are a number of file patterns in MAINTAINERS that >>> don't have an actual matching file in the kernel tree. >>> >>> Some of those are due to

Re: [PATCH v2] sound: Convert to using %pOF instead of full_name

On Fri, 21 Jul 2017 21:28:34 +0200, Rob Herring wrote: > > Now that we have a custom printf format specifier, convert users of > full_name to use %pOF instead. This is preparation to remove storing > of the full path string for each node. > > Signed-off-by: Rob Herring > Cc:

Re: [PATCH v2] sound: Convert to using %pOF instead of full_name

On Fri, 21 Jul 2017 21:28:34 +0200, Rob Herring wrote: > > Now that we have a custom printf format specifier, convert users of > full_name to use %pOF instead. This is preparation to remove storing > of the full path string for each node. > > Signed-off-by: Rob Herring > Cc: Johannes Berg >

[PATCH] of: provide of_n_{addr,size}_cells wrappers for !CONFIG_OF

The pci-rcar driver is enabled for compile tests, and this has now shown that the driver cannot build without CONFIG_OF, following the inclusion of f8f2fe7355fb "PCI: rcar: Use new OF interrupt mapping when possible": ../drivers/pci/host/pcie-rcar.c: In function 'pci_dma_range_parser_init':

[PATCH] of: provide of_n_{addr,size}_cells wrappers for !CONFIG_OF

The pci-rcar driver is enabled for compile tests, and this has now shown that the driver cannot build without CONFIG_OF, following the inclusion of f8f2fe7355fb "PCI: rcar: Use new OF interrupt mapping when possible": ../drivers/pci/host/pcie-rcar.c: In function 'pci_dma_range_parser_init':

Re: [PATCH V2] pci: quirk: Apply APM ACS quirk to XGene devices

On Thu, Jul 20, 2017 at 3:22 PM, Alex Williamson wrote: > On Wed, 19 Jul 2017 17:46:51 -0700 > Feng Kan wrote: > >> The APM X-Gene PCIe root port does not support ACS at this point. >> However, the hw provides isolation and source validation through >>

Re: [PATCH V2] pci: quirk: Apply APM ACS quirk to XGene devices

On Thu, Jul 20, 2017 at 3:22 PM, Alex Williamson wrote: > On Wed, 19 Jul 2017 17:46:51 -0700 > Feng Kan wrote: > >> The APM X-Gene PCIe root port does not support ACS at this point. >> However, the hw provides isolation and source validation through >> the SMMU. Turn on ACS but disable all the

[PATCH] [RESEND] pcmcia: badge4: avoid unused function warning

The pcmv_setup is only used when the badge4 driver is built-in, but not when it is a loadable module: drivers/pcmcia/sa_badge4.c:153:122: error: 'pcmv_setup' defined but not used [-Werror=unused-function] This adds an #ifdef to avoid the definition of the unused function in the modular

[PATCH] [RESEND] pcmcia: badge4: avoid unused function warning

The pcmv_setup is only used when the badge4 driver is built-in, but not when it is a loadable module: drivers/pcmcia/sa_badge4.c:153:122: error: 'pcmv_setup' defined but not used [-Werror=unused-function] This adds an #ifdef to avoid the definition of the unused function in the modular

[PATCH v2] cpufreq: s5pv210: add missing of_node_put

for_each_compatible_node performs an of_node_get on each iteration, so a return from the loop requires an of_node_put. The semantic patch that fixes this problem is as follows (http://coccinelle.lip6.fr): // @@ local idexpression n; expression e,e1,e2; statement S; iterator i1; iterator name

[PATCH v2] cpufreq: s5pv210: add missing of_node_put

for_each_compatible_node performs an of_node_get on each iteration, so a return from the loop requires an of_node_put. The semantic patch that fixes this problem is as follows (http://coccinelle.lip6.fr): // @@ local idexpression n; expression e,e1,e2; statement S; iterator i1; iterator name

Re: [PATCH v2 3/4] fs/dcache: Enable automatic pruning of negative dentries

On 07/21/2017 03:30 PM, James Bottomley wrote: > On Fri, 2017-07-21 at 09:43 -0400, Waiman Long wrote: >> Having a limit for the number of negative dentries does have an >> undesirable side effect that no new negative dentries will be allowed >> when the limit is reached. This will have

Re: [PATCH v2 3/4] fs/dcache: Enable automatic pruning of negative dentries

On 07/21/2017 03:30 PM, James Bottomley wrote: > On Fri, 2017-07-21 at 09:43 -0400, Waiman Long wrote: >> Having a limit for the number of negative dentries does have an >> undesirable side effect that no new negative dentries will be allowed >> when the limit is reached. This will have

[PATCH] [RESEND] nfs: blocklayout: avoid warnings on 32-bit sector_t

sector_t can be either 32-bit or 64-bit wide, but in the former case, the NFS blocklayout code produces a couple of warnings: blocklayout.c: In function 'bl_read_pagelist': blocklayout.c:225:45: error: large integer implicitly truncated to unsigned type [-Werror=overflow] struct

[PATCH] [RESEND] nfs: blocklayout: avoid warnings on 32-bit sector_t

sector_t can be either 32-bit or 64-bit wide, but in the former case, the NFS blocklayout code produces a couple of warnings: blocklayout.c: In function 'bl_read_pagelist': blocklayout.c:225:45: error: large integer implicitly truncated to unsigned type [-Werror=overflow] struct

Re: [PATCH 5/5] ubi: Allow to use read-only UBI volume with not enough PEBs

Pali, On Fri, Jun 2, 2017 at 5:43 PM, Pali Rohár wrote: > In read-only mode is skipped auto-resize. For pre-build images ready for > auto-resize there can be reserved more PEBs as whole size of pre-build > image. In read-only we do not do any write operation therefore this

Re: [PATCH 5/5] ubi: Allow to use read-only UBI volume with not enough PEBs

Pali, On Fri, Jun 2, 2017 at 5:43 PM, Pali Rohár wrote: > In read-only mode is skipped auto-resize. For pre-build images ready for > auto-resize there can be reserved more PEBs as whole size of pre-build > image. In read-only we do not do any write operation therefore this would > allow to use

[PATCH] f2fs: add ioctl to expose current features

This patch adds an ioctl to provide feature information to user. For exapmle, SQLite can use this ioctl to detect whether f2fs support atomic write or not. Signed-off-by: Jaegeuk Kim --- fs/f2fs/f2fs.h | 2 ++ fs/f2fs/file.c | 13 + 2 files changed, 15

[PATCH] f2fs: add ioctl to expose current features

This patch adds an ioctl to provide feature information to user. For exapmle, SQLite can use this ioctl to detect whether f2fs support atomic write or not. Signed-off-by: Jaegeuk Kim --- fs/f2fs/f2fs.h | 2 ++ fs/f2fs/file.c | 13 + 2 files changed, 15 insertions(+) diff --git

Re: [PATCH] EDAC: remove unnecessary static in edac_fake_inject_write()

On Mon, 17 Jul 2017, Borislav Petkov wrote: > On Tue, Jul 04, 2017 at 04:44:40PM -0500, Gustavo A. R. Silva wrote: > > Remove unnecessary static on local variable _type_. > > Such variable is initialized before being used, > > on every execution path throughout the function. > > The static has

Re: [PATCH] EDAC: remove unnecessary static in edac_fake_inject_write()

On Mon, 17 Jul 2017, Borislav Petkov wrote: > On Tue, Jul 04, 2017 at 04:44:40PM -0500, Gustavo A. R. Silva wrote: > > Remove unnecessary static on local variable _type_. > > Such variable is initialized before being used, > > on every execution path throughout the function. > > The static has

Re: [PATCH] perf tool sort: Use default sort if evlist is empty

On Fri, Jul 21, 2017 at 12:44 AM, Jiri Olsa wrote: > On Thu, Jul 20, 2017 at 10:11:57PM -0700, David Carrillo-Cisneros wrote: >> Fixes bug noted by Jiri in https://lkml.org/lkml/2017/6/13/755 and caused >> by commit d49dadea7862 ("perf tools: Make 'trace' or 'trace_fields' sort

Re: [PATCH] perf tool sort: Use default sort if evlist is empty

On Fri, Jul 21, 2017 at 12:44 AM, Jiri Olsa wrote: > On Thu, Jul 20, 2017 at 10:11:57PM -0700, David Carrillo-Cisneros wrote: >> Fixes bug noted by Jiri in https://lkml.org/lkml/2017/6/13/755 and caused >> by commit d49dadea7862 ("perf tools: Make 'trace' or 'trace_fields' sort >>key default

Re: [PATCH 4/5] mtd: block2mtd: Add support for deleting block2mtd mapping

Pali, On Fri, Jun 2, 2017 at 5:43 PM, Pali Rohár wrote: > This patch allows user to delete block2mtd mapping via parameters file > /sys/module/block2mtd/parameters/block2mtd > > Syntax is "del=device", e.g.: > > $ echo -n del=/dev/loop0 >

Re: [PATCH 4/5] mtd: block2mtd: Add support for deleting block2mtd mapping

Pali, On Fri, Jun 2, 2017 at 5:43 PM, Pali Rohár wrote: > This patch allows user to delete block2mtd mapping via parameters file > /sys/module/block2mtd/parameters/block2mtd > > Syntax is "del=device", e.g.: > > $ echo -n del=/dev/loop0 > /sys/module/block2mtd/parameters/block2mtd As I wrote in

Re: [PATCH 3/5] mtd: block2mtd: Fallback to read-only mode

Pali, On Fri, Jun 2, 2017 at 5:43 PM, Pali Rohár wrote: > Sometimes block device is readonly (e.g. loopbacks). This patch allows > block2mtd to fallback and create read-only MTD_ROM device instead of > fatal failure. > > Signed-off-by: Pali Rohár >

Re: [PATCH 3/5] mtd: block2mtd: Fallback to read-only mode

Pali, On Fri, Jun 2, 2017 at 5:43 PM, Pali Rohár wrote: > Sometimes block device is readonly (e.g. loopbacks). This patch allows > block2mtd to fallback and create read-only MTD_ROM device instead of > fatal failure. > > Signed-off-by: Pali Rohár > --- > drivers/mtd/devices/block2mtd.c | 39

Re: [RFC PATCH 0/9] Introduce housekeeping subsystem

On 7/21/2017 9:21 AM, Frederic Weisbecker wrote: I'm leaving for two weeks so this is food for thoughts in the meantime :) We have a design issue with nohz_full: it drives the isolation features through the *housekeeping*() functions: kthreads, unpinned timers, watchdog, ... But things should

Re: [RFC PATCH 0/9] Introduce housekeeping subsystem

On 7/21/2017 9:21 AM, Frederic Weisbecker wrote: I'm leaving for two weeks so this is food for thoughts in the meantime :) We have a design issue with nohz_full: it drives the isolation features through the *housekeeping*() functions: kthreads, unpinned timers, watchdog, ... But things should

Re: [PATCH 1/5] mtd: block2mtd: Check for valid user supplied erase size

On Fri, Jun 2, 2017 at 5:43 PM, Pali Rohár wrote: > Erase size is limited to 32bit unsigned integer, but value parsed from user > is limited up to size_t C type. > > Signed-off-by: Pali Rohár > --- > drivers/mtd/devices/block2mtd.c |2 +- > 1 file

Re: [PATCH 1/5] mtd: block2mtd: Check for valid user supplied erase size

On Fri, Jun 2, 2017 at 5:43 PM, Pali Rohár wrote: > Erase size is limited to 32bit unsigned integer, but value parsed from user > is limited up to size_t C type. > > Signed-off-by: Pali Rohár > --- > drivers/mtd/devices/block2mtd.c |2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > >

[PATCH v2 4/4] arm64: defconfig: add CONFIG_BRCMSTB_THERMAL

From: Markus Mayer Turn on CONFIG_BRCMSTB_THERMAL as module. Signed-off-by: Markus Mayer --- arch/arm64/configs/defconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig index

[PATCH v2 4/4] arm64: defconfig: add CONFIG_BRCMSTB_THERMAL

From: Markus Mayer Turn on CONFIG_BRCMSTB_THERMAL as module. Signed-off-by: Markus Mayer --- arch/arm64/configs/defconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig index 6c7d147..2449064 100644 ---

[PATCH v2 0/4] thermal: add brcmstb AVS TMON driver

From: Markus Mayer This series adds the brcmstb AVS TMON driver. The driver was originally written by Brian Norris. v1 of this series can be found at https://lkml.org/lkml/2017/6/5/921 Changes since v1: - Fixed wording in binding document - Fixed lincensing to

[PATCH v2 0/4] thermal: add brcmstb AVS TMON driver

From: Markus Mayer This series adds the brcmstb AVS TMON driver. The driver was originally written by Brian Norris. v1 of this series can be found at https://lkml.org/lkml/2017/6/5/921 Changes since v1: - Fixed wording in binding document - Fixed lincensing to consistently mention GPL v2 -

[PATCH v2 3/4] ARM: multi_v7_defconfig: add CONFIG_BRCMSTB_THERMAL

From: Markus Mayer Turn on CONFIG_BRCMSTB_THERMAL as module. Signed-off-by: Markus Mayer --- arch/arm/configs/multi_v7_defconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm/configs/multi_v7_defconfig

[PATCH v2 3/4] ARM: multi_v7_defconfig: add CONFIG_BRCMSTB_THERMAL

From: Markus Mayer Turn on CONFIG_BRCMSTB_THERMAL as module. Signed-off-by: Markus Mayer --- arch/arm/configs/multi_v7_defconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm/configs/multi_v7_defconfig b/arch/arm/configs/multi_v7_defconfig index 4d19c1b..230f7fa 100644 ---

[GIT PULL] overlayfs fixes for 4.13-rc1

Hi Linus, Please pull from: git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git overlayfs-linus This fixes a crash with SELinux and several other old and new bugs. Thanks, Miklos --- Amir Goldstein (6): ovl: fix random return value on mount ovl: mark parent impure on

[GIT PULL] overlayfs fixes for 4.13-rc1

Hi Linus, Please pull from: git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git overlayfs-linus This fixes a crash with SELinux and several other old and new bugs. Thanks, Miklos --- Amir Goldstein (6): ovl: fix random return value on mount ovl: mark parent impure on

[PATCH v2 1/4] Documentation: devicetree: add binding for Broadcom STB AVS TMON

From: Brian Norris Add binding for Broadcom STB thermal. Signed-off-by: Brian Norris Signed-off-by: Markus Mayer --- .../devicetree/bindings/thermal/brcm,avs-tmon.txt| 20 MAINTAINERS

[PATCH v2 2/4] thermal: add brcmstb AVS TMON driver

From: Brian Norris The AVS TMON core provides temperature readings, a pair of configurable high- and low-temperature threshold interrupts, and an emergency over-temperature chip reset. The driver utilizes the first two to provide temperature readings and

[PATCH v2 1/4] Documentation: devicetree: add binding for Broadcom STB AVS TMON

From: Brian Norris Add binding for Broadcom STB thermal. Signed-off-by: Brian Norris Signed-off-by: Markus Mayer --- .../devicetree/bindings/thermal/brcm,avs-tmon.txt| 20 MAINTAINERS | 8 2 files changed, 28

[PATCH v2 2/4] thermal: add brcmstb AVS TMON driver

From: Brian Norris The AVS TMON core provides temperature readings, a pair of configurable high- and low-temperature threshold interrupts, and an emergency over-temperature chip reset. The driver utilizes the first two to provide temperature readings and high-temperature notifications to

Re: [PATCH v2 3/4] fs/dcache: Enable automatic pruning of negative dentries

On Fri, 2017-07-21 at 09:43 -0400, Waiman Long wrote: > Having a limit for the number of negative dentries does have an > undesirable side effect that no new negative dentries will be allowed > when the limit is reached. This will have performance implication > for some types of workloads. This

Re: [PATCH v2 3/4] fs/dcache: Enable automatic pruning of negative dentries

On Fri, 2017-07-21 at 09:43 -0400, Waiman Long wrote: > Having a limit for the number of negative dentries does have an > undesirable side effect that no new negative dentries will be allowed > when the limit is reached. This will have performance implication > for some types of workloads. This

[PATCH v2] sound: fsl_dma: remove dma_object path member

dma_object.path is unused, so rather than fix it to work with DT full_name changes, just remove it. Signed-off-by: Rob Herring Cc: Timur Tabi Cc: Nicolin Chen Cc: Xiubo Li Cc: Fabio Estevam

[PATCH v2] sound: Convert to using %pOF instead of full_name

Now that we have a custom printf format specifier, convert users of full_name to use %pOF instead. This is preparation to remove storing of the full path string for each node. Signed-off-by: Rob Herring Cc: Johannes Berg Cc: Jaroslav Kysela

[PATCH v2] sound: fsl_dma: remove dma_object path member

dma_object.path is unused, so rather than fix it to work with DT full_name changes, just remove it. Signed-off-by: Rob Herring Cc: Timur Tabi Cc: Nicolin Chen Cc: Xiubo Li Cc: Fabio Estevam Cc: Liam Girdwood Cc: Mark Brown Cc: Jaroslav Kysela Cc: Takashi Iwai Cc:

[PATCH v2] sound: Convert to using %pOF instead of full_name

Now that we have a custom printf format specifier, convert users of full_name to use %pOF instead. This is preparation to remove storing of the full path string for each node. Signed-off-by: Rob Herring Cc: Johannes Berg Cc: Jaroslav Kysela Cc: Takashi Iwai Cc: Timur Tabi Cc: Nicolin Chen

[PATCH v2] media: Convert to using %pOF instead of full_name

Now that we have a custom printf format specifier, convert users of full_name to use %pOF instead. This is preparation to remove storing of the full path string for each node. Signed-off-by: Rob Herring Acked-by: Niklas Söderlund Acked-by:

[PATCH v2] media: Convert to using %pOF instead of full_name

Now that we have a custom printf format specifier, convert users of full_name to use %pOF instead. This is preparation to remove storing of the full path string for each node. Signed-off-by: Rob Herring Acked-by: Niklas Söderlund Acked-by: Laurent Pinchart Reviewed-by: Matthias Brugger

[PATCH v2] ARM: Convert to using %pOF instead of full_name

Now that we have a custom printf format specifier, convert users of full_name to use %pOF instead. This is preparation to remove storing of the full path string for each node. Signed-off-by: Rob Herring Acked-by: Krzysztof Kozlowski Acked-by: Heiko Stuebner

[PATCH v2] ARM: Convert to using %pOF instead of full_name

Now that we have a custom printf format specifier, convert users of full_name to use %pOF instead. This is preparation to remove storing of the full path string for each node. Signed-off-by: Rob Herring Acked-by: Krzysztof Kozlowski Acked-by: Heiko Stuebner Reviewed-by: Geert Uytterhoeven

[PATCH] perf, tools: Make build fail on JSON parse error

From: Andi Kleen Today, when a JSON file fails parsing the build continues, but there are no json files built in, which is difficult to debug later. Make the build stop on a parse error instead. Cc: suka...@linux.vnet.ibm.com Signed-off-by: Andi Kleen

Re: [PATCH] xen/pvcalls: use WARN_ON(1) instead of __WARN()

On Fri, 21 Jul 2017, Arnd Bergmann wrote: > __WARN() is an internal helper that is only available on > some architectures, but causes a build error e.g. on ARM64 > in some configurations: > > drivers/xen/pvcalls-back.c: In function 'set_backend_state': > drivers/xen/pvcalls-back.c:1097:5: error:

[PATCH] perf, tools: Make build fail on JSON parse error

From: Andi Kleen Today, when a JSON file fails parsing the build continues, but there are no json files built in, which is difficult to debug later. Make the build stop on a parse error instead. Cc: suka...@linux.vnet.ibm.com Signed-off-by: Andi Kleen --- tools/perf/pmu-events/jevents.c | 6

Re: [PATCH] xen/pvcalls: use WARN_ON(1) instead of __WARN()

On Fri, 21 Jul 2017, Arnd Bergmann wrote: > __WARN() is an internal helper that is only available on > some architectures, but causes a build error e.g. on ARM64 > in some configurations: > > drivers/xen/pvcalls-back.c: In function 'set_backend_state': > drivers/xen/pvcalls-back.c:1097:5: error:

Re: [REGRESSION] 28676d869bbb (scsi: sg: check for valid direction before starting the request) breaks mtx tape library control

> "JT" == Johannes Thumshirn writes: JT> Jason, can you try the above? If it works and Doug doesn't respond, JT> I'm inclined yo submit this band aid. Unfortunately it doesn't appear to work for me. Maybe I'm building the wrong thing, though. I checked out 4.12, cherry

Re: [REGRESSION] 28676d869bbb (scsi: sg: check for valid direction before starting the request) breaks mtx tape library control

> "JT" == Johannes Thumshirn writes: JT> Jason, can you try the above? If it works and Doug doesn't respond, JT> I'm inclined yo submit this band aid. Unfortunately it doesn't appear to work for me. Maybe I'm building the wrong thing, though. I checked out 4.12, cherry picked

Re: [PATCH 2/2] mfd: intel_soc_pmic: Differentiate between Bay and Cherry Trail CRC variants

On Fri, 2017-07-21 at 20:41 +0200, Hans de Goede wrote: > On 18-07-17 09:17, Lee Jones wrote: > > On Mon, 17 Jul 2017, Andy Shevchenko wrote: > > > > > On Mon, 2017-07-17 at 11:59 +0100, Lee Jones wrote: > > > > On Sat, 01 Jul 2017, Hans de Goede wrote: > > > > > > > > > Reported-and-tested-by:

Re: [PATCH 2/2] mfd: intel_soc_pmic: Differentiate between Bay and Cherry Trail CRC variants

On Fri, 2017-07-21 at 20:41 +0200, Hans de Goede wrote: > On 18-07-17 09:17, Lee Jones wrote: > > On Mon, 17 Jul 2017, Andy Shevchenko wrote: > > > > > On Mon, 2017-07-17 at 11:59 +0100, Lee Jones wrote: > > > > On Sat, 01 Jul 2017, Hans de Goede wrote: > > > > > > > > > Reported-and-tested-by:

Re: [RFC 1/2] net-next: add a dma_desc element to struct skb_shared_info

From: John Crispin Date: Fri, 21 Jul 2017 19:01:57 +0200 > When the flow offloading engine forwards a packet to the DMA it will > send additional info to the sw path. this includes > * physical switch port > * internal flow hash - this is required to populate the correct flow >

Re: [RFC 1/2] net-next: add a dma_desc element to struct skb_shared_info

From: John Crispin Date: Fri, 21 Jul 2017 19:01:57 +0200 > When the flow offloading engine forwards a packet to the DMA it will > send additional info to the sw path. this includes > * physical switch port > * internal flow hash - this is required to populate the correct flow > * table entry > *

Re: [PATCH v3 04/15] selinux: Refactor to remove bprm_secureexec hook

On Fri, Jul 21, 2017 at 1:37 PM, Kees Cook wrote: > On Fri, Jul 21, 2017 at 8:40 AM, Paul Moore wrote: >> On Thu, Jul 20, 2017 at 4:42 PM, Paul Moore wrote: >>> On Thu, Jul 20, 2017 at 1:06 PM, Kees Cook

Re: [PATCH v3 04/15] selinux: Refactor to remove bprm_secureexec hook

On Fri, Jul 21, 2017 at 1:37 PM, Kees Cook wrote: > On Fri, Jul 21, 2017 at 8:40 AM, Paul Moore wrote: >> On Thu, Jul 20, 2017 at 4:42 PM, Paul Moore wrote: >>> On Thu, Jul 20, 2017 at 1:06 PM, Kees Cook wrote: On Thu, Jul 20, 2017 at 6:42 AM, Paul Moore wrote: > Alternatively, if

Re: [PATCH V2 1/4] net-next: dsa: move struct dsa_device_ops to the global header file

A proper patch series submission must always have a proper "[PATCH 0/N] ..." header posting that explains at a high level what the patch series does, how it is doing it, and why it is doing it that way. Thank you.

Re: [PATCH V2 1/4] net-next: dsa: move struct dsa_device_ops to the global header file

A proper patch series submission must always have a proper "[PATCH 0/N] ..." header posting that explains at a high level what the patch series does, how it is doing it, and why it is doing it that way. Thank you.

Re: [PATCH net-next 1/2] rxrpc: Expose UAPI definitions to userspace

On Fri, 2017-07-21 at 19:29 +0100, David Howells wrote: > Move UAPI definitions from the internal header and place them in a UAPI > header file so that userspace can make use of them. Please use git format-patch -M to make the rename clearer.

Re: [PATCH net-next 1/2] rxrpc: Expose UAPI definitions to userspace

On Fri, 2017-07-21 at 19:29 +0100, David Howells wrote: > Move UAPI definitions from the internal header and place them in a UAPI > header file so that userspace can make use of them. Please use git format-patch -M to make the rename clearer.

Re: MAINTAINERS: F: file patterns without matches

On Fri, 2017-07-21 at 10:10 -0700, Randy Dunlap wrote: > On 07/21/2017 10:02 AM, Joe Perches wrote: > > There are a number of file patterns in MAINTAINERS that > > don't have an actual matching file in the kernel tree. > > > > Some of those are due to renames, some are typos, some > > are added

Re: MAINTAINERS: F: file patterns without matches

On Fri, 2017-07-21 at 10:10 -0700, Randy Dunlap wrote: > On 07/21/2017 10:02 AM, Joe Perches wrote: > > There are a number of file patterns in MAINTAINERS that > > don't have an actual matching file in the kernel tree. > > > > Some of those are due to renames, some are typos, some > > are added

Re: commit 16ecba59 breaks 82574L under heavy load.

On Thu, Jul 20, 2017 at 04:44:55PM -0700, Benjamin Poirier wrote: > Could you please test the following patch and let me know if it: > 1) reduces the interrupt rate of the Other msi-x vector > 2) avoids the link flaps > or > 3) logs some dmesg warnings of the form "Other interrupt with unhandled

Re: commit 16ecba59 breaks 82574L under heavy load.

On Thu, Jul 20, 2017 at 04:44:55PM -0700, Benjamin Poirier wrote: > Could you please test the following patch and let me know if it: > 1) reduces the interrupt rate of the Other msi-x vector > 2) avoids the link flaps > or > 3) logs some dmesg warnings of the form "Other interrupt with unhandled

Re: linux-next: build failure after merge of the drm-misc tree

Hi, On 21-07-17 09:24, Daniel Vetter wrote: Hi Greg, How are we going to handle this now? The refactor is deeply burried in drm-misc, I guess you could cherry-pick the relevant patches over. But that'll probably lead to more conflicts because git will get confused. Or you could just delete

Re: linux-next: build failure after merge of the drm-misc tree

Hi, On 21-07-17 09:24, Daniel Vetter wrote: Hi Greg, How are we going to handle this now? The refactor is deeply burried in drm-misc, I guess you could cherry-pick the relevant patches over. But that'll probably lead to more conflicts because git will get confused. Or you could just delete

[PATCH] netvsc: fix ptr_ret.cocci warnings

drivers/net/hyperv/netvsc_drv.c:737:8-14: WARNING: PTR_ERR_OR_ZERO can be used Use PTR_ERR_OR_ZERO rather than if(IS_ERR(...)) + PTR_ERR Generated by: scripts/coccinelle/api/ptr_ret.cocci Fixes: 9749fed5d43d ("netvsc: use ERR_PTR to avoid dereference issues") CC: stephen hemminger

[PATCH] netvsc: fix ptr_ret.cocci warnings

drivers/net/hyperv/netvsc_drv.c:737:8-14: WARNING: PTR_ERR_OR_ZERO can be used Use PTR_ERR_OR_ZERO rather than if(IS_ERR(...)) + PTR_ERR Generated by: scripts/coccinelle/api/ptr_ret.cocci Fixes: 9749fed5d43d ("netvsc: use ERR_PTR to avoid dereference issues") CC: stephen hemminger

man-pages-4.12 is released

The Linux man-pages maintainer proudly announces: man-pages-4.12 - man pages for Linux This release resulted from patches, bug reports, reviews, and comments from around 30 contributors. This relatively small release consists of just under 200 commits changing around 90 pages. Tarball

man-pages-4.12 is released

The Linux man-pages maintainer proudly announces: man-pages-4.12 - man pages for Linux This release resulted from patches, bug reports, reviews, and comments from around 30 contributors. This relatively small release consists of just under 200 commits changing around 90 pages. Tarball

Re: [PATCH 4/5] e1000e: Separate signaling for link check/link up

On Fri, Jul 21, 2017 at 11:36:26AM -0700, Benjamin Poirier wrote: > Lennart reported the following race condition: > > \ e1000_watchdog_task > \ e1000e_has_link > \ hw->mac.ops.check_for_link() === e1000e_check_for_copper_link > /* link is up */ >

Re: [PATCH 4/5] e1000e: Separate signaling for link check/link up

On Fri, Jul 21, 2017 at 11:36:26AM -0700, Benjamin Poirier wrote: > Lennart reported the following race condition: > > \ e1000_watchdog_task > \ e1000e_has_link > \ hw->mac.ops.check_for_link() === e1000e_check_for_copper_link > /* link is up */ >

Re: [PATCH 5/5] e1000e: Avoid receiver overrun interrupt bursts

On Fri, Jul 21, 2017 at 11:36:27AM -0700, Benjamin Poirier wrote: > When e1000e_poll() is not fast enough to keep up with incoming traffic, the > adapter (when operating in msix mode) raises the Other interrupt to signal > Receiver Overrun. > > This is a double problem because 1) at the moment

Re: [PATCH 5/5] e1000e: Avoid receiver overrun interrupt bursts

On Fri, Jul 21, 2017 at 11:36:27AM -0700, Benjamin Poirier wrote: > When e1000e_poll() is not fast enough to keep up with incoming traffic, the > adapter (when operating in msix mode) raises the Other interrupt to signal > Receiver Overrun. > > This is a double problem because 1) at the moment

Re: [PATCH 3/3] ghes_edac: add platform check to enable ghes_edac

On Fri, 2017-07-21 at 19:23 +0200, Borislav Petkov wrote: : > Not only that: thresholds depend on the DIMM types which means, BIOS > must know what DIMM types are in there which I doubt. BIOS knows DIMM model from the SPD data. > So exposing that to configuration instead of "deciding" for

Re: [PATCH 3/3] ghes_edac: add platform check to enable ghes_edac

On Fri, 2017-07-21 at 19:23 +0200, Borislav Petkov wrote: : > Not only that: thresholds depend on the DIMM types which means, BIOS > must know what DIMM types are in there which I doubt. BIOS knows DIMM model from the SPD data. > So exposing that to configuration instead of "deciding" for

Re: [PATCH 2/2] mfd: intel_soc_pmic: Differentiate between Bay and Cherry Trail CRC variants

Hi, On 18-07-17 09:17, Lee Jones wrote: On Mon, 17 Jul 2017, Andy Shevchenko wrote: On Mon, 2017-07-17 at 11:59 +0100, Lee Jones wrote: On Sat, 01 Jul 2017, Hans de Goede wrote: Both Bay and Cherry Trail devices may be used together with a Crystal Cove PMIC. Each platform has its own

Re: [PATCH 2/2] mfd: intel_soc_pmic: Differentiate between Bay and Cherry Trail CRC variants

Hi, On 18-07-17 09:17, Lee Jones wrote: On Mon, 17 Jul 2017, Andy Shevchenko wrote: On Mon, 2017-07-17 at 11:59 +0100, Lee Jones wrote: On Sat, 01 Jul 2017, Hans de Goede wrote: Both Bay and Cherry Trail devices may be used together with a Crystal Cove PMIC. Each platform has its own

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