On Tue, Dec 15, 2015 at 05:17:13PM +, Mark Brown wrote:
> On Tue, Dec 15, 2015 at 03:32:19PM +, Mark Rutland wrote:
> > On Tue, Dec 15, 2015 at 03:08:13PM +, Mark Brown wrote:
> > > On Tue, Dec 15, 2015 at 02:01:36PM +, Mark Rutland wrote:
>
> > > > I really don't want to see a
With introduction of packetized pipes, splice wasn't updated to respect this
new behaviour.
In terms of splice it means, that it never set PIPE_BUF_FLAG_PACKET on
created pipe buffer regarless pipe operating mode, thus breaking the whole
logic.
To fix this, new SPLICE_F_PACKET flag was introduced.
With introduction of packetized pipe mode, represented by O_DIRECT flag,
splice stopped working correctly with a pipe in this mode.
To be able to fix them, this helper have to exposed.
Signed-off-by: Stanislav Kinsburskiy
---
fs/pipe.c |2 +-
include/linux/pipe_fs_i.h |2
Hi,
This patch series adds generic cpufreq-dt driver support for
Exynos542x/5800 (using the new CPU clock type which allows it).
It has been tested on Exynos5422 based ODROID-XU3 Lite board.
Depends on:
- next-20151211 branch of linux-next kernel tree
- "[PATCH] ARM: dts: Make CPU configuration
From: Thomas Abraham
For Exynos542x/5800 platforms, add CPU operating points
for migrating from Exynos specific cpufreq driver to using
generic cpufreq driver.
Changes by Bartlomiej:
- split Exynos5420 support from the original patch
- merged Exynos5422 fixes from Ben
Changes by Ben Gamari:
-
Add cluster regulator supply properties as a preparation to
adding generic cpufreq-dt driver support for Exynos542x and
Exynos5800 based boards.
Cc: Kukjin Kim
Cc: Doug Anderson
Cc: Javier Martinez Canillas
Cc: Andreas Faerber
Cc: Thomas Abraham
Reviewed-by: Krzysztof Kozlowski
This patch uses SPLICE_F_PACKET as a flag, representing packetized pipe.
In splice_to_pipe() this flag is converted into PIPE_BUF_FLAG_PACKET on pipe
buffer.
Signed-off-by: Stanislav Kinsburskiy
---
fs/splice.c |8
1 file changed, 8 insertions(+)
diff --git a/fs/splice.c
> -Original Message-
> From: ja...@microsoft.com [mailto:ja...@microsoft.com]
> Sent: Wednesday, December 9, 2015 2:55 PM
> To: gre...@linuxfoundation.org; KY Srinivasan ; linux-
> ker...@vger.kernel.org; de...@linuxdriverproject.org; o...@aepfle.de;
> a...@canonical.com;
On Tue, Dec 15, 2015 at 06:14:19PM +, Simmons, James A. wrote:
>
> >> struct libcfs_ioctl_hdr {
> >>__u32 ioc_len;
> >> @@ -87,6 +88,13 @@ do {\
> >>data.ioc_hdr.ioc_len = sizeof(data);\
> >> } while (0)
> >>
>
Activate/deactivate the LCD_RESET signal as specified by the
reset-active DT property when the controller is disabled/enabled.
If the property is missing, leave the signal unchanged.
Signed-off-by: Mans Rullgard
---
drivers/video/fbdev/mxsfb.c | 28 +---
1 file changed,
Hi there. I plan to create a patch that puts additional ELF notes into
core dumps of user processes produced by the kernel. These are desired in
customer field work because 1) we often get a core without access to the
original machine and much of this would remove significant delays and
Some boards connect the LCD_RESET pin to a reset input on the
display panel. On these boards, this pin must be set to the
proper level for the display to function.
This adds an optional "reset-active" property to the "display"
subnode such that devicetrees can specify the desired polarity
of the
On Tue, 15 Dec 2015, Russell King - ARM Linux wrote:
> On Tue, Dec 15, 2015 at 10:33:25AM +0100, Pali Rohár wrote:
> > So am I understand correctly that solution would be to hack
> > arch/arm/mm/mmu.c to not overwrite page at PHYS_OFFSET?
>
> That's completely unnecessary: there are enough
On Tue, Dec 15, 2015 at 1:33 PM, Ville Syrjälä
wrote:
> On Tue, Dec 15, 2015 at 01:23:06PM -0500, Rob Clark wrote:
>> On Tue, Dec 15, 2015 at 1:07 PM, Lyude wrote:
>> > This reverts commit 5677d67ae394 ("drm: Stop resetting connector state to
>> > unknown")
>> >
>> > Unfortunately, not resetting
Daniel Vetter writes:
> On Mon, Dec 14, 2015 at 04:26:26PM -0800, Eric Anholt wrote:
>> VC4 wraps the CMA objects in its own structures, so it needs to do its
>> own teardown (waiting for GPU to finish, updating bo_stats tracking).
>> The other CMA drivers are using drm_gem_cma_free_object as
On Tue, Dec 15, 2015 at 04:50:45PM +, Okash Khawaja wrote:
> This patch fixes address space warnings from sparse. Function
> lprocfs_write_helper() accepts user space buffer but was being
> passed kernel space buffer by these functions:
>
> contention_seconds_store()
>
On Tue, Dec 15, 2015 at 06:10:03PM +, Mark Rutland wrote:
> On Tue, Dec 15, 2015 at 05:45:16PM +, Mark Brown wrote:
> > > I'm not sure I follow w.r.t. "inherently less information", unless you
> > > mean trying to debug without access to that DTB?
> > If what the kernel knows about the
On 12/14/2015 06:24 PM, Yuyang Du wrote:
>>> On Fri, Dec 11, 2015 at 06:01:45PM -0800, Steve Muckle wrote:
In init_entity_runnable_average() the last_update_time is initialized to
zero. The task is given max load and utilization as a pessimistic
initial estimate.
But if in
Spansion and Winbond have occasionally used the same manufacturer ID,
and they don't support the same features. Particularly, writing SR=0
seems to break read access for Spansion's s25fl064k. Unfortunately, we
don't currently have a way to differentiate these Spansion and Winbond
parts, so rather
On Tue, Dec 15, 2015 at 9:45 AM, Linus Torvalds
wrote:
> On Tue, Dec 15, 2015 at 1:40 AM, Pavel Machek wrote:
>>
>> I tried applying:
>>
>> [PATCH 1/2] x86_32/mm: Set NX in __supported_pte_mask before enabling
>> paging
>>
>> but I still get
>>
>> [2.691897] x86/mm: Found insecure W+X
On Tue, Dec 15, 2015 at 10:21:38AM -0800, Kamal Mostafa wrote:
> >From f424410bf4a6a0dd6ff88bec808798016f4161a0 Mon Sep 17 00:00:00 2001
> From: Kamal Mostafa
> Date: Wed, 11 Nov 2015 19:16:59 +
> Subject: tools/hv: Use include/uapi with __EXPORTED_HEADERS__
Why is all of this mess here?
On Tue, Dec 15, 2015 at 10:35:49AM -0800, Dan Williams wrote:
> Correction we have MOVNTDQA, but that requires saving the fpu state
> and marking the memory as WC, i.e. probably not worth it.
Not really. Last time I tried an SSE3 memcpy in the kernel like glibc
does, it wasn't worth it. The
On Tue, Dec 15, 2015 at 02:24:05PM +0100, Linus Walleij wrote:
> On Sun, Dec 13, 2015 at 5:44 PM, Dmitry Torokhov
> wrote:
> > On Sun, Dec 13, 2015 at 8:37 AM, Linus Walleij
> > wrote:
> >> On Wed, Dec 9, 2015 at 6:21 PM, Dmitry Torokhov
> >> wrote:
> >>
> > Hmm, I'd like to get this
>On Tue, Dec 15, 2015 at 06:14:19PM +, Simmons, James A. wrote:
>>
>> >> struct libcfs_ioctl_hdr {
>> >> __u32 ioc_len;
>> >> @@ -87,6 +88,13 @@ do { \
>> >> data.ioc_hdr.ioc_len = sizeof(data);\
>> >> } while (0)
>> >>
On Tue, Dec 15, 2015 at 9:53 AM, Luck, Tony wrote:
>>> ... and the non-temporal version is the optimal one even though we're
>>> defaulting to copy_user_enhanced_fast_string for memcpy on modern Intel
>>> CPUs...?
>
> My current generation cpu has a bit of an issue with recovering from a
>
> kgdb/kdb and the perf event system both present garbage status in dr6
> then subsequently write this status into the thread.debugreg6 variable,
> then in some cases call hw_breakpoint_restore() which writes this
> status back into the dr6 hardware register.
>
I wanted to note here that this is
On Tue, Dec 15, 2015 at 06:47:20PM +0100, Vincent Guittot wrote:
> On 15 December 2015 at 18:15, Mark Rutland wrote:
> > On Tue, Dec 15, 2015 at 05:59:34PM +0100, Vincent Guittot wrote:
> >> On 15 December 2015 at 17:41, Mark Rutland wrote:
> >> > On Tue, Dec 15, 2015 at 04:23:18PM +,
On Tue, Dec 15, 2015 at 01:23:06PM -0500, Rob Clark wrote:
> On Tue, Dec 15, 2015 at 1:07 PM, Lyude wrote:
> > This reverts commit 5677d67ae394 ("drm: Stop resetting connector state to
> > unknown")
> >
> > Unfortunately, not resetting the connector status to unknown actually
> > breaks reprobing
On Tue, 2015-12-15 at 19:26 +0100, SF Markus Elfring wrote:
> > rc = mdc_queue_wait(req);
> > goto out;
> > out:
> > ptlrpc_req_finished(req);
> > return rc;
> > }
> > -
> >
> > I think if the last goto out; is to be removed,
> > then it should be replaced by a
> rc = mdc_queue_wait(req);
> goto out;
> out:
> ptlrpc_req_finished(req);
> return rc;
> }
> -
>
> I think if the last goto out; is to be removed,
> then it should be replaced by a blank line.
>
> It separates the last operation block from the return.
On Tue, Dec 15, 2015 at 10:27 AM, Dan Williams wrote:
> On Tue, Dec 15, 2015 at 9:53 AM, Luck, Tony wrote:
... and the non-temporal version is the optimal one even though we're
defaulting to copy_user_enhanced_fast_string for memcpy on modern Intel
CPUs...?
>>
>> My current
On Sat, 2015-12-12 at 13:48 +0800, Herbert Xu wrote:
> On Fri, Dec 11, 2015 at 08:54:40AM -0800, Tim Chen wrote:
> > Direct call I assume have less overhead. Let me think about
>
> static inline int crypto_ablkcipher_encrypt(struct ablkcipher_request *req)
> {
> struct ablkcipher_tfm *crt
On Tue, Dec 15, 2015 at 1:07 PM, Lyude wrote:
> This reverts commit 5677d67ae394 ("drm: Stop resetting connector state to
> unknown")
>
> Unfortunately, not resetting the connector status to unknown actually
> breaks reprobing on suspend/resume in i915, which is important to have
> working since
On Tue, Dec 08, 2015 at 07:43:47AM +0100, Anton Bondarenko wrote:
> Also removing change introduced in f6ee9b582d2db652497b73c1f117591dfb6d3a90
> since this change only fix usecases with transfer size from 33 to 128 bytes
> and doesn't fix 129 bytes and bigger.
This is a bug fix for stable but
From: Paul Bolle
Date: Tue, 15 Dec 2015 18:11:27 +0100
> Sascha Levin reported that the syzkaller fuzzer triggered a WARNING in
> ser_gigaset (see https://lkml.kernel.org/g/56587467.8050...@oracle.com ). It
> turned out that ser_gigaset has always deallocated its platform device
> structure
>From f424410bf4a6a0dd6ff88bec808798016f4161a0 Mon Sep 17 00:00:00 2001
From: Kamal Mostafa
Date: Wed, 11 Nov 2015 19:16:59 +
Subject: tools/hv: Use include/uapi with __EXPORTED_HEADERS__
Use the local uapi headers to keep in sync with "recently" added #define's
(e.g. VSS_OP_REGISTER1).
From: Michal Hocko
This is based on the idea from Mel Gorman discussed during LSFMM 2015 and
independently brought up by Oleg Nesterov.
The OOM killer currently allows to kill only a single task in a good
hope that the task will terminate in a reasonable time and frees up its
memory. Such a
On Tue, Dec 15, 2015 at 09:45:40AM -0800, Linus Torvalds wrote:
> On Tue, Dec 15, 2015 at 1:40 AM, Pavel Machek wrote:
> >
> > I tried applying:
> >
> > [PATCH 1/2] x86_32/mm: Set NX in __supported_pte_mask before enabling
> > paging
> >
> > but I still get
> >
> > [2.691897] x86/mm: Found
On Tue, Dec 15, 2015 at 05:53:31PM +, Luck, Tony wrote:
> My current generation cpu has a bit of an issue with recovering from a
> machine check in a "rep mov" ... so I'm working with a version of memcpy
> that unrolls into individual mov instructions for now.
Ah.
> I can drop the "nti" from
On Tue, 2015-12-15 at 19:02 +0100, SF Markus Elfring wrote:
> > This is the original code:
> Really …?
> > result = baz();
> > if (result)
> > goto label;
> >
> > label:
> > go on...
>
> I do not see such a source code structure
> at the six places I propose to clean-up.
On Tue, Dec 15, 2015 at 06:14:19PM +, Simmons, James A. wrote:
>
> >> struct libcfs_ioctl_hdr {
> >>__u32 ioc_len;
> >> @@ -87,6 +88,13 @@ do {\
> >>data.ioc_hdr.ioc_len = sizeof(data);\
> >> } while (0)
> >>
>
From: Michal Hocko
__alloc_pages_slowpath retries costly allocations until at least
order worth of pages were reclaimed or the watermark check for at least
one zone would succeed after all reclaiming all pages if the reclaim
hasn't made any progress.
The first condition was added by
On 12/11, Peter Zijlstra wrote:
>
> On Fri, Dec 11, 2015 at 03:30:33AM -0800, Paul Turner wrote:
>
> > > Blergh, all I've managed to far is to confuse myself further. Even
> > > something like the original (+- the EINTR) should work when we consider
> > > the looping, even when mixed with an
From: Michal Hocko
__alloc_pages_slowpath has traditionally relied on the direct reclaim
and did_some_progress as an indicator that it makes sense to retry
allocation rather than declaring OOM. shrink_zones had to rely on
zone_reclaimable if shrink_zone didn't make any progress to prevent
from a
From: Michal Hocko
wait_iff_congested has been used to throttle allocator before it retried
another round of direct reclaim to allow the writeback to make some
progress and prevent reclaim from looping over dirty/writeback pages
without making any progress. We used to do congestion_wait before
Hi Alan,
On Mon, Dec 14, 2015 at 5:56 PM, Alan Tull wrote:
>> I had an offline discussion with Josh Cartwright about his concerns.
>> He brought up a good
>> point on w.r.t to the way FPGA Area (Bus) deals with things.
>>
>> Currently we only support complete status = "okay" vs "disabled" kind
Hi,
This is v4 of the series. The previous version was posted [1]. I have
dropped the RFC because this has been sitting and waiting for the
fundamental objections for quite some time and there were none. I still
do not think we should rush this and merge it no sooner than 4.6. Having
this in the
On Mon, 2015-12-14 at 19:11 -0800, Greg KH wrote:
> On Mon, Dec 14, 2015 at 04:01:53PM -0800, K. Y. Srinivasan wrote:
> > From: Kamal Mostafa
> >
> > Use the local uapi headers to keep in sync with "recently" added #define's
> > (e.g. VSS_OP_REGISTER1).
> >
> > Fixes:
>> struct libcfs_ioctl_hdr {
>> __u32 ioc_len;
>> @@ -87,6 +88,13 @@ do { \
>> data.ioc_hdr.ioc_len = sizeof(data);\
>> } while (0)
>>
>> +#define LIBCFS_IOC_INIT_V2(data, hdr) \
>> +do {
>> diff --git a/drivers/staging/lustre/lnet/selftest/conctl.c
>> b/drivers/staging/lustre/lnet/selftest/conctl.c
>> index 556c837..2ca7d0e 100644
>> --- a/drivers/staging/lustre/lnet/selftest/conctl.c
>> +++ b/drivers/staging/lustre/lnet/selftest/conctl.c
>> @@ -679,45 +679,46 @@ static int
>>
Sergei Ianovich writes:
> On Tue, 2015-12-15 at 18:02 +0100, Arnd Bergmann wrote:
>> On Tuesday 15 December 2015 19:42:07 Sergei Ianovich wrote:
>> > There are several board-specific devices on LP8x4x: custom FPGA,
>> > custom
>> > UART, custom IRQ on FPGA, custom parallel bus for industrial IO.
This patch fixes address space warnings from sparse. Function
lprocfs_write_helper() accepts user space buffer but was being
passed kernel space buffer by these functions:
contention_seconds_store()
lockless_truncate_store()
Since these functions are used to implement show and store functions
This reverts commit 5677d67ae394 ("drm: Stop resetting connector state to
unknown")
Unfortunately, not resetting the connector status to unknown actually
breaks reprobing on suspend/resume in i915, which is important to have
working since it means a user docking their laptop in suspend won't have
On Tue, 2015-12-15 at 20:48 +0300, Dan Carpenter wrote:
> On Tue, Dec 15, 2015 at 07:02:31AM -0800, Joe Perches wrote:
> > This is the original code:
> >
> > result = foo();
> > if (result)
> > goto label;
> >
> > result = bar();
> > if (result)
> > goto
On Tue, Dec 15, 2015 at 09:36:26AM -0800, Peter Hurley wrote:
> Hi Herton,
>
> On 12/14/2015 07:29 PM, Herton R. Krzesinski wrote:
> > pty_unix98_shutdown allows a potential use after free of inode from
> > slave tty->driver_data: if final pty close is called with slave
> > tty_struct, and inode
On Tue, Dec 15, 2015 at 05:45:16PM +, Mark Brown wrote:
> On Tue, Dec 15, 2015 at 05:28:37PM +, Mark Rutland wrote:
> > On Tue, Dec 15, 2015 at 05:17:13PM +, Mark Brown wrote:
>
> > > Obviously people are going to get upset if we introduce performance
> > > regressions - but that's
> This is the original code:
Really …?
> result = baz();
> if (result)
> goto label;
>
> label:
> go on...
I do not see such a source code structure
at the six places I propose to clean-up.
> I don't find the test->goto label; label: use offensive,
> but if he
Currently, all newly added memory blocks remain in 'offline' state unless
someone onlines them, some linux distributions carry special udev rules
like:
SUBSYSTEM=="memory", ACTION=="add", ATTR{state}=="offline", ATTR{state}="online"
to make this happen automatically. This is not a great solution
On Tue, Dec 15, 2015 at 9:56 AM, Toshi Kani wrote:
> On Tue, 2015-12-15 at 09:53 -0800, Dan Williams wrote:
[..]
>> > > > diff --git a/drivers/acpi/Kconfig b/drivers/acpi/Kconfig
>> > > > index 5eef4cb..5368baa 100644
>> > > > --- a/drivers/acpi/Kconfig
>> > > > +++ b/drivers/acpi/Kconfig
>> > >
From: Ben Hutchings
Date: Tue, 15 Dec 2015 15:12:43 +
> The backported version of commit 7f109f7cc371 ("vrf: fix double free
> and memory corruption on register_netdevice failure") incorrectly
> removed a kfree() from the failure path as well as the free_netdev().
> Add that back.
>
>
On Tue, Dec 15, 2015 at 2:01 AM, Maarten Lankhorst
wrote:
> Op 15-12-15 om 02:29 schreef Dmitry Torokhov:
>> Userspace can close the sync device while there are still active fence
>> points, in which case kernel produces the following warning:
>>
>> [ 43.853176] [ cut here
>Actually we're going to have to redo so much code that it's not worth it
>for me to review the rest of these patches.
Sorry I didn't get back to you sooner but I was on vacation. Thanks for
reviewing this work. Especially since this is the first major bug fixing merge
for the lustre client
On Tue, Dec 15, 2015 at 03:32:19PM +, Mark Rutland wrote:
> On Tue, Dec 15, 2015 at 03:08:13PM +, Mark Brown wrote:
> > On Tue, Dec 15, 2015 at 02:01:36PM +, Mark Rutland wrote:
> > > I really don't want to see a table of magic numbers in the kernel.
> > Right, there's pitfalls there
On Tue, Dec 15, 2015 at 1:26 AM, Daniel Vetter wrote:
> On Mon, Dec 14, 2015 at 05:29:55PM -0800, Dmitry Torokhov wrote:
>> Userspace can close the sync device while there are still active fence
>> points, in which case kernel produces the following warning:
>>
>> [ 43.853176] [ cut
From: Tilman Schmidt
Commit f34d7a5b7010 ("tty: The big operations rework") changed
tty->driver to tty->ops but left NULL checks for tty->driver untouched.
Fix.
Signed-off-by: Tilman Schmidt
[pebolle: removed Fixes tag]
Signed-off-by: Paul Bolle
---
drivers/isdn/gigaset/ser-gigaset.c | 6
On Tue, Dec 15, 2015 at 05:59:34PM +0100, Vincent Guittot wrote:
> On 15 December 2015 at 17:41, Mark Rutland wrote:
> > On Tue, Dec 15, 2015 at 04:23:18PM +, Catalin Marinas wrote:
> >> On Tue, Dec 15, 2015 at 03:57:37PM +, Mark Rutland wrote:
> >> > On Tue, Dec 15, 2015 at 03:46:51PM
From: Tilman Schmidt
When shutting down the device, the struct ser_cardstate must not be
kfree()d immediately after the call to platform_device_unregister()
since the embedded struct platform_device is still in use.
Move the kfree() call to the release method instead.
Signed-off-by: Tilman
Sascha Levin reported that the syzkaller fuzzer triggered a WARNING in
ser_gigaset (see https://lkml.kernel.org/g/56587467.8050...@oracle.com ). It
turned out that ser_gigaset has always deallocated its platform device
structure incorrectly. Tilman submitted the patch that fixes that (3/4) and a
Dexuan Cui writes:
>> -Original Message-
>> From: devel [mailto:driverdev-devel-boun...@linuxdriverproject.org] On Behalf
>> Of K. Y. Srinivasan
>> Sent: Tuesday, December 15, 2015 11:02
>> To: gre...@linuxfoundation.org; linux-kernel@vger.kernel.org;
>> de...@linuxdriverproject.org;
On Mon, 2015-12-14 at 22:39 -0800, Greg KH wrote:
> This is the LAST 4.2.y kernel to be released [...]
Canonical's kernel team will pick up stable maintenance where Greg KH
left off with v4.2.8 (thanks, Greg!)...
Canonical's Ubuntu kernel team is pleased to announce that we will be
providing
From: Tilman Schmidt
device->platform_data and platform_device->resource are never used
and remain NULL through their entire life. Drops the kfree() calls
for them from the device release method.
Signed-off-by: Tilman Schmidt
Signed-off-by: Paul Bolle
---
drivers/isdn/gigaset/ser-gigaset.c |
From: Alan Cox
These checks do nothing useful to protect the code from races. On the
other hand if the old code has been masking a real bug we would like to
know about it.
The check for tiocmset is kept because it is valid for a tty driver to
have a NULL tiocmset method. That in itself is
Hi Sudeep,
On mar., déc. 15 2015, Sudeep Holla wrote:
> On 21/10/15 11:10, Sudeep Holla wrote:
>> Though the driver will continue to check for and support the legacy
>> "isil,irq2-can-wakeup-machine" boolean property to wakeup source,
>> "wakeup-source" is the new standard binding.
>>
>> This
Sorry, this was from me; I didn't mean to forge Nikolay's address.
Ben.
On Tue, 2015-12-15 at 15:32 +, Nikolay Aleksandrov wrote:
> commit 7f109f7cc37108cba7243bc832988525b0d85909 upstream.
>
> When vrf's ->newlink is called, if register_netdevice() fails then it
> does free_netdev(), but
On Tuesday 15 December 2015 19:42:07 Sergei Ianovich wrote:
> On Tue, 2015-12-15 at 17:32 +0100, Arnd Bergmann wrote:
> > On Tuesday 15 December 2015 19:27:50 Sergei Ianovich wrote:
> > > .../devicetree/bindings/vendor-prefixes.txt| 1 +
> > > arch/arm/boot/dts/Makefile
On 15 December 2015 at 17:41, Mark Rutland wrote:
> On Tue, Dec 15, 2015 at 04:23:18PM +, Catalin Marinas wrote:
>> On Tue, Dec 15, 2015 at 03:57:37PM +, Mark Rutland wrote:
>> > On Tue, Dec 15, 2015 at 03:46:51PM +, Juri Lelli wrote:
>> > > On 15/12/15 15:32, Mark Rutland wrote:
>> >
On Tuesday 15 December 2015 09:20:51 Enric Balletbo i Serra wrote:
> In order to meet high performance an low power requirement for Rockchip
> enable the power domain support. The patch also fixes a drm/kms issue,
> driver deferring untils power-domains are available)
>
> Signed-off-by: Enric
Sorry again for the huge delay.
And all I can say is that I am all confused.
On 12/01, Peter Zijlstra wrote:
>
> On Fri, Nov 20, 2015 at 03:35:38PM +, Vladimir Murzin wrote:
> > commit 743162013d40ca612b4cb53d3a200dff2d9ab26e
> > Author: NeilBrown
> > Date: Mon Jul 7 15:16:04 2014 +1000
On Tue 15-12-15 14:03:18, Kirill A. Shutemov wrote:
> On Tue, Dec 15, 2015 at 09:52:33AM +0100, Michal Hocko wrote:
> > On Mon 14-12-15 14:04:56, Kirill A. Shutemov wrote:
> > > On Wed, Dec 09, 2015 at 02:02:05PM +0100, Michal Hocko wrote:
> > > > Hi Kirill,
> > >
> > > [ sorry for late reply,
From: Or Gerlitz
Date: Tue, 15 Dec 2015 11:09:40 +0200
> On 12/14/2015 12:05 PM, Andrzej Hajda wrote:
>> The function can return negative values, so its result should
>> be assigned to signed variable.
>>
>> The problem has been detected using proposed semantic patch
>>
ACPI 6.0 defines NFIT table and new persistent memory types for
EFI memory table (EFI_PERSISTENT_MEMORY) and e820 table (E820_PMEM).
setup_e820() enabled by EFI_STUB converts EFI_PERSISTENT_MEMORY to
E820_PMEM for the e820_map table on x86 EFI platforms. When EFI_STUB
is disabled, x86 kernels
On 14/12/15 22:42, Joshua Henderson wrote:
> From: Cristian Birsan
>
> This adds support for the interrupt controller present on PIC32 class
> devices.
>
> The following features are supported:
> - DT properties for EVIC and for devices that use interrupt lines
> - Persistent and
This patch fixes the following crash seen when MIC reset is invoked in
RESET_FAILED state due to device_del being called a second time on an
already deleted device:
[] device_del+0x45/0x1d0
[] device_unregister+0x1e/0x60
[] scif_unregister_device+0x12/0x20 [scif_bus]
[] cosm_stop+0xaa/0xe0
This is v2 of cleanup and freefall detection for mma8452 devices.
[PATCH 1/3] iio: mma8452: remove unused register description
[PATCH 2/3] iio: mma8452: use enum for channel index
[PATCH 3/3] iio: mma8452: add freefall detection for Freescale's
If freefall mode (x falling event) is enabled,
Signed-off-by: Martin Kepplinger
Signed-off-by: Christoph Muellner
---
drivers/iio/accel/mma8452.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/iio/accel/mma8452.c b/drivers/iio/accel/mma8452.c
index 116a6e4..162bbef 100644
--- a/drivers/iio/accel/mma8452.c
+++
This gets rid of some magic numbers by adding an enum.
Signed-off-by: Martin Kepplinger
Signed-off-by: Christoph Muellner
---
drivers/iio/accel/mma8452.c | 39 +++
1 file changed, 23 insertions(+), 16 deletions(-)
diff --git a/drivers/iio/accel/mma8452.c
This adds freefall event detection to the supported devices. It adds
the in_accel_x_mag_falling_en iio event attribute, which activates
freefall mode.
In freefall mode, the current acceleration magnitude (AND combination
of all axis values) is compared to the specified threshold.
If it falls
On Tue, Dec 15, 2015 at 2:35 AM, Joerg Roedel wrote:
> On Mon, Dec 14, 2015 at 03:17:39PM -0800, Dan Williams wrote:
>> commit db0fa0cb0157 "scatterlist: use sg_phys()" did replacements of the
>> form:
>>
>> phys_addr_t phys = page_to_phys(sg_page(s));
>> phys_addr_t phys = sg_phys(s) &
On 21/10/15 11:10, Sudeep Holla wrote:
Though the keyboard driver for GPIO buttons(gpio-keys) will continue to
check for/support the legacy "gpio-key,wakeup" boolean property to
enable gpio buttons as wakeup source, "wakeup-source" is the new
standard binding.
This patch replaces the legacy
On Tue, Dec 15, 2015 at 4:13 AM, Stefano Stabellini
wrote:
> On Mon, 14 Dec 2015, Andy Lutomirski wrote:
>> On Mon, Dec 14, 2015 at 6:12 AM, Michael S. Tsirkin wrote:
>> > On Mon, Dec 14, 2015 at 02:00:05PM +, David Vrabel wrote:
>> >> On 07/12/15 16:19, Stefano Stabellini wrote:
>> >> > Hi
On Tue, Dec 15, 2015 at 7:53 AM, Andrew Vagin wrote:
> On Mon, Dec 14, 2015 at 02:38:06PM -0800, Andy Lutomirski wrote:
>> On Dec 13, 2015 11:52 PM, "Andrew Vagin" wrote:
>> >
>> > On Thu, Dec 03, 2015 at 03:20:30PM -0800, Andy Lutomirski wrote:
>> > > On Tue, Nov 24, 2015 at 7:18 AM, Andrew
On Sat, 12 Dec 2015, Nicholas Krause wrote:
This adds proper locking protection in bnx2fc_ctrl_enabled around
the calls to the functions, _bnx2fc_enable and _bnx2fc_disable in
order to avoid concurrent access on these functions accessing global
referenced data structures in their internal
On 2015-12-15 07:04, Martin Kepplinger wrote:
> Am 2015-12-12 um 16:34 schrieb Jonathan Cameron:
>> On 08/12/15 16:21, Martin Kepplinger wrote:
>>> This adds freefall event detection to the supported devices. It adds
>>> the in_accel_x_mag_falling_en iio event attribute, which activates
>>>
Building with the attached random configuration file,
arch/x86/built-in.o: In function `map_vdso':
vma.c:(.text+0x13fc): undefined reference to `pvclock_pvti_cpu0_va'
--
Jim
#
# Automatically generated file; DO NOT EDIT.
# Linux/x86 4.4.0-rc5 Kernel Configuration
#
CONFIG_64BIT=y
On Tue, Dec 15, 2015 at 8:32 AM, Jim Davis wrote:
> Building with the attached random configuration file,
>
> arch/x86/built-in.o: In function `map_vdso':
> vma.c:(.text+0x13fc): undefined reference to `pvclock_pvti_cpu0_va'
Whoops, thanks! I confused CONFIG_PARAVIRT_CLOCK and CONFIG_KVM_GUEST.
On Tue, Dec 15, 2015 at 04:23:18PM +, Catalin Marinas wrote:
> On Tue, Dec 15, 2015 at 03:57:37PM +, Mark Rutland wrote:
> > On Tue, Dec 15, 2015 at 03:46:51PM +, Juri Lelli wrote:
> > > On 15/12/15 15:32, Mark Rutland wrote:
> > > > On Tue, Dec 15, 2015 at 03:08:13PM +, Mark Brown
On Tue, 2015-12-15 at 17:32 +0100, Arnd Bergmann wrote:
> On Tuesday 15 December 2015 19:27:50 Sergei Ianovich wrote:
> > .../devicetree/bindings/vendor-prefixes.txt| 1 +
> > arch/arm/boot/dts/Makefile | 3 +
> > arch/arm/boot/dts/pxa27x-lp8x4x-i105.dts
On 12/09/2015 06:35 AM, Linus Walleij wrote:
On Tue, Dec 8, 2015 at 8:16 PM, Mark Brown wrote:
On Mon, Dec 07, 2015 at 01:58:47PM -0600, Andrew F. Davis wrote:
As all of this driver should be taken though the MFD tree how
can this gpiolib change be handled? If we have gpio.parent it
will not
On Tuesday 15 December 2015 19:27:50 Sergei Ianovich wrote:
> .../devicetree/bindings/vendor-prefixes.txt| 1 +
> arch/arm/boot/dts/Makefile | 3 +
> arch/arm/boot/dts/pxa27x-lp8x4x-i105.dts | 50
> arch/arm/boot/dts/pxa27x-lp8x4x.dts
On 21/10/15 11:10, Sudeep Holla wrote:
Though the keyboard and other driver will continue to support the legacy
"gpio-key,wakeup", "linux,input-wakeup" boolean property to enable the
wakeup source, "wakeup-source" is the new standard binding.
This patch replaces all the legacy wakeup
401 - 500 of 1878 matches
Mail list logo
