[PATCH] media: fix media_device_unregister() to destroy media device device resource

When all drivers except usb-core driver is unbound, destroy the media device resource. Other wise, media device resource will persist in a defunct state. This leads to use-after-free and bad access errors during a subsequent bind. Fix it to destroy the media device resource when last reference is

[PATCH] media: fix media_device_unregister() to destroy media device device resource

When all drivers except usb-core driver is unbound, destroy the media device resource. Other wise, media device resource will persist in a defunct state. This leads to use-after-free and bad access errors during a subsequent bind. Fix it to destroy the media device resource when last reference is

Re: [PATCH RFC] block: fix bio merge checks when virt_boundary is set

On Wed, Mar 16, 2016 at 05:26:28PM +0100, Vitaly Kuznetsov wrote: > Ming Lei writes: > > We do have the above merge in bio_add_page(), so the two bios in > > your above example shouldn't have been observed if the two buffers > > are added to bio via the bio_add_page(). > >

Re: [PATCH RFC] block: fix bio merge checks when virt_boundary is set

On Wed, Mar 16, 2016 at 05:26:28PM +0100, Vitaly Kuznetsov wrote: > Ming Lei writes: > > We do have the above merge in bio_add_page(), so the two bios in > > your above example shouldn't have been observed if the two buffers > > are added to bio via the bio_add_page(). > > > > If you see short

Re: 4.5.0+ panic when setup loop device

On Fri, Mar 18, 2016 at 05:11:54AM +0100, Mike Galbraith wrote: > On Thu, 2016-03-17 at 10:52 +0100, Peter Zijlstra wrote: > > > Andreas; Borislav said to Cc you since you wrote all this. > > The issue is that Linux assumes: > > > > > nr_logical_cpus = nr_cores * nr_siblings > > It also

Re: 4.5.0+ panic when setup loop device

On Fri, Mar 18, 2016 at 05:11:54AM +0100, Mike Galbraith wrote: > On Thu, 2016-03-17 at 10:52 +0100, Peter Zijlstra wrote: > > > Andreas; Borislav said to Cc you since you wrote all this. > > The issue is that Linux assumes: > > > > > nr_logical_cpus = nr_cores * nr_siblings > > It also

Re: [PATCH] Staging: rtl8192e: fix line length coding style issue in rtllib_softmac.c

On Fri, Mar 18, 2016 at 10:54:42AM +, Yousof El-Sayed wrote: > This is a patch to the rtllib_softmac.c file that fixes up all instances of > the 'line over 80 characters' warnings found by the checkpatch.pl tool Your changelog should be wrapped, ironic given the contents of your patch :(

Re: [PATCH] Staging: rtl8192e: fix line length coding style issue in rtllib_softmac.c

On Fri, Mar 18, 2016 at 10:54:42AM +, Yousof El-Sayed wrote: > This is a patch to the rtllib_softmac.c file that fixes up all instances of > the 'line over 80 characters' warnings found by the checkpatch.pl tool Your changelog should be wrapped, ironic given the contents of your patch :(

Re: [PATCH] regulator: Rename files for Maxim PMIC drivers

Hi Javier, On 2016년 03월 18일 02:54, Javier Martinez Canillas wrote: > Most Maxim PMIC regulator drivers are for sub-devices of Multi-Function > Devices with drivers under drivers/mfd. But for many of these, the same > object file name was used for both the MFD and the regulator drivers. > >

Re: [PATCH] regulator: Rename files for Maxim PMIC drivers

Hi Javier, On 2016년 03월 18일 02:54, Javier Martinez Canillas wrote: > Most Maxim PMIC regulator drivers are for sub-devices of Multi-Function > Devices with drivers under drivers/mfd. But for many of these, the same > object file name was used for both the MFD and the regulator drivers. > >

[PATCH 14/15] dt-bindings: arm-gic: Drop 'clock-names' from binding document

Commit afbbd2338176 ("irqchip/gic: Document optional Clock and Power Domain properties") documented optional clock and power-dmoain properties for the ARM GIC. Currently, there are no users of these and for the Tegra210 Audio GIC (based upon the GIC-400) there are two clocks, a functional clock

Re: [PATCH v4 7/7] cpufreq: schedutil: New governor based on scheduler utilization data

On Wednesday, March 16, 2016 07:14:20 PM Peter Zijlstra wrote: > On Wed, Mar 16, 2016 at 03:59:18PM +0100, Rafael J. Wysocki wrote: > > +static void sugov_update_commit(struct sugov_policy *sg_policy, u64 time, > > + unsigned int next_freq) > > +{ > > + struct

Re: [PATCH 1/3] dt-bindings: Add binding docs for V3D.

On Fri, Mar 04, 2016 at 12:32:06PM -0800, Eric Anholt wrote: > This was missed in the upstreaming process. > > Signed-off-by: Eric Anholt > --- > Documentation/devicetree/bindings/display/brcm,bcm-vc4.txt | 12 > 1 file changed, 12 insertions(+) Acked-by: Rob

[PATCH 14/15] dt-bindings: arm-gic: Drop 'clock-names' from binding document

Commit afbbd2338176 ("irqchip/gic: Document optional Clock and Power Domain properties") documented optional clock and power-dmoain properties for the ARM GIC. Currently, there are no users of these and for the Tegra210 Audio GIC (based upon the GIC-400) there are two clocks, a functional clock

Re: [PATCH v4 7/7] cpufreq: schedutil: New governor based on scheduler utilization data

On Wednesday, March 16, 2016 07:14:20 PM Peter Zijlstra wrote: > On Wed, Mar 16, 2016 at 03:59:18PM +0100, Rafael J. Wysocki wrote: > > +static void sugov_update_commit(struct sugov_policy *sg_policy, u64 time, > > + unsigned int next_freq) > > +{ > > + struct

Re: [PATCH 1/3] dt-bindings: Add binding docs for V3D.

On Fri, Mar 04, 2016 at 12:32:06PM -0800, Eric Anholt wrote: > This was missed in the upstreaming process. > > Signed-off-by: Eric Anholt > --- > Documentation/devicetree/bindings/display/brcm,bcm-vc4.txt | 12 > 1 file changed, 12 insertions(+) Acked-by: Rob Herring

[PATCH 12/15] irqchip/gic: Pass GIC pointer to save/restore functions

Instead of passing the GIC index to the save/restore functions pass a pointer to the GIC chip data. This will allow these save/restore functions to be re-used by a platform driver where the GIC chip data structure is allocated dynamically and so there is no applicable index for identifying the

Re: [PATCH 2/2] x86/mtrr: Refactor PAT initialization code

On Mar 17, 2016 2:04 PM, "Toshi Kani" wrote: > > On Wed, 2016-03-16 at 00:29 +0100, Luis R. Rodriguez wrote: > > On Tue, Mar 15, 2016 at 05:48:44PM -0600, Toshi Kani wrote: > > > On Tue, 2016-03-15 at 01:15 +0100, Luis R. Rodriguez wrote: > > > > On Fri, Mar 11, 2016 at

[PATCH 12/15] irqchip/gic: Pass GIC pointer to save/restore functions

Instead of passing the GIC index to the save/restore functions pass a pointer to the GIC chip data. This will allow these save/restore functions to be re-used by a platform driver where the GIC chip data structure is allocated dynamically and so there is no applicable index for identifying the

Re: [PATCH 2/2] x86/mtrr: Refactor PAT initialization code

On Mar 17, 2016 2:04 PM, "Toshi Kani" wrote: > > On Wed, 2016-03-16 at 00:29 +0100, Luis R. Rodriguez wrote: > > On Tue, Mar 15, 2016 at 05:48:44PM -0600, Toshi Kani wrote: > > > On Tue, 2016-03-15 at 01:15 +0100, Luis R. Rodriguez wrote: > > > > On Fri, Mar 11, 2016 at 06:16:36PM -0700, Toshi

Re: [PATCH 14/15] dt-bindings: arm-gic: Drop 'clock-names' from binding document

Hi Jon, On Fri, Mar 18, 2016 at 11:13 AM, Jon Hunter wrote: > On 18/03/16 09:13, Geert Uytterhoeven wrote: >> On Thu, Mar 17, 2016 at 3:19 PM, Jon Hunter wrote: >>> Commit afbbd2338176 ("irqchip/gic: Document optional Clock and Power >>> Domain

Re: [PATCH 14/15] dt-bindings: arm-gic: Drop 'clock-names' from binding document

Hi Jon, On Fri, Mar 18, 2016 at 11:13 AM, Jon Hunter wrote: > On 18/03/16 09:13, Geert Uytterhoeven wrote: >> On Thu, Mar 17, 2016 at 3:19 PM, Jon Hunter wrote: >>> Commit afbbd2338176 ("irqchip/gic: Document optional Clock and Power >>> Domain properties") documented optional clock and

[PATCH 3.19.y-ckt 04/70] cfg80211/wext: fix message ordering

v3.19.8-ckt17 -stable review patch. If anyone has any objections, please let me know. ---8< From: Johannes Berg commit cb150b9d23be6ee7f3a0fff29784f1c5b5ac514d upstream. Since cfg80211 frequently takes

[PATCH 3.19.y-ckt 04/70] cfg80211/wext: fix message ordering

v3.19.8-ckt17 -stable review patch. If anyone has any objections, please let me know. ---8< From: Johannes Berg commit cb150b9d23be6ee7f3a0fff29784f1c5b5ac514d upstream. Since cfg80211 frequently takes actions from its netdev

Re: [PATCH] driver: input :touchscreen : add Raydium I2C touch driver

On Tue, Mar 15, 2016 at 04:44:17PM +0800, jeffrey.lin wrote: > Raydium I2C touch driver. > > Signed-off-by: jeffrey.lin > --- > .../devicetree/bindings/input/raydium_i2c_ts.txt | 23 + > .../devicetree/bindings/vendor-prefixes.txt| 1 + It is generally

Re: [PATCH] driver: input :touchscreen : add Raydium I2C touch driver

On Tue, Mar 15, 2016 at 04:44:17PM +0800, jeffrey.lin wrote: > Raydium I2C touch driver. > > Signed-off-by: jeffrey.lin > --- > .../devicetree/bindings/input/raydium_i2c_ts.txt | 23 + > .../devicetree/bindings/vendor-prefixes.txt| 1 + It is generally preferred to split bindings

[PATCH 3/5] thermal: x86_pkg_temp: Handle the FROZEN hot plug notifier actions.

When performing a suspend operation, the kernel brings all of the non-boot CPUs offline, calling the hot plug notifiers with the flag, CPU_TASKS_FROZEN, set in the action code. Similarly, during resume, the CPUs are brought back online, but again the notifiers have the FROZEN flag set. While

[PATCH 3/5] thermal: x86_pkg_temp: Handle the FROZEN hot plug notifier actions.

When performing a suspend operation, the kernel brings all of the non-boot CPUs offline, calling the hot plug notifiers with the flag, CPU_TASKS_FROZEN, set in the action code. Similarly, during resume, the CPUs are brought back online, but again the notifiers have the FROZEN flag set. While

[PATCH] x86: Avoid undefined behavior in macro expansion

C11 standard (at 6.10.3.3) says that ## operator (paste) has undefined behavior when one of the result operands is not a valid preprocessing token. Therefore the macro expansion may depend on compiler implementation which may or no preserve the leading white space. Moreover other places in

[PATCH] x86: Avoid undefined behavior in macro expansion

C11 standard (at 6.10.3.3) says that ## operator (paste) has undefined behavior when one of the result operands is not a valid preprocessing token. Therefore the macro expansion may depend on compiler implementation which may or no preserve the leading white space. Moreover other places in

[PATCH RFC 0/2] pxa_camera transition to v4l2 standalone device

Hi Hans and Guennadi, As Hans is converting sh_mobile_ceu_camera.c, let's see how close our ports are to see if there are things we could either reuse of change. The port is assuming : - the formation translation is transferred into soc_mediabus, so that it can be reused across all v4l2

[PATCH RFC 2/2] media: platform: pxa_camera: make a standalone v4l2 device

This patch removes the soc_camera API dependency from pxa_camera. In the current status : - all previously captures are working the same on pxa270 - the s_crop() call was removed, judged not working (see what happens soc_camera_s_crop() when get_crop() == NULL) - if the pixel clock is

[PATCH RFC 1/2] media: platform: transfer format translations to soc_mediabus

Transfer the formats translations to soc_mediabus. Even is soc_camera was to be deprecated, soc_mediabus will survive, and should describe all that happens on the bus connecting the image processing unit of the SoC and the sensor. The translation engine provides an easy way to compute the formats

[PATCH RFC 0/2] pxa_camera transition to v4l2 standalone device

Hi Hans and Guennadi, As Hans is converting sh_mobile_ceu_camera.c, let's see how close our ports are to see if there are things we could either reuse of change. The port is assuming : - the formation translation is transferred into soc_mediabus, so that it can be reused across all v4l2

[PATCH RFC 2/2] media: platform: pxa_camera: make a standalone v4l2 device

This patch removes the soc_camera API dependency from pxa_camera. In the current status : - all previously captures are working the same on pxa270 - the s_crop() call was removed, judged not working (see what happens soc_camera_s_crop() when get_crop() == NULL) - if the pixel clock is

[PATCH RFC 1/2] media: platform: transfer format translations to soc_mediabus

Transfer the formats translations to soc_mediabus. Even is soc_camera was to be deprecated, soc_mediabus will survive, and should describe all that happens on the bus connecting the image processing unit of the SoC and the sensor. The translation engine provides an easy way to compute the formats

Re: [PATCH v3] Fix OpenSSH pty regression on close

On Sat, Mar 19, 2016 at 01:40:21PM -0700, Brian Bloniarz wrote: > Hi, I haven't heard anything after sending this latest patch -- is there > anything I can do to help get this fixed? I wanted to get an ack or reviewed-by from Peter before applying it, and now the merge window is closed so I can't

Re: [PATCH v3] Fix OpenSSH pty regression on close

On Sat, Mar 19, 2016 at 01:40:21PM -0700, Brian Bloniarz wrote: > Hi, I haven't heard anything after sending this latest patch -- is there > anything I can do to help get this fixed? I wanted to get an ack or reviewed-by from Peter before applying it, and now the merge window is closed so I can't

Re: [PATCH v3] Fix OpenSSH pty regression on close

Hi, I haven't heard anything after sending this latest patch -- is there anything I can do to help get this fixed? Thanks and kind regards, -Brian

Re: [PATCH v3] Fix OpenSSH pty regression on close

Hi, I haven't heard anything after sending this latest patch -- is there anything I can do to help get this fixed? Thanks and kind regards, -Brian

[GIT PULL] DeviceTree updates for 4.6

Hi Linus, Please pull DeviceTree updates for 4.6. Details below. Rob The following changes since commit 92e963f50fc74041b5e9e744c330dca48e04f08d: Linux 4.5-rc1 (2016-01-24 13:06:47 -0800) are available in the git repository at:

[GIT PULL] DeviceTree updates for 4.6

Hi Linus, Please pull DeviceTree updates for 4.6. Details below. Rob The following changes since commit 92e963f50fc74041b5e9e744c330dca48e04f08d: Linux 4.5-rc1 (2016-01-24 13:06:47 -0800) are available in the git repository at:

[PATCH 00/15] Add support for Tegra210 AGIC

The Tegra210 AGIC interrupt controller is a 2nd level interrupt controller located in a separate power domain to the main GIC interrupt controller. It can route interrupts to the main CPU cluster or an Audio DSP slave. This series only support routing interrupts to the main CPU cluster. Ideally

[PATCH 00/15] Add support for Tegra210 AGIC

The Tegra210 AGIC interrupt controller is a 2nd level interrupt controller located in a separate power domain to the main GIC interrupt controller. It can route interrupts to the main CPU cluster or an Audio DSP slave. This series only support routing interrupts to the main CPU cluster. Ideally

[PATCH v2 3/3] ARM: OMAP3: hwmod data: Merge and remove the McBSP sidetone related data

McBSP2 and 3 have integrated sidetone block. The sidetone alone can not operate, can not be enabled separately from the McBSP it is attached to. The sidetone is enabled via McBSP register(s) and it is using the McBSP module's iclk as clock. While the sidetone block of McBSP does have it's

[PATCH v2 3/3] ARM: OMAP3: hwmod data: Merge and remove the McBSP sidetone related data

McBSP2 and 3 have integrated sidetone block. The sidetone alone can not operate, can not be enabled separately from the McBSP it is attached to. The sidetone is enabled via McBSP register(s) and it is using the McBSP module's iclk as clock. While the sidetone block of McBSP does have it's

Re: [PATCH v9 2/3] kernel.h: add to_user_ptr()

On Thu, Mar 17, 2016 at 5:19 PM, Gustavo Padovan wrote: > 2016-03-17 Joe Perches : > >> On Thu, 2016-03-17 at 16:50 -0400, Rob Clark wrote: >> > On Thu, Mar 17, 2016 at 4:40 PM, Joe Perches wrote: >> [] >> > > It's a name that seems like

Re: [PATCH v9 2/3] kernel.h: add to_user_ptr()

On Thu, Mar 17, 2016 at 5:19 PM, Gustavo Padovan wrote: > 2016-03-17 Joe Perches : > >> On Thu, 2016-03-17 at 16:50 -0400, Rob Clark wrote: >> > On Thu, Mar 17, 2016 at 4:40 PM, Joe Perches wrote: >> [] >> > > It's a name that seems like it should be a straightforward >> > > cast of a kernel

Re: [PATCH] ARC: build: Turn off -Wmaybe-uninitialized for ARC gcc 4.8

On Friday 18 March 2016 05:43 PM, Arnd Bergmann wrote: > I think it's dangerous to use -O3 in one architecture when nothing else > uses it. If you don't have a strong reason to use -O3, maybe just drop that > use the default -O2 -Wmaybe-uninitialized like everyone else does. I know what u mean.

Re: [PATCH] ARC: build: Turn off -Wmaybe-uninitialized for ARC gcc 4.8

On Friday 18 March 2016 05:43 PM, Arnd Bergmann wrote: > I think it's dangerous to use -O3 in one architecture when nothing else > uses it. If you don't have a strong reason to use -O3, maybe just drop that > use the default -O2 -Wmaybe-uninitialized like everyone else does. I know what u mean.

[PATCH v7 2/4] gadget: Support for the usb charger framework

For supporting the usb charger, it adds the usb_charger_init() and usb_charger_exit() functions for usb charger initialization and exit. It will report to the usb charger when the gadget state is changed, then the usb charger can do the power things. Introduce a callback 'get_charger_type' which

Re: [PATCH] scsi: ufs: select CONFIG_NLS

> "Arnd" == Arnd Bergmann writes: Arnd> A recent change to ufshcd introduced a call to utf16s_to_utf8s, a Arnd> function that is provided by the NLS module, so we get a link Arnd> error when that is not present: Applied to 4.6/scsi-fixes. -- Martin K. Petersen Oracle

[PATCH v7 2/4] gadget: Support for the usb charger framework

For supporting the usb charger, it adds the usb_charger_init() and usb_charger_exit() functions for usb charger initialization and exit. It will report to the usb charger when the gadget state is changed, then the usb charger can do the power things. Introduce a callback 'get_charger_type' which

Re: [PATCH] scsi: ufs: select CONFIG_NLS

> "Arnd" == Arnd Bergmann writes: Arnd> A recent change to ufshcd introduced a call to utf16s_to_utf8s, a Arnd> function that is provided by the NLS module, so we get a link Arnd> error when that is not present: Applied to 4.6/scsi-fixes. -- Martin K. Petersen Oracle Linux

Re: [PATCH] mtd: brcmnand: Add support for v6.2 controllers

On Thu, Mar 10, 2016 at 03:34:16PM -0800, Florian Fainelli wrote: > Document and match the brcm,brcmnand-v6.2 compatible string, the controller > has > a register layout identical to the v6.0 version and supports prefetch. Update > the > command shift logic to account for v6.2 controller which

Re: [PATCH] mtd: brcmnand: Add support for v6.2 controllers

On Thu, Mar 10, 2016 at 03:34:16PM -0800, Florian Fainelli wrote: > Document and match the brcm,brcmnand-v6.2 compatible string, the controller > has > a register layout identical to the v6.0 version and supports prefetch. Update > the > command shift logic to account for v6.2 controller which

Re: [PATCH 2/2] block: create ioctl to discard-or-zeroout a range of blocks

On Thu, Mar 17, 2016 at 02:00:18PM -0700, Chris Mason wrote: > > Thinking more, my guess is that google will just keep doing what they > are already doing ;) But there could be a flag in sysfs dedicated to > trim-for-fallocate so admins can see what their devices are reporting. > readonly in

Re: [PATCH 2/2] block: create ioctl to discard-or-zeroout a range of blocks

On Thu, Mar 17, 2016 at 02:00:18PM -0700, Chris Mason wrote: > > Thinking more, my guess is that google will just keep doing what they > are already doing ;) But there could be a flag in sysfs dedicated to > trim-for-fallocate so admins can see what their devices are reporting. > readonly in

Re: [PATCH 0/5] usb: dwc3: xhci: Add quirk for defective Port Enable/disable

Mathias, Roger Quadros writes: > Some devices from Texas Instruments suffer from > a silicon bug where XHCI Port Enabled/Disabled bit > should not be used to silence an erroneous device. > > The bug is so that if port is disabled with PED > bit, an IRQ for device removal (or

Re: [PATCH 0/5] usb: dwc3: xhci: Add quirk for defective Port Enable/disable

Mathias, Roger Quadros writes: > Some devices from Texas Instruments suffer from > a silicon bug where XHCI Port Enabled/Disabled bit > should not be used to silence an erroneous device. > > The bug is so that if port is disabled with PED > bit, an IRQ for device removal (or attachment) >

Re: [PATCH 3.4 000/107] 3.4.111-rc1 review

On 2016/3/17 1:51, Guenter Roeck wrote: > On Wed, Mar 16, 2016 at 04:05:41PM +0800, l...@kernel.org wrote: >> From: Zefan Li >> >> This is the start of the stable review cycle for the 3.4.111 release. >> There are 107 patches in this series, all will be posted as a response >>

Re: [PATCH 3.4 000/107] 3.4.111-rc1 review

On 2016/3/17 1:51, Guenter Roeck wrote: > On Wed, Mar 16, 2016 at 04:05:41PM +0800, l...@kernel.org wrote: >> From: Zefan Li >> >> This is the start of the stable review cycle for the 3.4.111 release. >> There are 107 patches in this series, all will be posted as a response >> to this one. If

[PATCH v4 0/8] CPUs capacity information for heterogeneous systems

Hi all, this is take 4 of "CPUs capacity information for heterogeneous systems" patchset [1]; some context follows. ARM systems may be configured to have CPUs with different power/performance characteristics within the same chip. In this case, additional information has to be made available to

[PATCH v4 0/8] CPUs capacity information for heterogeneous systems

Hi all, this is take 4 of "CPUs capacity information for heterogeneous systems" patchset [1]; some context follows. ARM systems may be configured to have CPUs with different power/performance characteristics within the same chip. In this case, additional information has to be made available to

Re: [PATCH] mmc: sdhci-acpi: add QCOM controllers

On 3 March 2016 at 17:38, Philip Elcan wrote: > This adds the HIDs for Qualcomm Technologies Inc SDHC > controllers: > QCOM8051: non-removable device that does not support 1.8v > QCOM8052: non-removable device that does support 1.8v > > Signed-off-by: Philip Elcan

Re: [PATCH] mmc: sdhci-acpi: add QCOM controllers

On 3 March 2016 at 17:38, Philip Elcan wrote: > This adds the HIDs for Qualcomm Technologies Inc SDHC > controllers: > QCOM8051: non-removable device that does not support 1.8v > QCOM8052: non-removable device that does support 1.8v > > Signed-off-by: Philip Elcan Thanks, applied for next!

Re: [PATCH] mmc: core: remove redundant memset of sdio_read_cccr

On 14 March 2016 at 05:41, Shawn Lin wrote: > When initializing sdio card, we get struct mmc_card > from mmc_alloc_card which allocates it by kzalloc. So we > don't need another memset while reading cccr. > > Signed-off-by: Shawn Lin Thanks,

Re: [PATCH] mmc: core: remove redundant memset of sdio_read_cccr

On 14 March 2016 at 05:41, Shawn Lin wrote: > When initializing sdio card, we get struct mmc_card > from mmc_alloc_card which allocates it by kzalloc. So we > don't need another memset while reading cccr. > > Signed-off-by: Shawn Lin Thanks, applied for next! Kind regards Uffe > --- > >

Re: [PATCH v6 7/7][Update] cpufreq: schedutil: New governor based on scheduler utilization data

Hi Rafael, all, I have (yet another) consideration regarding the definition of the margin for the frequency selection. On 17-Mar 17:01, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > Subject: [PATCH] cpufreq: schedutil: New governor based on scheduler >

Re: [PATCH v6 7/7][Update] cpufreq: schedutil: New governor based on scheduler utilization data

Hi Rafael, all, I have (yet another) consideration regarding the definition of the margin for the frequency selection. On 17-Mar 17:01, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > Subject: [PATCH] cpufreq: schedutil: New governor based on scheduler > utilization data > > Add a new

Re: [PATCH v3 1/2] mm, vmstat: calculate particular vm event

On Wed, Mar 16, 2016 at 04:54:13PM +0100, Vlastimil Babka wrote: > On 03/14/2016 10:40 PM, Ebru Akagunduz wrote: > >Currently, vmstat can calculate specific vm event with all_vm_events() > >however it allocates all vm events to stack. This patch introduces > >a helper to sum value of a specific vm

Re: [PATCH v3 1/2] mm, vmstat: calculate particular vm event

On Wed, Mar 16, 2016 at 04:54:13PM +0100, Vlastimil Babka wrote: > On 03/14/2016 10:40 PM, Ebru Akagunduz wrote: > >Currently, vmstat can calculate specific vm event with all_vm_events() > >however it allocates all vm events to stack. This patch introduces > >a helper to sum value of a specific vm

[PATCH] staging: rtl8192e: fixed coding style issues

staging: rtl8192e - dot11d.c [patch 1/2] Fixed throughout: spaces preferred around that '+' (ctx:VxV) [patch 2/2] Fixed throughout: Please don't use multiple blank lines Signed-off-by: Yousof El-Sayed --- drivers/staging/rtl8192e/dot11d.c | 14 ++

[PATCH] staging: rtl8192e: fixed coding style issues

staging: rtl8192e - dot11d.c [patch 1/2] Fixed throughout: spaces preferred around that '+' (ctx:VxV) [patch 2/2] Fixed throughout: Please don't use multiple blank lines Signed-off-by: Yousof El-Sayed --- drivers/staging/rtl8192e/dot11d.c | 14 ++ 1 file changed, 6 insertions(+),

Re: [GIT PULL v4.6] MDB Linux Kernel Debugger x86/x86_64

On 3/17/16, Joe Perches wrote: > On Thu, 2016-03-17 at 23:31 -0600, Jeffrey Merkey wrote: >> On 3/16/16, Jeffrey Merkey wrote: >> > On 3/15/16, Theodore Ts'o wrote: >> > > On Tue, Mar 15, 2016 at 01:03:39PM +1100, Stephen Rothwell wrote: >>

Re: [GIT PULL v4.6] MDB Linux Kernel Debugger x86/x86_64

On 3/17/16, Joe Perches wrote: > On Thu, 2016-03-17 at 23:31 -0600, Jeffrey Merkey wrote: >> On 3/16/16, Jeffrey Merkey wrote: >> > On 3/15/16, Theodore Ts'o wrote: >> > > On Tue, Mar 15, 2016 at 01:03:39PM +1100, Stephen Rothwell wrote: >> > > > >> > > > We don't generally PGP (GPG) sign

Re: [PATCH v2 09/11] usb: ohci-da8xx: Remove code that references mach

On Wed, 16 Mar 2016, David Lechner wrote: > Including mach/* is frowned upon in device drivers, so get rid of it. > > This replaces usb20_clk and code that pokes CFGCHIP2 with a proper phy > driver. > > Signed-off-by: David Lechner > --- > > v2 changes: Uses the new phy

Re: [PATCH v2 09/11] usb: ohci-da8xx: Remove code that references mach

On Wed, 16 Mar 2016, David Lechner wrote: > Including mach/* is frowned upon in device drivers, so get rid of it. > > This replaces usb20_clk and code that pokes CFGCHIP2 with a proper phy > driver. > > Signed-off-by: David Lechner > --- > > v2 changes: Uses the new phy driver instead of

[GIT PULL] libata changes for v4.6-rc1

Hello, Linus. libata changes for v4.6-rc1. * ahci grew runtime power management support so that the controller can be turned off if no devices are attached. * sata_via isn't dead yet. It got hotplug support and more refined workaround for certain WD drives. * Misc cleanups. There's a

[GIT PULL] libata changes for v4.6-rc1

Hello, Linus. libata changes for v4.6-rc1. * ahci grew runtime power management support so that the controller can be turned off if no devices are attached. * sata_via isn't dead yet. It got hotplug support and more refined workaround for certain WD drives. * Misc cleanups. There's a

Re: [RFD] workqueue: WQ_MEM_RECLAIM usage in network drivers

Hello, Jeff. On Thu, Mar 17, 2016 at 09:32:16PM -0400, Jeff Layton wrote: > > * Are network devices expected to be able to serve as a part of > > storage stack which is depended upon for memory reclamation? > > I think they should be. Cached NFS pages can consume a lot of memory, > and

Re: [RFD] workqueue: WQ_MEM_RECLAIM usage in network drivers

Hello, Jeff. On Thu, Mar 17, 2016 at 09:32:16PM -0400, Jeff Layton wrote: > > * Are network devices expected to be able to serve as a part of > > storage stack which is depended upon for memory reclamation? > > I think they should be. Cached NFS pages can consume a lot of memory, > and

[PATCH v1 2/2] netlink: add support for NIC driver ioctls

From: David Decotigny This patch removes the requirement that ethtool be tied to the support of a specific L3 protocol (ethtool uses an AF_INET socket today). Signed-off-by: David Decotigny --- net/netlink/af_netlink.c | 10 +- 1 file changed, 9

[PATCH v1 2/2] netlink: add support for NIC driver ioctls

From: David Decotigny This patch removes the requirement that ethtool be tied to the support of a specific L3 protocol (ethtool uses an AF_INET socket today). Signed-off-by: David Decotigny --- net/netlink/af_netlink.c | 10 +- 1 file changed, 9 insertions(+), 1 deletion(-) diff

Re: [PATCH 2/2] block: create ioctl to discard-or-zeroout a range of blocks

On Wed, Mar 16 2016, Theodore Ts'o wrote: > On Wed, Mar 16, 2016 at 09:33:13AM +1100, Dave Chinner wrote: >> >> Stale data escaping containment is a security issue. Enabling >> generic kernel mechanisms to *enable containment escape* is >> fundamentally wrong, and relying on userspace to Do The

Re: [PATCH 2/2] block: create ioctl to discard-or-zeroout a range of blocks

On Wed, Mar 16 2016, Theodore Ts'o wrote: > On Wed, Mar 16, 2016 at 09:33:13AM +1100, Dave Chinner wrote: >> >> Stale data escaping containment is a security issue. Enabling >> generic kernel mechanisms to *enable containment escape* is >> fundamentally wrong, and relying on userspace to Do The

Re: Nokia N900 - audio TPA6130A2 problems

On Thursday 17 March 2016 09:56:22 Ivaylo Dimitrov wrote: > Hi, > > On 17.03.2016 02:49, Sebastian Reichel wrote: > > > >mh both, the power gpio is turned off in tpa6130a2_power(0). I guess > >if you don't see the problem during probe() everything works? > > > >I have another idea though: In

Re: Nokia N900 - audio TPA6130A2 problems

On Thursday 17 March 2016 09:56:22 Ivaylo Dimitrov wrote: > Hi, > > On 17.03.2016 02:49, Sebastian Reichel wrote: > > > >mh both, the power gpio is turned off in tpa6130a2_power(0). I guess > >if you don't see the problem during probe() everything works? > > > >I have another idea though: In

[PATCH] arm/arm64/irqchip/pci: select PCI_MSI instead of depending on it

The PCI_MSI symbol is used inconsistently throughout the tree, with some drivers using 'select' and others using 'depends on', or using conditional selects. This keeps causing problems, and the latest one is a result of ARCH_ALPINE using a 'select' statement to enable its platform specific MSI

[PATCH] arm/arm64/irqchip/pci: select PCI_MSI instead of depending on it

The PCI_MSI symbol is used inconsistently throughout the tree, with some drivers using 'select' and others using 'depends on', or using conditional selects. This keeps causing problems, and the latest one is a result of ARCH_ALPINE using a 'select' statement to enable its platform specific MSI

Re: [PATCH v2 10/18] dt-bindings: Add PLX Technology OXNAS Standard Clocks bindings

On Wed, Mar 09, 2016 at 11:24:12AM +0100, Neil Armstrong wrote: > Signed-off-by: Neil Armstrong > --- > .../devicetree/bindings/clock/plxtech,stdclk.txt | 35 > ++ > 1 file changed, 35 insertions(+) > create mode 100644

Re: [PATCH v2 10/18] dt-bindings: Add PLX Technology OXNAS Standard Clocks bindings

On Wed, Mar 09, 2016 at 11:24:12AM +0100, Neil Armstrong wrote: > Signed-off-by: Neil Armstrong > --- > .../devicetree/bindings/clock/plxtech,stdclk.txt | 35 > ++ > 1 file changed, 35 insertions(+) > create mode 100644

[PATCH 3.19.y-ckt 02/70] Input: aiptek - fix crash on detecting device without endpoints

v3.19.8-ckt17 -stable review patch. If anyone has any objections, please let me know. ---8< From: Vladis Dronov commit 8e20cf2bce122ce9262d6034ee5d5b76fbb92f96 upstream. The aiptek driver crashes in

[PATCH 3.19.y-ckt 02/70] Input: aiptek - fix crash on detecting device without endpoints

v3.19.8-ckt17 -stable review patch. If anyone has any objections, please let me know. ---8< From: Vladis Dronov commit 8e20cf2bce122ce9262d6034ee5d5b76fbb92f96 upstream. The aiptek driver crashes in aiptek_probe() when a specially

[PATCH 3.19.y-ckt 18/70] iommu/amd: Apply workaround for ATS write permission check

v3.19.8-ckt17 -stable review patch. If anyone has any objections, please let me know. ---8< From: Jay Cornwall commit 358875fd52ab8f00f66328cbf1a1d2486f265829 upstream. The AMD Family 15h Models 30h-3Fh (Kaveri)

[PATCH 0/5] usb: dwc3: xhci: Add quirk for defective Port Enable/disable

Hi, Some devices from Texas Instruments suffer from a silicon bug where XHCI Port Enabled/Disabled bit should not be used to silence an erroneous device. The bug is so that if port is disabled with PED bit, an IRQ for device removal (or attachment) will never fire. Just for the sake of

Re: [PATCH] scsi: fc: use get/put_unaligned64 for wwn access

> "Arnd" == Arnd Bergmann writes: Arnd> A bug in the gcc-6.0 prerelease version caused at least one driver Arnd> (lpfc) to have excessive stack usage when dealing with wwn data, Arnd> on the ARM architecture. Applied to 4.6/scsi-fixes. -- Martin K. Petersen Oracle

[PATCH 3.19.y-ckt 18/70] iommu/amd: Apply workaround for ATS write permission check

v3.19.8-ckt17 -stable review patch. If anyone has any objections, please let me know. ---8< From: Jay Cornwall commit 358875fd52ab8f00f66328cbf1a1d2486f265829 upstream. The AMD Family 15h Models 30h-3Fh (Kaveri) BIOS and Kernel

[PATCH 0/5] usb: dwc3: xhci: Add quirk for defective Port Enable/disable

Hi, Some devices from Texas Instruments suffer from a silicon bug where XHCI Port Enabled/Disabled bit should not be used to silence an erroneous device. The bug is so that if port is disabled with PED bit, an IRQ for device removal (or attachment) will never fire. Just for the sake of

Re: [PATCH] scsi: fc: use get/put_unaligned64 for wwn access

> "Arnd" == Arnd Bergmann writes: Arnd> A bug in the gcc-6.0 prerelease version caused at least one driver Arnd> (lpfc) to have excessive stack usage when dealing with wwn data, Arnd> on the ARM architecture. Applied to 4.6/scsi-fixes. -- Martin K. Petersen Oracle Linux Engineering

<    5   6   7   8   9   10   11   12   13   14   >