Recent changes (4.4.0+) in module loader triggered oops on ARM :
The module in question is in-tree module :
drivers/misc/ti-st/st_drv.ko
The BUG is here :
[ 53.638335] [ cut here ]
[ 53.642967] kernel BUG at mm/memory.c:1878!
[ 53.647153] Internal error: Oops - BUG: 0
On Fri, Jan 22, 2016 at 12:33:24PM +0800, kernel test robot wrote:
> Greetings,
>
> 0day kernel testing robot got the below dmesg and the first bad commit is
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>
> commit 75925e1ad7f5a4e867bd14ff8e7f114ea1596434
>
On Thu, 21 Jan 2016, Shuah Khan wrote:
> On 01/21/2016 04:03 PM, John Stultz wrote:
> > David Herrmann mailed me pointing out that one of the
> > changes that landed in 4.5-rc broke users of ADJ_SETOFFSET
> > when used with ADJ_NANO.
> >
> > I've implemented a fix to this issue and also
On Thu, Jan 21, 2016 at 09:42:53AM +, Mel Gorman wrote:
> On Wed, Jan 20, 2016 at 04:43:35PM -0800, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.3.4 release.
>
> Any particular reason why "[PATCH 4.3-stable 0/5] Disable automatic numa
> balancing on
On Thu, Jan 21, 2016 at 01:37:34AM +, Ben Hutchings wrote:
> On Wed, 2016-01-20 at 16:43 -0800, Greg Kroah-Hartman wrote:
> > 4.3-stable review patch. If anyone has any objections, please let me
> > know.
> >
> > --
> >
> > From: Ben Hutchings
> [...]
>
> It's really From:
On Thu, Jan 21, 2016 at 08:06:27AM +0100, Willy Tarreau wrote:
> On Wed, Jan 20, 2016 at 04:14:51PM -0700, Shuah Khan wrote:
> > On 01/20/2016 03:00 PM, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 3.10.95 release.
> > > There are 35 patches in this series,
On Thu, Jan 21, 2016 at 04:24:36AM -0800, Guenter Roeck wrote:
> On 01/20/2016 04:43 PM, Greg Kroah-Hartman wrote:
> >This is the start of the stable review cycle for the 4.3.4 release.
> >There are 55 patches in this series, all will be posted as a response
> >to this one. If anyone has any
On Wed, Jan 20, 2016 at 06:39:48PM -0700, Shuah Khan wrote:
> On 01/20/2016 05:43 PM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.3.4 release.
> > There are 55 patches in this series, all will be posted as a response
> > to this one. If anyone has any
Hi Heiko,
On 2016年01月21日 17:21, Heiko Stuebner wrote:
Hi Xing,
Am Mittwoch, 20. Januar 2016, 16:37:17 schrieb Xing Zheng:
The apll may be closed if there are some child clock nodes below
it when the device startup. Therefore, the apll should be keep
critical.
The apll tree like this:
This patch add correct err handle if dw_mci_ctrl_reset
failed while probing.
Signed-off-by: Shawn Lin
---
drivers/mmc/host/dw_mmc.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/mmc/host/dw_mmc.c b/drivers/mmc/host/dw_mmc.c
index 065a8f5..ec19984 100644
---
On 2016-01-21 06:22, Dave Jones wrote:
> On Wed, Jan 20, 2016 at 06:22:04PM +, Linux Kernel wrote:
> > Web:
> https://git.kernel.org/torvalds/c/93209d65c1d38f86ffb3f61a1214130b581a9709
> > Commit: 93209d65c1d38f86ffb3f61a1214130b581a9709
> > Parent:
This patch make num_slots to 1 if pdata->num_slot is not
defined. Meanwhile, we need to make sure num_slots should
not larger that the supported slots
Signed-off-by: Shawn Lin
---
drivers/mmc/host/dw_mmc.c | 16 +---
1 file changed, 9 insertions(+), 7 deletions(-)
diff --git
On 22 January 2016 at 03:32, Pavel Machek wrote:
>
>> - goto repeat;
>> +
>> + /*check expires firstly for auto suspend mode,
>> + *if not, just go ahead to the async
>> + */
>
> English, coding style.
>
* Alexei Starovoitov wrote:
> > > I could be missing something. I think either this patch is not need or
> > > you
> > > need to teach the tool to ignore all JITed stuff. I don't think it's
> > > practical to annotate everything. Different JITs do their own magic. s390
> > > JIT is even
On Thu, Jan 21, 2016 at 04:52:45PM -0800, Joe Perches wrote:
> Whitespace patches, where git diff -w does not show
> any difference and objdiff on the objects for a few
> randconfigs are identical, maybe could be sifted
> into a separate category from other patches.
> Maybe the kbuild test robot
On 2016年01月21日 22:56, Thierry Reding wrote:
> * PGP Signed by an unknown key
>
> On Mon, Jan 18, 2016 at 06:02:25PM +0800, Wei Ni wrote:
>> This patchset adds following functions for tegra_soctherm driver:
>> 1. add T210 support.
>> 2. export debugfs to show some registers.
>> 3. add thermtrip
Add F81866 GPIO supports
Fintek F81866 is a SuperIO. It contains HWMON/GPIO/Serial Ports.
and it has totally 72(9x8 sets) gpio pins.
Here is the PDF spec:
http://www.alldatasheet.com/datasheet-pdf/pdf/459085/FINTEK/F81866AD-I.html
The control method is the same with F7188x, but we should care
Fintek F81866 is a SuperIO. It contains HWMON/GPIO/Serial Ports.
and it has totally 72(9x8 sets) gpio pins.
Here is the PDF spec:
http://www.alldatasheet.com/datasheet-pdf/pdf/459085/FINTEK/F81866AD-I.html
The control method is the same with F7188x, but we should care the address
of GPIO8x.
cpu_to_chip_id() does a DT walk through to find out the chip id by
taking a contended device tree lock. This adds an unnecessary overhead
in a hot path. So instead of calling cpu_to_chip_id() everytime cache
the chip ids for all cores in the array 'core_to_chip_map' and use it
in the hotpath.
Create sysfs attributes to export throttle information in
/sys/devices/system/cpu/cpufreq/chipN. The newly added sysfs files are as
follows:
1)/sys/devices/system/cpu/cpufreq/chip0/throttle_frequencies
This gives the throttle stats for each of the available frequencies.
The throttle stat of a
In the kworker_thread powernv_cpufreq_work_fn(), we can end up
sending an IPI to a cpu going offline. This is a rare corner case
which is fixed using {get/put}_online_cpus(). Along with this fix,
this patch adds changes to do oneshot cpumask_{clear/and} operation.
Suggested-by: Shreyas B Prabhu
Currently we use printk message to notify the throttle event. But this
can flood the console if the cpu is throttled frequently. So replace the
printk with the tracepoint to notify the throttle event. And also events
like throttle below nominal frequency and OCC_RESET are reduced to
This patch adds the powernv_throttle tracepoint to trace the CPU
frequency throttling event, which is used by the powernv-cpufreq
driver in POWER8.
Signed-off-by: Shilpasri G Bhat
Reviewed-by: Gautham R. Shenoy
CC: Ingo Molnar
CC: Steven Rostedt
---
No changes since v2.
In POWER8, OCC(On-Chip-Controller) can throttle the frequency of the
CPU when the chip crosses its thermal and power limits. Currently,
powernv-cpufreq driver detects and reports this event as a console
message. Some machines may not sustain the max turbo frequency in all
conditions and can be
On 01/22/2016 01:12 AM, David Rientjes wrote:
NACK to your patch as it is just covering up buggy code silently. The
problem needs to be addressed in change_memory_common() to return if
there is no size to change (numpages == 0). It's a two line fix to
that function.
So add a WARN_ON there
Hi, Arnaldo
Sorry for my tardy response.
On 01/21/2016 11:45 PM, Arnaldo Carvalho de Melo wrote:
Em Fri, Jan 08, 2016 at 08:39:34PM +0900, Taeung Song escreveu:
Explain 'annotate' section and its variables.
'hide_src_code', 'use_offset', 'jump_arrows',
'show_linenr', 'show_nr_jump' and
On Fri, Jan 22, 2016 at 12:35 AM, Andrew Morton
wrote:
> On Thu, 21 Jan 2016 17:22:31 +0200 Andy Shevchenko
> wrote:
>
>> From: Robert Elliott
>>
>> Print the base in the best-fit B, KiB, MiB, etc. units rather than
>> always MiB. This avoids rounding, which can be misleading.
>>
>> Use proper
Hi Wang,
[auto build test WARNING on tip/perf/core]
[also build test WARNING on v4.4 next-20160121]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Wang-Nan/perf-core-Get-rid-of-uses-dynamic
Currently /proc/meminfo will not show the memory from module.
This entry "VmallocUsed: xxx" only shows the memory in the range
[VMALLOC_START, VMALLOC_END] alloced by vmalloc() ->... ->
__vmalloc_node_range().
The memory which used by module is from module_alloc() ->
__vmalloc_node_range().
> Hi Bean,
>
> On Thu, 21 Jan 2016 01:06:48 +
> Bean Huo 霍斌斌 (beanhuo) wrote:
>
> > Hi, Adam and Boris
> >
> > For Micron MT25Q ,MT25T and MT35Q, they does not exist this action
> > even they are Multi-die devices. So when the last byte of the die
> > selected is read, the next byte output
This patch adds documentation for the DT bindings of the charger
subdevice of ACT8945A MFD.
Signed-off-by: Wenyou Yang
Reviewed-by: Krzysztof Kozlowski
---
Changes in v7: None
Changes in v6: None
Changes in v5:
- collect Reviewed-by from Krzysztof.
Changes in v4:
- change the properties
On 22 January 2016 at 03:20, kernel test robot
wrote:
> FYI, we noticed the below changes on
>
> https://git.linaro.org/people/ard.biesheuvel/linux-arm kallsyms-text-relative
> commit 06862f34f614bb6ff6a9fc9c4b0d849e2ee2018d ("kallsyms: add support for
> relative offsets in kallsyms address
This patch adds new driver for Active-semi ACT8945A ActivePath
charger (part of ACT8945A MFD driver) providing power supply class
information to userspace.
The driver can be configured through DT (such as, total timer,
precondition timer and input over-voltage threshold).
Signed-off-by: Wenyou
The ACT8945A is a Multi Function Device with the following subdevices:
- Regulator
- Charger
This patch set is to add regulator driver for ACT8945A.
It is based on the patch set:
http://lists.infradead.org/pipermail/linux-arm-kernel/2016-January/401044.html
Changes in v7:
- use the
On s390 with CONFIG_WARN_DYNAMIC_STACK set, 'uses dynamic stack
allocation' warning is issued when defining 'struct perf_sample_data'
local variable.
This patch suppress this warning by allocating extra 255 bytes and
compute aligned pointer manually.
Reported-by: kbuild test robot
On 01/22/2016 05:34 PM, Alexey Kardashevskiy wrote:
Recent change 03a76b60 "vfio: Include No-IOMMU mode" disabled VFIO
on systems which do not implement iommu_ops for the PCI bus even though
there is an VFIO IOMMU driver for it such as SPAPR TCE driver for
PPC64/powernv platform.
This moves
The Active-semi ACT8945A PMIC is a Multi-Function Device, it has
two subdevices:
- Regulator
- Charger
This patch adds documentation for ACT8945A DT bindings.
Signed-off-by: Wenyou Yang
Acked-by: Rob Herring
---
Changes in v7: None
Changes in v6:
- change the regulator name.
Changes in
This patch adds support for the Active-semi ACT8945A PMIC.
It is a Multi Function Device with the following subdevices:
- Regulator
- Charger
It is interfaced to the host controller using I2C interface,
ACT8945A is a child device of the I2C.
Signed-off-by: Wenyou Yang
Reviewed-by: Krzysztof
This patch set adds support for the Active-semi ACT8945A PMIC
MFD driver. It is a Multi Function Device with the following
subdevices:
- Regulator
- Charger
It is interfaced to the host controller using I2C interface,
ACT8945A is a child device of the I2C.
Changes in v7:
- remove struct
Hi,
During my presentation last year at Linuxcon Japan [1], I released
a proof-of-concept patch [2] for the seccomp subsystem. The main
purpose of that patch was to let applications restrict the order
in which their system calls are requested. In more technical terms,
a host-based anomaly
This patch allows applications to restrict the order in which
its system calls may be requested. In order to do that, we
provide seccomp-BPF scripts with information about the
previous system call requested.
An example use case consists of detecting (and stopping) return
oriented attacks that
On 22 January 2016 at 04:44, Michael Ellerman wrote:
> On Thu, 2016-01-21 at 14:55 -0800, Kees Cook wrote:
>> On Thu, Jan 21, 2016 at 2:50 PM, Andrew Morton
>> wrote:
>> > On Thu, 21 Jan 2016 18:19:43 +0100 Ard Biesheuvel
>> > wrote:
>> >
>> > > Similar to how relative extables are
Hi Peter,
Thank you for so much advice.
> -Original Message-
> From: Peter Korsgaard [mailto:jac...@gmail.com] On Behalf Of Peter Korsgaard
> Sent: 2016年1月21日 4:25
> To: Yang, Wenyou
> Cc: Sebastian Reichel ; Dmitry Eremin-Solenikov
> ; David Woodhouse ; Rob
> Herring ; Pawel Moll ;
Recent change 03a76b60 "vfio: Include No-IOMMU mode" disabled VFIO
on systems which do not implement iommu_ops for the PCI bus even though
there is an VFIO IOMMU driver for it such as SPAPR TCE driver for
PPC64/powernv platform.
This moves iommu_present() call under #ifdef CONFIG_VFIO_NOIOMMU as
On Thu, Jan 21, 2016 at 03:08:59PM +0530, Shilpasri G Bhat wrote:
> Signed-off-by: Shilpasri G Bhat
Reviewed-by: Gautham R. Shenoy
--
Thanks and Regards
gautham.
On 2016/1/22 13:56, 平松雅巳 / HIRAMATU，MASAMI wrote:
From: Wangnan (F) [mailto:wangn...@huawei.com]
On 2016/1/20 21:59, Arnaldo Carvalho de Melo wrote:
Em Tue, Jan 19, 2016 at 09:33:06PM +, Ben Hutchings escreveu:
gcc 5 doesn't seem to care about these, but gcc 6 does and that
results in a
On 01/22/2016 01:12 AM, David Rientjes wrote:
> On Thu, 21 Jan 2016, Mika Penttilä wrote:
>
>> Recent changes (4.4.0+) in module loader triggered oops on ARM :
>>
>> The module in question is in-tree module :
>> drivers/misc/ti-st/st_drv.ko
>>
>> The BUG is here :
>>
>> [ 53.638335]
On Thu, 21 Jan 2016, Waiman Long wrote:
On 01/21/2016 04:29 AM, Ding Tianhong wrote:
I got the vmcore and found that the ifconfig is already in the wait_list of the
rtnl_lock for 120 second, but my process could get and release the rtnl_lock
normally several times in one second, so it means
(I thought I had sent this earlier, but apparently the e-mail never
left my machine. Apologies if this is a duplicate, but I'm pretty
sure it was never sent on my end.)
The following changes since commit f41683a204ea61568f0fd0804d47c19561f2ee39:
Merge tag 'ext4_for_linus_stable' of
Hi Arnaldo,
On Wednesday 13 January 2016 10:29 PM, Arnaldo Carvalho de Melo wrote:
Em Tue, Dec 29, 2015 at 03:38:40PM +0530, Ravi Bangoria escreveu:
'perf kvm {record|report}' is used to record and report the profiled
performance of any workload on a guest. From the host, we can collect
guest
Hi Thor,
On 21.01.2016 19:34, ttha...@opensource.altera.com wrote:
> From: Thor Thayer
>
> Adding L2 Cache and On-Chip RAM EDAC support for the
> Altera SoCs using the EDAC device model. The SDRAM
> controller is using the Memory Controller model.
>
> Each type of ECC is individually
This patch contains core logic for enabling perf kvm {record|report} on
powerpc.
For perf kvm record,
This patch will replace default event(cycle) with kvm_hv:kvm_guest_exit
while recording guest data from host.
For perf kvm report,
This patch makes use of the 'kvm_guest_exit' tracepoint and
On 01/20/2016 10:35 PM, Michael S. Tsirkin wrote:
> On Tue, Dec 01, 2015 at 02:39:45PM +0800, Jason Wang wrote:
>> This patch tries to poll for new added tx buffer or socket receive
>> queue for a while at the end of tx/rx processing. The maximum time
>> spent on polling were specified through a
commit d49dadea7862 ("perf tools: Make 'trace' or 'trace_fields' sort key
default for tracepoint events") makes 'trace' sort key as a default
while displaying report for tracepoint.
As tracepoint(kvm_hv:kvm_guest_exit) is used as a default event for
recording data, perf kvm report will display
This patch changes prototype of perf_event__preprocess_sample() with
additional argument evsel added at last.
This change is required because perf_event__preprocess_sample()
function will use evsel to determine cpumode of samples for powerpc
architecture.
Signed-off-by: Ravi Bangoria
---
'perf kvm {record|report}' is used to record and report the profiled
performance of any workload on a guest. From the host, we can collect
guest kernel statistics which is useful in finding out any contentions
in guest kernel symbols for a certain workload.
This feature is not available on powerpc
>From: Wangnan (F) [mailto:wangn...@huawei.com]
>
>On 2016/1/20 21:59, Arnaldo Carvalho de Melo wrote:
>> Em Tue, Jan 19, 2016 at 09:33:06PM +, Ben Hutchings escreveu:
>>> gcc 5 doesn't seem to care about these, but gcc 6 does and that
>>> results in a build failure.
>> Ben, please CC the
On 01/20/2016 10:09 PM, Michael S. Tsirkin wrote:
> On Tue, Dec 01, 2015 at 02:39:44PM +0800, Jason Wang wrote:
>> Signed-off-by: Jason Wang
> Wow new API with no comments anywhere, and no
> commit log to say what it's good for.
> Want to know what it does and whether
> it's correct? You have
Hi,
> On Thu, Jan 21, 2016 at 12:33:11PM +0100, Lothar Waßmann wrote:
> > > On Thu, Jan 21, 2016 at 11:26:11AM +0100, Lothar Waßmann wrote:
> > > > > On Thu, Jan 21, 2016 at 08:05:24AM +0100, Lothar Waßmann wrote:
> > > > > > > On Wed, Jan 20, 2016 at 01:29:51PM +0100, Lothar Waßmann wrote:
>
>
From: Rich Felker
Add Yoshinori Sato and Rich Felker as maintainers for arch/sh
(SUPERH).
Signed-off-by: Rich Felker
Signed-off-by: Yoshinori Sato
Acked-by: D. Jeff Dionne
Acked-by: Rob Landley
Acked-by: Peter Zijlstra (Intel)
Acked-by: Simon Horman
Acked-by: Geert Uytterhoeven
---
On Thu, Jan 21, 2016 at 08:57:17PM +, Linux Kernel wrote:
> Web:
> https://git.kernel.org/torvalds/c/c6d308534aef6c99904bf5862066360ae067abc4
> Commit: c6d308534aef6c99904bf5862066360ae067abc4
> Parent: 68920c973254c5b71a684645c5f6f82d6732c5d6
> Refname:
> -Original Message-
> From: Radim Krčmář [mailto:rkrc...@redhat.com]
> Sent: Friday, January 22, 2016 4:17 AM
> To: Wu, Feng
> Cc: pbonz...@redhat.com; linux-kernel@vger.kernel.org;
> k...@vger.kernel.org
> Subject: Re: [PATCH v3 3/4] KVM: x86: Add lowest-priority support for vt-d
>
> -Original Message-
> From: Radim Krčmář [mailto:rkrc...@redhat.com]
> Sent: Friday, January 22, 2016 3:50 AM
> To: Wu, Feng
> Cc: pbonz...@redhat.com; linux-kernel@vger.kernel.org;
> k...@vger.kernel.org
> Subject: Re: [PATCH v3 2/4] KVM: x86: Use vector-hashing to deliver lowest-
>
On 01/22/2016 12:07 PM, Shawn Lin wrote:
> On 2016/1/22 10:46, Jaehoon Chung wrote:
>> Hi, Shawn.
>>
>> On 01/21/2016 04:52 PM, Shawn Lin wrote:
>>> num_slots comes from pdata if existing, otherwise from
>>> dw_mci_parse_dt which make it at least one slot. If
>>> num_slots is less than 1 for the
On 2016/1/22 11:21, Alexei Starovoitov wrote:
On Fri, Jan 22, 2016 at 10:21:19AM +0800, Wangnan (F) wrote:
On 2016/1/21 14:51, Wangnan (F) wrote:
On 2016/1/20 10:20, Alexei Starovoitov wrote:
On Wed, Jan 20, 2016 at 09:37:42AM +0800, Wangnan (F) wrote:
On 2016/1/20 1:42, Alexei
Hi Wolfram,
What do you think about this patch?
Thanks,
Zhonghui
On 12/24/2015 10:44 PM, Fu, Zhonghui wrote:
> Now, PM core supports asynchronous suspend/resume mode for devices
> during system suspend/resume, and the power state transition of one
> device may be completed in separate
Hi Wolfram,
What do you think about this patch?
Thanks,
Zhonghui
On 12/24/2015 10:41 PM, Fu, Zhonghui wrote:
> Now, PM core supports asynchronous suspend/resume mode for devices
> during system suspend/resume, and the power state transition of one
> device may be completed in separate
On 1/12/2016 10:43 PM, Ulf Hansson wrote:
> On 28 December 2015 at 16:41, Fu, Zhonghui
> wrote:
>> Now, PM core supports asynchronous suspend/resume mode for devices
>> during system suspend/resume, and the power state transition of one
>> device may be completed in separate kernel thread. PM
This patch enables sdhci-acpi devices to suspend/resume asynchronously.
This will improve system suspend/resume speed. After enabling the
sdhci-acpi devices and all their child devices to suspend/resume
asynchronously on ASUS T100TA, the system suspend-to-idle time is
reduced from 1645ms to
On Thu, Jan 21, 2016 at 09:55:31PM -0600, Josh Poimboeuf wrote:
> On Thu, Jan 21, 2016 at 06:44:28PM -0800, Alexei Starovoitov wrote:
> > On Thu, Jan 21, 2016 at 04:49:27PM -0600, Josh Poimboeuf wrote:
> > > bpf_jit.S has several callable non-leaf functions which don't honor
> > >
Hi All,
I'm glad to announce that SCST version 3.1 has just been released and available
for
download from http://scst.sourceforge.net/downloads.html.
Highlights for this release:
- Cluster support for SCSI reservations. This feature is essential for
initiator-side
clustering approaches based
On Thu, Jan 21, 2016 at 7:21 PM, Keith Busch wrote:
> On Thu, Jan 21, 2016 at 05:12:13PM -0800, Linus Torvalds wrote:
>>
>> I assume that in this case it's simply that
>>
>> - max_sectors is some odd number in sectors (ie 65535)
>>
>> - the block size is larger than a sector (ie 4k)
>
>
On Thu, Jan 21, 2016 at 06:55:41PM -0800, Alexei Starovoitov wrote:
> On Thu, Jan 21, 2016 at 04:49:35PM -0600, Josh Poimboeuf wrote:
> > stacktool reports the following false positive warnings:
> >
> > stacktool: kernel/bpf/core.o: __bpf_prog_run()+0x5c: sibling call from
> > callable
On 2016/1/22 1:21, rkrc...@redhat.com wrote:
2016-01-21 05:33+, Wu, Feng:
From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel-
ow...@vger.kernel.org] On Behalf Of Yang Zhang
On 2016/1/20 9:42, Feng Wu wrote:
+ /*
+* We may find a
Thanks for your time.
The C-Media CM6533 is a USB audio chip featuring it's jack detection
capability.The device originates an interrupt transfer via HID interface
each time when a jack event occurs.
The purpose of this patch is to handle hid raw events to keep the operating
system informed of
On 2016/1/19 1:03, Stefano Stabellini wrote:
> On Fri, 15 Jan 2016, Shannon Zhao wrote:
>> > From: Shannon Zhao
>> >
>> > When running on Xen hypervisor, runtime services are supported through
>> > hypercall. So call Xen specific function to initialize runtime services.
>> >
>> >
On Thu, Jan 21, 2016 at 1:27 PM, Jens Axboe wrote:
>
> Note that pulling this in will conflict with master, since the code was
> forked off pretty early, and we had a good chunk of nvme fixes later in
> the 4.4 cycle.
Not just conflict, but conflict in bad ways. I don't think I'll be
able to fix
On Thu, Jan 21, 2016 at 06:44:28PM -0800, Alexei Starovoitov wrote:
> On Thu, Jan 21, 2016 at 04:49:27PM -0600, Josh Poimboeuf wrote:
> > bpf_jit.S has several callable non-leaf functions which don't honor
> > CONFIG_FRAME_POINTER, which can result in bad stack traces.
> >
> > Create a stack
On 01/21/2016 05:11 PM, William Breathitt Gray wrote:
The WinSystems EBC-C384 has an onboard watchdog timer. The timeout range
supported by the watchdog timer is 1 second to 255 minutes. Timeouts
under 256 seconds have a 1 second resolution, while the rest have a 1
minute resolution.
This
On Thu, 2016-01-21 at 14:55 -0800, Kees Cook wrote:
> On Thu, Jan 21, 2016 at 2:50 PM, Andrew Morton
> wrote:
> > On Thu, 21 Jan 2016 18:19:43 +0100 Ard Biesheuvel
> > wrote:
> >
> > > Similar to how relative extables are implemented, it is possible to emit
> > > the kallsyms table in such a
Hi Rob,
On Wed, 2016-01-20 at 10:38 -0600, Rob Herring wrote:
> On Wed, Jan 20, 2016 at 01:14:38PM +0800, hs.l...@mediatek.com wrote:
> > From: HS Liao
> >
> > This adds documentation for the MediaTek Global Command Engine (GCE) unit
> > found in MT8173 SoCs.
> >
> > Signed-off-by: HS Liao
>
On 1/12/2016 10:42 PM, Ulf Hansson wrote:
> On 28 December 2015 at 16:39, Fu, Zhonghui
> wrote:
>> Now, PM core supports asynchronous suspend/resume mode for devices
>> during system suspend/resume, and the power state transition of one
>> device may be completed in separate kernel thread. PM
This patch enables mmc hosts to suspend/resume asynchronously.
This will improve system suspend/resume speed. After applying
this patch and enabling all mmc hosts' child devices to
suspend/resume asynchronously on ASUS T100TA, the system
suspend-to-idle time is reduced from 1645ms to 1107ms, and
Hi all,
Please do not add any material for v4.6 to your linux-next included
branches until after v4.5-rc1 is released.
Changes since 20160121:
The aio tree still had a build failure so I used the version from
next-20160111.
Non-merge commits (relative to Linus' tree): 1023
910 files changed
Hi,
I hit this while I was testing 4.5-rc1 with randconfig during merger period.
And now I noticed that it was fixed after Linus merged akpm branch.
commit eae21770b4fed5597623aad0d618190fa60426ff
Merge: e9f57eb 9f273c2
Author: Linus Torvalds
Date: Thu Jan 21 12:32:08 2016 -0800
Merge
On Thu, Jan 21, 2016 at 05:12:13PM -0800, Linus Torvalds wrote:
> On Thu, Jan 21, 2016 at 2:51 PM, Keith Busch wrote:
> >
> > My apologies for the trouble. I trust it really is broken, but I don't
> > quite see how. The patch supposedly splits the transfer to the max size
> > the request queue
On Fri, Jan 22, 2016 at 10:21:19AM +0800, Wangnan (F) wrote:
>
>
> On 2016/1/21 14:51, Wangnan (F) wrote:
> >
> >
> >On 2016/1/20 10:20, Alexei Starovoitov wrote:
> >>On Wed, Jan 20, 2016 at 09:37:42AM +0800, Wangnan (F) wrote:
> >>>
> >>>On 2016/1/20 1:42, Alexei Starovoitov wrote:
> On
for_each_child_of_node performs an of_node_get on each iteration, so
to break out of the loop an of_node_put is required.
Found using Coccinelle. The semantic patch used for this is as follows:
//
@@
expression e;
local idexpression n;
@@
for_each_child_of_node(n, ...) {
... when !=
On Thu, Jan 21, 2016 at 06:48:54PM -0800, Davidlohr Bueso wrote:
> On Thu, 21 Jan 2016, Paul E. McKenney wrote:
>
> >I did some testing, which exposed it to the 0day test robot, which
> >did note some performance differences. I was hoping that it would
> >clear up some instability from other
On 2016/1/22 10:46, Jaehoon Chung wrote:
Hi, Shawn.
On 01/21/2016 04:52 PM, Shawn Lin wrote:
num_slots comes from pdata if existing, otherwise from
dw_mci_parse_dt which make it at least one slot. If
num_slots is less than 1 for the existing pdata case,
current code return -ENODEV. But
[ Trimming KDE folks from Cc ]
On 21.01.2016 19:09, Daniel Vetter wrote:
> On Thu, Jan 21, 2016 at 05:36:46PM +0900, Michel Dänzer wrote:
>> On 21.01.2016 16:58, Daniel Vetter wrote:
>>>
>>> Can you please point me at the vblank on/off jump bug please?
>>
>> AFAIR I originally reported it in
Hi all,
On Fri, 22 Jan 2016 11:24:42 +1100 Stephen Rothwell
wrote:
>
> On Thu, 21 Jan 2016 07:38:59 +1100 Stephen Rothwell
> wrote:
> >
> > On Wed, 20 Jan 2016 15:09:47 +0100 Takashi Iwai wrote:
> > >
> > > On Sat, 16 Jan 2016 09:51:29 +0100,
> > > Takashi Iwai wrote:
> > > >
> > > >
On Thu, Jan 21, 2016 at 04:49:35PM -0600, Josh Poimboeuf wrote:
> stacktool reports the following false positive warnings:
>
> stacktool: kernel/bpf/core.o: __bpf_prog_run()+0x5c: sibling call from
> callable instruction with changed frame pointer
> stacktool: kernel/bpf/core.o:
On Thu, 21 Jan 2016, Paul E. McKenney wrote:
I did some testing, which exposed it to the 0day test robot, which
did note some performance differences. I was hoping that it would
clear up some instability from other patches, but no such luck. ;-)
Oh, that explains why we got a performance
On Fri, 22 Jan 2016, kernel test robot wrote:
FYI, we noticed the below changes on
https://github.com/0day-ci/linux
Ding-Tianhong/locking-mutexes-don-t-spin-on-owner-when-wait-list-is-not-NULL/20160121-173317
commit cb4bbc457bfed6194ffab1b10c7be73b3f16ca2d ("locking/mutexes: don't
Hi, Shawn.
On 01/21/2016 04:52 PM, Shawn Lin wrote:
> num_slots comes from pdata if existing, otherwise from
> dw_mci_parse_dt which make it at least one slot. If
> num_slots is less than 1 for the existing pdata case,
> current code return -ENODEV. But dw_mci_probe seems to
> treat this a
On Thu, Jan 21, 2016 at 04:49:27PM -0600, Josh Poimboeuf wrote:
> bpf_jit.S has several callable non-leaf functions which don't honor
> CONFIG_FRAME_POINTER, which can result in bad stack traces.
>
> Create a stack frame before the call instructions when
> CONFIG_FRAME_POINTER is enabled.
>
>
Hi all,
On Fri, 22 Jan 2016 11:24:42 +1100 Stephen Rothwell
wrote:
>
> On Thu, 21 Jan 2016 07:38:59 +1100 Stephen Rothwell
> wrote:
> >
> > On Wed, 20 Jan 2016 15:09:47 +0100 Takashi Iwai wrote:
> > >
> > > On Sat, 16 Jan 2016 09:51:29 +0100,
> > > Takashi Iwai wrote:
> > > >
> > > >
On Thu, Jan 21, 2016 at 01:23:09PM -0800, Tim Chen wrote:
> On Thu, 2016-01-21 at 17:29 +0800, Ding Tianhong wrote:
>
> >
> > diff --git a/kernel/locking/mutex.c b/kernel/locking/mutex.c
> > index 0551c21..596b341 100644
> > --- a/kernel/locking/mutex.c
> > +++ b/kernel/locking/mutex.c
> > @@
On 2016/1/21 14:51, Wangnan (F) wrote:
On 2016/1/20 10:20, Alexei Starovoitov wrote:
On Wed, Jan 20, 2016 at 09:37:42AM +0800, Wangnan (F) wrote:
On 2016/1/20 1:42, Alexei Starovoitov wrote:
On Tue, Jan 19, 2016 at 11:16:44AM +, Wang Nan wrote:
This patchset introduces two methods to
1 - 100 of 1696 matches
Mail list logo
