[PATCH v4 2/3] doc: update kptr_restrict documentation

Recently the behaviour of printk specifier %pK was changed. The documentation does not currently mirror this. Update documentation for sysctl kptr_restrict. Signed-off-by: Tobin C. Harding --- Documentation/sysctl/kernel.txt | 3 ++- 1 file changed, 2 insertions(+), 1

[PATCH v4 2/3] doc: update kptr_restrict documentation

Recently the behaviour of printk specifier %pK was changed. The documentation does not currently mirror this. Update documentation for sysctl kptr_restrict. Signed-off-by: Tobin C. Harding --- Documentation/sysctl/kernel.txt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git

[PATCH v4 0/3] doc: update printk documentation

This set converts printk-formats.txt -> core-api/printk-formats.rst We also update the documentation around printing kernel addresses. This is my first documentation conversion. Please do be hard on this patch series. I'd like to get it _really_ correct so that future conversions will require

[PATCH v4 0/3] doc: update printk documentation

This set converts printk-formats.txt -> core-api/printk-formats.rst We also update the documentation around printing kernel addresses. This is my first documentation conversion. Please do be hard on this patch series. I'd like to get it _really_ correct so that future conversions will require

Re: [PATCH] KVM: vmx: speed up MSR bitmap merge

On 19/12/2017 20:58, Jim Mattson wrote: >> + /* Disable read intercept for all MSRs between 0x800 and >> 0x8ff. */ > Aren't we actually adopting the read intercepts from VMCS12 and > *enabling* the *write* intercepts? Yeah, the comment isn't the best. What I mean is that L0

Re: [PATCH] KVM: vmx: speed up MSR bitmap merge

On 19/12/2017 20:58, Jim Mattson wrote: >> + /* Disable read intercept for all MSRs between 0x800 and >> 0x8ff. */ > Aren't we actually adopting the read intercepts from VMCS12 and > *enabling* the *write* intercepts? Yeah, the comment isn't the best. What I mean is that L0

[PATCH v4 2/5] iommu/vt-d: Add debugfs support to show context internals

From: Gayatri Kammela IOMMU internals states such as root and context can be exported to the userspace. Example of such dump in Kabylake: root@OTC-KBLH-01:~# cat /sys/kernel/debug/intel_iommu/dmar_translation_struct IOMMU dmar0: Extended Root Table Addr:402b9e800

[PATCH v4 2/5] iommu/vt-d: Add debugfs support to show context internals

From: Gayatri Kammela IOMMU internals states such as root and context can be exported to the userspace. Example of such dump in Kabylake: root@OTC-KBLH-01:~# cat /sys/kernel/debug/intel_iommu/dmar_translation_struct IOMMU dmar0: Extended Root Table Addr:402b9e800 Extended Root table entries:

Re: [PATCH 1/1] tpm: only attempt to disable the LPC CLKRUN if is already

Hi Javier, I love your patch! Yet something to improve: [auto build test ERROR on next-20171214] [cannot apply to char-misc/char-misc-testing v4.15-rc3 v4.15-rc2 v4.15-rc1 v4.15-rc4] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH 1/1] tpm: only attempt to disable the LPC CLKRUN if is already

Hi Javier, I love your patch! Yet something to improve: [auto build test ERROR on next-20171214] [cannot apply to char-misc/char-misc-testing v4.15-rc3 v4.15-rc2 v4.15-rc1 v4.15-rc4] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

[PATCH v4 0/5] Add Intel IOMMU debugfs support

Hi All, This series aims to add debugfs support for Intel IOMMU. It exposes IOMMU registers, internal context and dumps individual table entries to help debug Intel IOMMUs. The first patch does the ground work for the following patches by creating a new Kconfig option - INTEL_IOMMU_DEBUG. It

[PATCH v4 0/5] Add Intel IOMMU debugfs support

Hi All, This series aims to add debugfs support for Intel IOMMU. It exposes IOMMU registers, internal context and dumps individual table entries to help debug Intel IOMMUs. The first patch does the ground work for the following patches by creating a new Kconfig option - INTEL_IOMMU_DEBUG. It

[PATCH v4 4/5] iommu/vt-d: Add debugfs support to show Pasid table contents

From: Gayatri Kammela Debugfs extension to dump the internals such as pasid table entries for each IOMMU to the userspace. Example of such dump in Kabylake: root@OTC-KBLH-01:~# cat /sys/kernel/debug/intel_iommu/dmar_translation_struct IOMMU dmar0: Extended Root

[PATCH v4 4/5] iommu/vt-d: Add debugfs support to show Pasid table contents

From: Gayatri Kammela Debugfs extension to dump the internals such as pasid table entries for each IOMMU to the userspace. Example of such dump in Kabylake: root@OTC-KBLH-01:~# cat /sys/kernel/debug/intel_iommu/dmar_translation_struct IOMMU dmar0: Extended Root Table Addr:402b9e800 Extended

[PATCH v4 3/5] iommu/vt-d: Add debugfs support to show register contents

From: Gayatri Kammela Debugfs extension to dump all the register contents for each IOMMU device to the user space via debugfs. example: root@OTC-KBLH-01:~# cat /sys/kernel/debug/intel_iommu/iommu_regset DMAR: dmar1: reg_base_addr fed9 Name Offset

Re: [PATCH 2/2] scsi: ufs: use sysfs entry for health info

On Tue, 2017-12-19 at 12:02 -0800, Jaegeuk Kim wrote: > This patch introduces sysfs entries to show the information. What information does "the information" refer to? Regarding the patch title: I think this patch introduces new sysfs attributes instead of using existing sysfs entries. If so,

[PATCH v4 3/5] iommu/vt-d: Add debugfs support to show register contents

From: Gayatri Kammela Debugfs extension to dump all the register contents for each IOMMU device to the user space via debugfs. example: root@OTC-KBLH-01:~# cat /sys/kernel/debug/intel_iommu/iommu_regset DMAR: dmar1: reg_base_addr fed9 Name Offset Contents VER 0x00

Re: [PATCH 2/2] scsi: ufs: use sysfs entry for health info

On Tue, 2017-12-19 at 12:02 -0800, Jaegeuk Kim wrote: > This patch introduces sysfs entries to show the information. What information does "the information" refer to? Regarding the patch title: I think this patch introduces new sysfs attributes instead of using existing sysfs entries. If so,

[PATCH v4 5/5] iommu/vt-d: Add debugfs support for Interrupt remapping

Debugfs extension for Intel IOMMU to dump Interrupt remapping table entries for Interrupt remapping and Interrupt posting. The file /sys/kernel/debug/intel_iommu/ir_translation_struct provides detailed information, such as Index, Source Id, Destination Id, Vector and the raw values for entries

[PATCH v4 5/5] iommu/vt-d: Add debugfs support for Interrupt remapping

Debugfs extension for Intel IOMMU to dump Interrupt remapping table entries for Interrupt remapping and Interrupt posting. The file /sys/kernel/debug/intel_iommu/ir_translation_struct provides detailed information, such as Index, Source Id, Destination Id, Vector and the raw values for entries

[PATCH v4 1/5] iommu/vt-d: Add debugfs support for Intel IOMMU internals

From: Gayatri Kammela Enable Intel IOMMU debug to export Intel IOMMU internals in debugfs Cc: Sohil Mehta Cc: Fenghua Yu Cc: Ashok Raj Signed-off-by: Jacob Pan

[PATCH v4 1/5] iommu/vt-d: Add debugfs support for Intel IOMMU internals

From: Gayatri Kammela Enable Intel IOMMU debug to export Intel IOMMU internals in debugfs Cc: Sohil Mehta Cc: Fenghua Yu Cc: Ashok Raj Signed-off-by: Jacob Pan Signed-off-by: Gayatri Kammela --- v4: No change v3: No change v2: No change drivers/iommu/Kconfig | 10 ++

[PATCH v2] ARM: dts: sunxi: Add sid for a83t

Allwinner a83t has a 1 KB sid block with efuse for security rootkey and thermal calibration data, add node to describe it. a83t-sid is not currently supported by nvmem/sunxi-sid, but it is supported in an external driver for FreeBSD. Signed-off-by: Kyle Evans --- Changes in

[PATCH v2] ARM: dts: sunxi: Add sid for a83t

Allwinner a83t has a 1 KB sid block with efuse for security rootkey and thermal calibration data, add node to describe it. a83t-sid is not currently supported by nvmem/sunxi-sid, but it is supported in an external driver for FreeBSD. Signed-off-by: Kyle Evans --- Changes in v2: - remove bogus

Re: [PATCH] arm64: Stop printing the virtual memory layout

On Tue, Dec 19, 2017 at 11:28 AM, Laura Abbott wrote: > Printing kernel addresses should be done in limited circumstances, mostly > for debugging purposes. Printing out the virtual memory layout at every > kernel bootup doesn't really fall into this category so delete the

Re: [PATCH] arm64: Stop printing the virtual memory layout

On Tue, Dec 19, 2017 at 11:28 AM, Laura Abbott wrote: > Printing kernel addresses should be done in limited circumstances, mostly > for debugging purposes. Printing out the virtual memory layout at every > kernel bootup doesn't really fall into this category so delete the prints. > There are

Re: [RFC PATCH v2 03/13] bootsplash: Flush framebuffer after drawing

Hi, On Tue, Dec 19, 2017 at 10:41 AM, Max Staudt wrote: > I'm hooking into the in-kernel terminal emulator, because the bootsplash is a > functional extension of that. It just happens that fbcon sits on top of FB, > so I > work with what I get. > > And the console in turn

Re: [RFC PATCH v2 03/13] bootsplash: Flush framebuffer after drawing

Hi, On Tue, Dec 19, 2017 at 10:41 AM, Max Staudt wrote: > I'm hooking into the in-kernel terminal emulator, because the bootsplash is a > functional extension of that. It just happens that fbcon sits on top of FB, > so I > work with what I get. > > And the console in turn happens to work on all

Re: [PATCH] kfree_rcu() should use the new kfree_bulk() interface for freeing rcu structures

On Tue, Dec 19, 2017 at 09:41:58PM +0100, Jesper Dangaard Brouer wrote: > > On Tue, 19 Dec 2017 09:52:27 -0800 rao.sho...@oracle.com wrote: > > > +/* Main RCU function that is called to free RCU structures */ > > +static void > > +__rcu_bulk_free(struct rcu_head *head, rcu_callback_t func, int

Re: [PATCH] kfree_rcu() should use the new kfree_bulk() interface for freeing rcu structures

On Tue, Dec 19, 2017 at 09:41:58PM +0100, Jesper Dangaard Brouer wrote: > > On Tue, 19 Dec 2017 09:52:27 -0800 rao.sho...@oracle.com wrote: > > > +/* Main RCU function that is called to free RCU structures */ > > +static void > > +__rcu_bulk_free(struct rcu_head *head, rcu_callback_t func, int

[alsa-devel][PATCH v7] ASoC: TSCS42xx: Add support for Tempo Semiconductor's TSCS42xx audio CODEC

Currently there is no support for TSCS42xx audio CODECs. Add support for TSCS42xx audio CODECs. Reviewed-by: Charles Keepax Acked-by: Philippe Ombredanne Signed-off-by: Steven Eckhoff --- Thank you to

[alsa-devel][PATCH v7] ASoC: TSCS42xx: Add support for Tempo Semiconductor's TSCS42xx audio CODEC

Currently there is no support for TSCS42xx audio CODECs. Add support for TSCS42xx audio CODECs. Reviewed-by: Charles Keepax Acked-by: Philippe Ombredanne Signed-off-by: Steven Eckhoff --- Thank you to everyone involved in improving this driver. In the following history I have attempted to

Re: [lustre-devel] [PATCH 02/16] staging: lustre: replace simple cases of l_wait_event() with wait_event().

On Tue, Dec 19 2017, Dilger, Andreas wrote: > On Dec 18, 2017, at 11:03, Patrick Farrell wrote: >> >> The wait calls in ll_statahead_thread are done in a service thread, and >> should probably *not* contribute to load. >> >> The one in osc_extent_wait is perhaps tough - It is

Re: [lustre-devel] [PATCH 02/16] staging: lustre: replace simple cases of l_wait_event() with wait_event().

On Tue, Dec 19 2017, Dilger, Andreas wrote: > On Dec 18, 2017, at 11:03, Patrick Farrell wrote: >> >> The wait calls in ll_statahead_thread are done in a service thread, and >> should probably *not* contribute to load. >> >> The one in osc_extent_wait is perhaps tough - It is called both from

Re: [net-next: PATCH 0/8] Armada 7k/8k PP2 ACPI support

> Of course! v2 will not have such problem, I've been waiting however > for the feedback about the ACPI representation. Anyway, I'm strongly > leaning towards using _ADR/_CID objects in PHY's nodes for ACPI, so > maybe I'll just issue the v2 in order to push the discussion a bit > forward. Hi

Re: [net-next: PATCH 0/8] Armada 7k/8k PP2 ACPI support

> Of course! v2 will not have such problem, I've been waiting however > for the feedback about the ACPI representation. Anyway, I'm strongly > leaning towards using _ADR/_CID objects in PHY's nodes for ACPI, so > maybe I'll just issue the v2 in order to push the discussion a bit > forward. Hi

[PATCH v2] HID: elecom: rewrite report fixup for EX-G and future mice

This patch rewrites the mouse report fixup used for the DEFT and HUGE elecom trackballs in order to make it generic enough to fix other elecom mice with similar issues. This patch also uses this new report fixup function to fix the Elecom EX-G trackball which has 6 physical buttons and a similar

[PATCH v2] HID: elecom: rewrite report fixup for EX-G and future mice

This patch rewrites the mouse report fixup used for the DEFT and HUGE elecom trackballs in order to make it generic enough to fix other elecom mice with similar issues. This patch also uses this new report fixup function to fix the Elecom EX-G trackball which has 6 physical buttons and a similar

Re: BUG: bad usercopy in memdup_user

Adding Linus On Tue, Dec 19, 2017 at 03:12:05PM +0100, Dmitry Vyukov wrote: > On Tue, Dec 19, 2017 at 3:08 PM, Tetsuo Handa > wrote: > > Dmitry Vyukov wrote: > >> On Tue, Dec 19, 2017 at 2:22 PM, Matthew Wilcox > >> wrote: > >> >> > >>

Re: BUG: bad usercopy in memdup_user

Adding Linus On Tue, Dec 19, 2017 at 03:12:05PM +0100, Dmitry Vyukov wrote: > On Tue, Dec 19, 2017 at 3:08 PM, Tetsuo Handa > wrote: > > Dmitry Vyukov wrote: > >> On Tue, Dec 19, 2017 at 2:22 PM, Matthew Wilcox > >> wrote: > >> >> > >> This BUG is reporting > >> >> > >> > >> >> > >> [

Re: [PATCH] kfree_rcu() should use the new kfree_bulk() interface for freeing rcu structures

On Tue, 19 Dec 2017 09:52:27 -0800 rao.sho...@oracle.com wrote: > +/* Main RCU function that is called to free RCU structures */ > +static void > +__rcu_bulk_free(struct rcu_head *head, rcu_callback_t func, int cpu, bool > lazy) > +{ > + unsigned long offset; > + void *ptr; > +

Re: [PATCH] kfree_rcu() should use the new kfree_bulk() interface for freeing rcu structures

On Tue, 19 Dec 2017 09:52:27 -0800 rao.sho...@oracle.com wrote: > +/* Main RCU function that is called to free RCU structures */ > +static void > +__rcu_bulk_free(struct rcu_head *head, rcu_callback_t func, int cpu, bool > lazy) > +{ > + unsigned long offset; > + void *ptr; > +

Re: [PATCH for-4.15] wireless: create, don't append, to shipped-certs.c

On Tue, Dec 19, 2017 at 09:11:30PM +0100, Johannes Berg wrote: > I'm not really sure what that problem was - I think a combination of > missing clean-files and this perhaps? Anyway, I applied another fix for > this today, and it's on the way to Linus's tree, along with the missing > clean-files

Re: [PATCH for-4.15] wireless: create, don't append, to shipped-certs.c

On Tue, Dec 19, 2017 at 09:11:30PM +0100, Johannes Berg wrote: > I'm not really sure what that problem was - I think a combination of > missing clean-files and this perhaps? Anyway, I applied another fix for > this today, and it's on the way to Linus's tree, along with the missing > clean-files

Re: revamp vmem_altmap / dev_pagemap handling V2

On Fri, Dec 15, 2017 at 6:09 AM, Christoph Hellwig wrote: > > Hi all, > > this series started with two patches from Logan that now are in the > middle of the series to kill the memremap-internal pgmap structure > and to redo the dev_memreamp_pages interface to be better suitable >

Re: revamp vmem_altmap / dev_pagemap handling V2

On Fri, Dec 15, 2017 at 6:09 AM, Christoph Hellwig wrote: > > Hi all, > > this series started with two patches from Logan that now are in the > middle of the series to kill the memremap-internal pgmap structure > and to redo the dev_memreamp_pages interface to be better suitable > for future PCI

Re: BUG: bad usercopy in memdup_user

On Tue, Dec 19, 2017 at 05:22:46AM -0800, Matthew Wilcox wrote: > On Tue, Dec 19, 2017 at 07:37:46PM +1100, Tobin C. Harding wrote: > > On Tue, Dec 19, 2017 at 09:12:58AM +0100, Dmitry Vyukov wrote: > > > On Tue, Dec 19, 2017 at 1:57 AM, Kees Cook wrote: > > > > On Mon, Dec

Re: BUG: bad usercopy in memdup_user

On Tue, Dec 19, 2017 at 05:22:46AM -0800, Matthew Wilcox wrote: > On Tue, Dec 19, 2017 at 07:37:46PM +1100, Tobin C. Harding wrote: > > On Tue, Dec 19, 2017 at 09:12:58AM +0100, Dmitry Vyukov wrote: > > > On Tue, Dec 19, 2017 at 1:57 AM, Kees Cook wrote: > > > > On Mon, Dec 18, 2017 at 6:22 AM,

Re: [RFC PATCH v2 00/13] Kernel based bootsplash

Hi, > For example, having a userspace splash that starts as early as it can > (thus on vesafb/efifb on a PC) will cause the KMS driver to fail > reserving the entirety of video RAM, and thus fail loading. This cannot be > fixed. well the fix there is to use drm devices... like this:

Re: [RFC PATCH v2 00/13] Kernel based bootsplash

Hi, > For example, having a userspace splash that starts as early as it can > (thus on vesafb/efifb on a PC) will cause the KMS driver to fail > reserving the entirety of video RAM, and thus fail loading. This cannot be > fixed. well the fix there is to use drm devices... like this:

Re: [PATCH 3/4] sched: Comment on why sync wakeups try to run on the current CPU

On Tue, Dec 19, 2017 at 08:06:44PM +0100, Peter Zijlstra wrote: > On Mon, Dec 18, 2017 at 09:43:26AM +, Mel Gorman wrote: > > The sync wakeup logic in wake_affine_idle deserves a short description. > > > > Signed-off-by: Mel Gorman > > --- > >

Re: [PATCH 3/4] sched: Comment on why sync wakeups try to run on the current CPU

On Tue, Dec 19, 2017 at 08:06:44PM +0100, Peter Zijlstra wrote: > On Mon, Dec 18, 2017 at 09:43:26AM +, Mel Gorman wrote: > > The sync wakeup logic in wake_affine_idle deserves a short description. > > > > Signed-off-by: Mel Gorman > > --- > > kernel/sched/fair.c | 5 + > > 1 file

Re: [PATCH v5 0/6] enable creating [k,u]probe with perf_event_open

Took 1-4, Thanks!

Re: [PATCH v5 0/6] enable creating [k,u]probe with perf_event_open

Took 1-4, Thanks!

Re: [PATCH 2/4] perf/x86/intel: fix event update for auto-reload

On 12/19/2017 3:08 PM, Liang, Kan wrote: On 12/19/2017 1:58 PM, Peter Zijlstra wrote: On Mon, Dec 18, 2017 at 03:34:49AM -0800, kan.li...@linux.intel.com wrote:   arch/x86/events/core.c | 14 ++   arch/x86/events/intel/ds.c |  8 +++-   2 files changed, 21 insertions(+),

Re: [PATCH 2/4] perf/x86/intel: fix event update for auto-reload

On 12/19/2017 3:08 PM, Liang, Kan wrote: On 12/19/2017 1:58 PM, Peter Zijlstra wrote: On Mon, Dec 18, 2017 at 03:34:49AM -0800, kan.li...@linux.intel.com wrote:   arch/x86/events/core.c | 14 ++   arch/x86/events/intel/ds.c |  8 +++-   2 files changed, 21 insertions(+),

Re: [PATCH] kfree_rcu() should use the new kfree_bulk() interface for freeing rcu structures

On Tue, Dec 19, 2017 at 11:56:30AM -0800, Rao Shoaib wrote: > On 12/19/2017 11:30 AM, Matthew Wilcox wrote: > >On Tue, Dec 19, 2017 at 09:52:27AM -0800, rao.sho...@oracle.com wrote: [ . . . ] > >I've been doing a lot of thinking about this because I really want a > >way to kfree_rcu() an object

Re: [PATCH] kfree_rcu() should use the new kfree_bulk() interface for freeing rcu structures

On Tue, Dec 19, 2017 at 11:56:30AM -0800, Rao Shoaib wrote: > On 12/19/2017 11:30 AM, Matthew Wilcox wrote: > >On Tue, Dec 19, 2017 at 09:52:27AM -0800, rao.sho...@oracle.com wrote: [ . . . ] > >I've been doing a lot of thinking about this because I really want a > >way to kfree_rcu() an object

Re: [PATCH v5 1/6] dt: bindings: lp8860: Update bindings for lp8860

Dan, Thanks for the updated patch set. Applied to linux-leds.git. -- Best regards, Jacek Anaszewski On 12/18/2017 09:23 PM, Dan Murphy wrote: > Update the lp8860 bindings to fix various issues > found. Rename enable-gpio to enable-gpios, > update the node name to the device name and > indent

Re: [PATCH v5 1/6] dt: bindings: lp8860: Update bindings for lp8860

Dan, Thanks for the updated patch set. Applied to linux-leds.git. -- Best regards, Jacek Anaszewski On 12/18/2017 09:23 PM, Dan Murphy wrote: > Update the lp8860 bindings to fix various issues > found. Rename enable-gpio to enable-gpios, > update the node name to the device name and > indent

Re: [BISECTED] tpm CLKRUN breaks PS/2 keyboard and touchpad on Braswell system

On Tue, Dec 19, 2017 at 03:04:32PM +0200, Jarkko Sakkinen wrote: > > That makes it a BIOS bug, not a chipset bug, and we shouldn't be > > trying to fix it like this in Linux. > > > > Based on the original discussion I always thought this was an Intel > > chipset bug and applies to all cases. >

Re: [BISECTED] tpm CLKRUN breaks PS/2 keyboard and touchpad on Braswell system

On Tue, Dec 19, 2017 at 03:04:32PM +0200, Jarkko Sakkinen wrote: > > That makes it a BIOS bug, not a chipset bug, and we shouldn't be > > trying to fix it like this in Linux. > > > > Based on the original discussion I always thought this was an Intel > > chipset bug and applies to all cases. >

Re: [PATCH v2 1/2] clk: tegra: Mark HCLK, SCLK, EMC, MC and PLL_P outputs as critical

On 19.12.2017 22:56, Michael Turquette wrote: > Quoting Dmitry Osipenko (2017-12-18 19:59:06) >> Machine dies if HCLK, SCLK or EMC is disabled, hence mark these clocks >> as critical. Currently some of drivers do not manage clocks properly, >> expecting clocks to be 'always enabled', these clocks

Re: [PATCH v2 1/2] clk: tegra: Mark HCLK, SCLK, EMC, MC and PLL_P outputs as critical

On 19.12.2017 22:56, Michael Turquette wrote: > Quoting Dmitry Osipenko (2017-12-18 19:59:06) >> Machine dies if HCLK, SCLK or EMC is disabled, hence mark these clocks >> as critical. Currently some of drivers do not manage clocks properly, >> expecting clocks to be 'always enabled', these clocks

Re: [PATCH net 0/3] Few mvneta fixes

On Tue, Dec 19, 2017 at 5:59 PM, Gregory CLEMENT wrote: > Hello, > > here it is a small series of fixes found on the mvneta driver. They > had been already used in the vendor kernel and are now ported to > mainline. Does one of the patches look like it

Re: [PATCH net 0/3] Few mvneta fixes

On Tue, Dec 19, 2017 at 5:59 PM, Gregory CLEMENT wrote: > Hello, > > here it is a small series of fixes found on the mvneta driver. They > had been already used in the vendor kernel and are now ported to > mainline. Does one of the patches look like it addresses the rare Oops we discussed on

[PATCH] platform/x86/dell-smo8800: Delete an error message for a failed memory allocation in smo8800_add()

From: Markus Elfring Date: Tue, 19 Dec 2017 21:12:10 +0100 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

[PATCH] platform/x86/dell-smo8800: Delete an error message for a failed memory allocation in smo8800_add()

From: Markus Elfring Date: Tue, 19 Dec 2017 21:12:10 +0100 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring --- drivers/platform/x86/dell-smo8800.c | 4 +--- 1 file changed, 1

[PATCH v4 5/5] staging: rtl8712: style fix returned error code

This patch fixes a coding style issues in the rtl8712 module as noted by checkpatch.pl regarding the returned error code. It fixes the following checkpatch.pl warning: WARNING: ENOSYS means 'invalid syscall nr' and nothing else Signed-off-by: Martin Homuth ---

[PATCH v4 5/5] staging: rtl8712: style fix returned error code

This patch fixes a coding style issues in the rtl8712 module as noted by checkpatch.pl regarding the returned error code. It fixes the following checkpatch.pl warning: WARNING: ENOSYS means 'invalid syscall nr' and nothing else Signed-off-by: Martin Homuth ---

[PATCH v4 1/5] staging: rtl8712: style fix over 80 characters warnings

This patch fixes various coding style issues in the rtl8712 module as noted by checkpatch.pl by reducing the characters per line to under 80. It fixes the following checkpatch.pl warning: WARNING: line over 80 characters Signed-off-by: Martin Homuth ---

[PATCH v4 1/5] staging: rtl8712: style fix over 80 characters warnings

This patch fixes various coding style issues in the rtl8712 module as noted by checkpatch.pl by reducing the characters per line to under 80. It fixes the following checkpatch.pl warning: WARNING: line over 80 characters Signed-off-by: Martin Homuth --- drivers/staging/rtl8712/ieee80211.c

[PATCH v4 2/5] staging: rtl8712: style fix multiple line dereferences

This patch fixes various coding style issues in the rtl8712 module as noted by checkpatch.pl related to dereferencing over multiple lines. It fixes the following checkpatch.pl warning: WARNING: Avoid multiple line dereference - prefer %s Signed-off-by: Martin Homuth ---

[PATCH v4 0/5] staging: rtl8712: fix several checkpatch style issues

This patch series fixes some coding style issues reported by checkpatch.pl. It is based on next-20171218 v2: - avoid line-wrapping by thunderbird - use temporary pointers to avoid index in separate line ([2/5]) v3: - missed one reference simplification ([2/5]) - fix some checkpatch checks

[PATCH v4 2/5] staging: rtl8712: style fix multiple line dereferences

This patch fixes various coding style issues in the rtl8712 module as noted by checkpatch.pl related to dereferencing over multiple lines. It fixes the following checkpatch.pl warning: WARNING: Avoid multiple line dereference - prefer %s Signed-off-by: Martin Homuth ---

[PATCH v4 0/5] staging: rtl8712: fix several checkpatch style issues

This patch series fixes some coding style issues reported by checkpatch.pl. It is based on next-20171218 v2: - avoid line-wrapping by thunderbird - use temporary pointers to avoid index in separate line ([2/5]) v3: - missed one reference simplification ([2/5]) - fix some checkpatch checks

[PATCH v4 4/5] staging: rtl8712: style fix unneeded else

This patch fixes a coding style issues in the rtl8712 module as noted by checkpatch.pl where an unnecessary else is used. It fixes the following checkpatch.pl warning: WARNING: else is not generally useful after a break or return Signed-off-by: Martin Homuth ---

[PATCH v4 4/5] staging: rtl8712: style fix unneeded else

This patch fixes a coding style issues in the rtl8712 module as noted by checkpatch.pl where an unnecessary else is used. It fixes the following checkpatch.pl warning: WARNING: else is not generally useful after a break or return Signed-off-by: Martin Homuth ---

[PATCH v4 3/5] staging: rtl8712: style fix indentation

This patch fixes various coding style issues in the rtl8712 module as noted by checkpatch.pl related to indentation. It fixes the following checkpatch.pl warning: WARNING: suspect code indent for conditional statements Signed-off-by: Martin Homuth ---

[PATCH v4 3/5] staging: rtl8712: style fix indentation

This patch fixes various coding style issues in the rtl8712 module as noted by checkpatch.pl related to indentation. It fixes the following checkpatch.pl warning: WARNING: suspect code indent for conditional statements Signed-off-by: Martin Homuth ---

Re: [PATCH] PCI: dwc: Use {upper,lower}_32_bits() macros for clarity

On 12/11, Lorenzo Pieralisi wrote: > On Tue, Nov 28, 2017 at 04:53:34PM -0800, Stephen Boyd wrote: > > We have macros for getting the upper or lower 32 bits of a > > number. Use them here to shave a couple lines off the code. > > > > Signed-off-by: Stephen Boyd > > --- > >

Re: [PATCH] PCI: dwc: Use {upper,lower}_32_bits() macros for clarity

On 12/11, Lorenzo Pieralisi wrote: > On Tue, Nov 28, 2017 at 04:53:34PM -0800, Stephen Boyd wrote: > > We have macros for getting the upper or lower 32 bits of a > > number. Use them here to shave a couple lines off the code. > > > > Signed-off-by: Stephen Boyd > > --- > >

[RFC] MIPS memblock: Remove bootmem code and switch to NO_BOOTMEM

Hello folks, Almost a year ago I sent a patchset to the Linux MIPS community. The main target of the patchset was to get rid from the old bootmem allocator usage at the MIPS architecture. Additionally I had a problem with CMA usage on my MIPS machine due to some struct page-related issue.

[RFC] MIPS memblock: Remove bootmem code and switch to NO_BOOTMEM

Hello folks, Almost a year ago I sent a patchset to the Linux MIPS community. The main target of the patchset was to get rid from the old bootmem allocator usage at the MIPS architecture. Additionally I had a problem with CMA usage on my MIPS machine due to some struct page-related issue.

Re: [PATCH 2/3, V2] kernel: Move groups_sort to the caller of set_groups.

On Tue, Dec 19 2017, J. Bruce Fields wrote: > On Tue, Dec 05, 2017 at 07:11:00AM +1100, NeilBrown wrote: >> On Mon, Dec 04 2017, Thiago Rafael Becker wrote: >> >> > On Mon, 4 Dec 2017, NeilBrown wrote: >> > >> >> I think you need to add groups_sort() in a few more places. >> >> Almost anywhere

Re: [PATCH linux-next] mqueue: fix IPC namespace use-after-free

On Tue, Dec 19, 2017 at 07:40:43PM +0100, Giuseppe Scrivano wrote: > Giuseppe Scrivano writes: > > > The only issue I've seen with my version is that if I do: > > > > # unshare -im /bin/sh > > # mount -t mqueue mqueue /dev/mqueue > > # touch /dev/mqueue/foo > > # umount

Re: [PATCH 2/3, V2] kernel: Move groups_sort to the caller of set_groups.

On Tue, Dec 19 2017, J. Bruce Fields wrote: > On Tue, Dec 05, 2017 at 07:11:00AM +1100, NeilBrown wrote: >> On Mon, Dec 04 2017, Thiago Rafael Becker wrote: >> >> > On Mon, 4 Dec 2017, NeilBrown wrote: >> > >> >> I think you need to add groups_sort() in a few more places. >> >> Almost anywhere

Re: [PATCH linux-next] mqueue: fix IPC namespace use-after-free

On Tue, Dec 19, 2017 at 07:40:43PM +0100, Giuseppe Scrivano wrote: > Giuseppe Scrivano writes: > > > The only issue I've seen with my version is that if I do: > > > > # unshare -im /bin/sh > > # mount -t mqueue mqueue /dev/mqueue > > # touch /dev/mqueue/foo > > # umount /dev/mqueue > > # mount

[PATCH] ARM: dts: sunxi: Add sid for a83t

From: Kyle Evans Allwinner a83t has a 1 KB sid block with efuse for security rootkey and thermal calibration data, add node to describe it. a83t-sid is not currently supported by nvmem/sunxi-sid, but it is supported in an external driver for FreeBSD. Signed-off-by: Kyle Evans

[PATCH] ARM: dts: sunxi: Add sid for a83t

From: Kyle Evans Allwinner a83t has a 1 KB sid block with efuse for security rootkey and thermal calibration data, add node to describe it. a83t-sid is not currently supported by nvmem/sunxi-sid, but it is supported in an external driver for FreeBSD. Signed-off-by: Kyle Evans ---

Re: [PATCH] bug.h: Work around GCC PR82365 in BUG()

On Tue, Dec 19, 2017 at 5:57 PM, Vineet Gupta wrote: > On 12/19/2017 03:41 AM, Arnd Bergmann wrote: >> In case of ARC and CRIS, it turns out that the BUG() implementation >> actually does return (or at least the compiler thinks it does), resulting >> in lots of

Re: [PATCH] bug.h: Work around GCC PR82365 in BUG()

On Tue, Dec 19, 2017 at 5:57 PM, Vineet Gupta wrote: > On 12/19/2017 03:41 AM, Arnd Bergmann wrote: >> In case of ARC and CRIS, it turns out that the BUG() implementation >> actually does return (or at least the compiler thinks it does), resulting >> in lots of warnings about uninitialized

linux-next: Signed-off-by missing for commits in the char-misc tree

Hi all, Commits 46a2bb5a7f7e ("slimbus: core: Add slim controllers support") afbdcc7c384b ("slimbus: Add messaging APIs to slimbus framework") are missing a Signed-off-by from their author. -- Cheers, Stephen Rothwell

linux-next: Signed-off-by missing for commits in the char-misc tree

Hi all, Commits 46a2bb5a7f7e ("slimbus: core: Add slim controllers support") afbdcc7c384b ("slimbus: Add messaging APIs to slimbus framework") are missing a Signed-off-by from their author. -- Cheers, Stephen Rothwell

Re: [PATCH for-4.15] wireless: create, don't append, to shipped-certs.c

On Tue, 2017-12-19 at 11:23 -0800, Brian Norris wrote: > > In practice, this is seen often by having a separate source and build > directory, where the build artifacts remain but the source tree changes > (even if Seth's cert doesn't change, it might get created/removed when > checking out

Re: [PATCH for-4.15] wireless: create, don't append, to shipped-certs.c

On Tue, 2017-12-19 at 11:23 -0800, Brian Norris wrote: > > In practice, this is seen often by having a separate source and build > directory, where the build artifacts remain but the source tree changes > (even if Seth's cert doesn't change, it might get created/removed when > checking out

Re: [PATCH 4/4] perf/x86/intel: drain PEBS buffer in event read

On 12/19/2017 2:02 PM, Peter Zijlstra wrote: On Mon, Dec 18, 2017 at 03:34:51AM -0800, kan.li...@linux.intel.com wrote: --- a/arch/x86/events/intel/ds.c +++ b/arch/x86/events/intel/ds.c @@ -926,6 +926,16 @@ void intel_pmu_pebs_del(struct perf_event *event) pebs_update_state(needed_cb,

Re: [PATCH 4/4] perf/x86/intel: drain PEBS buffer in event read

On 12/19/2017 2:02 PM, Peter Zijlstra wrote: On Mon, Dec 18, 2017 at 03:34:51AM -0800, kan.li...@linux.intel.com wrote: --- a/arch/x86/events/intel/ds.c +++ b/arch/x86/events/intel/ds.c @@ -926,6 +926,16 @@ void intel_pmu_pebs_del(struct perf_event *event) pebs_update_state(needed_cb,

Re: [PATCH v2 09/13] MIPS: mscc: Add initial support for Microsemi MIPS SoCs

Hi, On 19/12/2017 at 20:27:02 +0530, PrasannaKumar Muralidharan wrote: > Given the fact that setup code is very small and most of it is generic > code I strongly believe that it is plausible to make use of generic > code completely. Please have a look at [1] and [2]. > > 1.

Re: [PATCH v2 09/13] MIPS: mscc: Add initial support for Microsemi MIPS SoCs

Hi, On 19/12/2017 at 20:27:02 +0530, PrasannaKumar Muralidharan wrote: > Given the fact that setup code is very small and most of it is generic > code I strongly believe that it is plausible to make use of generic > code completely. Please have a look at [1] and [2]. > > 1.

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