On Tue, Feb 02, 2016 at 07:42:16PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Tue, Feb 02, 2016 at 07:22:47PM -0300, Arnaldo Carvalho de Melo escreveu:
> > Ok, so I rebased it on top of my perf/core branch, adjusting some stuff
> > wrt recent patchkits from Namhyung (hist_entry__callchain_fprintf(
It seems that on H3, just like on A10, when GPIOs are configured as
external interrupt data registers does not contain their value. When
value is read, GPIO function must be temporary switched to input for
reads.
Signed-off-by: Krzysztof Adamski
---
Changes compared to v1:
- None, but the patc
Reviewed-by: Matt Ranostay
On Tue, Feb 2, 2016 at 6:36 AM, Arnd Bergmann wrote:
> The newly added atlas-ph-sensor driver uses irq_work_queue, which
> may not always be enabled:
>
> ERROR: "irq_work_queue" [drivers/iio/chemical/atlas-ph-sensor.ko] undefined!
>
> This adds a 'select' statement to
Hi Jisheng,
On mer., févr. 03 2016, Jisheng Zhang wrote:
> On Tue, 2 Feb 2016 19:07:41 +0100 Gregory CLEMENT wrote:
>
>> The Armada 3700 is an mvebu ARM64 SoC using one or two Cortex-A53 cores
>> depending of the variant.
>>
>> Signed-off-by: Gregory CLEMENT
>> Reviewed-by: Thomas Petazzoni
On Tue, Feb 02, 2016 at 04:33:16PM -0800, Jared Hulbert wrote:
> On Tue, Feb 2, 2016 at 3:41 PM, Dan Williams wrote:
> > On Tue, Feb 2, 2016 at 3:36 PM, Jared Hulbert wrote:
> >> On Tue, Feb 2, 2016 at 3:19 PM, Al Viro wrote:
> >>>
> >>> On Tue, Feb 02, 2016 at 04:11:42PM -0700, Ross Zwisler wro
memcg_destroy_kmem_caches shutdowns in the first place kmem_caches under
slab_mutex which involves freeing NUMA node structures for kmem_cache
and only then under release_caches removes corresponding sysfs files for
these caches. Which may lead to dereferencing NULL ptr on read.
Lets remove sysfs f
Signed-off-by: Nikolay Borisov
---
include/net/netns/ipv4.h | 2 ++
include/net/tcp.h | 1 -
net/ipv4/sysctl_net_ipv4.c | 18 +-
net/ipv4/tcp.c | 3 ++-
net/ipv4/tcp_ipv4.c| 2 ++
net/ipv4/tcp_timer.c | 4 ++--
6 files changed, 17 insertio
Signed-off-by: Nikolay Borisov
---
include/net/netns/ipv4.h| 1 +
include/net/tcp.h | 1 -
net/ipv4/inet_connection_sock.c | 7 ++-
net/ipv4/sysctl_net_ipv4.c | 14 +++---
net/ipv4/tcp_ipv4.c | 1 +
net/ipv4/tcp_timer.c| 3 +--
6
Signed-off-by: Nikolay Borisov
---
include/net/netns/ipv4.h | 1 +
include/net/tcp.h | 1 -
net/ipv4/sysctl_net_ipv4.c | 16
net/ipv4/tcp_ipv4.c| 1 +
net/ipv4/tcp_timer.c | 8
5 files changed, 14 insertions(+), 13 deletions(-)
diff --git a/
This patch series continues making more of the tcp-related
sysctl knobs be per net-namespace. Most of these apply per
socket and have global defaults so should be safe and I
don't expect any breakages.
Having those per net-namespace is useful when multiple
containers are hosted and it is requir
Signed-off-by: Nikolay Borisov
---
include/net/netns/ipv4.h | 2 ++
include/net/tcp.h | 1 -
net/ipv4/syncookies.c | 4 +---
net/ipv4/sysctl_net_ipv4.c | 18 +-
net/ipv4/tcp_input.c | 10 ++
net/ipv4/tcp_ipv4.c| 3 ++-
net/ipv4/tcp_minisoc
Signed-off-by: Nikolay Borisov
---
include/net/netns/ipv4.h | 1 +
include/net/tcp.h | 4 ++--
net/ipv4/sysctl_net_ipv4.c | 14 +++---
net/ipv4/tcp_ipv4.c| 1 +
net/ipv4/tcp_output.c | 3 ---
5 files changed, 11 insertions(+), 12 deletions(-)
diff --git a/incl
Signed-off-by: Nikolay Borisov
---
include/net/netns/ipv4.h | 1 +
include/net/tcp.h | 1 -
net/ipv4/sysctl_net_ipv4.c | 14 +++---
net/ipv4/tcp_ipv4.c| 1 +
net/ipv4/tcp_output.c | 3 ++-
net/ipv4/tcp_timer.c | 5 ++---
6 files changed, 13 insertions(+)
On 02/03/2016 12:20 AM, Stefan Agner wrote:
Add device tree support for the I2C and SPI variant of AD7879(-1).
This allows to specify the touchscreen controller as a I2C client
node or SPI slave device. Most of the options available in platform
data are also available as device tree properties, t
* a...@linux-foundation.org wrote:
> diff -puN
> arch/x86/include/asm/pgtable_64.h~x86-add-support-for-pud-sized-transparent-hugepages-checkpatch-fixes
> arch/x86/include/asm/pgtable_64.h
> ---
> a/arch/x86/include/asm/pgtable_64.h~x86-add-support-for-pud-sized-transparent-hugepages-checkpatc
On 02/03/2016 12:20 AM, Stefan Agner wrote:
The X/Y position measurements read from the controller are interpreted
wrong. The first measurement X+ contains the Y position, and the second
measurement Y+ the X position (see also Table 11 Register Table in the
data sheet).
The problem is already kn
Doug,
Thanks for your detail debug information, pls add my Reviewed-by for
this patch.
Thanks,
- Kever
On 02/03/2016 06:47 AM, Doug Anderson wrote:
Kever,
On Mon, Feb 1, 2016 at 11:46 PM, Kever Yang wrote:
Doug,
On 01/29/2016 10:20 AM, Douglas Anderson wrote:
When setting up ISO and INT
On Tue, 02 Feb 2016 22:23:55 +0100,
Dmitry Vyukov wrote:
>
> On Mon, Jan 25, 2016 at 11:47 AM, Takashi Iwai wrote:
> > On Sun, 24 Jan 2016 10:44:34 +0100,
> > Dmitry Vyukov wrote:
> >>
> >> Hello,
> >>
> >> While running syzkaller fuzzer I've got the following lockdep report:
> >>
> >> ==
Signed-off-by: Nikolay Borisov
---
include/net/netns/ipv4.h | 1 +
include/net/tcp.h | 1 -
net/ipv4/sysctl_net_ipv4.c | 14 +++---
net/ipv4/tcp_ipv4.c| 1 +
net/ipv4/tcp_timer.c | 3 +--
5 files changed, 10 insertions(+), 10 deletions(-)
diff --git a/include
Signed-off-by: Nikolay Borisov
---
include/net/netns/ipv4.h | 2 +-
include/net/tcp.h | 4 +++-
net/ipv4/sysctl_net_ipv4.c | 14 +++---
net/ipv4/tcp.c | 2 +-
net/ipv4/tcp_input.c | 12 ++--
net/ipv4/tcp_ipv4.c| 2 +-
net/ipv4/tcp_metrics.c
Signed-off-by: Nikolay Borisov
---
include/net/netns/ipv4.h | 1 +
include/net/tcp.h | 3 +--
net/ipv4/sysctl_net_ipv4.c | 14 +++---
net/ipv4/tcp.c | 7 +++
net/ipv4/tcp_ipv4.c| 1 +
5 files changed, 13 insertions(+), 13 deletions(-)
diff --git a/i
* a...@linux-foundation.org wrote:
>
> The patch titled
> Subject: kernel/locking/lockdep.c: make lockdep initialize itself on
> demand
> has been added to the -mm tree. Its filename is
> kernel-locking-lockdepc-make-lockdep-initialize-itself-on-demand.patch
>
> This patch should s
We broke interval data displays with commit:
3f416f22d1e2 perf stat: Do not clean event's private stats
This commit removed stats cleaning, which is important
for '-r' option to carry counters data over the whole
run. But it's necessary to clean it for interval mode,
otherwise the displayed valu
On (02/03/16 08:28), Ingo Molnar wrote:
[..]
> So why not move printk away from semaphores? Semaphores are classical
> constructs
> that have legacies and are somewhat non-obvious to use, compared to modern,
> simpler locking primitives. I'd not touch their implementation, unless we are
> absol
* Richard Henderson wrote:
> GCC 6 adds support for __seg_fs and __seg_gs as named address spaces,
> producing the obvious segment overrides for objects so marked.
>
> Exposing the memory reference allows slightly better code generation
> in some cases (and in others, merely affects the schedul
* Byungchul Park wrote:
> void up(struct semaphore *sem)
> {
> unsigned long flags;
> + struct task_struct *p = NULL;
>
> raw_spin_lock_irqsave(&sem->lock, flags);
> if (likely(list_empty(&sem->wait_list)))
> sem->count++;
> else
> - __up
This patch to add a generic PHY driver for ROCKCHIP eMMC PHY.
Access the PHY via registers provided by GRF (general register
files) module.
Signed-off-by: Shawn Lin
---
Changes in v3:
- remove empty init/exit
- fix copyright timestamp
- add comment for delay
Changes in v2:
- remove phy from ro
This patch adds a binding that describes the Rockchip eMMC PHYs
found on Rockchip SoCs eMMC interface.
Signed-off-by: Shawn Lin
---
Changes in v3: None
Changes in v2: None
.../devicetree/bindings/phy/rockchip-emmc-phy.txt | 19 +++
1 file changed, 19 insertions(+)
create m
On 2 February 2016 at 23:31, Maxime Ripard
wrote:
> Hi,
>
> On Tue, Feb 02, 2016 at 03:49:53PM +0100, codekip...@gmail.com wrote:
>> From: Marcus Cooper
>>
>> Add devicetree bindings for the SPDIF transceiver found on
>> found on Allwinners A10 and A20 SoCs.
>>
>> Signed-off-by: Marcus Cooper
>>
Hi Kishon,
On 2016/2/3 14:39, Kishon Vijay Abraham I wrote:
Hi,
On Tuesday 05 January 2016 06:38 AM, Shawn Lin wrote:
This patch to add a generic PHY driver for ROCKCHIP eMMC PHY.
Access the PHY via registers provided by GRF (general register
[...]
+ *
+ * Copyright (C) 2015 Shawn Lin
+ *
Hi,
On 01/26/2016 12:26 AM, Torsten Duwe wrote:
The gcc switch -mprofile-kernel, available for ppc64 on gcc > 4.8.5,
allows to call _mcount very early in the function, which low-level
ASM code and code patching functions need to consider.
Especially the link register and the parameter registers
Move panel driver from drivers/staging/panel to drivers/misc.
Signed-off-by: Ksenija Stanojevic
Acked-by: Willy Tarreau
---
Changes in v4:
- modify driver location in MAINTAINERS file
Changes in v3:
- modify driver location in MAINTAINERS file
Changes in v2:
- modify MA
On Tue, 02 Feb 2016 22:59:49 +0100,
Dmitry Vyukov wrote:
>
> On Mon, Feb 1, 2016 at 12:55 PM, Takashi Iwai wrote:
> > On Mon, 01 Feb 2016 12:31:20 +0100,
> > Dmitry Vyukov wrote:
> >>
> >> Hello,
> >>
> >> The following program triggers a splash of WARNINGs in
> >> rawmidi_transmit_ack.
> >> Tak
On 2016/2/3 5:19, Davidlohr Bueso wrote:
> On Mon, 01 Feb 2016, Peter Zijlstra wrote:
>
>> Subject: locking/mutex: Avoid spinner vs waiter starvation
>> From: Peter Zijlstra
>> Date: Fri, 22 Jan 2016 12:06:53 +0100
>>
>> Ding Tianhong reported that under his load the optimistic spinners
>> would
On 2/02/2016 5:52 p.m., Arnaldo Carvalho de Melo wrote:
Em Tue, Feb 02, 2016 at 12:24:19PM +0200, Adrian Hunter escreveu:
This patch does not fix the problem because the thread__zput() will still
segfault later if the error path is not taken.
Sorry, I didn't look closely at this patch because I
GCC 6 adds support for __seg_fs and __seg_gs as named address spaces,
producing the obvious segment overrides for objects so marked.
Exposing the memory reference allows slightly better code generation
in some cases (and in others, merely affects the scheduling). E.g.:
[1]
- mov%gs:0x0(%rip)
Hello,
On (02/03/16 16:27), Stephen Rothwell wrote:
> Hi Andrew,
>
> After merging the akpm-current tree, today's linux-next build (arm
> allnoconfig) failed like this:
>
> In file included from kernel/memremap.c:17:0:
> include/linux/pfn_t.h:108:7: error: 'pud_mkdevmap' declared as function
>
On Wed, Feb 3, 2016 at 5:21 AM, Krzysztof Adamski wrote:
> This patch adds support for APB0 in H3. It seems to be compatible with
> earlier SOCs. apb0 gates controls R_ block peripherals (R_PIO, R_IR,
> etc).
>
> Signed-off-by: Krzysztof Adamski
> ---
> Documentation/devicetree/bindings/clock/su
Hi,
On Wed, Feb 3, 2016 at 5:21 AM, Krzysztof Adamski wrote:
> sunxi_pmx_set accepts pin number and then calculates offset by
> subtracting pin_base from it. sunxi_pinctrl_gpio_get, on the other hand,
> gets offset so we have to convert it to pin number so we won't get
> negative value in sunxi_p
On 02-02-16, 21:06, Saravana Kannan wrote:
> I disagree. I think it's way better and simpler than this patch set. It also
> doesn't tie into cpufreq_governor.* which is a good thing IMO since it keeps
> things simpler for sched-dvfs too.
Lets discuss it further on the other thread ..
--
viresh
On 02-02-16, 22:23, Rafael J. Wysocki wrote:
> On Tue, Feb 2, 2016 at 11:57 AM, Viresh Kumar wrote:
> "The ondemand and conservative governors use the global-attr or
> freq-attr structures to represent sysfs attributes corresponding to
> their tunables
> (which of them is actually used depends o
On 02-02-16, 20:03, Saravana Kannan wrote:
> This is the hotplug case I mentioned. The sysfs file removals will happen
> only for the last CPU in that policy (we thankfully optimized that part last
> year). We also know that multiple CPUs can't be hotplugged at the same time.
> So, in the start of
On 02-02-16, 17:32, Saravana Kannan wrote:
> But if we are expecting sched dvfs to come in, why make it worse for it. It
> would be completely pointless to try and shoehorn sched dvfs to use
> cpufreq_governor.c
We can move the common part to cpufreq core and not make sched-dvfs
reuse cpufreq_gove
On 02-02-16, 14:21, Saravana Kannan wrote:
> I also don't like this patch because it forces governors to either implement
> their own macros and management of their attributes or force them to use the
> governor structs that come with cpufreq_governor.h. cpufreq_governor.h IMHO
> is very ondemand a
Acked-by: Anil Gurumurthy
-Original Message-
From: Dan Carpenter [mailto:dan.carpen...@oracle.com]
Sent: 30 January 2016 20:06
To: Anil Gurumurthy
Cc: Sudarsana Kalluru ; James E.J. Bottomley
; Martin K. Petersen ;
linux-scsi ; linux-kernel
; kernel-janit...@vger.kernel.org
Subject:
On Wed, Feb 3, 2016 at 9:28 AM, Joe Perches wrote:
> On Wed, 2016-02-03 at 11:19 +1100, Julian Calaby wrote:
>> On Tue, Feb 2, 2016 at 9:27 PM, Chen-Yu Tsai wrote:
>> > Add an entry for X-Powers AXP family PMIC drivers and list myself
>> > as maintainer.
> []
>> > diff --git a/MAINTAINERS b/MAINT
From: Hari Prasath Gujulan Elango
Use the managed version of the dma_alloc_coherent() i.e. the
dmam_alloc_coherent() & accordingly cleanup the error handling
part.Also,remove the references to dma_free_coherent
Signed-off-by: Hari Prasath Gujulan Elango
---
v2:kbuild test robot reported
On Tue, Feb 02, 2016 at 09:45:48PM -0500, Martin K. Petersen wrote:
> > "Kirill" == Kirill A Shutemov writes:
>
> Kirill> I have the same problem.
>
> Kirill> Shouldn't we put quirk for that?
>
> I was hoping that Hannes' patch would do the trick so we could avoid
> blacklisting:
>
>
On Tue, 2 Feb 2016 19:07:45 +0100 Gregory CLEMENT wrote:
> Add initial dtsi files to support Marvell Armada 3700 SoC with Cortex-A53
> CPUs. There are two members in this family: the Armada 3710 (Single CPU)
> and the Armada 3720 (Dual CPUs).
>
> It also adds a dts file for the Marvell Armada 372
> Hi Dan,
>
> Thanks for your comment.
> This solution looks good to me.
> I will change it as your suggestion.
>
> But, I have a question about 'mask out the provided *device virtual*
> address'.
> Are lower 16-bits (or 24-bits for JUMP op) of device virtual address the
> same as device physical a
Hi,
On Tuesday 05 January 2016 06:38 AM, Shawn Lin wrote:
> This patch to add a generic PHY driver for ROCKCHIP eMMC PHY.
> Access the PHY via registers provided by GRF (general register
> files) module.
>
> Signed-off-by: Shawn Lin
>
> ---
>
> Changes in v2:
> - remove phy from rockchip_emmc_
On 02-02-16, 17:01, Juri Lelli wrote:
> Hi Rafael,
>
> On 02/02/16 17:35, Rafael J. Wysocki wrote:
> > On Tue, Feb 2, 2016 at 4:47 PM, Juri Lelli wrote:
> > > This patch cleans things up a lot, that's good.
> > >
> > > One thing I'm still concerned about, though: don't we need some locking
> > >
On Tue, 2 Feb 2016 19:07:41 +0100 Gregory CLEMENT wrote:
> The Armada 3700 is an mvebu ARM64 SoC using one or two Cortex-A53 cores
> depending of the variant.
>
> Signed-off-by: Gregory CLEMENT
> Reviewed-by: Thomas Petazzoni
> ---
> arch/arm64/Kconfig.platforms | 6 ++
> 1 file changed, 6
On Thu, Jan 28, 2016 at 10:17 AM, Konstantin Khlebnikov
wrote:
> On Thu, Jan 28, 2016 at 12:17 AM, Matthew Wilcox
> wrote:
>> From: Matthew Wilcox
>>
>> The first two patches here are bugfixes, and I would like to see them
>> make their way into stable ASAP since they can lead to data corruption
On Wed, Feb 3, 2016 at 3:05 AM, Sebastian Reichel wrote:
> Hi Ross,
>
> Please don't top-post on kernel mailinglists. Use either inline
> style or bottom posting.
>
> On Tue, Feb 02, 2016 at 04:41:13PM +1100, Ross Green wrote:
>> On Tue, Feb 2, 2016 at 3:34 PM, Sebastian Reichel wrote:
>> > On Mo
Hi,
On Thursday 28 January 2016 01:44 PM, Shawn Lin wrote:
> If phy_pm_runtime_get_sync failed but we already
> enable regulator, current code return directly without
> doing regulator_disable. This patch fix this problem
> and cleanup err handle of phy_power_on to be more readable.
>
> Fixes: 3b
> On Feb 3, 2016, at 14:07, Deepa Dinamani wrote:
>
> CURRENT_TIME macro is not appropriate for filesystems as it
> doesn't use the right granularity for filesystem timestamps.
> Use current_fs_time() instead.
>
> Signed-off-by: Deepa Dinamani
> Cc: "Yan, Zheng"
> Cc: Sage Weil
> Cc: Ilya Dr
On Tuesday 26 January 2016 03:54 AM, Richard Weinberger wrote:
> Not every arch has io memory.
> So, unbreak the build by fixing the dependencies.
>
> Signed-off-by: Richard Weinberger
Acked-by: Kishon Vijay Abraham I
> ---
> drivers/phy/Kconfig | 4
> 1 file changed, 4 insertions(+)
>
> >On Tue, Feb 02, 2016 at 04:15:43AM +, Bean Huo 霍斌斌 wrote:
> > > Hi Bean,
> > >
> > > [auto build test WARNING on v4.5-rc2]
> >
> > This version 2.0 patches are based on 4.2-rc7.
>
> Please don't send patches against ancient kernel versions.
Brian
Sorry for this. this patches codes are too
Dear Richard
Thanks for reviewing my patches and valuable feedback.
I also want to work with you and Boris on such solution,
I know this is a complicated task, need our joint effort.
Following is my explanation for each of concerns:
> Bean,
>
> Am 02.02.2016 um 03:30 schrieb Bean Huo:
> > This
This is in preparation for the series that transitions
filesystem timestamps to use 64 bit time and hence make
them y2038 safe.
CURRENT_TIME macro will be deleted before merging the
aforementioned series.
Filesystems will use current_fs_time() instead of
CURRENT_TIME.
Use ktime_get_real_ts() here
CURRENT_TIME macro is not appropriate for filesystems as it
doesn't use the right granularity for filesystem timestamps.
Use ext4_current_time() instead which is appropriate for ext4
timestamps.
Signed-off-by: Deepa Dinamani
Cc: "Theodore Ts'o"
Cc: Andreas Dilger
Cc: linux-e...@vger.kernel.org
The macro CURRENT_TIME_SEC does not represent filesystem times
correctly as it cannot perform range checks.
current_fs_time_sec() will be extended to include this.
CURRENT_TIME_SEC is also not y2038 safe. current_fs_time_sec()
will be transitioned to use 64 bit time along with vfs in a
separate se
CURRENT_TIME macro is not appropriate for filesystems as it
doesn't use the right granularity for filesystem timestamps.
Use current_fs_time() instead.
Signed-off-by: Deepa Dinamani
Cc: "Yan, Zheng"
Cc: Sage Weil
Cc: Ilya Dryomov
Cc: ceph-de...@vger.kernel.org
---
fs/ceph/file.c | 4 ++--
fs
CURRENT_TIME macro is not appropriate for filesystems as it
doesn't use the right granularity for filesystem timestamps.
Use current_fs_time() instead.
Signed-off-by: Deepa Dinamani
Cc: Chris Mason
Cc: Josef Bacik
Cc: David Sterba
Cc: linux-bt...@vger.kernel.org
---
fs/btrfs/file.c|
This is in preparation for the series that transitions
filesystem timestamps to use 64 bit time and hence make
them y2038 safe.
The function is meant to replace CURRENT_TIME_SEC macro.
The macro CURRENT_TIME_SEC does not represent filesystem times
correctly as it cannot perform range checks.
curre
This is in preparation for the series that transitions
filesystem timestamps to use 64 bit time and hence make
them y2038 safe.
CURRENT_TIME macro will be deleted before merging the
aforementioned series.
Filesystems will use current_fs_time() instead of
CURRENT_TIME.
Use get_seconds() here as th
This is in preparation for the series that transitions
filesystem timestamps to use 64 bit time and hence make
them y2038 safe.
CURRENT_TIME macro will be deleted before merging the
aforementioned series.
Filesystem times will use current_fs_time() instead of
CURRENT_TIME.
Use ktime_get_real_ts()
The CURRENT_TIME macro is not sufficient for filesystem timestamps since
it does not truncate the values according to filesystem granularity.
simple_link(), simple_unlink() and simple_rename() only need a single
call to current_fs_time() since they do not span filesystems.
Signed-off-by: Deepa Di
CURRENT_TIME macro is not appropriate for filesystems as it
doesn't use the right granularity for filesystem timestamps.
Use current_fs_time() instead.
Change signature of helper cifs_all_info_to_fattr since it
now needs both super_block and cifs_sb_info.
Note: The inode timestamps read from the
Introduction
This patch series is aimed at getting rid of CURRENT_TIME and CURRENT_TIME_SEC
macros.
The idea for the series evolved from my discussions with Arnd Bergmann.
This was originally part of the RFC series[2]:
https://lkml.org/lkml/2016/1/7/20 (under discussion).
Dave Chinner suggested
On 02/02/2016 09:40 PM, kbuild test robot wrote:
drivers/net/wireless/realtek/rtlwifi/core.c:59:2-3: Unneeded semicolon
Remove unneeded semicolon.
Generated by: scripts/coccinelle/misc/semicolon.cocci
CC: Byeoungwook Kim
Signed-off-by: Fengguang Wu
---
Acked-by: Larry Finger
Thanks,
On 02-02-16, 16:49, Juri Lelli wrote:
> There are still paths where we call __cpufreq_governor() without holding
> policy->rwsem, but those should be fixed with my cleanups (that I intend
> to refresh and post soon). So, I'm not sure we can safely remove this
> yet.
No, we can't.. Though I haven't
change from v1 to v2
- remove unnecessary overhead by the redundant spin(un)lock.
Since I faced a infinite recursive printk() bug, I've tried to propose
patches the title of which is "lib/spinlock_debug.c: prevent a recursive
cycle in the debug code". But I noticed the root problem cannot be fixed
On Wed, 2016-02-03 at 09:40 +0800, Cawa Cheng (鄭曄禧) wrote:
>
> -Original Message-
> From: djku...@google.com [mailto:djku...@google.com] On Behalf Of Daniel Kurtz
> Sent: Wednesday, February 03, 2016 12:22 AM
> To: Hs Liao (廖宏祥)
> Cc: Rob Herring; Matthias Brugger; Sascha Hauer; open list:
The attachment(thread.c) can tell us the new mechanism improve output
from the user space code (thread,c) by 1.14x (1174810406/1026910602,
kernel spinlock consumption is reduced from 25% to 15%) as below:
ORG NEW
38186815 43644156
38340186 43121265
38383155 44087753
38567102 43532586
38
On Wed, Feb 03, 2016 at 04:10:30PM +1100, Stephen Rothwell wrote:
> Hi Andrew,
>
> After merging the akpm-current tree, today's linux-next build (i386
> defconfig) failed like this:
>
> In file included from include/linux/mm.h:67:0,
> from include/linux/suspend.h:8,
>
On 02-02-16, 22:53, Rafael J. Wysocki wrote:
> First of all, this is effectively reverting commit 955ef4833574, so
> the subject should be "Revert commit 955ef4833574 (cpufreq: Drop rwsem
> lock around CPUFREQ_GOV_POLICY_EXIT)".
>
> There should be a Fixes: tag pointing to commit 955ef4833574 and
Hi Hari,
[auto build test WARNING on staging/staging-testing]
[also build test WARNING on v4.5-rc2 next-20160202]
[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/Gujulan-Elango-Hari-Prasath-H
This is a kludge, but no one has come up with a a better idea yet.
We'll introduce DMA API support guarded by vring_use_dma_api().
Eventually we may be able to return true on more and more systems,
and hopefully we can get rid of vring_use_dma_api() entirely some
day.
Signed-off-by: Andy Lutomirsk
From: Christian Borntraeger
We are going to require dma_ops for several common drivers, even for
systems that do have an identity mapping. Lets provide some minimal
no-op dma_ops that can be used for that purpose.
Signed-off-by: Christian Borntraeger
Reviewed-by: Joerg Roedel
Signed-off-by: An
This switches virtio to use the DMA API on Xen and if requested by
module option.
This fixes virtio on Xen, and it should break anything because it's
off by default on everything except Xen PV on x86.
To the Xen people: is this okay? If it doesn't work on other Xen
variants (PVH? HVM?), can you
virtio_ring currently sends the device (usually a hypervisor)
physical addresses of its I/O buffers. This is okay when DMA
addresses and physical addresses are the same thing, but this isn't
always the case. For example, this never works on Xen guests, and
it is likely to fail if a physical "virt
From: Christian Borntraeger
As virtio-ccw will have dma ops, we can no longer default to the
zPCI ones. Make use of dev_archdata to keep the dma_ops per device.
The pci devices now use that to override the default, and the
default is changed to use the noop ops for everything that does not
specif
This switches to vring_create_virtqueue, simplifying the driver and
adding DMA API support.
Signed-off-by: Andy Lutomirski
---
drivers/virtio/virtio_mmio.c | 67 ++--
1 file changed, 15 insertions(+), 52 deletions(-)
diff --git a/drivers/virtio/virtio_mmi
This leaves vring_new_virtqueue alone for compatbility, but it
adds two new improved APIs:
vring_create_virtqueue: Creates a virtqueue backed by automatically
allocated coherent memory. (Some day it this could be extended to
support non-coherent memory, too, if there ends up being a platform
on w
Signed-off-by: Andy Lutomirski
---
drivers/virtio/virtio_ring.c | 12
1 file changed, 12 insertions(+)
diff --git a/drivers/virtio/virtio_ring.c b/drivers/virtio/virtio_ring.c
index e46d08107a50..5c802d47892c 100644
--- a/drivers/virtio/virtio_ring.c
+++ b/drivers/virtio/virtio_ring
From: Christian Borntraeger
Some of the alpha pci noop dma ops are identical to the common ones.
Use them.
Signed-off-by: Christian Borntraeger
Reviewed-by: Joerg Roedel
Signed-off-by: Andy Lutomirski
---
arch/alpha/kernel/pci-noop.c | 46
1 file
This switches to vring_create_virtqueue, simplifying the driver and
adding DMA API support.
This fixes virtio-pci on platforms and busses that have IOMMUs. This
will break the experimental QEMU Q35 IOMMU support until QEMU is
fixed. In exchange, it fixes physical virtio hardware as well as
virti
New patch vs 98ee377144935857d8ad5d7d70cdab1da4ede32e on
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input follows.
Confirmed builds and works as expected with that kernel branch.
Signed-off-by: Richard Pospesel
---
diff --git a/drivers/input/mouse/byd.c b/drivers/input/mouse/byd.c
inde
On Tue, 2016-02-02 at 19:38 +, Mark Brown wrote:
> On Fri, Jan 29, 2016 at 08:11:19PM +0800, menghui lin wrote:
> > On Fri, 2016-01-29 at 12:27 +0100, Mark Brown wrote:
>
> > > None of this is answering my question - I know what the current API is,
> > > describing it doesn't tell me about act
From: Xinming Hu
This patch implements a framework for board specific wakeup.
driver parse irq/gpio number from device tree, corresponding
resources will be allocated, and used for host suspend/resume.
Device tree binding file is also updated in the patch.
Signed-off-by: Xinming Hu
Signed-off-b
From: Xinming Hu
Platform device and driver provide easy way to
interact with device-tree-enabled system.
This patch registers platform driver and reorganise
existing device tree specific code.
Signed-off-by: Xinming Hu
Signed-off-by: Amitkumar Karwar
---
Documentation/devicetree/bindings/bt
On 01/30/2016 05:28 AM, Stephen Boyd wrote:
> On 01/13, Joshua Henderson wrote:
>> diff --git a/drivers/clk/clk-pic32.c b/drivers/clk/clk-pic32.c
>> new file mode 100644
>> index 000..9dc5f78
>> --- /dev/null
>> +++ b/drivers/clk/clk-pic32.c
>> @@ -0,0 +1,1801 @@
>> +/*
>> + * Purna Chandra Ma
Hi Andrew,
After merging the akpm-current tree, today's linux-next build (arm
ep93xx_defconfig) failed like this:
mm/slab.c: In function 'is_debug_pagealloc_cache':
mm/slab.c:1608:2: error: implicit declaration of function
'debug_pagealloc_enabled' [-Werror=implicit-function-declaration]
Caused
Hi Andrew,
After merging the akpm-current tree, today's linux-next build (arm
allnoconfig) failed like this:
In file included from kernel/memremap.c:17:0:
include/linux/pfn_t.h:108:7: error: 'pud_mkdevmap' declared as function
returning an array
Caused by commit
a27da20ed50e ("mm: add suppor
From: Hari Prasath Gujulan Elango
Use the managed version of the dma_alloc_coherent() i.e. the
dmam_alloc_coherent() & accordingly cleanup the error handling
part.Also,remove the references to dma_free_coherent.
Signed-off-by: Hari Prasath Gujulan Elango
---
drivers/staging/android/ion/ion_cma
Hi Matthias,
On Tue, 2016-02-02 at 11:44 +0100, Matthias Brugger wrote:
> On 02/02/16 07:56, James Liao wrote:
> > On Sun, 2016-01-31 at 12:51 +0100, Matthias Brugger wrote:
> >> >On 20/01/16 07:08, James Liao wrote:
> >>> > >Refine scpsys driver common code to support multiple SoC / platform.
> >
Conditional codes in rtl_addr_delay() were improved in readability and
performance by using switch codes.
Reviewed-by: Julian Calaby
Signed-off-by: Byeoungwook Kim
Signed-off-by: Fengguang Wu
---
V3 remove unneeded semicolon.
V2 split in separate patchs.
drivers/net/wireless/realtek/rtlwifi/co
Hi all,
Changes since 20160202:
The btrfs-kdave lost its build failure.
The tip tree gained a conflict against Linus' tree.
The gpio tree still had its build failure so I used the version from
next-20160128.
The aio tree still had a build failure so I used the version from
next-20160111.
1 - 100 of 1167 matches
Mail list logo
