Re: [PATCH v2] phy: sun4i: check PMU presence when poking unknown bit of pmu

On Friday 28 October 2016 11:45 PM, Hans de Goede wrote: > Hi, > > On 28-10-16 18:27, Icenowy Zheng wrote: >> Allwinner SoC's PHY 0, when used as OTG controller, have no pmu part. >> The code that poke some unknown bit of PMU for H3/A64 didn't check >> the PHY, and will cause kernel oops when

Re: [PATCH v2] phy: sun4i: check PMU presence when poking unknown bit of pmu

On Friday 28 October 2016 11:45 PM, Hans de Goede wrote: > Hi, > > On 28-10-16 18:27, Icenowy Zheng wrote: >> Allwinner SoC's PHY 0, when used as OTG controller, have no pmu part. >> The code that poke some unknown bit of PMU for H3/A64 didn't check >> the PHY, and will cause kernel oops when

Re: [PATCH] phy-rockchip-pcie: remove deassert of phy_rst from exit callback

On Friday 28 October 2016 02:01 PM, Heiko Stuebner wrote: > Am Donnerstag, 13. Oktober 2016, 12:42:13 CEST schrieb Shawn Lin: >> The deassert of phy_rst from exit callback is incorrect as when >> doing phy_exit, we expect the phy_rst is on asserted state which was >> done by power_off callback,

Re: [PATCH] phy-rockchip-pcie: remove deassert of phy_rst from exit callback

On Friday 28 October 2016 02:01 PM, Heiko Stuebner wrote: > Am Donnerstag, 13. Oktober 2016, 12:42:13 CEST schrieb Shawn Lin: >> The deassert of phy_rst from exit callback is incorrect as when >> doing phy_exit, we expect the phy_rst is on asserted state which was >> done by power_off callback,

Re: [PATCH V3 0/6] ARM64: Uprobe support added

On Saturday 05 November 2016 12:16 AM, Catalin Marinas wrote: On Fri, Nov 04, 2016 at 11:49:51AM -0600, Catalin Marinas wrote: On Wed, Nov 02, 2016 at 02:40:40PM +0530, Pratyush Anand wrote: Pratyush Anand (6): arm64: kprobe: protect/rename few definitions to be reused by uprobe arm64:

Re: [PATCH V3 0/6] ARM64: Uprobe support added

On Saturday 05 November 2016 12:16 AM, Catalin Marinas wrote: On Fri, Nov 04, 2016 at 11:49:51AM -0600, Catalin Marinas wrote: On Wed, Nov 02, 2016 at 02:40:40PM +0530, Pratyush Anand wrote: Pratyush Anand (6): arm64: kprobe: protect/rename few definitions to be reused by uprobe arm64:

Re: [PATCH v2 2/3] phy: da8xx-usb: rename the ohci device to ohci-da8xx

On Thursday 03 November 2016 09:33 PM, Axel Haslam wrote: > The ohci device name has changed in the board configuraion files, > hence, change the phy lookup table to match the new name. > > Signed-off-by: Axel Haslam merged, thanks. -Kishon > --- >

Re: [PATCH v2 2/3] phy: da8xx-usb: rename the ohci device to ohci-da8xx

On Thursday 03 November 2016 09:33 PM, Axel Haslam wrote: > The ohci device name has changed in the board configuraion files, > hence, change the phy lookup table to match the new name. > > Signed-off-by: Axel Haslam merged, thanks. -Kishon > --- > drivers/phy/phy-da8xx-usb.c | 5 +++-- > 1

Re: [RFC 0/8] Define coherent device memory node

On 10/25/2016 09:56 AM, Aneesh Kumar K.V wrote: > I looked at the hmm-v13 w.r.t migration and I guess some form of device > callback/acceleration during migration is something we should definitely > have. I still haven't figured out how non addressable and coherent device > memory can fit together

Re: [RFC 0/8] Define coherent device memory node

On 10/25/2016 09:56 AM, Aneesh Kumar K.V wrote: > I looked at the hmm-v13 w.r.t migration and I guess some form of device > callback/acceleration during migration is something we should definitely > have. I still haven't figured out how non addressable and coherent device > memory can fit together

Re: redraw issues on i915 since 4.9-rc

> It won't apply directly, but you could try testing that commit and its > parent to see if my hunch was correct. Unfortunately parent commit was also ok. I am trying to bisect, but somehow git tells me something about "...merge commit..." - will see how it goes. Norbert -- PREINING Norbert +

Re: redraw issues on i915 since 4.9-rc

> It won't apply directly, but you could try testing that commit and its > parent to see if my hunch was correct. Unfortunately parent commit was also ok. I am trying to bisect, but somehow git tells me something about "...merge commit..." - will see how it goes. Norbert -- PREINING Norbert +

task isolation discussion at Linux Plumbers

A bunch of people got together this week at the Linux Plumbers Conference to discuss nohz_full, task isolation, and related stuff. (Thanks to Thomas for getting everyone gathered at one place and time!) Here are the notes I took; I welcome any corrections and follow-up. == rcu_nocbs == We

task isolation discussion at Linux Plumbers

A bunch of people got together this week at the Linux Plumbers Conference to discuss nohz_full, task isolation, and related stuff. (Thanks to Thomas for getting everyone gathered at one place and time!) Here are the notes I took; I welcome any corrections and follow-up. == rcu_nocbs == We

Re: [PATCH 4/7] mm: defer vmalloc from atomic context

On Mon, Oct 24, 2016 at 8:44 AM, Andrey Ryabinin wrote: > > > On 10/22/2016 06:17 PM, Christoph Hellwig wrote: >> We want to be able to use a sleeping lock for freeing vmap to keep >> latency down. For this we need to use the deferred vfree mechanisms >> no only from

Re: [PATCH 4/7] mm: defer vmalloc from atomic context

On Mon, Oct 24, 2016 at 8:44 AM, Andrey Ryabinin wrote: > > > On 10/22/2016 06:17 PM, Christoph Hellwig wrote: >> We want to be able to use a sleeping lock for freeing vmap to keep >> latency down. For this we need to use the deferred vfree mechanisms >> no only from interrupt, but from any

Re: [PATCH 2/3] ARM: cache-uniphier: refactor jump label to follow coding style guideline

2016-11-04 22:32 GMT+09:00 Russell King - ARM Linux : > On Fri, Nov 04, 2016 at 09:50:56PM +0900, Masahiro Yamada wrote: >> Hi Russell, >> >> 2016-11-04 21:23 GMT+09:00 Russell King - ARM Linux : >> > On Fri, Nov 04, 2016 at 08:43:35PM +0900, Masahiro

Re: [PATCH 2/3] ARM: cache-uniphier: refactor jump label to follow coding style guideline

2016-11-04 22:32 GMT+09:00 Russell King - ARM Linux : > On Fri, Nov 04, 2016 at 09:50:56PM +0900, Masahiro Yamada wrote: >> Hi Russell, >> >> 2016-11-04 21:23 GMT+09:00 Russell King - ARM Linux : >> > On Fri, Nov 04, 2016 at 08:43:35PM +0900, Masahiro Yamada wrote: >> >> Documentation/CodingStyle

[PATCH v2 2/2] Revert "f2fs: do not recover from previous remained wrong dnodes"

From: Chao Yu i_times of inode will be set with current system time which can be configured through 'date', so it's not safe to judge dnode block as garbage data or unchanged inode depend on i_times. Now, we have used enhanced 'cp_ver + cp' crc method to verify valid dnode

[PATCH v2 2/2] Revert "f2fs: do not recover from previous remained wrong dnodes"

From: Chao Yu i_times of inode will be set with current system time which can be configured through 'date', so it's not safe to judge dnode block as garbage data or unchanged inode depend on i_times. Now, we have used enhanced 'cp_ver + cp' crc method to verify valid dnode block, so I expect

Re: [PATCH 2/2] f2fs: don't skip recovering inode depend on i_times

On 2016/11/5 6:53, Jaegeuk Kim wrote: > On Fri, Nov 04, 2016 at 04:30:09PM +0800, Chao Yu wrote: >> On 2016/11/4 2:02, Jaegeuk Kim wrote: >>> On Fri, Nov 04, 2016 at 12:26:56AM +0800, Chao Yu wrote: From: Chao Yu i_times of inode will be set with current system

Re: [PATCH 2/2] f2fs: don't skip recovering inode depend on i_times

On 2016/11/5 6:53, Jaegeuk Kim wrote: > On Fri, Nov 04, 2016 at 04:30:09PM +0800, Chao Yu wrote: >> On 2016/11/4 2:02, Jaegeuk Kim wrote: >>> On Fri, Nov 04, 2016 at 12:26:56AM +0800, Chao Yu wrote: From: Chao Yu i_times of inode will be set with current system time which can be

Re: [PATCH] include/linux/rtmutex.h: NOOP rt_mutex_destroy if !CONFIG_DEBUG_RT_MUTEXES

Pinging in case this got buried. Thanks, Alex

Re: [PATCH] include/linux/rtmutex.h: NOOP rt_mutex_destroy if !CONFIG_DEBUG_RT_MUTEXES

Pinging in case this got buried. Thanks, Alex

Re: [GIT PULL] overlayfs fixes for 4.9-rc3

On Fri, Nov 4, 2016 at 2:30 AM, Miklos Szeredi wrote: > > Also introduce the concept of feature flags to allow backward incompatible > changes to the overlay format. This should have been there from day one; the > best we can do now is backport to stable kernels. Add the

Re: [GIT PULL] overlayfs fixes for 4.9-rc3

On Fri, Nov 4, 2016 at 2:30 AM, Miklos Szeredi wrote: > > Also introduce the concept of feature flags to allow backward incompatible > changes to the overlay format. This should have been there from day one; the > best we can do now is backport to stable kernels. Add the check for features >

Re: [PATCH 1/3] tpm, tpm_vtpm_proxy: add kdoc comments for VTPM_PROXY_IOC_NEW_DEV

On Thu, Nov 03, 2016 at 05:57:50PM -0600, Jarkko Sakkinen wrote: > Added kdoc comments for VTPM_PROXY_IOC_NEW_DEV so that these can be > imported to the kernel documentation written with rst markup and > generated with Sphinx. > > Signed-off-by: Jarkko Sakkinen

Re: [PATCH 1/3] tpm, tpm_vtpm_proxy: add kdoc comments for VTPM_PROXY_IOC_NEW_DEV

On Thu, Nov 03, 2016 at 05:57:50PM -0600, Jarkko Sakkinen wrote: > Added kdoc comments for VTPM_PROXY_IOC_NEW_DEV so that these can be > imported to the kernel documentation written with rst markup and > generated with Sphinx. > > Signed-off-by: Jarkko Sakkinen Stefan, is this OK? Are you

Re: [PATCH 2/3] tpm: transition tpm_vtpm_proxy documentation to the Sphinx

On Thu, Nov 03, 2016 at 05:57:51PM -0600, Jarkko Sakkinen wrote: > Transitioned the tpm_vtpm_proxy documentation to the Sphinx > infrastructure and removed parts from the documentation that are easier > to pull from the sources. Restructured vtpm_proxy.h and tpm_vtpm_proxy.c > to be compatible

Re: [PATCH 2/3] tpm: transition tpm_vtpm_proxy documentation to the Sphinx

On Thu, Nov 03, 2016 at 05:57:51PM -0600, Jarkko Sakkinen wrote: > Transitioned the tpm_vtpm_proxy documentation to the Sphinx > infrastructure and removed parts from the documentation that are easier > to pull from the sources. Restructured vtpm_proxy.h and tpm_vtpm_proxy.c > to be compatible

Re: [PATCH v2 1/2] phy: rockchip-inno-usb2: support otg-port for rk3399

Hi Kishon, 在 2016年11月04日 01:17, Kishon Vijay Abraham I 写道: On Thursday 03 November 2016 07:36 AM, William Wu wrote: The rk3399 SoC USB2 PHY is comprised of one Host port and one OTG port. And OTG port is for USB2.0 part of USB3.0 OTG controller, as a part to construct a fully feature Type-C

Re: [PATCH v2 1/2] phy: rockchip-inno-usb2: support otg-port for rk3399

Hi Kishon, 在 2016年11月04日 01:17, Kishon Vijay Abraham I 写道: On Thursday 03 November 2016 07:36 AM, William Wu wrote: The rk3399 SoC USB2 PHY is comprised of one Host port and one OTG port. And OTG port is for USB2.0 part of USB3.0 OTG controller, as a part to construct a fully feature Type-C

Re: [PATCH 0/3] Add memremap executable mapping and extend drivers/misc/sram.c

Hi, On 27/10/2016 at 13:56:09 -0500, Dave Gerlach wrote : > There are several instances when one would want to execute out of on-chip > SRAM, such as PM code on ARM platforms, so once again revisiting this > series to allow that in a generic manner. Seems that having a solution for > allowing

Re: [PATCH 0/3] Add memremap executable mapping and extend drivers/misc/sram.c

Hi, On 27/10/2016 at 13:56:09 -0500, Dave Gerlach wrote : > There are several instances when one would want to execute out of on-chip > SRAM, such as PM code on ARM platforms, so once again revisiting this > series to allow that in a generic manner. Seems that having a solution for > allowing

Re: [f2fs-dev] [PATCH 3/3 v2] f2fs: keep dirty inodes selectively for checkpoint

On 2016/10/20 10:26, Jaegeuk Kim wrote: > Change log from v1: > o avoid performance regression > >>From b34a3d3c4c3fa2d6e000acc99bc5216a247bd6cb Mon Sep 17 00:00:00 2001 > From: Jaegeuk Kim > Date: Fri, 14 Oct 2016 11:51:23 -0700 > Subject: [PATCH] f2fs: keep dirty inodes

Re: [f2fs-dev] [PATCH 3/3 v2] f2fs: keep dirty inodes selectively for checkpoint

On 2016/10/20 10:26, Jaegeuk Kim wrote: > Change log from v1: > o avoid performance regression > >>From b34a3d3c4c3fa2d6e000acc99bc5216a247bd6cb Mon Sep 17 00:00:00 2001 > From: Jaegeuk Kim > Date: Fri, 14 Oct 2016 11:51:23 -0700 > Subject: [PATCH] f2fs: keep dirty inodes selectively for

Re: [PATCH] KVM: nVMX: add tracepoint for vmwrite

Hi Paolo, [auto build test ERROR on kvm/linux-next] [also build test ERROR on v4.9-rc3 next-20161028] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH] KVM: nVMX: add tracepoint for vmwrite

Hi Paolo, [auto build test ERROR on kvm/linux-next] [also build test ERROR on v4.9-rc3 next-20161028] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH 1/2] rtc: omap: Fix selecting external osc

On 27/10/2016 at 11:27:25 +0530, Keerthy wrote : > From: Lokesh Vutla > > RTC can be clocked from an external 32KHz oscillator, or from the > Peripheral PLL. The RTC has an internal oscillator buffer to support > direct operation with a crystal. > >

Re: [PATCH 1/2] rtc: omap: Fix selecting external osc

On 27/10/2016 at 11:27:25 +0530, Keerthy wrote : > From: Lokesh Vutla > > RTC can be clocked from an external 32KHz oscillator, or from the > Peripheral PLL. The RTC has an internal oscillator buffer to support > direct operation with a crystal. > >

[PATCH] pstore/dump: solution pstore data abort.

If not return,data abort will happen when two threads call pstore_dump at the same time. Signed-off-by: Liu Hailong Signed-off-by: Li Pengcheng Signed-off-by: Li Zhong --- fs/pstore/platform.c | 1 + 1 file changed, 1

[PATCH] pstore/dump: solution pstore data abort.

If not return,data abort will happen when two threads call pstore_dump at the same time. Signed-off-by: Liu Hailong Signed-off-by: Li Pengcheng Signed-off-by: Li Zhong --- fs/pstore/platform.c | 1 + 1 file changed, 1 insertion(+) diff --git a/fs/pstore/platform.c b/fs/pstore/platform.c

Re: How to debug DEBUG_TEST_DRIVER_REMOVE hang during loading of kernel?

On 11/04/16 13:47, Maarten Maathuis wrote: > Anyone have advice where else I can ask? > > On Sat, Oct 29, 2016 at 1:07 PM, Maarten Maathuis > wrote: >> Anyone have suggestions? Besides serial console, there are also netconsole, earlycon (probably not useful to you), and

Re: How to debug DEBUG_TEST_DRIVER_REMOVE hang during loading of kernel?

On 11/04/16 13:47, Maarten Maathuis wrote: > Anyone have advice where else I can ask? > > On Sat, Oct 29, 2016 at 1:07 PM, Maarten Maathuis > wrote: >> Anyone have suggestions? Besides serial console, there are also netconsole, earlycon (probably not useful to you), and earlyprintk. You can

[PATCH] drm: move allocation out of drm_get_format_name()

Fixes: 90844f00049e9f42573fd31d7c32e8fd31d3fd07 drm: make drm_get_format_name thread-safe Signed-off-by: Eric Engestrom [danvet: Clarify that the returned pointer must be freed with kfree().] Signed-off-by: Daniel Vetter

[PATCH] drm: move allocation out of drm_get_format_name()

Fixes: 90844f00049e9f42573fd31d7c32e8fd31d3fd07 drm: make drm_get_format_name thread-safe Signed-off-by: Eric Engestrom [danvet: Clarify that the returned pointer must be freed with kfree().] Signed-off-by: Daniel Vetter Suggested-by: Ville Syrjälä Signed-off-by: Eric

Re: Children Under Miserable Condition

Good Day, As an Aging widow with no child, suffering from long time incurable illness; presently admitted in a private hospital. I decided to give away my estate to the vulnerable through a sincere person. This is because at this point, life seems miserable for there is nobody to inherit my

Re: Children Under Miserable Condition

Good Day, As an Aging widow with no child, suffering from long time incurable illness; presently admitted in a private hospital. I decided to give away my estate to the vulnerable through a sincere person. This is because at this point, life seems miserable for there is nobody to inherit my

[GIT PULL] MD update for 4.9-rc3

Hi Linus, Please pull MD changes for 4.9-rc3. There are several bug fixes queued: - Fix raid5-cache recovery bugs - Fix discard IO error handling for raid1/10 - Fix array sync writes bogus position to superblock - Fix IO error handling for raid array with external metadata Thanks, Shaohua The

[GIT PULL] MD update for 4.9-rc3

Hi Linus, Please pull MD changes for 4.9-rc3. There are several bug fixes queued: - Fix raid5-cache recovery bugs - Fix discard IO error handling for raid1/10 - Fix array sync writes bogus position to superblock - Fix IO error handling for raid array with external metadata Thanks, Shaohua The

I Hope You Get My Message This Time

-- This is the second time i am sending you this mail.I, Friedrich Mayrhofer Donate $ 1,000,000.00 to You, Email Me personally for more details. Regards. Friedrich Mayrhofer

I Hope You Get My Message This Time

-- This is the second time i am sending you this mail.I, Friedrich Mayrhofer Donate $ 1,000,000.00 to You, Email Me personally for more details. Regards. Friedrich Mayrhofer

Re: Children Under Miserable Condition

Good Day, As an Aging widow with no child, suffering from long time incurable illness; presently admitted in a private hospital. I decided to give away my estate to the vulnerable through a sincere person. This is because at this point, life seems miserable for there is nobody to inherit my

Re: Children Under Miserable Condition

Good Day, As an Aging widow with no child, suffering from long time incurable illness; presently admitted in a private hospital. I decided to give away my estate to the vulnerable through a sincere person. This is because at this point, life seems miserable for there is nobody to inherit my

[GIT PULL] MTD updates for 4.9-rc4

Hi Linus, The following changes since commit 07d9a380680d1c0eb51ef87ff2eab5c994949e69: Linux 4.9-rc2 (2016-10-23 17:10:14 -0700) are available in the git repository at: git://git.infradead.org/linux-mtd.git tags/for-linus-20161104 for you to fetch changes up

[GIT PULL] MTD updates for 4.9-rc4

Hi Linus, The following changes since commit 07d9a380680d1c0eb51ef87ff2eab5c994949e69: Linux 4.9-rc2 (2016-10-23 17:10:14 -0700) are available in the git repository at: git://git.infradead.org/linux-mtd.git tags/for-linus-20161104 for you to fetch changes up

Re: [PATCH v8 7/7] KVM: x86: virtualize cpuid faulting

On Fri, Nov 4, 2016 at 2:57 PM, Paolo Bonzini wrote: > > On 04/11/2016 21:34, David Matlack wrote: >> On Mon, Oct 31, 2016 at 6:37 PM, Kyle Huey wrote: >>> + case MSR_PLATFORM_INFO: >>> + /* cpuid faulting is supported */ >>> +

Re: [PATCH v8 7/7] KVM: x86: virtualize cpuid faulting

On Fri, Nov 4, 2016 at 2:57 PM, Paolo Bonzini wrote: > > On 04/11/2016 21:34, David Matlack wrote: >> On Mon, Oct 31, 2016 at 6:37 PM, Kyle Huey wrote: >>> + case MSR_PLATFORM_INFO: >>> + /* cpuid faulting is supported */ >>> + msr_info->data =

[PATCH] staging: lustre: o2iblnd: replace space indentation with tabs

This patch fixes all CODE_INDENT checkpatch errors in o2iblnd. Signed-off-by: Nicholas Hanley --- .../staging/lustre/lnet/klnds/o2iblnd/o2iblnd.c| 2 +- .../staging/lustre/lnet/klnds/o2iblnd/o2iblnd_cb.c | 22 +++--- 2 files changed, 12

[PATCH] staging: lustre: o2iblnd: replace space indentation with tabs

This patch fixes all CODE_INDENT checkpatch errors in o2iblnd. Signed-off-by: Nicholas Hanley --- .../staging/lustre/lnet/klnds/o2iblnd/o2iblnd.c| 2 +- .../staging/lustre/lnet/klnds/o2iblnd/o2iblnd_cb.c | 22 +++--- 2 files changed, 12 insertions(+), 12 deletions(-) diff

Re: [PATCH v2 1/3] remoteproc: qcom: Encapsulate pvt data structure for q6v56 hexagon.

ure-for-q6v56-hexagon/20161104-220712 base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next config: arm64-allyesconfig (attached as .config) compiler: aarch64-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705 reproduce: wget https://git.kernel.org/cgit/linux/kernel/git/

Re: [PATCH v2 1/3] remoteproc: qcom: Encapsulate pvt data structure for q6v56 hexagon.

ure-for-q6v56-hexagon/20161104-220712 base: https://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git for-next config: arm64-allyesconfig (attached as .config) compiler: aarch64-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705 reproduce: wget https://git.kernel.org/cgit/linux/kernel/git/

Re: [PATCH] mm: only enable sys_pkey* when ARCH_HAS_PKEYS

On Wed, Nov 02, 2016 at 12:15:50PM -0700, Dave Hansen wrote: > On 10/31/2016 05:08 PM, Mark Rutland wrote: > > When an architecture does not select CONFIG_ARCH_HAS_PKEYS, the pkey_alloc > > syscall will return -ENOSPC for all (otherwise well-formed) requests, as the > > generic implementation of

Re: [PATCH] mm: only enable sys_pkey* when ARCH_HAS_PKEYS

On Wed, Nov 02, 2016 at 12:15:50PM -0700, Dave Hansen wrote: > On 10/31/2016 05:08 PM, Mark Rutland wrote: > > When an architecture does not select CONFIG_ARCH_HAS_PKEYS, the pkey_alloc > > syscall will return -ENOSPC for all (otherwise well-formed) requests, as the > > generic implementation of

[PATCH] drm/vc4: Use runtime autosuspend to avoid thrashing V3D power state.

The pm_runtime_put() we were using immediately released power on the device, which meant that we were generally turning the device off and on once per frame. In many profiles I've looked at, that added up to about 1% of CPU time, but this could get worse in the case of frequent rendering and

Re: [PATCH v3 1/3] dt-bindings: mediatek: Add a binding for Mediatek JPEG Decoder

Hi Rick, Thank you for the patch. On Friday 04 Nov 2016 13:51:18 Rick Chang wrote: > Add a DT binding documentation for Mediatek JPEG Decoder of > MT2701 SoC. This version looks much better ! > Signed-off-by: Rick Chang > Signed-off-by: Minghsiu Tsai

[PATCH] drm/vc4: Use runtime autosuspend to avoid thrashing V3D power state.

The pm_runtime_put() we were using immediately released power on the device, which meant that we were generally turning the device off and on once per frame. In many profiles I've looked at, that added up to about 1% of CPU time, but this could get worse in the case of frequent rendering and

Re: [PATCH v3 1/3] dt-bindings: mediatek: Add a binding for Mediatek JPEG Decoder

Hi Rick, Thank you for the patch. On Friday 04 Nov 2016 13:51:18 Rick Chang wrote: > Add a DT binding documentation for Mediatek JPEG Decoder of > MT2701 SoC. This version looks much better ! > Signed-off-by: Rick Chang > Signed-off-by: Minghsiu Tsai > --- >

Re: v4.8-rc1: thinkpad x60: running at low frequency even during kernel build

On Fri, 2016-11-04 at 23:16 +0100, Pavel Machek wrote: > Hi! > [...] > So we seem to have thermal or ACPI regression in v4.9-rc3. > It is possible. Can you add either add printk in acpi_processor_ppc_has_changed() or use ftrace and see do you get to these functions acpi_processor_ppc_init()

Re: [v17 2/2] drm/bridge: Add I2C based driver for ps8640 bridge

On Tue, Oct 25, 2016 at 6:23 AM, Matthias Brugger wrote: > > On 10/18/2016 04:37 PM, Enric Balletbo Serra wrote: > [...] >>> --- /dev/null >>> +++ b/drivers/gpu/drm/bridge/parade-ps8640.c > [...] >>> >>> + >>> +/* Firmware */ >>> +#define PS_FW_NAME

Re: v4.8-rc1: thinkpad x60: running at low frequency even during kernel build

On Fri, 2016-11-04 at 23:16 +0100, Pavel Machek wrote: > Hi! > [...] > So we seem to have thermal or ACPI regression in v4.9-rc3. > It is possible. Can you add either add printk in acpi_processor_ppc_has_changed() or use ftrace and see do you get to these functions acpi_processor_ppc_init()

Re: [v17 2/2] drm/bridge: Add I2C based driver for ps8640 bridge

On Tue, Oct 25, 2016 at 6:23 AM, Matthias Brugger wrote: > > On 10/18/2016 04:37 PM, Enric Balletbo Serra wrote: > [...] >>> --- /dev/null >>> +++ b/drivers/gpu/drm/bridge/parade-ps8640.c > [...] >>> >>> + >>> +/* Firmware */ >>> +#define PS_FW_NAME "ps864x_fw.bin" >>> + >> >> From

[PATCH] KVM: nVMX: add tracepoint for vmwrite

Both the field and the value are in registers, so they are not clear from existing tracepoints. Cc: Ladi Prosek Signed-off-by: Paolo Bonzini --- arch/x86/kvm/trace.h | 23 +++ arch/x86/kvm/vmx.c | 2 ++ 2 files changed, 25

[PATCH] KVM: nVMX: add tracepoint for vmwrite

Both the field and the value are in registers, so they are not clear from existing tracepoints. Cc: Ladi Prosek Signed-off-by: Paolo Bonzini --- arch/x86/kvm/trace.h | 23 +++ arch/x86/kvm/vmx.c | 2 ++ 2 files changed, 25 insertions(+) diff --git a/arch/x86/kvm/trace.h

[PATCH] crypto: caam: do not register AES-XTS mode on LP units

When using AES-XTS on a Wandboard, we receive a Mode error: caam_jr 2102000.jr1: 20001311: CCB: desc idx 19: AES: Mode error. Due to the Security Reference Manual, the Low Power AES units of the i.MX6 do not support the XTS mode. Therefore we should try to provide them them in the API.

[PATCH] crypto: caam: do not register AES-XTS mode on LP units

When using AES-XTS on a Wandboard, we receive a Mode error: caam_jr 2102000.jr1: 20001311: CCB: desc idx 19: AES: Mode error. Due to the Security Reference Manual, the Low Power AES units of the i.MX6 do not support the XTS mode. Therefore we should try to provide them them in the API.

Re: [PATCH 1/4] block: add scalable completion tracking of requests

On Fri, Nov 4, 2016 at 12:55 AM, Jens Axboe wrote: > On 11/03/2016 08:57 AM, Ming Lei wrote: >> >> On Thu, Nov 3, 2016 at 9:38 PM, Jens Axboe wrote: >>> >>> On 11/03/2016 05:17 AM, Ming Lei wrote: > > > diff --git a/block/blk-core.c b/block/blk-core.c

Re: [PATCH 1/4] block: add scalable completion tracking of requests

On Fri, Nov 4, 2016 at 12:55 AM, Jens Axboe wrote: > On 11/03/2016 08:57 AM, Ming Lei wrote: >> >> On Thu, Nov 3, 2016 at 9:38 PM, Jens Axboe wrote: >>> >>> On 11/03/2016 05:17 AM, Ming Lei wrote: > > > diff --git a/block/blk-core.c b/block/blk-core.c > index

Re: [PATCH 3/4] rtc: Enable compile testing for Maxim and Samsung drivers

On 02/10/2016 at 22:58:16 +0200, Krzysztof Kozlowski wrote : > max8907, max77686 and s5m RTC drivers can be compile tested to increase > build coverage. The s5m-rtc uses REGMAP_IRQ so add this as explicit > dependency. > > Signed-off-by: Krzysztof Kozlowski > --- >

Re: [PATCH 3/4] rtc: Enable compile testing for Maxim and Samsung drivers

On 02/10/2016 at 22:58:16 +0200, Krzysztof Kozlowski wrote : > max8907, max77686 and s5m RTC drivers can be compile tested to increase > build coverage. The s5m-rtc uses REGMAP_IRQ so add this as explicit > dependency. > > Signed-off-by: Krzysztof Kozlowski > --- > drivers/rtc/Kconfig | 7

Re: [PATCH v3 1/7] rtc: rtc-jz4740: Add support for the RTC in the jz4780 SoC

On 31/10/2016 at 21:39:45 +0100, Paul Cercueil wrote : > The RTC unit present in the JZ4780 works mostly the same as the one in > the JZ4740. The major difference is that register writes need to be > explicitly enabled, by writing a magic code (0xA55A) to a "write > enable" register before each

Re: [PATCH v3 1/7] rtc: rtc-jz4740: Add support for the RTC in the jz4780 SoC

On 31/10/2016 at 21:39:45 +0100, Paul Cercueil wrote : > The RTC unit present in the JZ4780 works mostly the same as the one in > the JZ4740. The major difference is that register writes need to be > explicitly enabled, by writing a magic code (0xA55A) to a "write > enable" register before each

Re: Children Under Miserable Condition

Good Day, As an Aging widow with no child, suffering from long time incurable illness; presently admitted in a private hospital. I decided to give away my estate to the vulnerable through a sincere person. This is because at this point, life seems miserable for there is nobody to inherit my

Re: Children Under Miserable Condition

Good Day, As an Aging widow with no child, suffering from long time incurable illness; presently admitted in a private hospital. I decided to give away my estate to the vulnerable through a sincere person. This is because at this point, life seems miserable for there is nobody to inherit my

Re: [PATCH V5] pinctrl: qcom: Add msm8994 pinctrl driver

On Thu, Nov 3, 2016 at 10:15 PM, Michael Scott wrote: > Initial pinctrl driver for QCOM msm8994 platforms. > > In order to continue the initial board support for QCOM msm8994/msm8992 > presented in patches from Jeremy McNicoll , let's put > a proper

Re: [PATCH V5] pinctrl: qcom: Add msm8994 pinctrl driver

On Thu, Nov 3, 2016 at 10:15 PM, Michael Scott wrote: > Initial pinctrl driver for QCOM msm8994 platforms. > > In order to continue the initial board support for QCOM msm8994/msm8992 > presented in patches from Jeremy McNicoll , let's put > a proper pinctrl driver in place. > > Currently, the DT

[PATCH 2/2] f2fs: remove checkpoint in f2fs_freeze

The generic freeze_super() calls sync_filesystems() before f2fs_freeze(). So, basically we don't need to do checkpoint in f2fs_freeze(). But, in xfs/068, it triggers circular locking problem below due to gc_mutex for checkpoint. == [ INFO:

[PATCH 2/2] f2fs: remove checkpoint in f2fs_freeze

The generic freeze_super() calls sync_filesystems() before f2fs_freeze(). So, basically we don't need to do checkpoint in f2fs_freeze(). But, in xfs/068, it triggers circular locking problem below due to gc_mutex for checkpoint. == [ INFO:

[PATCH 1/2] f2fs: assign segments correctly for direct_io

Previously, we assigned CURSEG_WARM_DATA for direct_io, but if we have two or four logs, we do not use that type at all. Let's fix it. Signed-off-by: Jaegeuk Kim --- fs/f2fs/segment.c | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git

[PATCH 1/2] f2fs: assign segments correctly for direct_io

Previously, we assigned CURSEG_WARM_DATA for direct_io, but if we have two or four logs, we do not use that type at all. Let's fix it. Signed-off-by: Jaegeuk Kim --- fs/f2fs/segment.c | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/fs/f2fs/segment.c

Re: [PATCH 2/2] f2fs: don't skip recovering inode depend on i_times

On Fri, Nov 04, 2016 at 04:30:09PM +0800, Chao Yu wrote: > On 2016/11/4 2:02, Jaegeuk Kim wrote: > > On Fri, Nov 04, 2016 at 12:26:56AM +0800, Chao Yu wrote: > >> From: Chao Yu > >> > >> i_times of inode will be set with current system time which can be > >> configured through

Re: [PATCH 2/2] f2fs: don't skip recovering inode depend on i_times

On Fri, Nov 04, 2016 at 04:30:09PM +0800, Chao Yu wrote: > On 2016/11/4 2:02, Jaegeuk Kim wrote: > > On Fri, Nov 04, 2016 at 12:26:56AM +0800, Chao Yu wrote: > >> From: Chao Yu > >> > >> i_times of inode will be set with current system time which can be > >> configured through 'date', so it's not

[PATCH net-next 5/5] net: l2tp: fix negative assignment to unsigned int

recv_seq, send_seq and lns_mode mode are all defined as unsigned int foo:1; Signed-off-by: Asbjoern Sloth Toennesen --- net/l2tp/l2tp_core.c | 2 +- net/l2tp/l2tp_ppp.c | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/net/l2tp/l2tp_core.c

[PATCH net-next 5/5] net: l2tp: fix negative assignment to unsigned int

recv_seq, send_seq and lns_mode mode are all defined as unsigned int foo:1; Signed-off-by: Asbjoern Sloth Toennesen --- net/l2tp/l2tp_core.c | 2 +- net/l2tp/l2tp_ppp.c | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/net/l2tp/l2tp_core.c b/net/l2tp/l2tp_core.c index

[PATCH net-next 4/5] net: l2tp: cleanup: remove redundant condition

These assignments follow this pattern: unsigned int foo:1; struct nlattr *nla = info->attrs[bar]; if (nla) foo = nla_get_flag(nla); /* expands to: foo = !!nla */ This could be simplified to: if (nla) foo = 1; but lets just remove the condition and use the

[PATCH net-next 4/5] net: l2tp: cleanup: remove redundant condition

These assignments follow this pattern: unsigned int foo:1; struct nlattr *nla = info->attrs[bar]; if (nla) foo = nla_get_flag(nla); /* expands to: foo = !!nla */ This could be simplified to: if (nla) foo = 1; but lets just remove the condition and use the

[PATCH net-next 1/5] net: l2tp: fix L2TP_ATTR_UDP_CSUM attribute type

L2TP_ATTR_UDP_CSUM is a flag, and gets read with nla_get_flag, but it is defined as NLA_U8 in the nla_policy. It appears that this is only publicly used in iproute2, where it's broken, because it's used as a NLA_FLAG, and fails validation as a NLA_U8. The only place it's used as a NLA_U8 is in

[PATCH net-next 2/5] net: l2tp: fix L2TP_ATTR_UDP_ZERO_CSUM6_{RX,TX} attribute types

The attributes L2TP_ATTR_UDP_ZERO_CSUM6_RX and L2TP_ATTR_UDP_ZERO_CSUM6_TX are used as flags, but is defined as a u8 in a comment. This patch redocuments them as flags, and adds them to the nla_policy, so they gets validated. The only publicly user, iproute2, already treat these attributes as

[PATCH net-next 1/5] net: l2tp: fix L2TP_ATTR_UDP_CSUM attribute type

L2TP_ATTR_UDP_CSUM is a flag, and gets read with nla_get_flag, but it is defined as NLA_U8 in the nla_policy. It appears that this is only publicly used in iproute2, where it's broken, because it's used as a NLA_FLAG, and fails validation as a NLA_U8. The only place it's used as a NLA_U8 is in

[PATCH net-next 2/5] net: l2tp: fix L2TP_ATTR_UDP_ZERO_CSUM6_{RX,TX} attribute types

The attributes L2TP_ATTR_UDP_ZERO_CSUM6_RX and L2TP_ATTR_UDP_ZERO_CSUM6_TX are used as flags, but is defined as a u8 in a comment. This patch redocuments them as flags, and adds them to the nla_policy, so they gets validated. The only publicly user, iproute2, already treat these attributes as

  1   2   3   4   5   6   7   8   9   10   >