Several subsystems in the kernel (task scheduler and/or thermal at the
time of writing) can benefit from knowing about the energy consumed by
CPUs. Yet, this information can come from different sources (DT or
firmware for example), in different formats, hence making it hard to
exploit without a
Several subsystems in the kernel (task scheduler and/or thermal at the
time of writing) can benefit from knowing about the energy consumed by
CPUs. Yet, this information can come from different sources (DT or
firmware for example), in different formats, hence making it hard to
exploit without a
The existing scheduling domain hierarchy is defined to map to the cache
topology of the system. However, Energy Aware Scheduling (EAS) requires
more knowledge about the platform, and specifically needs to know about
the span of Performance Domains (PD), which do not always align with
caches.
To
The schedutil governor maps utilization values to frequencies by applying
a 25% margin. Since this sort of mapping mechanism can be needed by other
users (i.e. EAS), factor the utilization-to-frequency mapping code out
of schedutil and move it to include/linux/sched/cpufreq.h to avoid code
By default, arch_scale_cpu_capacity() is only visible from within the
kernel/sched folder. Relocate it to include/linux/sched/topology.h to
make it visible to other clients needing to know about the capacity of
CPUs, such as the Energy Model framework.
Cc: Ingo Molnar
Cc: Peter Zijlstra
Expose the Energy Model (read-only) of all performance domains in sysfs
for convenience. To do so, add a kobject to the CPU subsystem under the
umbrella of which a kobject for each performance domain is attached.
The resulting hierarchy is as follows for a platform with two
performance domains
This patch series introduces Energy Aware Scheduling (EAS) for CFS tasks
on platforms with asymmetric CPU topologies (e.g. Arm big.LITTLE).
For more details about the ideas behind it and the overall design,
please refer to the cover letter of version 5 [1].
1. Version History
--
The existing scheduling domain hierarchy is defined to map to the cache
topology of the system. However, Energy Aware Scheduling (EAS) requires
more knowledge about the platform, and specifically needs to know about
the span of Performance Domains (PD), which do not always align with
caches.
To
The schedutil governor maps utilization values to frequencies by applying
a 25% margin. Since this sort of mapping mechanism can be needed by other
users (i.e. EAS), factor the utilization-to-frequency mapping code out
of schedutil and move it to include/linux/sched/cpufreq.h to avoid code
By default, arch_scale_cpu_capacity() is only visible from within the
kernel/sched folder. Relocate it to include/linux/sched/topology.h to
make it visible to other clients needing to know about the capacity of
CPUs, such as the Energy Model framework.
Cc: Ingo Molnar
Cc: Peter Zijlstra
Expose the Energy Model (read-only) of all performance domains in sysfs
for convenience. To do so, add a kobject to the CPU subsystem under the
umbrella of which a kobject for each performance domain is attached.
The resulting hierarchy is as follows for a platform with two
performance domains
This patch series introduces Energy Aware Scheduling (EAS) for CFS tasks
on platforms with asymmetric CPU topologies (e.g. Arm big.LITTLE).
For more details about the ideas behind it and the overall design,
please refer to the cover letter of version 5 [1].
1. Version History
--
Signed-off-by: Chuanhua Han
---
Changes in v2:
- Place the adjusted transfer bytes code in spi_mem_adjust_op_size()
and check spi_max_message_size(mem->spi) value before subtracting
opcode, addr and dummy bytes.
*fixes:
spi: Extend the core to ease integration of
Signed-off-by: Chuanhua Han
---
Changes in v2:
- Place the adjusted transfer bytes code in spi_mem_adjust_op_size()
and check spi_max_message_size(mem->spi) value before subtracting
opcode, addr and dummy bytes.
*fixes:
spi: Extend the core to ease integration of
On Sat, Aug 18, 2018 at 07:54:09PM +0530, Bhaskar Singh wrote:
> This patch might suppress some warrning.
>
Which warning? You should find out which program is generating the
warning and delete it from your computer because that is a nonsense
warning.
regards,
dan carpenter
On Sat, Aug 18, 2018 at 07:54:09PM +0530, Bhaskar Singh wrote:
> This patch might suppress some warrning.
>
Which warning? You should find out which program is generating the
warning and delete it from your computer because that is a nonsense
warning.
regards,
dan carpenter
qcom_slim_ngd_runtime_suspend is protected by an #ifdef,
qcom_slim_ngd_runtime_idle is now, which causes a build time warning:
drivers/slimbus/qcom-ngd-ctrl.c:1470:12: error: 'qcom_slim_ngd_runtime_idle'
defined but not used [-Werror=unused-function]
Marking both as __maybe_unused lets us get
qcom_slim_ngd_runtime_suspend is protected by an #ifdef,
qcom_slim_ngd_runtime_idle is now, which causes a build time warning:
drivers/slimbus/qcom-ngd-ctrl.c:1470:12: error: 'qcom_slim_ngd_runtime_idle'
defined but not used [-Werror=unused-function]
Marking both as __maybe_unused lets us get
On Sun, Aug 19, 2018 at 12:36:40AM +0530, Bhaskar Singh wrote:
> This patch removed function named rtw_malloc2d.
>
> I removed this function because this function is used exactly once and
> function call have some overhead also.
>
> Maybe this will improve code runtime slightly.
>
>
On Sun, Aug 19, 2018 at 12:36:40AM +0530, Bhaskar Singh wrote:
> This patch removed function named rtw_malloc2d.
>
> I removed this function because this function is used exactly once and
> function call have some overhead also.
>
> Maybe this will improve code runtime slightly.
>
>
On Wed, Aug 01, 2018 at 12:57:20PM +0200, Jerome Brunet wrote:
> Current clock name looks like this:
> /soc/bus@ffd0/pwm@1b000#mux0
>
> This is bad because CCF uses the clock to create a directory in clk debugfs.
> With such name, the directory creation (silently) fails and the debugfs
>
Hello Larry,
>>> On 2018/8/16 at 19:24, in message <20180816112426.12218-1-lc...@suse.com>,
Larry Chen wrote:
> ocfs2_duplicate_clusters_by_page may crash if an extent's page is dirty.
> When a page has not been written back, it is still in dirty state. If at
> that moment,
On Wed, Aug 01, 2018 at 12:57:20PM +0200, Jerome Brunet wrote:
> Current clock name looks like this:
> /soc/bus@ffd0/pwm@1b000#mux0
>
> This is bad because CCF uses the clock to create a directory in clk debugfs.
> With such name, the directory creation (silently) fails and the debugfs
>
Hello Larry,
>>> On 2018/8/16 at 19:24, in message <20180816112426.12218-1-lc...@suse.com>,
Larry Chen wrote:
> ocfs2_duplicate_clusters_by_page may crash if an extent's page is dirty.
> When a page has not been written back, it is still in dirty state. If at
> that moment,
On Fri, Jul 20, 2018 at 09:16:32AM +0200, Fabrice Gasnier wrote:
> LPTimer has only one pwm channel (npwm = 1). Remove useless for loop
> in remove routine.
>
> Signed-off-by: Fabrice Gasnier
> ---
> drivers/pwm/pwm-stm32-lp.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
Applied,
On Fri, Jul 20, 2018 at 09:16:32AM +0200, Fabrice Gasnier wrote:
> LPTimer has only one pwm channel (npwm = 1). Remove useless for loop
> in remove routine.
>
> Signed-off-by: Fabrice Gasnier
> ---
> drivers/pwm/pwm-stm32-lp.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
Applied,
On Fri, Aug 17, 2018 at 06:03:43AM -0700, Barry Song wrote:
> as you are already in a tasklet, it is unnecessary to call spin_lock_bh.
>
> Signed-off-by: Barry Song <21cn...@gmail.com>
Acked-by: Ludovic Desroches
Thanks
> ---
> drivers/dma/at_xdmac.c | 4 ++--
> 1 file changed, 2
On Fri, Aug 17, 2018 at 06:03:43AM -0700, Barry Song wrote:
> as you are already in a tasklet, it is unnecessary to call spin_lock_bh.
>
> Signed-off-by: Barry Song <21cn...@gmail.com>
Acked-by: Ludovic Desroches
Thanks
> ---
> drivers/dma/at_xdmac.c | 4 ++--
> 1 file changed, 2
Wolfram Sang writes:
> On Thu, Aug 16, 2018 at 10:43:14AM +0200, Esben Haabendal wrote:
>> From: Esben Haabendal
>>
>> Gives substantial performance improvement for transfers larger than 16
>> bytes (DMA_THRESHOLD). Smaller transfers are unaffected.
>>
>> Signed-off-by: Esben Haabendal
>
>
Wolfram Sang writes:
> On Thu, Aug 16, 2018 at 10:43:14AM +0200, Esben Haabendal wrote:
>> From: Esben Haabendal
>>
>> Gives substantial performance improvement for transfers larger than 16
>> bytes (DMA_THRESHOLD). Smaller transfers are unaffected.
>>
>> Signed-off-by: Esben Haabendal
>
>
Rerun the pad calibration procedure before sdhci_request() if
the 100 ms recalibration interval has been exceeded.
Signed-off-by: Aapo Vienamo
---
drivers/mmc/host/sdhci-tegra.c | 22 ++
1 file changed, 22 insertions(+)
diff --git a/drivers/mmc/host/sdhci-tegra.c
On Sun, Aug 19, 2018 at 03:35:02PM +0530, Nishad Kamdar wrote:
> #define N_MSG(evt, fmt, args...)
> /*
> -do {\
> -if ((DBG_EVT_##evt) & sd_debug_zone[host->id]) { \
> -printk(KERN_ERR TAG"%d -> "fmt" <- %s() : L<%d> PID<%s><0x%x>\n", \
> -host->id, ##args ,
Rerun the pad calibration procedure before sdhci_request() if
the 100 ms recalibration interval has been exceeded.
Signed-off-by: Aapo Vienamo
---
drivers/mmc/host/sdhci-tegra.c | 22 ++
1 file changed, 22 insertions(+)
diff --git a/drivers/mmc/host/sdhci-tegra.c
On Sun, Aug 19, 2018 at 03:35:02PM +0530, Nishad Kamdar wrote:
> #define N_MSG(evt, fmt, args...)
> /*
> -do {\
> -if ((DBG_EVT_##evt) & sd_debug_zone[host->id]) { \
> -printk(KERN_ERR TAG"%d -> "fmt" <- %s() : L<%d> PID<%s><0x%x>\n", \
> -host->id, ##args ,
Allow SDHCI drivers to hook code before and after sdhci_request() by
making it externally visible.
Signed-off-by: Aapo Vienamo
---
drivers/mmc/host/sdhci.c | 3 ++-
drivers/mmc/host/sdhci.h | 1 +
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/mmc/host/sdhci.c
Hi all,
This series implements pad drive strength recalibration. The calibration
is rerun to compensate possible changes in temperature. The calibration
procedure is rerun as part of mmc_host_ops.request before
sdhci_request() is run. The calibration is executed only if the 100 ms
recalibration
Allow SDHCI drivers to hook code before and after sdhci_request() by
making it externally visible.
Signed-off-by: Aapo Vienamo
---
drivers/mmc/host/sdhci.c | 3 ++-
drivers/mmc/host/sdhci.h | 1 +
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/mmc/host/sdhci.c
Hi all,
This series implements pad drive strength recalibration. The calibration
is rerun to compensate possible changes in temperature. The calibration
procedure is rerun as part of mmc_host_ops.request before
sdhci_request() is run. The calibration is executed only if the 100 ms
recalibration
On Fri, Aug 17, 2018 at 11:51:09PM -0700, Sinan Kaya wrote:
> --- a/drivers/pci/hotplug/pciehp_ctrl.c
> +++ b/drivers/pci/hotplug/pciehp_ctrl.c
> @@ -222,9 +222,27 @@ void pciehp_handle_disable_request(struct slot *slot)
> void pciehp_handle_presence_or_link_change(struct slot *slot, u32 events)
On Fri, Aug 17, 2018 at 11:51:09PM -0700, Sinan Kaya wrote:
> --- a/drivers/pci/hotplug/pciehp_ctrl.c
> +++ b/drivers/pci/hotplug/pciehp_ctrl.c
> @@ -222,9 +222,27 @@ void pciehp_handle_disable_request(struct slot *slot)
> void pciehp_handle_presence_or_link_change(struct slot *slot, u32 events)
Wolfram Sang writes:
> On Thu, Aug 16, 2018 at 10:43:13AM +0200, Esben Haabendal wrote:
>> From: Esben Haabendal
>>
>> Always update the stopped state when busy status have been checked.
>> This is identical to what was done before, with the exception of error
>> handling.
>> Without this
Wolfram Sang writes:
> On Thu, Aug 16, 2018 at 10:43:13AM +0200, Esben Haabendal wrote:
>> From: Esben Haabendal
>>
>> Always update the stopped state when busy status have been checked.
>> This is identical to what was done before, with the exception of error
>> handling.
>> Without this
At present, the "parent <- child" and "suppiler <- consumer" ordering info
are stored duplicate in two places dpm_list and devices_kset, and
corresponding, there are two sets of routines to manipulate them. The patch
pushes the dpm_list and dpm_list_mtx out of CONFIG_PM, and let
device_shutdown()
At present, the "parent <- child" and "suppiler <- consumer" ordering info
are stored duplicate in two places dpm_list and devices_kset, and
corresponding, there are two sets of routines to manipulate them. The patch
pushes the dpm_list and dpm_list_mtx out of CONFIG_PM, and let
device_shutdown()
Now, shutdown seq is unified with PM, and there is no need to maintain the
"parent <- child" or "supplier <- consumer" order in devices_kset any more,
hence removing the corresponding routines
Cc: Greg Kroah-Hartman
Cc: "Rafael J. Wysocki"
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Pingfan
Now, shutdown seq is unified with PM, and there is no need to maintain the
"parent <- child" or "supplier <- consumer" order in devices_kset any more,
hence removing the corresponding routines
Cc: Greg Kroah-Hartman
Cc: "Rafael J. Wysocki"
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Pingfan
Consider the shutdown as a system state transition, i.e. something like
suspend, hibernate, hence move it under the base/power. (This is a first
step to unify the duplicate code logic on devices_kset and dpm_list.)
Cc: Greg Kroah-Hartman
Cc: "Rafael J. Wysocki"
Cc: linux-kernel@vger.kernel.org
Consider the shutdown as a system state transition, i.e. something like
suspend, hibernate, hence move it under the base/power. (This is a first
step to unify the duplicate code logic on devices_kset and dpm_list.)
Cc: Greg Kroah-Hartman
Cc: "Rafael J. Wysocki"
Cc: linux-kernel@vger.kernel.org
At present, the "parent <- child" and "suppiler <- consumer" ordering info
are stored duplicate in two places dpm_list and devices_kset, and
corresponding, there are two sets of routines to manipulate them. The patch
pushes the dpm_list and dpm_list_mtx out of CONFIG_PM, and let
device_shutdown()
At present, the "parent <- child" and "suppiler <- consumer" ordering info
are stored duplicate in two places dpm_list and devices_kset, and
corresponding, there are two sets of routines to manipulate them. The patch
pushes the dpm_list and dpm_list_mtx out of CONFIG_PM, and let
device_shutdown()
On Thu, Aug 16, 2018 at 10:43:14AM +0200, Esben Haabendal wrote:
> From: Esben Haabendal
>
> Gives substantial performance improvement for transfers larger than 16
> bytes (DMA_THRESHOLD). Smaller transfers are unaffected.
>
> Signed-off-by: Esben Haabendal
This needs to go via arm-soc. The
On Thu, Aug 16, 2018 at 10:43:14AM +0200, Esben Haabendal wrote:
> From: Esben Haabendal
>
> Gives substantial performance improvement for transfers larger than 16
> bytes (DMA_THRESHOLD). Smaller transfers are unaffected.
>
> Signed-off-by: Esben Haabendal
This needs to go via arm-soc. The
On Sat, Aug 18, 2018 at 11:57:00PM +0200, Rafael J. Wysocki wrote:
> So I have given more consideration to this and my conclusion is that
> restarting the tick between cpuidle_select() and call_cpuidle() is a
> bad idea.
Ack, we should only restart the tick once we leave the idle loop.
> First
On Sat, Aug 18, 2018 at 11:57:00PM +0200, Rafael J. Wysocki wrote:
> So I have given more consideration to this and my conclusion is that
> restarting the tick between cpuidle_select() and call_cpuidle() is a
> bad idea.
Ack, we should only restart the tick once we leave the idle loop.
> First
On Thu, Aug 16, 2018 at 10:43:12AM +0200, Esben Haabendal wrote:
> From: Esben Haabendal
>
> This fixes a race condition, where the DMAEN bit ends up being set after
> I2C slave has transmitted a byte following the dummy read. When that
> happens, an interrupt is generated instead, and no DMA
On Thu, Aug 16, 2018 at 10:43:12AM +0200, Esben Haabendal wrote:
> From: Esben Haabendal
>
> This fixes a race condition, where the DMAEN bit ends up being set after
> I2C slave has transmitted a byte following the dummy read. When that
> happens, an interrupt is generated instead, and no DMA
On Thu, Aug 16, 2018 at 10:43:13AM +0200, Esben Haabendal wrote:
> From: Esben Haabendal
>
> Always update the stopped state when busy status have been checked.
> This is identical to what was done before, with the exception of error
> handling.
> Without this change, some errors cause the
On Thu, Aug 16, 2018 at 10:43:13AM +0200, Esben Haabendal wrote:
> From: Esben Haabendal
>
> Always update the stopped state when busy status have been checked.
> This is identical to what was done before, with the exception of error
> handling.
> Without this change, some errors cause the
From: Sean Wang
v2:
add fixes and enhancements based on [1]
* include /sys/kernel/debug/usb/devices portion in the commit message.
* turn default into n for config BT_HCIBTUSB_MTK in Kconfig
* only add MediaTek support to btusb.c
* drop cmd_sync callback usage
* use __hci_cmd_send to send WMT
From: Sean Wang
This adds the support of enabling MT7668U Bluetooth function running
on the top of btusb driver.
The information in /sys/kernel/debug/usb/devices about the Bluetooth
device is listed as the below.
T: Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=5000 MxCh= 0
D: Ver= 3.00
From: Sean Wang
v2:
add fixes and enhancements based on [1]
* include /sys/kernel/debug/usb/devices portion in the commit message.
* turn default into n for config BT_HCIBTUSB_MTK in Kconfig
* only add MediaTek support to btusb.c
* drop cmd_sync callback usage
* use __hci_cmd_send to send WMT
From: Sean Wang
This adds the support of enabling MT7668U Bluetooth function running
on the top of btusb driver.
The information in /sys/kernel/debug/usb/devices about the Bluetooth
device is listed as the below.
T: Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=5000 MxCh= 0
D: Ver= 3.00
On Monday, August 20, 2018 12:15:11 PM CEST Ding Xiang wrote:
> For single statement blocks,braces are not necessary.
> And "else" is not useful after return. So,remove these code.
>
> Signed-off-by: Ding Xiang
> ---
> drivers/cpufreq/acpi-cpufreq.c | 10 --
> 1 file changed, 4
From: Sean Wang
This adds the support of enabling MT7663U Bluetooth function running
on the top of btusb driver.
The information in /sys/kernel/debug/usb/devices about the Bluetooth
device is listed as the below.
T: Bus=04 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 5 Spd=5000 MxCh= 0
D: Ver= 3.00
From: Sean Wang
This adds the support of enabling MT7663U Bluetooth function running
on the top of btusb driver.
The information in /sys/kernel/debug/usb/devices about the Bluetooth
device is listed as the below.
T: Bus=04 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 5 Spd=5000 MxCh= 0
D: Ver= 3.00
On Monday, August 20, 2018 12:15:11 PM CEST Ding Xiang wrote:
> For single statement blocks,braces are not necessary.
> And "else" is not useful after return. So,remove these code.
>
> Signed-off-by: Ding Xiang
> ---
> drivers/cpufreq/acpi-cpufreq.c | 10 --
> 1 file changed, 4
For single statement blocks,braces are not necessary.
And "else" is not useful after return. So,remove these code.
Signed-off-by: Ding Xiang
---
drivers/cpufreq/acpi-cpufreq.c | 10 --
1 file changed, 4 insertions(+), 6 deletions(-)
diff --git a/drivers/cpufreq/acpi-cpufreq.c
For single statement blocks,braces are not necessary.
And "else" is not useful after return. So,remove these code.
Signed-off-by: Ding Xiang
---
drivers/cpufreq/acpi-cpufreq.c | 10 --
1 file changed, 4 insertions(+), 6 deletions(-)
diff --git a/drivers/cpufreq/acpi-cpufreq.c
On Wednesday, August 15, 2018 2:01:02 AM CEST Henry Willard wrote:
> If cppc_cpufreq.ko is deleted at the same time that tuned-adm is
> changing profiles, there is a small chance that a race can occur
> between cpufreq_dbs_governor_exit() and cpufreq_dbs_governor_limits()
> resulting in a system
On Wednesday, August 15, 2018 2:01:02 AM CEST Henry Willard wrote:
> If cppc_cpufreq.ko is deleted at the same time that tuned-adm is
> changing profiles, there is a small chance that a race can occur
> between cpufreq_dbs_governor_exit() and cpufreq_dbs_governor_limits()
> resulting in a system
Linus,
Enjoy!
The following changes since commit ce397d215ccd07b8ae3f71db689aedb85d56ab40:
Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/lee/backlight.git
backlight-next-4.19
for you to fetch changes up
Linus,
Enjoy!
The following changes since commit ce397d215ccd07b8ae3f71db689aedb85d56ab40:
Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/lee/backlight.git
backlight-next-4.19
for you to fetch changes up
The conversion to sg_copy_{from,to}_buffer has been done in the wrong
way. sg_copy_to_buffer is a copy from an SG list to a linear buffer so
it can't replace memcpy(buf + offset, , remaining) where buf is
the virtual address of the SG. Same for sg_copy_to_buffer but in the
opposite way.
The conversion to sg_copy_{from,to}_buffer has been done in the wrong
way. sg_copy_to_buffer is a copy from an SG list to a linear buffer so
it can't replace memcpy(dest, host->virt_base, data->sg->length) where
dest is the virtual address of the SG. Same for sg_copy_from_buffer
but in the
The conversion to sg_copy_{from,to}_buffer has been done in the wrong
way. sg_copy_to_buffer is a copy from an SG list to a linear buffer so
it can't replace memcpy(buf + offset, , remaining) where buf is
the virtual address of the SG. Same for sg_copy_to_buffer but in the
opposite way.
The conversion to sg_copy_{from,to}_buffer has been done in the wrong
way. sg_copy_to_buffer is a copy from an SG list to a linear buffer so
it can't replace memcpy(dest, host->virt_base, data->sg->length) where
dest is the virtual address of the SG. Same for sg_copy_from_buffer
but in the
Hi,
Dougas Gilbert noticed that atmel-mci was broken with the 4.18 release.
He found the culprit commit which is 5b4277814e3fd
("[PATCH 2/7] mmc: atmel-mci: use sg_copy_{from,to}_buffer"). The from/to
logic was inverted: sg_copy_to_buffer copies from an SG list to a linear
buffer so it can't
Hi,
Dougas Gilbert noticed that atmel-mci was broken with the 4.18 release.
He found the culprit commit which is 5b4277814e3fd
("[PATCH 2/7] mmc: atmel-mci: use sg_copy_{from,to}_buffer"). The from/to
logic was inverted: sg_copy_to_buffer copies from an SG list to a linear
buffer so it can't
Could you please provide your input? Thanks.
Zhe
On 2018年08月14日 23:33, zhe...@windriver.com wrote:
> From: He Zhe
>
> memory_corruption_check[{_period|_size}]'s handlers do not check input
> argument before passing it to kstrtoul or simple_strtoull. The argument
> would be a NULL pointer if
Could you please provide your input? Thanks.
Zhe
On 2018年08月14日 23:33, zhe...@windriver.com wrote:
> From: He Zhe
>
> memory_corruption_check[{_period|_size}]'s handlers do not check input
> argument before passing it to kstrtoul or simple_strtoull. The argument
> would be a NULL pointer if
From: Oscar Salvador
Currently, NODEMASK_ALLOC allocates a nodemask_t with kmalloc when
NODES_SHIFT is higher than 8, otherwise it declares it within the stack.
The comment says that the reasoning behind this, is that nodemask_t will be
256 bytes when NODES_SHIFT is higher than 8, but this is
From: Oscar Salvador
Currently, NODEMASK_ALLOC allocates a nodemask_t with kmalloc when
NODES_SHIFT is higher than 8, otherwise it declares it within the stack.
The comment says that the reasoning behind this, is that nodemask_t will be
256 bytes when NODES_SHIFT is higher than 8, but this is
On Sat, 18 Aug 2018 05:49:32 +
Naga Sureshkumar Relli wrote:
> Hi Boris,
>
> Thanks for the review.
>
> > -Original Message-
> > From: Boris Brezillon [mailto:boris.brezil...@bootlin.com]
> > Sent: Friday, August 17, 2018 11:29 PM
> > To: Naga Sureshkumar Relli
> > Cc:
On Sat, 18 Aug 2018 05:49:32 +
Naga Sureshkumar Relli wrote:
> Hi Boris,
>
> Thanks for the review.
>
> > -Original Message-
> > From: Boris Brezillon [mailto:boris.brezil...@bootlin.com]
> > Sent: Friday, August 17, 2018 11:29 PM
> > To: Naga Sureshkumar Relli
> > Cc:
Hi Ravi,
On 2018-08-17 23:21, RaviChandra Sadineni wrote:
> From: RaviChandra Sadineni
>
> hi Merek,
>
> Unfortunately I could not get the device to boot even after using the
> exynos_defconfig.
> Can you please try this patch and see if this fixes the issue. If not can you
> enable the
>
Hi Ravi,
On 2018-08-17 23:21, RaviChandra Sadineni wrote:
> From: RaviChandra Sadineni
>
> hi Merek,
>
> Unfortunately I could not get the device to boot even after using the
> exynos_defconfig.
> Can you please try this patch and see if this fixes the issue. If not can you
> enable the
>
Linus,
NOTE: Please be aware that there are 3 trivial conflicts to be aware
of when merging. 2 of them were fixed in -next by Stephen [0][1], the
other one (in drivers/gpu/drm/i915/Kconfig) fixed itself (?)), but is
also very easy to rectify - both lines should be added.
[0]
Linus,
NOTE: Please be aware that there are 3 trivial conflicts to be aware
of when merging. 2 of them were fixed in -next by Stephen [0][1], the
other one (in drivers/gpu/drm/i915/Kconfig) fixed itself (?)), but is
also very easy to rectify - both lines should be added.
[0]
The autofs_sbi() inline function does not check the super block
magic number to verify it has been given an autofs super block.
Reported-by: syzbot+87c3c541582e56943...@syzkaller.appspotmail.com
Signed-off-by: Ian Kent
---
fs/autofs/autofs_i.h |4 +++-
fs/autofs/inode.c|1 -
2 files
The autofs_sbi() inline function does not check the super block
magic number to verify it has been given an autofs super block.
Reported-by: syzbot+87c3c541582e56943...@syzkaller.appspotmail.com
Signed-off-by: Ian Kent
---
fs/autofs/autofs_i.h |4 +++-
fs/autofs/inode.c|1 -
2 files
Hi Torsten,
On 17/08/18 11:27, Torsten Duwe wrote:
This is more an RFC in the original sense: is this basically
the correct approach? (as I had to tweak the save_stack API a bit).
In particular the code does not detect interrupts and exception
frames, and does not yet check whether the code
Hi Torsten,
On 17/08/18 11:27, Torsten Duwe wrote:
This is more an RFC in the original sense: is this basically
the correct approach? (as I had to tweak the save_stack API a bit).
In particular the code does not detect interrupts and exception
frames, and does not yet check whether the code
Hi Marcus,
On 08/19/2018 11:50 PM, Marcus Folkesson wrote:
Hi,
On Tue, Aug 07, 2018 at 12:27:03PM +0200, Parthiban Nallathambi wrote:
Add support for VCNL4035, which is capable of Ambient light
sensing (ALS) and proximity function. This patch adds support
only for ALS function
Signed-off-by:
Hi Marcus,
On 08/19/2018 11:50 PM, Marcus Folkesson wrote:
Hi,
On Tue, Aug 07, 2018 at 12:27:03PM +0200, Parthiban Nallathambi wrote:
Add support for VCNL4035, which is capable of Ambient light
sensing (ALS) and proximity function. This patch adds support
only for ALS function
Signed-off-by:
On 08/08/2018 03:40 PM, Krzysztof Kozlowski wrote:
> Sylwester,
>
> It still did not reach linux-next... do you expect someone to pick it up?
No, please disregard this patch. I decided to drop it as it would
really be needed
for less than one release period.
--
Regards,
Sylwester
On 08/08/2018 03:40 PM, Krzysztof Kozlowski wrote:
> Sylwester,
>
> It still did not reach linux-next... do you expect someone to pick it up?
No, please disregard this patch. I decided to drop it as it would
really be needed
for less than one release period.
--
Regards,
Sylwester
On Fri, Aug 17, 2018 at 11:51:10PM -0700, Sinan Kaya wrote:
> +static int pciehp_control_surprise_error(struct controller *ctrl, bool
> enable)
The return value isn't checked, so this could return void.
> @@ -280,6 +303,9 @@ static int pciehp_probe(struct pcie_device *dev)
>
>
On Fri, Aug 17, 2018 at 11:51:10PM -0700, Sinan Kaya wrote:
> +static int pciehp_control_surprise_error(struct controller *ctrl, bool
> enable)
The return value isn't checked, so this could return void.
> @@ -280,6 +303,9 @@ static int pciehp_probe(struct pcie_device *dev)
>
>
On Sat, Aug 18, 2018 at 2:50 PM Thomas Gleixner wrote:
>
> On Fri, 17 Aug 2018, Greg Kroah-Hartman wrote:
> > On Fri, Aug 17, 2018 at 02:39:00PM +0200, Jinpu Wang wrote:
> > >
> > > I found the problem, CONFIG_HOTPLUG_SMT is enable due to CONFIG_SMP,
> > > but I did explicitly enable
On Mon, Aug 20, 2018 at 12:12:47PM +1000, Benjamin Herrenschmidt wrote:
> On Sun, 2018-08-19 at 09:46 -0700, Linus Torvalds wrote:
> > On Sun, Aug 19, 2018 at 6:51 AM Sedat Dilek wrote:
> > >
> > > This can be dropped with commit 771c035372a036f83353eef46dbb829780330234
> > > ("deprecate the
701 - 800 of 844 matches
Mail list logo
