[RESEND PATCH 3/6] apalis-tk1: optional displayport hot-plug detect

From: Marcel Ziswiler Configure DP_HPD_PFF0 pin as optional DisplayPort hot-plug detect. Signed-off-by: Marcel Ziswiler --- arch/arm/boot/dts/tegra124-apalis.dtsi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/boot/dts/tegra124-apalis.dtsi

[RESEND PATCH 2/6] apalis-tk1: temp alert pull-up

From: Marcel Ziswiler Pull-up GPIO_PI6 connected to TMP451's ALERT#/THERM2#. Signed-off-by: Marcel Ziswiler --- arch/arm/boot/dts/tegra124-apalis.dtsi | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/arch/arm/boot/dts/tegra124-apalis.dtsi

Re: [PATCH V4 11/15] blk-throttle: add interface to configure think time threshold

On Wed, Nov 23, 2016 at 04:32:43PM -0500, Tejun Heo wrote: > On Mon, Nov 14, 2016 at 02:22:18PM -0800, Shaohua Li wrote: > > Add interface to configure the threshold > > > > Signed-off-by: Shaohua Li > > --- > > block/blk-sysfs.c| 7 +++ > > block/blk-throttle.c | 25

[RESEND PATCH 5/6] apalis-tk1: working sd card detect on v1.1 hw

From: Marcel Ziswiler Add sd card detect SD1_CD# applicable for V1.1 modules using GPIO_PV2. Signed-off-by: Marcel Ziswiler --- arch/arm/boot/dts/tegra124-apalis-eval.dts | 10 ++ 1 file changed, 2 insertions(+), 8 deletions(-) diff --git a/arch/arm/boot/dts/tegra124-apalis-eval.dts

[RESEND PATCH 0/6] apalis-tk1: updates for v1.1 hw

From: Marcel Ziswiler This series updates the device tree for the upcoming V1.1 HW samples. All changes are purely opportunistic meaning they fix stuff which on older HW was anyway broken so there should be no backwards compatibility issues. Marcel Ziswiler (6):

[RESEND PATCH 1/6] apalis-tk1: remove spurious new lines

From: Marcel Ziswiler Remove some spurious new lines. Signed-off-by: Marcel Ziswiler --- arch/arm/boot/dts/tegra124-apalis-eval.dts | 1 - arch/arm/boot/dts/tegra124-apalis.dtsi | 12 2 files changed, 13 deletions(-)

[RESEND PATCH 0/6] apalis-tk1: updates for v1.1 hw

From: Marcel Ziswiler This series updates the device tree for the upcoming V1.1 HW samples. All changes are purely opportunistic meaning they fix stuff which on older HW was anyway broken so there should be no backwards compatibility issues. Marcel Ziswiler (6): apalis-tk1: remove spurious

[RESEND PATCH 1/6] apalis-tk1: remove spurious new lines

From: Marcel Ziswiler Remove some spurious new lines. Signed-off-by: Marcel Ziswiler --- arch/arm/boot/dts/tegra124-apalis-eval.dts | 1 - arch/arm/boot/dts/tegra124-apalis.dtsi | 12 2 files changed, 13 deletions(-) diff --git a/arch/arm/boot/dts/tegra124-apalis-eval.dts

Re: [PATCH V4 09/15] blk-throttle: make bandwidth change smooth

On Wed, Nov 23, 2016 at 04:23:35PM -0500, Tejun Heo wrote: > Hello, > > On Mon, Nov 14, 2016 at 02:22:16PM -0800, Shaohua Li wrote: > > cg1/cg2 bps: 10/80 -> 15/105 -> 20/100 -> 25/95 -> 30/90 -> 35/85 -> 40/80 > > -> 45/75 -> 10/80 > > I wonder whether it'd make sense to make the clamping down

Re: [PATCH V4 09/15] blk-throttle: make bandwidth change smooth

On Wed, Nov 23, 2016 at 04:23:35PM -0500, Tejun Heo wrote: > Hello, > > On Mon, Nov 14, 2016 at 02:22:16PM -0800, Shaohua Li wrote: > > cg1/cg2 bps: 10/80 -> 15/105 -> 20/100 -> 25/95 -> 30/90 -> 35/85 -> 40/80 > > -> 45/75 -> 10/80 > > I wonder whether it'd make sense to make the clamping down

Re: [PATCH] powerpc/eeh/of: use builtin_platform_driver

On Wed, 2016-11-23 at 22:58 +0800, Geliang Tang wrote: > Use builtin_platform_driver() helper to simplify the code. > > Signed-off-by: Geliang Tang > --- Acked-by: Russell Currey

Re: [PATCH] powerpc/eeh/of: use builtin_platform_driver

On Wed, 2016-11-23 at 22:58 +0800, Geliang Tang wrote: > Use builtin_platform_driver() helper to simplify the code. > > Signed-off-by: Geliang Tang > --- Acked-by: Russell Currey

Re: [PATCH 2/2] clk: uniphier: add clock data for cpufreq

Hi Stephen, 2016-11-24 9:05 GMT+09:00 Stephen Boyd : >> +#if 1 >> + /* >> + * TODO: >> + * The return type of .round_rate() is "long", which is 32 bit wide on >> + * 32 bit systems. Clock rate greater than LONG_MAX (~ 2.15 GHz) is >> + * treated as

Re: [PATCH 2/2] clk: uniphier: add clock data for cpufreq

Hi Stephen, 2016-11-24 9:05 GMT+09:00 Stephen Boyd : >> +#if 1 >> + /* >> + * TODO: >> + * The return type of .round_rate() is "long", which is 32 bit wide on >> + * 32 bit systems. Clock rate greater than LONG_MAX (~ 2.15 GHz) is >> + * treated as an error. Needs a

[RFC 2/6] vfs: Add checks for filesystem timestamp limits

Allow read only mounts for filesystems that do not have maximum timestamps beyond the y2038 expiry timestamp. Also, allow a sysctl override to all such filesystems to be mounted with write permissions. Alternatively, a mount option can be created to allow or disallow range check based clamps and

[RFC 4/6] ext4: Initialize timestamps limits

ext4 has different overflow limits for max filesystem timestamps based on the extra bytes available. Signed-off-by: Deepa Dinamani Cc: "Theodore Ts'o" Cc: Andreas Dilger Cc: linux-e...@vger.kernel.org --- fs/ext4/ext4.h | 4

[RFC 2/6] vfs: Add checks for filesystem timestamp limits

Allow read only mounts for filesystems that do not have maximum timestamps beyond the y2038 expiry timestamp. Also, allow a sysctl override to all such filesystems to be mounted with write permissions. Alternatively, a mount option can be created to allow or disallow range check based clamps and

[RFC 4/6] ext4: Initialize timestamps limits

ext4 has different overflow limits for max filesystem timestamps based on the extra bytes available. Signed-off-by: Deepa Dinamani Cc: "Theodore Ts'o" Cc: Andreas Dilger Cc: linux-e...@vger.kernel.org --- fs/ext4/ext4.h | 4 fs/ext4/super.c | 7 ++- 2 files changed, 10

[RFC 5/6] vfs: Add timestamp_truncate() api

timespec_trunc() function is used to truncate a filesystem timestamp to the right granularity. But, the function does not clamp tv_sec part of the timestamps according to the filesystem timestamp limits. Also, timespec_trunc() is exclusively used for filesystem timestamps. Move the api to be part

[RFC 6/6] utimes: Clamp the timestamps before update

POSIX.1 section for futimens, utimensat and utimes says: The file's relevant timestamp shall be set to the greatest value supported by the file system that is not greater than the specified time. Clamp the timestamps accordingly before assignment. Note that clamp_t macro is used for clamping

[RFC 0/6] vfs: Add timestamp range check support

The original thread is at https://lkml.org/lkml/2016/11/2/294 The branch is available at https://github.com/deepa-hub/vfs.git refs/heads/vfs_timestamp_policy Changes since v1: * return EROFS on mount errors * fix mtime copy/paste error in utimes Deepa Dinamani (6): vfs: Add file timestamp

[RFC 6/6] utimes: Clamp the timestamps before update

POSIX.1 section for futimens, utimensat and utimes says: The file's relevant timestamp shall be set to the greatest value supported by the file system that is not greater than the specified time. Clamp the timestamps accordingly before assignment. Note that clamp_t macro is used for clamping

[RFC 0/6] vfs: Add timestamp range check support

The original thread is at https://lkml.org/lkml/2016/11/2/294 The branch is available at https://github.com/deepa-hub/vfs.git refs/heads/vfs_timestamp_policy Changes since v1: * return EROFS on mount errors * fix mtime copy/paste error in utimes Deepa Dinamani (6): vfs: Add file timestamp

[RFC 5/6] vfs: Add timestamp_truncate() api

timespec_trunc() function is used to truncate a filesystem timestamp to the right granularity. But, the function does not clamp tv_sec part of the timestamps according to the filesystem timestamp limits. Also, timespec_trunc() is exclusively used for filesystem timestamps. Move the api to be part

[RFC 3/6] afs: Add time limits in the super block

Note that all the filesystems that have such simple limits will be initialized in the same patch. Signed-off-by: Deepa Dinamani Cc: linux-...@lists.infradead.org --- fs/afs/super.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/fs/afs/super.c b/fs/afs/super.c

[RFC 3/6] afs: Add time limits in the super block

Note that all the filesystems that have such simple limits will be initialized in the same patch. Signed-off-by: Deepa Dinamani Cc: linux-...@lists.infradead.org --- fs/afs/super.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/fs/afs/super.c b/fs/afs/super.c index fbdb022..ab00434

Re: [PATCH V2 1/2] clk: qcom: gdsc: Add support for gdscs with HW control

On 11/18, Sricharan R wrote: > From: Rajendra Nayak > > Some GDSCs might support a HW control mode, where in the power > domain (gdsc) is brought in and out of low power state (while > unsued) without any SW assistance, saving power. > Such GDSCs can be configured in a HW

[RFC 1/6] vfs: Add file timestamp range support

Add fields to the superblock to track the min and max timestamps supported by filesystems. Initially, when a superblock is allocated, initialize it to the max and min values the fields can hold. Individual filesystems override these to match their actual limits. Pseudo filesystems are assumed to

Re: [PATCH V2 1/2] clk: qcom: gdsc: Add support for gdscs with HW control

On 11/18, Sricharan R wrote: > From: Rajendra Nayak > > Some GDSCs might support a HW control mode, where in the power > domain (gdsc) is brought in and out of low power state (while > unsued) without any SW assistance, saving power. > Such GDSCs can be configured in a HW control mode when

[RFC 1/6] vfs: Add file timestamp range support

Add fields to the superblock to track the min and max timestamps supported by filesystems. Initially, when a superblock is allocated, initialize it to the max and min values the fields can hold. Individual filesystems override these to match their actual limits. Pseudo filesystems are assumed to

Re: Enabling peer to peer device transactions for PCIe devices

On Wed, Nov 23, 2016 at 02:11:29PM -0700, Logan Gunthorpe wrote: > Perhaps I am not following what Serguei is asking for, but I > understood the desire was for a complex GPU allocator that could > migrate pages between GPU and CPU memory under control of the GPU > driver, among other things. The

Re: Enabling peer to peer device transactions for PCIe devices

On Wed, Nov 23, 2016 at 02:11:29PM -0700, Logan Gunthorpe wrote: > Perhaps I am not following what Serguei is asking for, but I > understood the desire was for a complex GPU allocator that could > migrate pages between GPU and CPU memory under control of the GPU > driver, among other things. The

Re: [PATCH] clk: Register clkdev after setup of fixed-rate and fixed-factor clocks

On 11/12, Xiaolong Zhang wrote: > On 二, 10月 25, 2016 at 08:40:08下午 +, Stephen Boyd wrote: > > On 10/22, Xiaolong Zhang wrote: > > > On 四, 10月 20, 2016 at 04:01:03下午 -0700, Stephen Boyd wrote: > > > > On 10/11, Orson Zhai wrote: > > > > > From: Xiaolong Zhang > >

Re: [PATCH] clk: Register clkdev after setup of fixed-rate and fixed-factor clocks

On 11/12, Xiaolong Zhang wrote: > On 二, 10月 25, 2016 at 08:40:08下午 +, Stephen Boyd wrote: > > On 10/22, Xiaolong Zhang wrote: > > > On 四, 10月 20, 2016 at 04:01:03下午 -0700, Stephen Boyd wrote: > > > > On 10/11, Orson Zhai wrote: > > > > > From: Xiaolong Zhang > > > > > > > > > > When common

[PATCH v1 11/11] scsi: ufs: fix default power mode to FAST/SLOW

We would by default like to run in FAST/SLOW mode instead of FASTAUTO/SLOWAUTO mode for performance reasons. This change sets the default speed mode to FAST/SLOW mode. Reviewed-by: Venkat Gopalakrishnan Signed-off-by: Subhash Jadavani ---

[PATCH v1 11/11] scsi: ufs: fix default power mode to FAST/SLOW

We would by default like to run in FAST/SLOW mode instead of FASTAUTO/SLOWAUTO mode for performance reasons. This change sets the default speed mode to FAST/SLOW mode. Reviewed-by: Venkat Gopalakrishnan Signed-off-by: Subhash Jadavani --- drivers/scsi/ufs/ufshcd.c | 8 1 file changed,

[PATCH v1 03/11] scsi: ufs: update device descriptor maximum size

From: Yaniv Gardi According to JESD220B - UFS v2.0, the maximum size of device descriptor has changed from 0x1F to 0x40. This patch updates the maximum size of this descriptor. Signed-off-by: Yaniv Gardi Signed-off-by: Subhash Jadavani

[PATCH v1 03/11] scsi: ufs: update device descriptor maximum size

From: Yaniv Gardi According to JESD220B - UFS v2.0, the maximum size of device descriptor has changed from 0x1F to 0x40. This patch updates the maximum size of this descriptor. Signed-off-by: Yaniv Gardi Signed-off-by: Subhash Jadavani --- drivers/scsi/ufs/ufs.h | 2 +- 1 file changed, 1

[PATCH v1 07/11] scsi: ufs: issue link starup 2 times if device isn't active

If we issue the link startup to the device while its UniPro state is LinkDown (and device state is sleep/power-down) then link startup will not move the device state to Active. Device will only move to active state if the link starup is issued when its UniPro state is LinkUp. So in this case, we

[PATCH v1 07/11] scsi: ufs: issue link starup 2 times if device isn't active

If we issue the link startup to the device while its UniPro state is LinkDown (and device state is sleep/power-down) then link startup will not move the device state to Active. Device will only move to active state if the link starup is issued when its UniPro state is LinkUp. So in this case, we

[PATCH v1 04/11] scsi: ufs: fix failure to read the string descriptor

While reading variable size descriptors (like string descriptor), some UFS devices may report the "LENGTH" (field in "Transaction Specific fields" of Query Response UPIU) same as what was requested in Query Request UPIU instead of reporting the actual size of the variable size descriptor. Although

[PATCH v1 04/11] scsi: ufs: fix failure to read the string descriptor

While reading variable size descriptors (like string descriptor), some UFS devices may report the "LENGTH" (field in "Transaction Specific fields" of Query Response UPIU) same as what was requested in Query Request UPIU instead of reporting the actual size of the variable size descriptor. Although

[PATCH v1 01/11] scsi: ufs: add queries retry mechanism

From: Dolev Raviv Some of the queries might fail during init. To avoid system failure, we add retry mechanism to issue queries several times. Signed-off-by: Dolev Raviv Signed-off-by: Subhash Jadavani ---

[PATCH v1 09/11] scsi: ufs: fix condition in which DME command failure msg is printed out

From: Yaniv Gardi The condition in which error message is printed out was incorrect and resulted error message only if retries exhausted. But retries happens only if DME command is a peer command, and thus DME commands which are not peer commands and fail are not printed

[PATCH v1 05/11] scsi: ufs: increase the scsi query response timeout

It is found thats UFS device may take longer than 30ms to respond to query requests and in this case we might run into following scenario: 1. UFS host SW sends a query request to UFS device to read an attribute value. SW uses tag #31 for this purpose. 2. UFS host SW waits for 30ms to get the

[PATCH v1 06/11] scsi: ufs: ensure that host pa_tactivate is higher than device

Some UFS devices require host PA_TACTIVATE to be higher than device PA_TACTIVATE otherwise it may get stuck during hibern8 sequence. This change allows this by using quirk. Reviewed-by: Venkat Gopalakrishnan Signed-off-by: Subhash Jadavani ---

[PATCH v1 08/11] scsi: ufs: handle errors from PHY_ADAPTER_ERROR register

From: Dolev Raviv The PHY_ADAPTER_ERROR status register indicates PHY lane errors reported by the M-PHY layer. In some occasions the controller can recover from such errors. When the error is not recoverable, a stuck DB error will occur. Since the stuck DB error is spotted

[PATCH v1 10/11] scsi: ufs: optimize system suspend handling

Consider following sequence of events: 1. UFS is runtime suspended, link_state = Hibern8, device_state = sleep 2. System goes into system suspend, ufshcd_system_suspend() brings both link and device to active state and then puts the device in Power_Down state and link in OFF state. 3. System

[PATCH v1 01/11] scsi: ufs: add queries retry mechanism

From: Dolev Raviv Some of the queries might fail during init. To avoid system failure, we add retry mechanism to issue queries several times. Signed-off-by: Dolev Raviv Signed-off-by: Subhash Jadavani --- drivers/scsi/ufs/ufshcd.c | 54 +++ 1 file

[PATCH v1 09/11] scsi: ufs: fix condition in which DME command failure msg is printed out

From: Yaniv Gardi The condition in which error message is printed out was incorrect and resulted error message only if retries exhausted. But retries happens only if DME command is a peer command, and thus DME commands which are not peer commands and fail are not printed out. This change fixes

[PATCH v1 05/11] scsi: ufs: increase the scsi query response timeout

It is found thats UFS device may take longer than 30ms to respond to query requests and in this case we might run into following scenario: 1. UFS host SW sends a query request to UFS device to read an attribute value. SW uses tag #31 for this purpose. 2. UFS host SW waits for 30ms to get the

[PATCH v1 06/11] scsi: ufs: ensure that host pa_tactivate is higher than device

Some UFS devices require host PA_TACTIVATE to be higher than device PA_TACTIVATE otherwise it may get stuck during hibern8 sequence. This change allows this by using quirk. Reviewed-by: Venkat Gopalakrishnan Signed-off-by: Subhash Jadavani --- drivers/scsi/ufs/ufs_quirks.h | 9 ++

[PATCH v1 10/11] scsi: ufs: optimize system suspend handling

Consider following sequence of events: 1. UFS is runtime suspended, link_state = Hibern8, device_state = sleep 2. System goes into system suspend, ufshcd_system_suspend() brings both link and device to active state and then puts the device in Power_Down state and link in OFF state. 3. System

[PATCH v1 08/11] scsi: ufs: handle errors from PHY_ADAPTER_ERROR register

From: Dolev Raviv The PHY_ADAPTER_ERROR status register indicates PHY lane errors reported by the M-PHY layer. In some occasions the controller can recover from such errors. When the error is not recoverable, a stuck DB error will occur. Since the stuck DB error is spotted separately, no action

[PATCH v1 02/11] scsi: ufs: add index details to query error messages

From: Yaniv Gardi When sending query to the device, the index of the failure is additional useful information that should be printed out as it might specify the logical unit (LU) where the error occurred. Signed-off-by: Yaniv Gardi Signed-off-by:

[PATCH v1 02/11] scsi: ufs: add index details to query error messages

From: Yaniv Gardi When sending query to the device, the index of the failure is additional useful information that should be printed out as it might specify the logical unit (LU) where the error occurred. Signed-off-by: Yaniv Gardi Signed-off-by: Subhash Jadavani ---

Re: [PATCH v3 0/3] Stop sched tick in idle injection task

On Wed, 23 Nov 2016 23:38:39 +0100 "Rafael J. Wysocki" wrote: > On Wed, Nov 23, 2016 at 10:45 PM, Peter Zijlstra > wrote: > > On Wed, Nov 23, 2016 at 10:12:46PM +0100, Rafael J. Wysocki wrote: > >> On Wed, Nov 23, 2016 at 9:13 PM, Jacob Pan > > >

Re: [PATCH v3 0/3] Stop sched tick in idle injection task

On Wed, 23 Nov 2016 23:38:39 +0100 "Rafael J. Wysocki" wrote: > On Wed, Nov 23, 2016 at 10:45 PM, Peter Zijlstra > wrote: > > On Wed, Nov 23, 2016 at 10:12:46PM +0100, Rafael J. Wysocki wrote: > >> On Wed, Nov 23, 2016 at 9:13 PM, Jacob Pan > > > >> > >> Any objections anyone? > >> > >>

Re: [PATCH v3 0/3] Stop sched tick in idle injection task

On Thu, Nov 24, 2016 at 1:25 AM, Jacob Pan wrote: > On Wed, 23 Nov 2016 23:38:39 +0100 > "Rafael J. Wysocki" wrote: > >> On Wed, Nov 23, 2016 at 10:45 PM, Peter Zijlstra >> wrote: >> > On Wed, Nov 23, 2016 at 10:12:46PM

Re: [PATCH v3 0/3] Stop sched tick in idle injection task

On Thu, Nov 24, 2016 at 1:25 AM, Jacob Pan wrote: > On Wed, 23 Nov 2016 23:38:39 +0100 > "Rafael J. Wysocki" wrote: > >> On Wed, Nov 23, 2016 at 10:45 PM, Peter Zijlstra >> wrote: >> > On Wed, Nov 23, 2016 at 10:12:46PM +0100, Rafael J. Wysocki wrote: >> >> On Wed, Nov 23, 2016 at 9:13 PM,

[PATCH] scsi/ipr: Fix runaway IRQs when falling back from MSI to LSI

LSIs must be ack'ed with an MMIO otherwise they remain asserted forever. This is controlled by the "clear_isr" flag. While we set that flag properly when deciding initially whether to use LSIs or MSIs, we fail to set it if we first chose MSIs, the test fails, then fallback to LSIs.

[PATCH] scsi/ipr: Fix runaway IRQs when falling back from MSI to LSI

LSIs must be ack'ed with an MMIO otherwise they remain asserted forever. This is controlled by the "clear_isr" flag. While we set that flag properly when deciding initially whether to use LSIs or MSIs, we fail to set it if we first chose MSIs, the test fails, then fallback to LSIs.

Re: [PATCH] cxl: drop duplicate header sched.h

On 24/11/16 02:27, Geliang Tang wrote: Drop duplicate header sched.h from native.c. Signed-off-by: Geliang Tang Good catch! Reviewed-by: Andrew Donnellan -- Andrew Donnellan OzLabs, ADL Canberra andrew.donnel...@au1.ibm.com

Re: [PATCH] cxl: drop duplicate header sched.h

On 24/11/16 02:27, Geliang Tang wrote: Drop duplicate header sched.h from native.c. Signed-off-by: Geliang Tang Good catch! Reviewed-by: Andrew Donnellan -- Andrew Donnellan OzLabs, ADL Canberra andrew.donnel...@au1.ibm.com IBM Australia Limited

Re: [PATCHv12 2/3] usb: USB Type-C connector class

On Tue, Nov 22, 2016 at 04:11:46PM +0200, Heikki Krogerus wrote: > The purpose of USB Type-C connector class is to provide > unified interface for the user space to get the status and > basic information about USB Type-C connectors on a system, > control over data role swapping, and when the port

Re: [PATCHv12 1/3] lib/string: add sysfs_match_string helper

On Tue, Nov 22, 2016 at 04:11:45PM +0200, Heikki Krogerus wrote: > Make a simple helper for matching strings with sysfs > attribute files. In most parts the same as match_string(), > except sysfs_match_string() uses sysfs_streq() instead of > strcmp() for matching. This is more convenient when

Re: [PATCHv12 1/3] lib/string: add sysfs_match_string helper

On Tue, Nov 22, 2016 at 04:11:45PM +0200, Heikki Krogerus wrote: > Make a simple helper for matching strings with sysfs > attribute files. In most parts the same as match_string(), > except sysfs_match_string() uses sysfs_streq() instead of > strcmp() for matching. This is more convenient when

Re: [PATCHv12 2/3] usb: USB Type-C connector class

On Tue, Nov 22, 2016 at 04:11:46PM +0200, Heikki Krogerus wrote: > The purpose of USB Type-C connector class is to provide > unified interface for the user space to get the status and > basic information about USB Type-C connectors on a system, > control over data role swapping, and when the port

Re: [PATCH] x86: fix kaslr and memmap collision

On Tue, Nov 22, 2016 at 11:01:32AM -0800, Dan Williams wrote: > On Tue, Nov 22, 2016 at 10:54 AM, Kees Cook wrote: > > On Tue, Nov 22, 2016 at 9:26 AM, Dan Williams > > wrote: > >> No, you're right, we need to handle multiple ranges. Since the >

Re: [PATCH] x86: fix kaslr and memmap collision

On Tue, Nov 22, 2016 at 11:01:32AM -0800, Dan Williams wrote: > On Tue, Nov 22, 2016 at 10:54 AM, Kees Cook wrote: > > On Tue, Nov 22, 2016 at 9:26 AM, Dan Williams > > wrote: > >> No, you're right, we need to handle multiple ranges. Since the > >> mem_avoid array is statically allocated

Re: [PATCH 2/2] clk: uniphier: add clock data for cpufreq

On 10/27, Masahiro Yamada wrote: > Data needed for CPU-gear change (cpufreq). > > Note: > At this moment, some clock data for Pro5/Pxs2 (32bit SoCs) are > a bit faked because clock rates greater than LONG_MAX (~2.15 GHz) > must be avoided on 32 bit systems. > > Signed-off-by: Masahiro Yamada

Re: [PATCH 2/2] clk: uniphier: add clock data for cpufreq

On 10/27, Masahiro Yamada wrote: > Data needed for CPU-gear change (cpufreq). > > Note: > At this moment, some clock data for Pro5/Pxs2 (32bit SoCs) are > a bit faked because clock rates greater than LONG_MAX (~2.15 GHz) > must be avoided on 32 bit systems. > > Signed-off-by: Masahiro Yamada >

Re: [PATCH RESEND 2/2] gpio: axp209: add pinctrl support

Hi Quentin, [auto build test ERROR on gpio/for-next] [also build test ERROR on v4.9-rc6 next-20161123] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Quentin-Schulz/add-support-for-AXP209-GPIOs

Re: [PATCH RESEND 2/2] gpio: axp209: add pinctrl support

Hi Quentin, [auto build test ERROR on gpio/for-next] [also build test ERROR on v4.9-rc6 next-20161123] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Quentin-Schulz/add-support-for-AXP209-GPIOs

RE: [Intel-wired-lan] [PATCH] igb: use igb_adapter->io_addr instead of e1000_hw->hw_addr

> From: Intel-wired-lan [intel-wired-lan-boun...@lists.osuosl.org] on behalf of > Cao jin [caoj.f...@cn.fujitsu.com] > Sent: Monday, November 07, 2016 11:06 PM To> : linux-kernel@vger.kernel.org; net...@vger.kernel.org > Cc: izumi.t...@jp.fujitsu.com; intel-wired-...@lists.osuosl.org > Subject:

RE: [Intel-wired-lan] [PATCH] igb: use igb_adapter->io_addr instead of e1000_hw->hw_addr

> From: Intel-wired-lan [intel-wired-lan-boun...@lists.osuosl.org] on behalf of > Cao jin [caoj.f...@cn.fujitsu.com] > Sent: Monday, November 07, 2016 11:06 PM To> : linux-kernel@vger.kernel.org; net...@vger.kernel.org > Cc: izumi.t...@jp.fujitsu.com; intel-wired-...@lists.osuosl.org > Subject:

linux-next: manual merge of the powerpc tree with the powerpc-fixes tree

Hi all, Today's linux-next merge of the powerpc tree got a conflict in: arch/powerpc/include/asm/asm-prototypes.h between commit: 9e5f68842276 ("powerpc: Fix missing CRCs, add more asm-prototypes.h declarations") from the powerpc-fixes tree and commit: 82de5797a260 ("powerpc: Remove

linux-next: manual merge of the powerpc tree with the powerpc-fixes tree

Hi all, Today's linux-next merge of the powerpc tree got a conflict in: arch/powerpc/include/asm/asm-prototypes.h between commit: 9e5f68842276 ("powerpc: Fix missing CRCs, add more asm-prototypes.h declarations") from the powerpc-fixes tree and commit: 82de5797a260 ("powerpc: Remove

[PATCH v2] mtd: maps: add missing iounmap() in error path

This patch was triggered by the following Coccinelle error: ./drivers/mtd/maps/sc520cdp.c:246:3-9: \ ERROR: missing iounmap; ioremap on line 242 \ and execution via conditional on line 244 Since do_map_probe() is also invoked in this loop, it is also necessary to map_destroy()

[PATCH v2] mtd: maps: add missing iounmap() in error path

This patch was triggered by the following Coccinelle error: ./drivers/mtd/maps/sc520cdp.c:246:3-9: \ ERROR: missing iounmap; ioremap on line 242 \ and execution via conditional on line 244 Since do_map_probe() is also invoked in this loop, it is also necessary to map_destroy()

Re: module: Ensure a module's state is set accordingly during module coming cleanup code

+++ Miroslav Benes [16/11/16 16:49 +0100]: On Wed, 9 Nov 2016, Jessica Yu wrote: +++ Rusty Russell [26/10/16 11:24 +1030]: > Aaron Tomlin writes: > > In load_module() in the event of an error, for e.g. unknown module > > parameter(s) specified we go to perform some module

Re: module: Ensure a module's state is set accordingly during module coming cleanup code

+++ Miroslav Benes [16/11/16 16:49 +0100]: On Wed, 9 Nov 2016, Jessica Yu wrote: +++ Rusty Russell [26/10/16 11:24 +1030]: > Aaron Tomlin writes: > > In load_module() in the event of an error, for e.g. unknown module > > parameter(s) specified we go to perform some module coming clean up > >

Re: [PATCH 01/14] perf/x86: Introduce PERF_RECORD_OVERHEAD

On Wed, Nov 23, 2016 at 04:44:39AM -0500, kan.li...@intel.com wrote: > From: Kan Liang > > A new perf record is introduced to export perf overhead information to > userspace. So we can measure the overhead of sampling directly. > > To output the overhead information, it

Re: [PATCH 01/14] perf/x86: Introduce PERF_RECORD_OVERHEAD

On Wed, Nov 23, 2016 at 04:44:39AM -0500, kan.li...@intel.com wrote: > From: Kan Liang > > A new perf record is introduced to export perf overhead information to > userspace. So we can measure the overhead of sampling directly. > > To output the overhead information, it takes advantage of the

Re: [PATCH 14/14] perf script: show overhead events

On Wed, Nov 23, 2016 at 04:44:52AM -0500, kan.li...@intel.com wrote: SNIP > +} > + > static void sig_handler(int sig __maybe_unused) > { > session_done = 1; > @@ -1287,6 +1319,8 @@ static int __cmd_script(struct perf_script *script) > } > if (script->show_switch_events) >

Re: [PATCH 14/14] perf script: show overhead events

On Wed, Nov 23, 2016 at 04:44:52AM -0500, kan.li...@intel.com wrote: SNIP > +} > + > static void sig_handler(int sig __maybe_unused) > { > session_done = 1; > @@ -1287,6 +1319,8 @@ static int __cmd_script(struct perf_script *script) > } > if (script->show_switch_events) >

Re: [PATCH 14/14] perf script: show overhead events

On Wed, Nov 23, 2016 at 04:44:52AM -0500, kan.li...@intel.com wrote: > From: Kan Liang > > Introduce a new option --show-overhead to show overhead events in perf > script > > Signed-off-by: Kan Liang > --- > tools/perf/builtin-script.c | 36

Re: [PATCH 14/14] perf script: show overhead events

On Wed, Nov 23, 2016 at 04:44:52AM -0500, kan.li...@intel.com wrote: > From: Kan Liang > > Introduce a new option --show-overhead to show overhead events in perf > script > > Signed-off-by: Kan Liang > --- > tools/perf/builtin-script.c | 36 >

Re: [PATCH 3/4] KVM: nVMX: accurate emulation of MSR_IA32_CR{0,4}_FIXED1

On Wed, Nov 23, 2016 at 2:11 PM, Paolo Bonzini wrote: > On 23/11/2016 23:07, David Matlack wrote: >> A downside of this scheme is we'd have to remember to update >> nested_vmx_cr4_fixed1_update() before giving VMs new CPUID bits. If we >> forget, a VM could end up with

Re: [PATCH 3/4] KVM: nVMX: accurate emulation of MSR_IA32_CR{0,4}_FIXED1

On Wed, Nov 23, 2016 at 2:11 PM, Paolo Bonzini wrote: > On 23/11/2016 23:07, David Matlack wrote: >> A downside of this scheme is we'd have to remember to update >> nested_vmx_cr4_fixed1_update() before giving VMs new CPUID bits. If we >> forget, a VM could end up with different values for

Re: [PATCH 14/14] perf script: show overhead events

On Wed, Nov 23, 2016 at 04:44:52AM -0500, kan.li...@intel.com wrote: > From: Kan Liang > > Introduce a new option --show-overhead to show overhead events in perf > script please add exmaple output into changelog thanks, jirka

Re: [PATCH 14/14] perf script: show overhead events

On Wed, Nov 23, 2016 at 04:44:52AM -0500, kan.li...@intel.com wrote: > From: Kan Liang > > Introduce a new option --show-overhead to show overhead events in perf > script please add exmaple output into changelog thanks, jirka

Re: Enabling peer to peer device transactions for PCIe devices

On Wed, Nov 23, 2016 at 02:42:12PM -0800, Dan Williams wrote: > > The crucial part for this discussion is the ability to fence and block > > DMA for a specific range. This is the hardware capability that lets > > page migration happen: fence DMA, migrate page, update page > > table in HCA, unblock

Re: Enabling peer to peer device transactions for PCIe devices

On Wed, Nov 23, 2016 at 02:42:12PM -0800, Dan Williams wrote: > > The crucial part for this discussion is the ability to fence and block > > DMA for a specific range. This is the hardware capability that lets > > page migration happen: fence DMA, migrate page, update page > > table in HCA, unblock

Re: [PATCH V5 3/3] ARM64 LPC: LPC driver implementation on Hip06

On Wednesday, November 23, 2016 6:07:11 PM CET Arnd Bergmann wrote: > On Wednesday, November 23, 2016 3:22:33 PM CET Gabriele Paoloni wrote: > > From: Arnd Bergmann [mailto:a...@arndb.de] > > > On Friday, November 18, 2016 5:03:11 PM CET Gabriele Paoloni wrote: > > Please don't proliferate the use

Re: [PATCH] clk: bcm: Make COMMON_CLK_IPROC into a library

Hi Stephen, On 16-11-23 02:41 PM, Stephen Boyd wrote: The broadcom clk driver Kconfig file selects and depends on the COMMON_CLK_IPROC config for different SoC specific drivers. Let's simplify this by always selecting the COMMON_CLK_IPROC config, turning it into a set of library code. We still

Re: [PATCH V5 3/3] ARM64 LPC: LPC driver implementation on Hip06

On Wednesday, November 23, 2016 6:07:11 PM CET Arnd Bergmann wrote: > On Wednesday, November 23, 2016 3:22:33 PM CET Gabriele Paoloni wrote: > > From: Arnd Bergmann [mailto:a...@arndb.de] > > > On Friday, November 18, 2016 5:03:11 PM CET Gabriele Paoloni wrote: > > Please don't proliferate the use

Re: [PATCH] clk: bcm: Make COMMON_CLK_IPROC into a library

Hi Stephen, On 16-11-23 02:41 PM, Stephen Boyd wrote: The broadcom clk driver Kconfig file selects and depends on the COMMON_CLK_IPROC config for different SoC specific drivers. Let's simplify this by always selecting the COMMON_CLK_IPROC config, turning it into a set of library code. We still

[ANNOUNCE] Git v2.11.0-rc3

A release candidate Git v2.11.0-rc3 is now available for testing at the usual places. It is comprised of 666 non-merge commits since v2.10.0, contributed by 73 people, 15 of which are new faces. It turns out that one recent fix exposed codepaths that have not been using the API correctly,

[ANNOUNCE] Git v2.11.0-rc3

A release candidate Git v2.11.0-rc3 is now available for testing at the usual places. It is comprised of 666 non-merge commits since v2.10.0, contributed by 73 people, 15 of which are new faces. It turns out that one recent fix exposed codepaths that have not been using the API correctly,

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