MAINTAINERS missing links

Here's a current list of the W: links that seem dead. It'd be good to update some of them like the analog ones. I suppose some links are useful for historic purposes, but perhaps better would be to retrieve the link contents from archive.org or similar and store them in the tree. produced by:

Re: [PATCH net-next] net: dsa: rename switch operations structure

On 08/23/2016 09:38 AM, Vivien Didelot wrote: > Now that the dsa_switch_driver structure contains only function pointers > as it is supposed to, rename it to the more appropriate dsa_switch_ops, > uniformly to any other operations structure in the kernel. > > No functional changes here, basically

Re: [PATCH v2 0/6] Intel Integrated Sensor Hub Support (ISH)

On Wed, 24 Aug 2016, Grant Likely wrote: > >> v2: > >> - Overview in documentation show analogy with usbhid implementation > >> - sparse errors for statics. Also pointed by Jiri > >> - Clearly marking exported function header file. Clean up all exports > >> unused inteface functions > >> -

Re: [PATCH v2 0/6] Intel Integrated Sensor Hub Support (ISH)

On Wed, 24 Aug 2016, Grant Likely wrote: > >> v2: > >> - Overview in documentation show analogy with usbhid implementation > >> - sparse errors for statics. Also pointed by Jiri > >> - Clearly marking exported function header file. Clean up all exports > >> unused inteface functions > >> -

Re: [PATCH 4.7 146/186] floppy: fix open(O_ACCMODE) for ioctl-only open

On Wed, 24 Aug 2016, Greg Kroah-Hartman wrote: > > I have a problem with this patch. It only fixes one of the regressions > > caused by the original change to the floppy driver. It does not address the > > user land breakage of removing the NODELAY flag checks. > > Does the same problem also

Re: [PATCH 4.7 146/186] floppy: fix open(O_ACCMODE) for ioctl-only open

On Wed, 24 Aug 2016, Greg Kroah-Hartman wrote: > > I have a problem with this patch. It only fixes one of the regressions > > caused by the original change to the floppy driver. It does not address the > > user land breakage of removing the NODELAY flag checks. > > Does the same problem also

[PATCH v2 0/2] ASoC: Chromebook Pixel 2015 audio support

This is the second version of the series originally posted here [1]. The second patch is largely unchanged and is still derived from the Chromium OS 3.14 source, but the patch to the codec driver now takes a different approach that I hope is easier to review as well resulting in less code. [1]

[PATCH v2 0/2] ASoC: Chromebook Pixel 2015 audio support

This is the second version of the series originally posted here [1]. The second patch is largely unchanged and is still derived from the Chromium OS 3.14 source, but the patch to the codec driver now takes a different approach that I hope is easier to review as well resulting in less code. [1]

[PATCH v2 1/2] ASoC: rt5677: Add ACPI support

The Chromebook Pixel 2015 uses this codec with the ACPI ID RT5677CE, but does not use the standard DT property names so add a new function to parse the codec properties from these ACPI properties. Also, the GPIOs are only available by index, so we need to register a mapping to allow machine

[PATCH v2 2/2] ASoC: Intel: boards: Add bdw-rt5677 machine driver

This is used by the Chromebook Pixel 2015. Signed-off-by: Ben Zhang Signed-off-by: Dylan Reid [j...@metanate.com: - forward-port driver from Chromium OS 3.14 tree to master - remove wake on voice function that isn't supported by upstream rt5677

[PATCH v2 1/2] ASoC: rt5677: Add ACPI support

The Chromebook Pixel 2015 uses this codec with the ACPI ID RT5677CE, but does not use the standard DT property names so add a new function to parse the codec properties from these ACPI properties. Also, the GPIOs are only available by index, so we need to register a mapping to allow machine

[PATCH v2 2/2] ASoC: Intel: boards: Add bdw-rt5677 machine driver

This is used by the Chromebook Pixel 2015. Signed-off-by: Ben Zhang Signed-off-by: Dylan Reid [j...@metanate.com: - forward-port driver from Chromium OS 3.14 tree to master - remove wake on voice function that isn't supported by upstream rt5677 driver - remote owner assignment in

Re: [PATCH V3] leds: trigger: Introduce an USB port trigger

On Wed, Aug 24, 2016 at 11:29:51AM +0200, Rafał Miłecki wrote: > On 24 August 2016 at 11:22, Greg KH wrote: > > On Wed, Aug 24, 2016 at 12:03:29AM +0200, Rafał Miłecki wrote: > >> +static ssize_t ports_show(struct device *dev, struct device_attribute > >> *attr, > >>

Re: [PATCH V3] leds: trigger: Introduce an USB port trigger

On Wed, Aug 24, 2016 at 11:29:51AM +0200, Rafał Miłecki wrote: > On 24 August 2016 at 11:22, Greg KH wrote: > > On Wed, Aug 24, 2016 at 12:03:29AM +0200, Rafał Miłecki wrote: > >> +static ssize_t ports_show(struct device *dev, struct device_attribute > >> *attr, > >> + char

[PATCH 3/9] PCI: PCIe aerdrv: make it explicitly non-modular

The Makefile fragments currently controlling compilation of this code are: obj-$(CONFIG_PCIEAER) += aerdriver.o aerdriver-objs := aerdrv_errprint.o aerdrv_core.o aerdrv.o The Kconfig currently controlling compilation of this code is: drivers/pci/pcie/aer/Kconfig:config PCIEAER

[PATCH 3/9] PCI: PCIe aerdrv: make it explicitly non-modular

The Makefile fragments currently controlling compilation of this code are: obj-$(CONFIG_PCIEAER) += aerdriver.o aerdriver-objs := aerdrv_errprint.o aerdrv_core.o aerdrv.o The Kconfig currently controlling compilation of this code is: drivers/pci/pcie/aer/Kconfig:config PCIEAER

[PATCH 2/9] PCI: PCIe pme: make it explicitly non-modular

The Kconfig for this option is currently: config PCIE_PME def_bool y depends on PCIEPORTBUS && PM ...where both dependencies are also bool items. That means it currently is not being built as a module by anyone. Lets remove all traces of modularity, so that when reading the

[PATCH 2/9] PCI: PCIe pme: make it explicitly non-modular

The Kconfig for this option is currently: config PCIE_PME def_bool y depends on PCIEPORTBUS && PM ...where both dependencies are also bool items. That means it currently is not being built as a module by anyone. Lets remove all traces of modularity, so that when reading the

Re: [Regression?] Commit cb4f71c429 deliberately changes order of network interfaces

On Wed, Aug 24, 2016 at 09:52:00PM +0200, Thomas Petazzoni wrote: > I'll let the platform maintainers decide what's the least > intrusive/problematic option. Both solutions have drawbacks, so it's > really a "political" decision to make here. I think the main valid argument for a revert is that

[PATCH 7/9] PCI: PCIe xilinx-nwl: make host code explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/pci/host/Kconfig:config PCIE_XILINX_NWL drivers/pci/host/Kconfig: bool "NWL PCIe Core" ...meaning that it currently is not being built as a module by anyone. Lets remove the modular code that is essentially orphaned,

[PATCH 4/9] PCI: dra7xx: make host code explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/pci/host/Kconfig:config PCI_DRA7XX drivers/pci/host/Kconfig: bool "TI DRA7xx PCIe controller" ...meaning that it currently is not being built as a module by anyone. Lets remove the modular code that is essentially

Re: [Regression?] Commit cb4f71c429 deliberately changes order of network interfaces

On Wed, Aug 24, 2016 at 09:52:00PM +0200, Thomas Petazzoni wrote: > I'll let the platform maintainers decide what's the least > intrusive/problematic option. Both solutions have drawbacks, so it's > really a "political" decision to make here. I think the main valid argument for a revert is that

[PATCH 7/9] PCI: PCIe xilinx-nwl: make host code explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/pci/host/Kconfig:config PCIE_XILINX_NWL drivers/pci/host/Kconfig: bool "NWL PCIe Core" ...meaning that it currently is not being built as a module by anyone. Lets remove the modular code that is essentially orphaned,

[PATCH 4/9] PCI: dra7xx: make host code explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/pci/host/Kconfig:config PCI_DRA7XX drivers/pci/host/Kconfig: bool "TI DRA7xx PCIe controller" ...meaning that it currently is not being built as a module by anyone. Lets remove the modular code that is essentially

[PATCH 5/9] PCI: PCIe qcom: make host code explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/pci/host/Kconfig:config PCIE_QCOM drivers/pci/host/Kconfig: bool "Qualcomm PCIe controller" ...meaning that it currently is not being built as a module by anyone. Lets remove the modular code that is essentially

[PATCH 5/9] PCI: PCIe qcom: make host code explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/pci/host/Kconfig:config PCIE_QCOM drivers/pci/host/Kconfig: bool "Qualcomm PCIe controller" ...meaning that it currently is not being built as a module by anyone. Lets remove the modular code that is essentially

[PATCH 8/9] PCI: hotplug_core: make it explicitly non-modular

The Makefile bits currently controlling compilation of this code are: obj-$(CONFIG_HOTPLUG_PCI) += pci_hotplug.o [...] pci_hotplug-objs:= pci_hotplug_core.o and the Kconfig is: drivers/pci/hotplug/Kconfig:menuconfig HOTPLUG_PCI drivers/pci/hotplug/Kconfig:

[PATCH 1/9] PCI: PCIe dpc: make it explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/pci/pcie/Kconfig:config PCIE_DPC drivers/pci/pcie/Kconfig: bool "PCIe Downstream Port Containment support" ...meaning that it currently is not being built as a module by anyone. Lets remove the modular code that is

[PATCH 0/9] PCI: final demodularization of non-modular code

This final (assuming more new instances don't leak back in) series ensures all the PCI code out there that remains using module.h is actually modular or containing some use of modular infrastructure. These last commits are slightly more involved than some of the earlier ones since we are actually

[PATCH 9/9] PCI: hotplug: make PCIe core code explicitly non-modular

The Makefile fragments currently controlling compilation of this code are: obj-$(CONFIG_HOTPLUG_PCI_PCIE) += pciehp.o [...] pciehp-objs := pciehp_core.o \ The Kconfig currently controlling compilation of this code is: drivers/pci/pcie/Kconfig:config

[PATCH 8/9] PCI: hotplug_core: make it explicitly non-modular

The Makefile bits currently controlling compilation of this code are: obj-$(CONFIG_HOTPLUG_PCI) += pci_hotplug.o [...] pci_hotplug-objs:= pci_hotplug_core.o and the Kconfig is: drivers/pci/hotplug/Kconfig:menuconfig HOTPLUG_PCI drivers/pci/hotplug/Kconfig:

[PATCH 1/9] PCI: PCIe dpc: make it explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/pci/pcie/Kconfig:config PCIE_DPC drivers/pci/pcie/Kconfig: bool "PCIe Downstream Port Containment support" ...meaning that it currently is not being built as a module by anyone. Lets remove the modular code that is

[PATCH 0/9] PCI: final demodularization of non-modular code

This final (assuming more new instances don't leak back in) series ensures all the PCI code out there that remains using module.h is actually modular or containing some use of modular infrastructure. These last commits are slightly more involved than some of the earlier ones since we are actually

[PATCH 9/9] PCI: hotplug: make PCIe core code explicitly non-modular

The Makefile fragments currently controlling compilation of this code are: obj-$(CONFIG_HOTPLUG_PCI_PCIE) += pciehp.o [...] pciehp-objs := pciehp_core.o \ The Kconfig currently controlling compilation of this code is: drivers/pci/pcie/Kconfig:config

[PATCH 6/9] PCI: PCIe xilinx: make host code explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/pci/host/Kconfig:config PCIE_XILINX drivers/pci/host/Kconfig: bool "Xilinx AXI PCIe host bridge support" ...meaning that it currently is not being built as a module by anyone. Lets remove the modular code that is

[PATCH 6/9] PCI: PCIe xilinx: make host code explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/pci/host/Kconfig:config PCIE_XILINX drivers/pci/host/Kconfig: bool "Xilinx AXI PCIe host bridge support" ...meaning that it currently is not being built as a module by anyone. Lets remove the modular code that is

Re: [PACTH,v6,1/2] usb: xhci: plat: Enable runtime PM

On 2016-08-22 11:23 PM, Brian Norris wrote: + others Hi Robert and Felipe, I have a few questions for one or both of you. I'm not really an expert on runtime PM, so please take my questions with a grain of salt. On Wed, Aug 10, 2016 at 04:32:15PM -0400, robert.f...@collabora.com wrote:

Re: [PACTH,v6,1/2] usb: xhci: plat: Enable runtime PM

On 2016-08-22 11:23 PM, Brian Norris wrote: + others Hi Robert and Felipe, I have a few questions for one or both of you. I'm not really an expert on runtime PM, so please take my questions with a grain of salt. On Wed, Aug 10, 2016 at 04:32:15PM -0400, robert.f...@collabora.com wrote:

Re: [PATCH v6 2/2] clocksource: add J-Core timer/clocksource driver

On Wed, Aug 24, 2016 at 10:01:08PM +0200, Arnd Bergmann wrote: > On Wednesday, August 24, 2016 1:40:01 PM CEST Rich Felker wrote: > > On Wed, Aug 24, 2016 at 06:42:05PM +0200, Daniel Lezcano wrote: > > > > diff --git a/drivers/clocksource/Kconfig b/drivers/clocksource/Kconfig > > > > index

Re: [PATCH v6 2/2] clocksource: add J-Core timer/clocksource driver

On Wed, Aug 24, 2016 at 10:01:08PM +0200, Arnd Bergmann wrote: > On Wednesday, August 24, 2016 1:40:01 PM CEST Rich Felker wrote: > > On Wed, Aug 24, 2016 at 06:42:05PM +0200, Daniel Lezcano wrote: > > > > diff --git a/drivers/clocksource/Kconfig b/drivers/clocksource/Kconfig > > > > index

[PATCH] bluetooth, regression: MSG_TRUNC fixes

Recent 4.8-rc changes to bluetooth MSG_TRUNC handling introduced regression; pairing finishes but connecting profiles not. With the below fixes to MSG_TRUNC handling the connection is established normally. --Mika Signed-off-by: Mika Penttilä --- diff --git

[PATCH] bluetooth, regression: MSG_TRUNC fixes

Recent 4.8-rc changes to bluetooth MSG_TRUNC handling introduced regression; pairing finishes but connecting profiles not. With the below fixes to MSG_TRUNC handling the connection is established normally. --Mika Signed-off-by: Mika Penttilä --- diff --git a/net/bluetooth/af_bluetooth.c

Re: [PATCH] mm, swap: Add swap_cluster_list

On Wed, 2016-08-24 at 12:35 -0700, Huang, Ying wrote: > From: Huang Ying > > This is a code clean up patch without functionality changes.  The > swap_cluster_list data structure and its operations are introduced to > provide some better encapsulation for the free cluster

Re: [PATCH] mm, swap: Add swap_cluster_list

On Wed, 2016-08-24 at 12:35 -0700, Huang, Ying wrote: > From: Huang Ying > > This is a code clean up patch without functionality changes.  The > swap_cluster_list data structure and its operations are introduced to > provide some better encapsulation for the free cluster and discard > cluster

[PATCH] powerpc/powernv/pci: Use kmalloc_array() in two functions

From: Markus Elfring Date: Wed, 24 Aug 2016 22:26:37 +0200 A multiplication for the size determination of a memory allocation indicated that an array data structure should be processed. Thus reuse the corresponding function "kmalloc_array". This issue was detected

[PATCH] mm: silently skip readahead for DAX inodes

For DAX inodes we need to be careful to never have page cache pages in the mapping->page_tree. This radix tree should be composed only of DAX exceptional entries and zero pages. ltp's readahead02 test was triggering a warning because we were trying to insert a DAX exceptional entry but found

[PATCH] powerpc/powernv/pci: Use kmalloc_array() in two functions

From: Markus Elfring Date: Wed, 24 Aug 2016 22:26:37 +0200 A multiplication for the size determination of a memory allocation indicated that an array data structure should be processed. Thus reuse the corresponding function "kmalloc_array". This issue was detected by using the Coccinelle

[PATCH] mm: silently skip readahead for DAX inodes

For DAX inodes we need to be careful to never have page cache pages in the mapping->page_tree. This radix tree should be composed only of DAX exceptional entries and zero pages. ltp's readahead02 test was triggering a warning because we were trying to insert a DAX exceptional entry but found

Re: [PATCH 03/10] reset: lpc18xx: add driver Kconfig option

Hi Philipp, On 24 August 2016 at 15:28, Philipp Zabel wrote: > Visible only if COMPILE_TEST is enabled, this allows to include the > driver in build tests. > > Cc: Joachim Eastwood > Signed-off-by: Philipp Zabel > --- >

Re: [PATCH 03/10] reset: lpc18xx: add driver Kconfig option

Hi Philipp, On 24 August 2016 at 15:28, Philipp Zabel wrote: > Visible only if COMPILE_TEST is enabled, this allows to include the > driver in build tests. > > Cc: Joachim Eastwood > Signed-off-by: Philipp Zabel > --- > drivers/reset/Kconfig | 7 +++ > drivers/reset/Makefile | 2 +- > 2

Re: [PATCH RFC V3.5] leds: trigger: Introduce an USB port trigger

On 24 August 2016 at 20:48, Bjørn Mork wrote: > Rafał Miłecki writes: > >> The last big missing thing is Documentation update (this is why I'm >> sending RFC). Greg pointed out we should have some entries in >> Documentation/ABI, but it seems none of triggers

Re: [PATCH RFC V3.5] leds: trigger: Introduce an USB port trigger

On 24 August 2016 at 20:48, Bjørn Mork wrote: > Rafał Miłecki writes: > >> The last big missing thing is Documentation update (this is why I'm >> sending RFC). Greg pointed out we should have some entries in >> Documentation/ABI, but it seems none of triggers have it. > > There's a lot missing,

Re: [PATCH] mm: silently skip readahead for DAX inodes

On Wed, 24 Aug 2016 14:37:12 -0600 Ross Zwisler wrote: > For DAX inodes we need to be careful to never have page cache pages in the > mapping->page_tree. This radix tree should be composed only of DAX > exceptional entries and zero pages. > > ltp's readahead02

Re: [PATCH] mm: silently skip readahead for DAX inodes

On Wed, 24 Aug 2016 14:37:12 -0600 Ross Zwisler wrote: > For DAX inodes we need to be careful to never have page cache pages in the > mapping->page_tree. This radix tree should be composed only of DAX > exceptional entries and zero pages. > > ltp's readahead02 test was triggering a warning

Re: [Regression?] Commit cb4f71c429 deliberately changes order of network interfaces

Hi Thomas On Wed, 24 Aug 2016 20:15:31 +0200 Thomas Petazzoni wrote: > Hello, > > On Wed, 24 Aug 2016 19:10:04 +0200, Ralph Sennhauser wrote: > > > Going forward, as we disagree and it's basically a political > > decision, whom do we ask to rule here?

Re: [Regression?] Commit cb4f71c429 deliberately changes order of network interfaces

Hi Thomas On Wed, 24 Aug 2016 20:15:31 +0200 Thomas Petazzoni wrote: > Hello, > > On Wed, 24 Aug 2016 19:10:04 +0200, Ralph Sennhauser wrote: > > > Going forward, as we disagree and it's basically a political > > decision, whom do we ask to rule here? Linus? > > I don't think Linus will

Re: [PATCH v2 2/5] firmware: annotate thou shalt not request fw on init or probe

On Wed, Aug 24, 2016 at 08:55:55AM +0200, Daniel Vetter wrote: > On Fri, Jun 17, 2016 at 12:54 AM, Luis R. Rodriguez wrote: > > Thou shalt not make firmware calls early on init or probe. <-- snip --> > > There are 4 offenders at this time: > > > > mcgrof@ergon ~/linux-next

Re: [PATCH v2 2/5] firmware: annotate thou shalt not request fw on init or probe

On Wed, Aug 24, 2016 at 08:55:55AM +0200, Daniel Vetter wrote: > On Fri, Jun 17, 2016 at 12:54 AM, Luis R. Rodriguez wrote: > > Thou shalt not make firmware calls early on init or probe. <-- snip --> > > There are 4 offenders at this time: > > > > mcgrof@ergon ~/linux-next (git::20160609)$

RCU Judy Array (optimisation over Radix Tree)

Hi Matthew, Following our discussion at LinuxCon about Radix Trees and Judy Array, here is a pointer to my user-space implementation prototype of RCU Judy Array. I've simplified it a bit (removing features you don't need, just keeping fixed-sized integer keys), and it can still be simplified

RCU Judy Array (optimisation over Radix Tree)

Hi Matthew, Following our discussion at LinuxCon about Radix Trees and Judy Array, here is a pointer to my user-space implementation prototype of RCU Judy Array. I've simplified it a bit (removing features you don't need, just keeping fixed-sized integer keys), and it can still be simplified

Re: CVE-2014-9900 fix is not upstream

On 24.08.2016 16:03, Lennart Sorensen wrote: > On Tue, Aug 23, 2016 at 10:25:45PM +0100, Al Viro wrote: >> Sadly, sizeof is what we use when copying that sucker to userland. So these >> padding bits in the end would've leaked, true enough, and the case is >> somewhat >> weaker. And any normal

Re: CVE-2014-9900 fix is not upstream

On 24.08.2016 16:03, Lennart Sorensen wrote: > On Tue, Aug 23, 2016 at 10:25:45PM +0100, Al Viro wrote: >> Sadly, sizeof is what we use when copying that sucker to userland. So these >> padding bits in the end would've leaked, true enough, and the case is >> somewhat >> weaker. And any normal

Re: [PATCH] ALSA: snd-aoa: enable sound on PowerBook G4 12"

Hi, On Wed, Aug 24, 2016 at 09:43:23PM +0200, Johannes Berg wrote: > On Wed, 2016-08-24 at 20:57 +0300, Aaro Koskinen wrote: > > Enable sound on PowerBook G4 12". > > Looks good to me, I assume you tested it and it works :) Yes, I have this laptop in use. A.

Re: [PATCH] ALSA: snd-aoa: enable sound on PowerBook G4 12"

Hi, On Wed, Aug 24, 2016 at 09:43:23PM +0200, Johannes Berg wrote: > On Wed, 2016-08-24 at 20:57 +0300, Aaro Koskinen wrote: > > Enable sound on PowerBook G4 12". > > Looks good to me, I assume you tested it and it works :) Yes, I have this laptop in use. A.

Re: [PATCH 4.7 146/186] floppy: fix open(O_ACCMODE) for ioctl-only open

On Wed, Aug 24, 2016 at 09:34:44AM -0400, Mark Hounschell wrote: > On 08/18/2016 09:59 AM, Greg Kroah-Hartman wrote: > > 4.7-stable review patch. If anyone has any objections, please let me know. > > > > -- > > > > From: Jiri Kosina > > > > commit

Re: [PATCH 4.7 146/186] floppy: fix open(O_ACCMODE) for ioctl-only open

On Wed, Aug 24, 2016 at 09:34:44AM -0400, Mark Hounschell wrote: > On 08/18/2016 09:59 AM, Greg Kroah-Hartman wrote: > > 4.7-stable review patch. If anyone has any objections, please let me know. > > > > -- > > > > From: Jiri Kosina > > > > commit

Re: Hotplug not working for USB 3.1 docking station on Dell XPS 13

[+cc Andreas, linux-kernel] On Wed, Aug 24, 2016 at 05:40:53PM +0100, Richard van der Hoff wrote: > I'm having problems with a Plugable USB-C docking station, with my > laptop, a Dell XPS 13 (9350). If the docking station is plugged in > at boot, it works correctly; however, when I hotplug it

Re: Hotplug not working for USB 3.1 docking station on Dell XPS 13

[+cc Andreas, linux-kernel] On Wed, Aug 24, 2016 at 05:40:53PM +0100, Richard van der Hoff wrote: > I'm having problems with a Plugable USB-C docking station, with my > laptop, a Dell XPS 13 (9350). If the docking station is plugged in > at boot, it works correctly; however, when I hotplug it

[PATCH v8 2/2 RESEND] Add ioctl to issue ZBC/ZAC commands via block layer

(RESENDING to include f2fs, fs-devel and dm-devel) Add support for ZBC ioctl's BLKREPORT - Issue Report Zones to device. BLKZONEACTION - Issue a Zone Action (Close, Finish, Open, or Reset) Signed-off-by: Shaun Tancheff --- v8: - Changed ioctl for zone

[PATCH v8 2/2 RESEND] Add ioctl to issue ZBC/ZAC commands via block layer

(RESENDING to include f2fs, fs-devel and dm-devel) Add support for ZBC ioctl's BLKREPORT - Issue Report Zones to device. BLKZONEACTION - Issue a Zone Action (Close, Finish, Open, or Reset) Signed-off-by: Shaun Tancheff --- v8: - Changed ioctl for zone actions to a single ioctl that

[PATCH v8 1/2 RESEND] Add bio/request flags to issue ZBC/ZAC commands

(RESENDING to include f2fs, fs-devel and dm-devel) Add op flags to access to zone information as well as open, close and reset zones: - REQ_OP_ZONE_REPORT - Query zone information (Report zones) - REQ_OP_ZONE_OPEN - Explicitly open a zone for writing - REQ_OP_ZONE_CLOSE - Explicitly close a

[PATCH v8 1/2 RESEND] Add bio/request flags to issue ZBC/ZAC commands

(RESENDING to include f2fs, fs-devel and dm-devel) Add op flags to access to zone information as well as open, close and reset zones: - REQ_OP_ZONE_REPORT - Query zone information (Report zones) - REQ_OP_ZONE_OPEN - Explicitly open a zone for writing - REQ_OP_ZONE_CLOSE - Explicitly close a

[PATCH v8 0/2 RESEND] Block layer support ZAC/ZBC commands

(RESENDING to include f2fs, fs-devel and dm-devel) Hi Jens, This series is based on linus' v4.8-rc2 branch. As Host Aware drives are becoming available we would like to be able to make use of such drives. This series is also intended to be suitable for use by Host Managed drives. ZBC [and ZAC]

[PATCH v8 0/2 RESEND] Block layer support ZAC/ZBC commands

(RESENDING to include f2fs, fs-devel and dm-devel) Hi Jens, This series is based on linus' v4.8-rc2 branch. As Host Aware drives are becoming available we would like to be able to make use of such drives. This series is also intended to be suitable for use by Host Managed drives. ZBC [and ZAC]

Re: [BISECTED REGRESSION] v4.8-rc: gpio-leds broken on OCTEON

On 08/23/2016 03:36 PM, Aaro Koskinen wrote: Hi, gpio-leds fails to probe on OCTEON with v4.8-rc3 and when using arch/mips/boot/dts/cavium-octeon/dlink_dsr-1000n.dts. Leds still worked with v4.7. I bisected this to: commit 15cc2ed6dcf91a8658e084be4e140147161819d7 Author: Jon

Re: [BISECTED REGRESSION] v4.8-rc: gpio-leds broken on OCTEON

On 08/23/2016 03:36 PM, Aaro Koskinen wrote: Hi, gpio-leds fails to probe on OCTEON with v4.8-rc3 and when using arch/mips/boot/dts/cavium-octeon/dlink_dsr-1000n.dts. Leds still worked with v4.7. I bisected this to: commit 15cc2ed6dcf91a8658e084be4e140147161819d7 Author: Jon

[RFC PATCH] powerpc: fsl_pci: fix inbound ATMU entries for systems with >4G RAM

For systems with >4G of RAM, the current implementation adds a second inbound PCIe window starting at 128G this leaves all memory from 4G to 128G inaccessible to inbound PCIe transactions. The according errors can be observed by using the EDAC driver for MPC85XX. This patch changes this behaviour

[RFC PATCH] powerpc: fsl_pci: fix inbound ATMU entries for systems with >4G RAM

For systems with >4G of RAM, the current implementation adds a second inbound PCIe window starting at 128G this leaves all memory from 4G to 128G inaccessible to inbound PCIe transactions. The according errors can be observed by using the EDAC driver for MPC85XX. This patch changes this behaviour

Re: Memory (skb) leak in kernel 4.8-rc2

On 08/21/2016 07:09 AM, Frederic Dalleau wrote: Hi Marcel, Johan, I am unable to unload module bluetooth to verify that the second leak is not a false positive; however, the one in btusb is a real memory leak. There was a bugzilla last week with that backtrace:

Re: Memory (skb) leak in kernel 4.8-rc2

On 08/21/2016 07:09 AM, Frederic Dalleau wrote: Hi Marcel, Johan, I am unable to unload module bluetooth to verify that the second leak is not a false positive; however, the one in btusb is a real memory leak. There was a bugzilla last week with that backtrace:

[PATCH 2/6 linux-next] ext4: remove unneeded test in ext4_alloc_file_blocks()

ext4_alloc_file_blocks() is called from ext4_zero_range() and ext4_fallocate() both already testing EXT4_INODE_EXTENTS We can call ext_depth(inode) unconditionnally. Signed-off-by: Fabian Frederick --- fs/ext4/extents.c | 8 +--- 1 file changed, 1 insertion(+), 7

Re: [PATCH 3/6] x86/dumpstack: make printk_stack_address() more generally useful

On Wed, 2016-08-24 at 14:24 -0500, Josh Poimboeuf wrote: > On Wed, Aug 24, 2016 at 12:07:06PM -0700, Joe Perches wrote: > > On Wed, 2016-08-24 at 13:43 -0500, Josh Poimboeuf wrote: > > > On Wed, Aug 24, 2016 at 10:28:38AM -0700, Joe Perches wrote: > > > > On Wed, 2016-08-24 at 11:50 -0500, Josh

[GIT PULL] UML fixes for 4.8-rc4

Linus, The following changes since commit 7a1dcf6adaa7cc4b8cd93a3883267497a77b1051: Merge tag 'usercopy-v4.8-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux (2016-08-23 14:32:38 -0400) are available in the git repository at:

Re: [PATCH 01/10] reset: ath79: add driver Kconfig option

On Thursday, August 25, 2016 3:18:55 AM CEST Masahiro Yamada wrote: > Hi Arnd, > > > 2016-08-25 0:51 GMT+09:00 Arnd Bergmann : > > On Wednesday, August 24, 2016 3:28:53 PM CEST Philipp Zabel wrote: > >> if RESET_CONTROLLER > >> > >> +config RESET_ATH79 > >> + bool "AR71xx

[GIT PULL] UML fixes for 4.8-rc4

Linus, The following changes since commit 7a1dcf6adaa7cc4b8cd93a3883267497a77b1051: Merge tag 'usercopy-v4.8-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux (2016-08-23 14:32:38 -0400) are available in the git repository at:

Re: [PATCH 01/10] reset: ath79: add driver Kconfig option

On Thursday, August 25, 2016 3:18:55 AM CEST Masahiro Yamada wrote: > Hi Arnd, > > > 2016-08-25 0:51 GMT+09:00 Arnd Bergmann : > > On Wednesday, August 24, 2016 3:28:53 PM CEST Philipp Zabel wrote: > >> if RESET_CONTROLLER > >> > >> +config RESET_ATH79 > >> + bool "AR71xx Reset Driver" if

[PATCH 2/6 linux-next] ext4: remove unneeded test in ext4_alloc_file_blocks()

ext4_alloc_file_blocks() is called from ext4_zero_range() and ext4_fallocate() both already testing EXT4_INODE_EXTENTS We can call ext_depth(inode) unconditionnally. Signed-off-by: Fabian Frederick --- fs/ext4/extents.c | 8 +--- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git

Re: [PATCH 3/6] x86/dumpstack: make printk_stack_address() more generally useful

On Wed, 2016-08-24 at 14:24 -0500, Josh Poimboeuf wrote: > On Wed, Aug 24, 2016 at 12:07:06PM -0700, Joe Perches wrote: > > On Wed, 2016-08-24 at 13:43 -0500, Josh Poimboeuf wrote: > > > On Wed, Aug 24, 2016 at 10:28:38AM -0700, Joe Perches wrote: > > > > On Wed, 2016-08-24 at 11:50 -0500, Josh

[PATCH 0/6 linux-next] ext4: fix extent leaking and clean-up

Last patch of this small patchset fixes an extent path memory leak. The rest is some clean-up. Fabian Frederick (6): ext4: avoid EXT4_INODE_EXTENTS double checking ext4: remove unneeded test in ext4_alloc_file_blocks() ext4: create EXT4_MAX_BLOCKS() macro ext4: use bool for check in

[PATCH 0/6 linux-next] ext4: fix extent leaking and clean-up

Last patch of this small patchset fixes an extent path memory leak. The rest is some clean-up. Fabian Frederick (6): ext4: avoid EXT4_INODE_EXTENTS double checking ext4: remove unneeded test in ext4_alloc_file_blocks() ext4: create EXT4_MAX_BLOCKS() macro ext4: use bool for check in

[PATCH 1/6 linux-next] ext4: avoid EXT4_INODE_EXTENTS double checking

ext4_collapse_range() and ext4_insert_range() already checked inode flag at the beginning of function. Signed-off-by: Fabian Frederick --- fs/ext4/extents.c | 11 --- 1 file changed, 11 deletions(-) diff --git a/fs/ext4/extents.c b/fs/ext4/extents.c index

Re: [PATCH v6 2/2] clocksource: add J-Core timer/clocksource driver

On Wednesday, August 24, 2016 1:40:01 PM CEST Rich Felker wrote: > On Wed, Aug 24, 2016 at 06:42:05PM +0200, Daniel Lezcano wrote: > > > diff --git a/drivers/clocksource/Kconfig b/drivers/clocksource/Kconfig > > > index 5677886..3210ca5 100644 > > > --- a/drivers/clocksource/Kconfig > > > +++

[PATCH 1/6 linux-next] ext4: avoid EXT4_INODE_EXTENTS double checking

ext4_collapse_range() and ext4_insert_range() already checked inode flag at the beginning of function. Signed-off-by: Fabian Frederick --- fs/ext4/extents.c | 11 --- 1 file changed, 11 deletions(-) diff --git a/fs/ext4/extents.c b/fs/ext4/extents.c index d7ccb7f..5d9f99a 100644 ---

Re: [PATCH v6 2/2] clocksource: add J-Core timer/clocksource driver

On Wednesday, August 24, 2016 1:40:01 PM CEST Rich Felker wrote: > On Wed, Aug 24, 2016 at 06:42:05PM +0200, Daniel Lezcano wrote: > > > diff --git a/drivers/clocksource/Kconfig b/drivers/clocksource/Kconfig > > > index 5677886..3210ca5 100644 > > > --- a/drivers/clocksource/Kconfig > > > +++

[PATCH 4/6 linux-next] ext4: use bool for check in ext4_ext_space_()

check is used in 0/1 context. Also use unsigned int instead of unsigned (checkpatch warning) Signed-off-by: Fabian Frederick --- fs/ext4/extents.c | 33 ++--- 1 file changed, 18 insertions(+), 15 deletions(-) diff --git a/fs/ext4/extents.c

[PATCH 5/6 linux-next] ext4: remove unused definition

MAX_32_NUM isn't used in ext4 Signed-off-by: Fabian Frederick --- fs/ext4/ioctl.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/fs/ext4/ioctl.c b/fs/ext4/ioctl.c index 10686fd..5a708c87 100644 --- a/fs/ext4/ioctl.c +++ b/fs/ext4/ioctl.c @@ -19,8 +19,6 @@ #include

[PATCH 4/6 linux-next] ext4: use bool for check in ext4_ext_space_()

check is used in 0/1 context. Also use unsigned int instead of unsigned (checkpatch warning) Signed-off-by: Fabian Frederick --- fs/ext4/extents.c | 33 ++--- 1 file changed, 18 insertions(+), 15 deletions(-) diff --git a/fs/ext4/extents.c b/fs/ext4/extents.c index

[PATCH 5/6 linux-next] ext4: remove unused definition

MAX_32_NUM isn't used in ext4 Signed-off-by: Fabian Frederick --- fs/ext4/ioctl.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/fs/ext4/ioctl.c b/fs/ext4/ioctl.c index 10686fd..5a708c87 100644 --- a/fs/ext4/ioctl.c +++ b/fs/ext4/ioctl.c @@ -19,8 +19,6 @@ #include "ext4_jbd2.h" #include

[PATCH 6/6 linux-next] ext4: fix memory leak in ext4_insert_range()

Running xfstests generic/013 with kmemleak gives the following: unreferenced object 0x8801d3d27de0 (size 96): comm "fsstress", pid 4941, jiffies 4294860168 (age 53.485s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00

[PATCH 3/6 linux-next] ext4: create EXT4_MAX_BLOCKS() macro

Create a macro to calculate length + offset -> maximum blocks This adds more readability. Signed-off-by: Fabian Frederick --- fs/ext4/ext4.h| 3 +++ fs/ext4/extents.c | 15 +++ fs/ext4/file.c| 3 +-- 3 files changed, 7 insertions(+), 14 deletions(-) diff

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