Re: [RFC v2 2/5] vfio/type1: Check reserve region conflict and update iova list

On Fri, 12 Jan 2018 16:45:28 + Shameer Kolothum wrote: > This retrieves the reserved regions associated with dev group and > checks for conflicts with any existing dma mappings. Also update > the iova list excluding the reserved regions. > >

Re: [RFC v2 2/5] vfio/type1: Check reserve region conflict and update iova list

On Fri, 12 Jan 2018 16:45:28 + Shameer Kolothum wrote: > This retrieves the reserved regions associated with dev group and > checks for conflicts with any existing dma mappings. Also update > the iova list excluding the reserved regions. > > Signed-off-by: Shameer Kolothum > --- >

Re: [RFC v2 1/5] vfio/type1: Introduce iova list and add iommu aperture validity check

On Fri, 12 Jan 2018 16:45:27 + Shameer Kolothum wrote: > This introduces an iova list that is valid for dma mappings. Make > sure the new iommu aperture window is valid and doesn't conflict > with any existing dma mappings during attach. Also update the

Re: [RFC v2 1/5] vfio/type1: Introduce iova list and add iommu aperture validity check

On Fri, 12 Jan 2018 16:45:27 + Shameer Kolothum wrote: > This introduces an iova list that is valid for dma mappings. Make > sure the new iommu aperture window is valid and doesn't conflict > with any existing dma mappings during attach. Also update the iova > list with new aperture window

Re: [PATCH] input: joystick: make USB drivers depend on USB

On 01/17/2018 01:53 PM, Dmitry Torokhov wrote: > On Wed, Jan 17, 2018 at 10:30:10PM +0100, Marcus Folkesson wrote: >> A driver should not enable an entire subsystem. > > I disagree. As you go through menuconfig and you encounter this option > and you have the hardware and you want to enable it,

Re: [PATCH] input: joystick: make USB drivers depend on USB

On 01/17/2018 01:53 PM, Dmitry Torokhov wrote: > On Wed, Jan 17, 2018 at 10:30:10PM +0100, Marcus Folkesson wrote: >> A driver should not enable an entire subsystem. > > I disagree. As you go through menuconfig and you encounter this option > and you have the hardware and you want to enable it,

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

On Wed, Nov 29, 2017 at 05:38:19PM +0100, Alexandre Belloni wrote: > Hi Paul, > > On 28/11/2017 at 11:50:02 -0800, Paul Burton wrote: > > On Tue, Nov 28, 2017 at 05:31:51PM +, James Hogan wrote: > > > On Tue, Nov 28, 2017 at 05:53:59PM +0100, Alexandre Belloni wrote: > > > > On 28/11/2017 at

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

On Wed, Nov 29, 2017 at 05:38:19PM +0100, Alexandre Belloni wrote: > Hi Paul, > > On 28/11/2017 at 11:50:02 -0800, Paul Burton wrote: > > On Tue, Nov 28, 2017 at 05:31:51PM +, James Hogan wrote: > > > On Tue, Nov 28, 2017 at 05:53:59PM +0100, Alexandre Belloni wrote: > > > > On 28/11/2017 at

Re: [RFC PATCH 0/5] softirq: Per vector threading v2

On Wed, Jan 17, 2018 at 10:07 AM, Frederic Weisbecker wrote: > > I see, so you may want to test (possibly much) higher values of > MAX_SOFTIRQ_RESTART, > such as 50 or 100. I suspect the "number of softiqs per jiffy" is hardly interesting at all. We used to allow up to 2mS

Re: [RFC PATCH 0/5] softirq: Per vector threading v2

On Wed, Jan 17, 2018 at 10:07 AM, Frederic Weisbecker wrote: > > I see, so you may want to test (possibly much) higher values of > MAX_SOFTIRQ_RESTART, > such as 50 or 100. I suspect the "number of softiqs per jiffy" is hardly interesting at all. We used to allow up to 2mS or ten iterations

Re: [PATCH 0/3] PCI: move DT PCI functions to PCI core

On Thu, Jan 04, 2018 at 03:12:12PM -0600, Rob Herring wrote: > Most subsystem specific functions have been moved into the respective > subsystems. Only PCI and networking remain. This series moves most of the > PCI related code to drivers/pci/of.c. Some bus address functions for PCI > remain in

Re: [PATCH 0/3] PCI: move DT PCI functions to PCI core

On Thu, Jan 04, 2018 at 03:12:12PM -0600, Rob Herring wrote: > Most subsystem specific functions have been moved into the respective > subsystems. Only PCI and networking remain. This series moves most of the > PCI related code to drivers/pci/of.c. Some bus address functions for PCI > remain in

Re: [PATCH net-next] net: core: Expose number of link up/down transitions

Thu, Jan 18, 2018 at 12:06:57AM CET, f.faine...@gmail.com wrote: >From: David Decotigny > >Expose the number of times the link has been going UP or DOWN, and >update the "carrier_changes" counter to be the sum of these two events. >While at it, also update the sysfs-class-net

Re: [PATCH net-next] net: core: Expose number of link up/down transitions

Thu, Jan 18, 2018 at 12:06:57AM CET, f.faine...@gmail.com wrote: >From: David Decotigny > >Expose the number of times the link has been going UP or DOWN, and >update the "carrier_changes" counter to be the sum of these two events. >While at it, also update the sysfs-class-net documentation to

Re: [PATCH net-next] net: core: Expose number of link up/down transitions

On Wed, Jan 17, 2018 at 03:06:57PM -0800, Florian Fainelli wrote: > From: David Decotigny > > Expose the number of times the link has been going UP or DOWN, and > update the "carrier_changes" counter to be the sum of these two events. > While at it, also update the

Re: [PATCH net-next] net: core: Expose number of link up/down transitions

On Wed, Jan 17, 2018 at 03:06:57PM -0800, Florian Fainelli wrote: > From: David Decotigny > > Expose the number of times the link has been going UP or DOWN, and > update the "carrier_changes" counter to be the sum of these two events. > While at it, also update the sysfs-class-net documentation

Re: [PATCH] linux-next: docs-rst: Fix typos in kfigure.py

On Thu, 11 Jan 2018 20:00:28 +0900 Masanari Iida wrote: > This patch fixes some spelling typos found in kfigure.py > > Signed-off-by: Masanari Iida Applied, thanks. jon

Re: [PATCH] linux-next: docs-rst: Fix typos in kfigure.py

On Thu, 11 Jan 2018 20:00:28 +0900 Masanari Iida wrote: > This patch fixes some spelling typos found in kfigure.py > > Signed-off-by: Masanari Iida Applied, thanks. jon

Re: [PATCH] linux-next: DOC: HWPOISON: Fix path to debugfs in hwpoison.txt

On Thu, 11 Jan 2018 22:28:37 +0900 Masanari Iida wrote: > This patch fixes an incorrect path for debugfs in hwpoison.txt > > Signed-off-by: Masanari Iida Applied, thanks. jon

Re: [PATCH] linux-next: DOC: HWPOISON: Fix path to debugfs in hwpoison.txt

On Thu, 11 Jan 2018 22:28:37 +0900 Masanari Iida wrote: > This patch fixes an incorrect path for debugfs in hwpoison.txt > > Signed-off-by: Masanari Iida Applied, thanks. jon

Re: [PATCH v3] firmware: qcom: scm: Fix incorrect of_node_put calls in scm_init

On Tue, Jan 16, 2018 at 08:45:49AM -0800, Bjorn Andersson wrote: > On Fri 15 Dec 05:40 PST 2017, Loys Ollivier wrote: > > > When using other platform architectures, in the init of the qcom_scm > > driver, of_node_put is called on /firmware if no qcom dt is found. > > This results in a kernel

Re: [PATCH v3] firmware: qcom: scm: Fix incorrect of_node_put calls in scm_init

On Tue, Jan 16, 2018 at 08:45:49AM -0800, Bjorn Andersson wrote: > On Fri 15 Dec 05:40 PST 2017, Loys Ollivier wrote: > > > When using other platform architectures, in the init of the qcom_scm > > driver, of_node_put is called on /firmware if no qcom dt is found. > > This results in a kernel

Re: [PATCH] x86/mm: Rework wbinvd, hlt operation in stop_this_cpu()

On 1/17/2018 5:41 PM, Tom Lendacky wrote: > Some issues have been reported with the for loop in stop_this_cpu() that > issues the 'wbinvd; hlt' sequence. Reverting this sequence to halt() > has been shown to resolve the issue. > > However, the wbinvd is needed when running with SME. The reason

Re: [PATCH] x86/mm: Rework wbinvd, hlt operation in stop_this_cpu()

On 1/17/2018 5:41 PM, Tom Lendacky wrote: > Some issues have been reported with the for loop in stop_this_cpu() that > issues the 'wbinvd; hlt' sequence. Reverting this sequence to halt() > has been shown to resolve the issue. > > However, the wbinvd is needed when running with SME. The reason

Re: [PATCH] Documentation: Fix misconversion of #if

On Tue, 16 Jan 2018 19:40:55 -0800 Matthew Wilcox wrote: > At some stage of the conversion pipeline, something thought that the > DocBook entity should be rendered as NUM instead of #. Haven't you heard? It's a new, improved form of C trigraph... :) Applied, thanks. jon

Re: [PATCH] Documentation: Fix misconversion of #if

On Tue, 16 Jan 2018 19:40:55 -0800 Matthew Wilcox wrote: > At some stage of the conversion pipeline, something thought that the > DocBook entity should be rendered as NUM instead of #. Haven't you heard? It's a new, improved form of C trigraph... :) Applied, thanks. jon

Re: [PATCH 08/16] x86/pgtable/32: Allocate 8k page-tables when PTI is enabled

On Tue, Jan 16, 2018 at 8:36 AM, Joerg Roedel wrote: > From: Joerg Roedel > > Allocate a kernel and a user page-table root when PTI is > enabled. Also allocate a full page per root for PAEm because > otherwise the bit to flip in cr3 to switch between them >

Re: [PATCH 08/16] x86/pgtable/32: Allocate 8k page-tables when PTI is enabled

On Tue, Jan 16, 2018 at 8:36 AM, Joerg Roedel wrote: > From: Joerg Roedel > > Allocate a kernel and a user page-table root when PTI is > enabled. Also allocate a full page per root for PAEm because > otherwise the bit to flip in cr3 to switch between them > would be non-constant, which creates a

[PATCH] x86/mm: Rework wbinvd, hlt operation in stop_this_cpu()

Some issues have been reported with the for loop in stop_this_cpu() that issues the 'wbinvd; hlt' sequence. Reverting this sequence to halt() has been shown to resolve the issue. However, the wbinvd is needed when running with SME. The reason for the wbinvd is to prevent cache flush races

[PATCH] x86/mm: Rework wbinvd, hlt operation in stop_this_cpu()

Some issues have been reported with the for loop in stop_this_cpu() that issues the 'wbinvd; hlt' sequence. Reverting this sequence to halt() has been shown to resolve the issue. However, the wbinvd is needed when running with SME. The reason for the wbinvd is to prevent cache flush races

Re: [PATCH 14/16] x86/mm/legacy: Populate the user page-table with user pgd's

On Tue, Jan 16, 2018 at 8:36 AM, Joerg Roedel wrote: > From: Joerg Roedel > > Also populate the user-spage pgd's in the user page-table. > > Signed-off-by: Joerg Roedel > --- > arch/x86/include/asm/pgtable-2level.h | 3 +++ > 1 file changed, 3

Re: [PATCH 14/16] x86/mm/legacy: Populate the user page-table with user pgd's

On Tue, Jan 16, 2018 at 8:36 AM, Joerg Roedel wrote: > From: Joerg Roedel > > Also populate the user-spage pgd's in the user page-table. > > Signed-off-by: Joerg Roedel > --- > arch/x86/include/asm/pgtable-2level.h | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git

Re: [PATCH RFC v1] arm64: Handle traps from accessing CNTVCT/CNTFRQ for CONFIG_COMPAT

On Wed, Jan 17, 2018 at 11:35:08PM +, Robin Murphy wrote: > On Wed, 17 Jan 2018 12:41:56 -0800 > Nicolin Chen wrote: > > > On Wed, Jan 17, 2018 at 09:03:48AM +, Marc Zyngier wrote: > > > > > > So ignoring a condition for a Thumb instruction may cause its IT > > >

Re: [PATCH RFC v1] arm64: Handle traps from accessing CNTVCT/CNTFRQ for CONFIG_COMPAT

On Wed, Jan 17, 2018 at 11:35:08PM +, Robin Murphy wrote: > On Wed, 17 Jan 2018 12:41:56 -0800 > Nicolin Chen wrote: > > > On Wed, Jan 17, 2018 at 09:03:48AM +, Marc Zyngier wrote: > > > > > > So ignoring a condition for a Thumb instruction may cause its IT > > > > scope shifting. For

Re: [PATCH for 4.16 07/11] x86: Implement sync_core_before_usermode (v3)

On Wed, Jan 17, 2018 at 3:25 PM, Mathieu Desnoyers wrote: > - On Jan 17, 2018, at 1:13 PM, Andy Lutomirski l...@kernel.org wrote: > >> On Wed, Jan 17, 2018 at 10:10 AM, Mathieu Desnoyers >> wrote: >>> - On Jan 17, 2018, at

Re: [PATCH for 4.16 07/11] x86: Implement sync_core_before_usermode (v3)

On Wed, Jan 17, 2018 at 3:25 PM, Mathieu Desnoyers wrote: > - On Jan 17, 2018, at 1:13 PM, Andy Lutomirski l...@kernel.org wrote: > >> On Wed, Jan 17, 2018 at 10:10 AM, Mathieu Desnoyers >> wrote: >>> - On Jan 17, 2018, at 12:53 PM, Andy Lutomirski l...@kernel.org wrote: >>> On Wed,

Re: [PATCH RFC v1] arm64: Handle traps from accessing CNTVCT/CNTFRQ for CONFIG_COMPAT

On Wed, 17 Jan 2018 12:41:56 -0800 Nicolin Chen wrote: > On Wed, Jan 17, 2018 at 09:03:48AM +, Marc Zyngier wrote: > > > > So ignoring a condition for a Thumb instruction may cause its IT > > > scope shifting. For ARM mode, the only penalty could be two Rts > > >

Re: [PATCH RFC v1] arm64: Handle traps from accessing CNTVCT/CNTFRQ for CONFIG_COMPAT

On Wed, 17 Jan 2018 12:41:56 -0800 Nicolin Chen wrote: > On Wed, Jan 17, 2018 at 09:03:48AM +, Marc Zyngier wrote: > > > > So ignoring a condition for a Thumb instruction may cause its IT > > > scope shifting. For ARM mode, the only penalty could be two Rts > > > getting written -- which

Re: [PATCH 0/3] PCI: move DT PCI functions to PCI core

On Thu, Jan 04, 2018 at 03:12:12PM -0600, Rob Herring wrote: > Most subsystem specific functions have been moved into the respective > subsystems. Only PCI and networking remain. This series moves most of the > PCI related code to drivers/pci/of.c. Some bus address functions for PCI > remain in

Re: [PATCH 0/3] PCI: move DT PCI functions to PCI core

On Thu, Jan 04, 2018 at 03:12:12PM -0600, Rob Herring wrote: > Most subsystem specific functions have been moved into the respective > subsystems. Only PCI and networking remain. This series moves most of the > PCI related code to drivers/pci/of.c. Some bus address functions for PCI > remain in

Re: [PATCH] rcu: Use wrapper for lockdep asserts

On Wed, Jan 17, 2018 at 06:24:30AM -0800, Matthew Wilcox wrote: > > From: Matthew Wilcox > > Commits c0b334c5bfa9 and ea9b0c8a26a2 introduced new sparse warnings > by accessing rcu_node->lock directly and ignoring the __private > marker. Introduce a new wrapper and use

Re: [PATCH] rcu: Use wrapper for lockdep asserts

On Wed, Jan 17, 2018 at 06:24:30AM -0800, Matthew Wilcox wrote: > > From: Matthew Wilcox > > Commits c0b334c5bfa9 and ea9b0c8a26a2 introduced new sparse warnings > by accessing rcu_node->lock directly and ignoring the __private > marker. Introduce a new wrapper and use it. Also fix a similar

Re: [PATCH v4 2/5] PCI/ERR: Rename error reporting to generic pci naming

On Wed, Jan 17, 2018 at 02:00:40PM +0530, p...@codeaurora.org wrote: > On 2018-01-17 13:54, p...@codeaurora.org wrote: > >On 2018-01-17 06:46, Bjorn Helgaas wrote: > >>On Tue, Jan 16, 2018 at 03:28:40PM +0530, Oza Pawandeep wrote: > >>>This patch renames error reporting to generic function with >

Re: [PATCH v4 2/5] PCI/ERR: Rename error reporting to generic pci naming

On Wed, Jan 17, 2018 at 02:00:40PM +0530, p...@codeaurora.org wrote: > On 2018-01-17 13:54, p...@codeaurora.org wrote: > >On 2018-01-17 06:46, Bjorn Helgaas wrote: > >>On Tue, Jan 16, 2018 at 03:28:40PM +0530, Oza Pawandeep wrote: > >>>This patch renames error reporting to generic function with >

Re: [PATCH 0/1] Re: kernel BUG at fs/userfaultfd.c:LINE!

On Wed, Jan 17, 2018 at 09:56:29AM +0100, Pavel Machek wrote: > Hi! > > > > Andrea Arcangeli (1): > > > userfaultfd: clear the vma->vm_userfaultfd_ctx if UFFD_EVENT_FORK > > > fails > > > > > > fs/userfaultfd.c | 20 ++-- > > > 1 file changed, 18 insertions(+), 2

Re: [PATCH 0/1] Re: kernel BUG at fs/userfaultfd.c:LINE!

On Wed, Jan 17, 2018 at 09:56:29AM +0100, Pavel Machek wrote: > Hi! > > > > Andrea Arcangeli (1): > > > userfaultfd: clear the vma->vm_userfaultfd_ctx if UFFD_EVENT_FORK > > > fails > > > > > > fs/userfaultfd.c | 20 ++-- > > > 1 file changed, 18 insertions(+), 2

Re: [PATCH for 4.16 07/11] x86: Implement sync_core_before_usermode (v3)

- On Jan 17, 2018, at 1:13 PM, Andy Lutomirski l...@kernel.org wrote: > On Wed, Jan 17, 2018 at 10:10 AM, Mathieu Desnoyers > wrote: >> - On Jan 17, 2018, at 12:53 PM, Andy Lutomirski l...@kernel.org wrote: >> >>> On Wed, Jan 17, 2018 at 8:54 AM, Mathieu

Re: [PATCH for 4.16 07/11] x86: Implement sync_core_before_usermode (v3)

- On Jan 17, 2018, at 1:13 PM, Andy Lutomirski l...@kernel.org wrote: > On Wed, Jan 17, 2018 at 10:10 AM, Mathieu Desnoyers > wrote: >> - On Jan 17, 2018, at 12:53 PM, Andy Lutomirski l...@kernel.org wrote: >> >>> On Wed, Jan 17, 2018 at 8:54 AM, Mathieu Desnoyers >>> wrote: Ensure

RE: radeon 0000:01:00.0: swiotlb buffer is full (sz: 2097152 bytes)

> -Original Message- > From: Borislav Petkov [mailto:b...@alien8.de] > Sent: Wednesday, January 17, 2018 4:04 PM > To: Deucher, Alexander ; Koenig, Christian > > Cc: lkml > Subject: radeon :01:00.0:

RE: radeon 0000:01:00.0: swiotlb buffer is full (sz: 2097152 bytes)

> -Original Message- > From: Borislav Petkov [mailto:b...@alien8.de] > Sent: Wednesday, January 17, 2018 4:04 PM > To: Deucher, Alexander ; Koenig, Christian > > Cc: lkml > Subject: radeon :01:00.0: swiotlb buffer is full (sz: 2097152 bytes) > > Hi guys, > > seen this already? > >

Re: [PATCH net-next] net: core: Expose number of link up/down transitions

On Wed, 17 Jan 2018 15:06:57 -0800, Florian Fainelli wrote: > +What:/sys/class/net// ?

Re: [PATCH net-next] net: core: Expose number of link up/down transitions

On Wed, 17 Jan 2018 15:06:57 -0800, Florian Fainelli wrote: > +What:/sys/class/net// ?

Re: [PATCH net-next] net: stmmac: Fix reception of Broadcom switches tags

Hi Peppe, On 01/16/2018 11:06 PM, Giuseppe CAVALLARO wrote: > Hi Florian > > for gmac4.x and gmac3.x series the ACS bit is the Automatic Pad or CRC > Stripping, so the > core strips the Pad or FCS on frames if the value of the length field is > < 1536 bytes. > For MAC10-100 there is the Bit 8

Re: [PATCH net-next] net: stmmac: Fix reception of Broadcom switches tags

Hi Peppe, On 01/16/2018 11:06 PM, Giuseppe CAVALLARO wrote: > Hi Florian > > for gmac4.x and gmac3.x series the ACS bit is the Automatic Pad or CRC > Stripping, so the > core strips the Pad or FCS on frames if the value of the length field is > < 1536 bytes. > For MAC10-100 there is the Bit 8

Re: [PATCH v2 01/16] drivers: pwm: core: use a single of xlate function

On Tue, Jan 16, 2018 at 10:24:59AM +0200, Claudiu Beznea wrote: > Please explain me further. From this I understand, as a general rule, > that the device tree binaries from, e.g. 3 years ago, should be > compatible with, e.g. the current version of kernel? Yes.

Re: [PATCH v2 01/16] drivers: pwm: core: use a single of xlate function

On Tue, Jan 16, 2018 at 10:24:59AM +0200, Claudiu Beznea wrote: > Please explain me further. From this I understand, as a general rule, > that the device tree binaries from, e.g. 3 years ago, should be > compatible with, e.g. the current version of kernel? Yes.

Re: [PATCH 07/12] i2c: rk3x: account for const type of of_device_id.data

On Tue, Jan 02, 2018 at 02:28:03PM +0100, Julia Lawall wrote: > This driver creates a number of const structures that it stores in > the data field of an of_device_id array. > > The data field of an of_device_id structure has type const void *, so > there is no need for a const-discarding cast

Re: [PATCH 07/12] i2c: rk3x: account for const type of of_device_id.data

On Tue, Jan 02, 2018 at 02:28:03PM +0100, Julia Lawall wrote: > This driver creates a number of const structures that it stores in > the data field of an of_device_id array. > > The data field of an of_device_id structure has type const void *, so > there is no need for a const-discarding cast

Re: [PATCH] cifs: remove redundant duplicated assignment of pointer 'node'

Reviewed-by: Ronnie Sahlberg - Original Message - From: "Colin King" To: "Steve French" , linux-c...@vger.kernel.org, samba-techni...@lists.samba.org Cc: kernel-janit...@vger.kernel.org, linux-kernel@vger.kernel.org

Re: [PATCH] cifs: remove redundant duplicated assignment of pointer 'node'

Reviewed-by: Ronnie Sahlberg - Original Message - From: "Colin King" To: "Steve French" , linux-c...@vger.kernel.org, samba-techni...@lists.samba.org Cc: kernel-janit...@vger.kernel.org, linux-kernel@vger.kernel.org Sent: Wednesday, 17 January, 2018 8:52:39 PM Subject: [PATCH] cifs:

Re: [PATCH v2 03/16] pwm: cros-ec: update documentation regarding pwm-cells

On Wed, Jan 17, 2018 at 10:29:53AM +0200, Claudiu Beznea wrote: > With these changes, if pwm-cells=1 then only PWM-channel will be parsed, I'm not sure if I'm understanding you correctly but...no. If cells is 1, then your driver change just causes us not to parse correctly, and everything fails.

Re: [PATCH v2 03/16] pwm: cros-ec: update documentation regarding pwm-cells

On Wed, Jan 17, 2018 at 10:29:53AM +0200, Claudiu Beznea wrote: > With these changes, if pwm-cells=1 then only PWM-channel will be parsed, I'm not sure if I'm understanding you correctly but...no. If cells is 1, then your driver change just causes us not to parse correctly, and everything fails.

Re: [PATCH] [v2] i2c: acorn: add MODULE_LICENSE tag

On Mon, Jan 15, 2018 at 09:28:39PM +0100, Arnd Bergmann wrote: > As of v4.15, Kbuild warns about missing MODULE_LICENSE tags: > > WARNING: modpost: missing MODULE_LICENSE() in drivers/i2c/busses/i2c-acorn.o > > This adds a license, author and description tag, matching the > comment at the start

Re: [PATCH] [v2] i2c: acorn: add MODULE_LICENSE tag

On Mon, Jan 15, 2018 at 09:28:39PM +0100, Arnd Bergmann wrote: > As of v4.15, Kbuild warns about missing MODULE_LICENSE tags: > > WARNING: modpost: missing MODULE_LICENSE() in drivers/i2c/busses/i2c-acorn.o > > This adds a license, author and description tag, matching the > comment at the start

[PATCH net-next] net: core: Expose number of link up/down transitions

From: David Decotigny Expose the number of times the link has been going UP or DOWN, and update the "carrier_changes" counter to be the sum of these two events. While at it, also update the sysfs-class-net documentation to cover: carrier_changes (3.15), count_link_up (4.16)

[PATCH net-next] net: core: Expose number of link up/down transitions

From: David Decotigny Expose the number of times the link has been going UP or DOWN, and update the "carrier_changes" counter to be the sum of these two events. While at it, also update the sysfs-class-net documentation to cover: carrier_changes (3.15), count_link_up (4.16) and count_link_down

Re: [PATCH] [RESEND] aoe: use ktime_t instead of timeval

On 01/17/2018 10:41 AM, Jens Axboe wrote: ... Applied, thanks Arnd/Tina. Thank you for the CC. Sorry for the lack of response in November. -- Ed

Re: [PATCH] [RESEND] aoe: use ktime_t instead of timeval

On 01/17/2018 10:41 AM, Jens Axboe wrote: ... Applied, thanks Arnd/Tina. Thank you for the CC. Sorry for the lack of response in November. -- Ed

linux-next: build failure after merge of the f2fs tree

Hi Jaegeuk, After merging the f2fs tree, today's linux-next build (x86_64 allmodconfig) failed like this: /home/sfr/next/next/fs/f2fs/super.c: In function 'f2fs_fill_super': /home/sfr/next/next/fs/f2fs/super.c:2563:18: error: 'SB_I_CGROUPWB' undeclared (first use in this function); did you mean

linux-next: build failure after merge of the f2fs tree

Hi Jaegeuk, After merging the f2fs tree, today's linux-next build (x86_64 allmodconfig) failed like this: /home/sfr/next/next/fs/f2fs/super.c: In function 'f2fs_fill_super': /home/sfr/next/next/fs/f2fs/super.c:2563:18: error: 'SB_I_CGROUPWB' undeclared (first use in this function); did you mean

Re: [PATCH v2 2/2] mm: skip HWPoisoned pages when onlining pages

On Fri, 28 Apr 2017 08:30:48 +0200 Michal Hocko wrote: > On Wed 26-04-17 03:13:04, Naoya Horiguchi wrote: > > On Wed, Apr 26, 2017 at 12:10:15PM +1000, Balbir Singh wrote: > > > On Tue, 2017-04-25 at 16:27 +0200, Laurent Dufour wrote: > > > > The commit b023f46813cd

Re: [PATCH v2 2/2] mm: skip HWPoisoned pages when onlining pages

On Fri, 28 Apr 2017 08:30:48 +0200 Michal Hocko wrote: > On Wed 26-04-17 03:13:04, Naoya Horiguchi wrote: > > On Wed, Apr 26, 2017 at 12:10:15PM +1000, Balbir Singh wrote: > > > On Tue, 2017-04-25 at 16:27 +0200, Laurent Dufour wrote: > > > > The commit b023f46813cd ("memory-hotplug: skip

Re: [REGRESSION][v4.14.y][v4.15] x86/intel_rdt/cqm: Improve limbo list processing

On 01/17/2018 05:55 PM, Thomas Gleixner wrote: > On Wed, 17 Jan 2018, Joseph Salisbury wrote: >> On 01/16/2018 01:59 PM, Thomas Gleixner wrote: >> >> Testing of your patch shows that your patch resolves the bug.  Thanks >> for the assistance!  Is this something you could submit to mainline? >

Re: [REGRESSION][v4.14.y][v4.15] x86/intel_rdt/cqm: Improve limbo list processing

On 01/17/2018 05:55 PM, Thomas Gleixner wrote: > On Wed, 17 Jan 2018, Joseph Salisbury wrote: >> On 01/16/2018 01:59 PM, Thomas Gleixner wrote: >> >> Testing of your patch shows that your patch resolves the bug.  Thanks >> for the assistance!  Is this something you could submit to mainline? >

Re: LKML admins (syzbot emails are not delivered)

On Wed, 2018-01-17 at 18:16 +0100, Dmitry Vyukov wrote: [...] > Agree, but as far as I understand it is specifically restricted. You > can see docs here: > https://cloud.google.com/appengine/docs/standard/php/mail/mail-with-headers-attachments ROTFL - as if almost no one at Google know that there

Re: LKML admins (syzbot emails are not delivered)

On Wed, 2018-01-17 at 18:16 +0100, Dmitry Vyukov wrote: [...] > Agree, but as far as I understand it is specifically restricted. You > can see docs here: > https://cloud.google.com/appengine/docs/standard/php/mail/mail-with-headers-attachments ROTFL - as if almost no one at Google know that there

[PATCH] cfg80211: stop demanding lots of new stuff

"make oldconfig" from 4.14 (when CONFIG_CFG80211_CERTIFICATION_ONUS is not set) to 4.15-rc, gets into asking lots of new questions, and configuring in unwanted stuff: I'm unsure of my Kconfig skills, but it looks like CFG80211_REQUIRE_SIGNED_REGDB's "default y" needs to be toned down when we don't

Re: [REGRESSION][v4.14.y][v4.15] x86/intel_rdt/cqm: Improve limbo list processing

On Wed, 17 Jan 2018, Joseph Salisbury wrote: > On 01/16/2018 01:59 PM, Thomas Gleixner wrote: > > Testing of your patch shows that your patch resolves the bug.  Thanks > for the assistance!  Is this something you could submit to mainline? Already there :)

[PATCH] cfg80211: stop demanding lots of new stuff

"make oldconfig" from 4.14 (when CONFIG_CFG80211_CERTIFICATION_ONUS is not set) to 4.15-rc, gets into asking lots of new questions, and configuring in unwanted stuff: I'm unsure of my Kconfig skills, but it looks like CFG80211_REQUIRE_SIGNED_REGDB's "default y" needs to be toned down when we don't

Re: [REGRESSION][v4.14.y][v4.15] x86/intel_rdt/cqm: Improve limbo list processing

On Wed, 17 Jan 2018, Joseph Salisbury wrote: > On 01/16/2018 01:59 PM, Thomas Gleixner wrote: > > Testing of your patch shows that your patch resolves the bug.  Thanks > for the assistance!  Is this something you could submit to mainline? Already there :)

Re: [RFC 1/2] softirq: Defer net rx/tx processing to ksoftirqd context

On Wed, 17 Jan 2018, David Miller wrote: > From: Eric Dumazet > Date: Wed, 17 Jan 2018 14:02:43 -0800 > > > On Wed, Jan 17, 2018 at 2:00 PM, Thomas Gleixner wrote: > >> On Wed, 17 Jan 2018, Linus Torvalds wrote: > >> > >>> On Wed, Jan 17, 2018 at 1:54

Re: [RFC 1/2] softirq: Defer net rx/tx processing to ksoftirqd context

On Wed, 17 Jan 2018, David Miller wrote: > From: Eric Dumazet > Date: Wed, 17 Jan 2018 14:02:43 -0800 > > > On Wed, Jan 17, 2018 at 2:00 PM, Thomas Gleixner wrote: > >> On Wed, 17 Jan 2018, Linus Torvalds wrote: > >> > >>> On Wed, Jan 17, 2018 at 1:54 PM, Thomas Gleixner > >>> wrote: > >>> >

Re: kexec reboot fails with extra wbinvd introduced for AME SME

On 1/17/2018 2:01 PM, Tom Lendacky wrote: > On 1/17/2018 1:42 PM, Linus Torvalds wrote: >> On Tue, Jan 16, 2018 at 11:22 PM, Dave Young wrote: >>> >>> For the kexec reboot hang, if I remove the wbinvd in stop_this_cpu() >>> then kexec works fine. like this: >> >> Honestly, I

Re: kexec reboot fails with extra wbinvd introduced for AME SME

On 1/17/2018 2:01 PM, Tom Lendacky wrote: > On 1/17/2018 1:42 PM, Linus Torvalds wrote: >> On Tue, Jan 16, 2018 at 11:22 PM, Dave Young wrote: >>> >>> For the kexec reboot hang, if I remove the wbinvd in stop_this_cpu() >>> then kexec works fine. like this: >> >> Honestly, I think we should apply

[PATCH] x86/retpoline: Optimize inline assembler for vmexit_fill_RSB

From: Andi Kleen I was looking at the generated assembler for the C fill RSB inline asm operations, and noticed several issues: - The C code sets up the loop register, which is then immediately overwritten in __FILL_RETURN_BUFFER with the same value again. - The C code

[PATCH] x86/retpoline: Optimize inline assembler for vmexit_fill_RSB

From: Andi Kleen I was looking at the generated assembler for the C fill RSB inline asm operations, and noticed several issues: - The C code sets up the loop register, which is then immediately overwritten in __FILL_RETURN_BUFFER with the same value again. - The C code also passes in the

Re: [PATCH] hwmon: (lm75) Fix trailing semicolon

On Wed, Jan 17, 2018 at 06:24:48PM +, Luis de Bethencourt wrote: > The trailing semicolon is an empty statement that does no operation. > Removing it since it doesn't do anything. > > Signed-off-by: Luis de Bethencourt Applied. Thanks, Guenter > --- > > Hi, > > After

Re: [PATCH] hwmon: (lm75) Fix trailing semicolon

On Wed, Jan 17, 2018 at 06:24:48PM +, Luis de Bethencourt wrote: > The trailing semicolon is an empty statement that does no operation. > Removing it since it doesn't do anything. > > Signed-off-by: Luis de Bethencourt Applied. Thanks, Guenter > --- > > Hi, > > After fixing the same

Re: [REGRESSION] (>= v4.12) IO w/dmcrypt causing audio underruns

On Mon, Dec 18, 2017 at 10:25:33AM +0100, Enric Balletbo Serra wrote: > Hi Vito, > > 2017-12-01 22:33 GMT+01:00 : > > On Wed, Nov 29, 2017 at 10:39:19AM -0800, vcap...@pengaru.com wrote: > >> Hello, > >> > >> Recently I noticed substantial audio dropouts when listening to

Re: [REGRESSION] (>= v4.12) IO w/dmcrypt causing audio underruns

On Mon, Dec 18, 2017 at 10:25:33AM +0100, Enric Balletbo Serra wrote: > Hi Vito, > > 2017-12-01 22:33 GMT+01:00 : > > On Wed, Nov 29, 2017 at 10:39:19AM -0800, vcap...@pengaru.com wrote: > >> Hello, > >> > >> Recently I noticed substantial audio dropouts when listening to MP3s in > >> `cmus`

Re: ipv6 redefinition build issue with 4.15-rc8

On 01/17/2018 11:20 PM, Hauke Mehrtens wrote: On 01/17/2018 08:31 PM, Neil MacLeod wrote: All Further to my previous reply (reproduced below having been bounced by linux-kernel) I have successfully built LibreELEC when using the ConnMan patch from Jonas - there were no other failures. I have

Re: ipv6 redefinition build issue with 4.15-rc8

On 01/17/2018 11:20 PM, Hauke Mehrtens wrote: On 01/17/2018 08:31 PM, Neil MacLeod wrote: All Further to my previous reply (reproduced below having been bounced by linux-kernel) I have successfully built LibreELEC when using the ConnMan patch from Jonas - there were no other failures. I have

Re: [patch -mm 0/4] mm, memcg: introduce oom policies

On Wed, 17 Jan 2018, Roman Gushchin wrote: > You're introducing a new oom_policy knob, which has two separate sets > of possible values for the root and non-root cgroups. I don't think > it aligns with the existing cgroup v2 design. > The root mem cgroup can use "none" or "cgroup" to either

Re: [patch -mm 0/4] mm, memcg: introduce oom policies

On Wed, 17 Jan 2018, Roman Gushchin wrote: > You're introducing a new oom_policy knob, which has two separate sets > of possible values for the root and non-root cgroups. I don't think > it aligns with the existing cgroup v2 design. > The root mem cgroup can use "none" or "cgroup" to either

[PATCH 03/14] MIPS: memblock: Reserve initrd memory in memblock

There is no reserve_bootmem() method in the nobootmem interface, so we need to replace it with memblock-specific one. Signed-off-by: Serge Semin --- arch/mips/kernel/setup.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/mips/kernel/setup.c

[PATCH 03/14] MIPS: memblock: Reserve initrd memory in memblock

There is no reserve_bootmem() method in the nobootmem interface, so we need to replace it with memblock-specific one. Signed-off-by: Serge Semin --- arch/mips/kernel/setup.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/mips/kernel/setup.c b/arch/mips/kernel/setup.c

[PATCH 04/14] MIPS: memblock: Discard bootmem initialization

Since memblock is going to be used for the early memory allocation lets discard the bootmem node setup and all the related free-space search code. Low/high PFN extremums should be still calculated since they are needed on the paging_init stage. Since the current code is already doing memblock

[PATCH 02/14] MIPS: memblock: Surely map BSS kernel memory section

The current MIPS code makes sure the kernel code/data/init sections are in the maps, but BSS should also be there. Signed-off-by: Serge Semin --- arch/mips/kernel/setup.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/arch/mips/kernel/setup.c

[PATCH 04/14] MIPS: memblock: Discard bootmem initialization

Since memblock is going to be used for the early memory allocation lets discard the bootmem node setup and all the related free-space search code. Low/high PFN extremums should be still calculated since they are needed on the paging_init stage. Since the current code is already doing memblock

[PATCH 02/14] MIPS: memblock: Surely map BSS kernel memory section

The current MIPS code makes sure the kernel code/data/init sections are in the maps, but BSS should also be there. Signed-off-by: Serge Semin --- arch/mips/kernel/setup.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/arch/mips/kernel/setup.c b/arch/mips/kernel/setup.c index

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