[PATCH 1/1] drm/i915: Fix BUG in i915_gem.c when switch to console

In intel_crtc_page_flip, intel_display.c, the code changed the framebuffer assigned to plane crtc->primary by crtc->primary->fb = fb; However, it forgot to change crtc->primary->state->fb. However, when we switch to console, some kernel code will read crtc->primary->state->fb to get the

linux-next: Tree for Mar 11

Hi all, Changes since 20150310: New tree: drm-exynos The sound-asoc tree still had its build failure so I used the version from next-20150306. The regulator tree lost its build failure. The tip tree gained a conflict against the usb-gadget-fixes tree. The staging tree lost its build failure

Re: [PATCH v6 3/3] ARM: dts: vf610: add Miscellaneous System Control Module (MSCM)

On Wed, Mar 11, 2015 at 08:48:15AM +0800, Shawn Guo wrote: > On Sun, Mar 01, 2015 at 11:41:29PM +0100, Stefan Agner wrote: > > Add the Miscellaneous System Control Module (MSCM) to the base > > device tree for Vybrid SoC's. This module contains registers > > to get information of the individual

Re: [PATCH v2 1/2] cgroups: allow a cgroup subsystem to reject a fork

Hello Tejun, On Wed, Mar 11, 2015 at 2:17 AM, Tejun Heo wrote: > On Wed, Mar 11, 2015 at 01:51:06AM +1100, Aleksa Sarai wrote: >> Actually, I'm fairly sure we can do it all inside cgroup_post_fork() because >> inside cgroup_post_fork() we have access to both the old css_set and the new >> one.

Re: [RFC 1/6] drm: Add top level Kconfig option for DRM fbdev emulation

On 03/10/2015 09:03 PM, Jani Nikula wrote: On Tue, 10 Mar 2015, Archit Taneja wrote: On 03/10/2015 03:35 PM, Daniel Vetter wrote: On Tue, Mar 10, 2015 at 03:22:49PM +0530, Archit Taneja wrote: On 03/10/2015 03:17 PM, Daniel Vetter wrote: On Tue, Mar 10, 2015 at 03:11:28PM +0530, Archit

Re: [RFC 5/6] drm/imx: Remove local fbdev emulation Kconfig option

On 03/10/2015 04:24 PM, Philipp Zabel wrote: Hi Archit, thanks for the cleanup! Am Dienstag, den 10.03.2015, 15:11 +0530 schrieb Archit Taneja: DRM_IMX_FB_HELPER config is currently used to enable/disable fbdev emulation for the imx kms driver. Remove this local config option and use the

Re: [RFC] shmem: Add eventfd notification on utlilization level

On Tue, Mar 10, 2015 at 11:22 PM, Jan Kara wrote: > On Tue 10-03-15 06:03:23, Christoph Hellwig wrote: >> On Tue, Mar 10, 2015 at 10:51:41AM +0900, Kyungmin Park wrote: >> > Any updates? >> >> Please just add disk quota support to tmpfs so thast the standard quota >> netlink notifications can be

Re: [PATCH -next] zsmalloc: Include linux/sched.h to fix build error

Hello Guenter, On Tue, Mar 10, 2015 at 08:41:02PM -0700, Guenter Roeck wrote: > Fix: > > mm/zsmalloc.c: In function '__zs_compact': > mm/zsmalloc.c:1747:2: error: implicit declaration of function 'cond_resched' > > seen when building mips:allmodconfig. > > Fixes: c4d204c38734 ("zsmalloc:

[PATCH v2] x86: Bypass legacy PIC and PIT in ACPI hardware reduced mode

On a platform in ACPI Hardware-reduced mode, the legacy PIC and PIT may not be initialized even though they may be present in silicon. Touching these legacy components causes unexpected result on system. On Bay Trail-T(ASUS-T100) platform, touching these legacy components blocks platform hardware

Re: [PATCH 3/4] mm: move lazy free pages to inactive list

On Wed, Mar 11, 2015 at 10:14:51AM +0800, Wang, Yalin wrote: > > -Original Message- > > From: Minchan Kim [mailto:minc...@kernel.org] > > Sent: Wednesday, March 11, 2015 9:21 AM > > To: Andrew Morton > > Cc: linux-kernel@vger.kernel.org; linux...@kvack.org; Michal Hocko; > > Johannes

TOI: introducing Split Lists hybrids of doubly linked lists within the Linux Kernel

Please note that this proposal is from this engineer and not from the company he works for. This SHOULD also fulfills any legal notification of work done, but not submitted to the Linux Kernel. Transfer of Information : Introduction to what I term as split lists ——-

Re: [RFC V2 04/12] i2c: opal: make use of the new infrastructure for quirks

On 03/11/2015 04:42 AM, Benjamin Herrenschmidt wrote: On Tue, 2015-03-10 at 22:43 +0530, Neelesh Gupta wrote: I tested the i2c opal driver after updating the patch as below. Basically I think we can also support write-then-{read/write} for the number of messages = 2. Ben, any issues if we

[PATCH v2 man-pages] bpf.2: new page documenting bpf(2)

Signed-off-by: Alexei Starovoitov --- man2/bpf.2 | 630 1 file changed, 630 insertions(+) create mode 100644 man2/bpf.2 diff --git a/man2/bpf.2 b/man2/bpf.2 new file mode 100644 index 000..a605489 --- /dev/null +++ b/man2/bpf.2

Re: [PATCH 4/5] Documentation: rename of_selftest.txt to of_unittest.txt

Please use -M flag while sending rename patch, as mentioned in my other mail. On Tue, Mar 10, 2015 at 8:37 PM, Wang Long wrote: > Since the test of the devicetree's OF api use unittest as > its name. so we should rename of_selftest.txt to of_unittest.txt. > > Signed-off-by: Wang Long > --- >

[PATCH v6 tip 2/8] tracing: attach BPF programs to kprobes

User interface: struct perf_event_attr attr = {.type = PERF_TYPE_TRACEPOINT, .config = event_id, ...}; event_fd = perf_event_open(,...); ioctl(event_fd, PERF_EVENT_IOC_SET_BPF, prog_fd); prog_fd is a file descriptor associated with BPF program previously loaded. event_id is an ID of created

[PATCH v6 tip 5/8] samples: bpf: simple non-portable kprobe filter example

tracex1_kern.c - C program compiled into BPF. It attaches to kprobe:netif_receive_skb When skb->dev->name == "lo", it prints sample debug message into trace_pipe via bpf_trace_printk() helper function. tracex1_user.c - corresponding user space component that: - loads bpf program via bpf() syscall

[PATCH v6 tip 4/8] tracing: allow BPF programs to call bpf_trace_printk()

Debugging of BPF programs needs some form of printk from the program, so let programs call limited trace_printk() with %d %u %x %p modifiers only. Similar to kernel modules, during program load verifier checks whether program is calling bpf_trace_printk() and if so, kernel allocates trace_printk

[PATCH v6 tip 1/8] bpf: make internal bpf API independent of CONFIG_BPF_SYSCALL ifdefs

From: Daniel Borkmann Socket filter code and other subsystems with upcoming eBPF support should not need to deal with the fact that we have CONFIG_BPF_SYSCALL defined or not. Having the bpf syscall as a config option is a nice thing and I'd expect it to stay that way for expert users (I presume

[PATCH v6 tip 6/8] samples: bpf: counting example for kfree_skb and write syscall

this example has two probes in one C file that attach to different kprove events and use two different maps. 1st probe is x64 specific equivalent of dropmon. It attaches to kfree_skb, retrevies 'ip' address of kfree_skb() caller and counts number of packet drops at that 'ip' address. User space

[PATCH v6 tip 7/8] samples: bpf: IO latency analysis (iosnoop/heatmap)

BPF C program attaches to blk_mq_start_request/blk_update_request kprobe events to calculate IO latency. For every completed block IO event it computes the time delta in nsec and records in a histogram map: map[log10(delta)*10]++ User space reads this histogram map every 2 seconds and prints it as

[PATCH v6 tip 8/8] samples: bpf: kmem_alloc/free tracker

One bpf program attaches to kmem_cache_alloc_node() and remembers all allocated objects in the map. Another program attaches to kmem_cache_free() and deletes corresponding object from the map. User space walks the map every second and prints any objects which are older than 1 second. Usage: $

[PATCH v6 tip 0/8] tracing: attach eBPF programs to kprobes

Hi Ingo, Steven, Peter, Please review/ack. Thanks! V5->V6: - added simple recursion check to trace_call_bpf() - added tracex4 example that does kmem_cache_alloc/free tracking. It remembers every allocated object in a map and user space periodically prints a set of old objects. With more work

[PATCH v6 tip 3/8] tracing: allow BPF programs to call bpf_ktime_get_ns()

bpf_ktime_get_ns() is used by programs to compue time delta between events or as a timestamp Signed-off-by: Alexei Starovoitov --- include/uapi/linux/bpf.h |1 + kernel/trace/bpf_trace.c | 11 +++ 2 files changed, 12 insertions(+) diff --git a/include/uapi/linux/bpf.h

Re: [PATCH] x86: Bypass legacy PIC and PIT on ACPI hardware reduced platform

On 2015/3/10 16:06, Ingo Molnar wrote: > > * Li, Aubrey wrote: > - in x86_reduced_hw_init() set 'legacy_pic' to 'null_legacy_pic' - clean up 'global_clock_event' handling: instead of a global variable, move its management into x86_platform_ops::get_clockevent()

trust you

My name is Gatan Magsino, I work with Mediterranean Bank in Malta. Can i trust you with a business worth 8.3 million USD? Please reply ONLY to my private email: ta...@rogers.com for more information. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a

[PATCH v4 8/9] selftests/mqueue: Use implicit rules

There's no need to open-code the build rules, use the implicit ones. This has the nice side effect of enabling cross compilation. Signed-off-by: Michael Ellerman --- tools/testing/selftests/mqueue/Makefile | 15 +-- 1 file changed, 9 insertions(+), 6 deletions(-) diff --git

[PATCH v4 9/9] selftests/mount: Use implicit rules

There's no need to open-code the build rules, use the implicit ones. This has the nice side effect of enabling cross compilation. Signed-off-by: Michael Ellerman --- tools/testing/selftests/mount/Makefile | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git

[PATCH v4 4/9] selftests: Add install target

This adds make install support to selftests. The basic usage is: $ cd tools/testing/selftests $ make install That installs into tools/testing/selftests/install, which can then be copied where ever necessary. The install destination is also configurable using eg: $ INSTALL_PATH=/mnt/selftests

[PATCH v4 5/9] selftests: Add install support for the powerpc tests

The bulk of the selftests are actually below the powerpc sub directory. This adds support for installing them, when on a powerpc machine, or if ARCH and CROSS_COMPILE are set appropriately. This is a little more complicated because of the sub directory structure under powerpc, but much of the

[PATCH v4 1/9] kbuild: Don't pass -rR to selftest makefiles

The makefiles under tools/testing/selftests are not real kbuild makefiles, they are regular stand alone makefiles. As such they *do* want all the standard implicit rules and variables defined. So before calling those makefiles, filter -rR out of MAKEFLAGS. Without this not all the selftests are

[PATCH v4 7/9] selftests/timers: Use implicit rules

There's no need to open-code the build rules, use the implicit ones. This has the nice side effect of enabling cross compilation. Signed-off-by: Michael Ellerman --- tools/testing/selftests/timers/Makefile | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git

[PATCH v4 6/9] selftests: Set CC using CROSS_COMPILE once in lib.mk

This avoids repeating the logic in every Makefile. We mimic the top-level Makefile and use $(CROSS_COMPILE)gcc. Signed-off-by: Michael Ellerman --- tools/testing/selftests/efivarfs/Makefile | 1 - tools/testing/selftests/exec/Makefile | 1 - tools/testing/selftests/kcmp/Makefile | 1 -

[PATCH v4 2/9] kbuild: Don't pass LDFLAGS to selftest Makefile

The makefile in arch/x86/Makefile.um sets LDFLAGS and exports it, which is then propagated to the selftest Makefiles and leads to build errors there. The build errors occur because we are passing LDFLAGS to CC, but the option set in Makefile.um (-m elf_x86_64) is not understood by CC. We could fix

[PATCH v4 3/9] selftests: Introduce minimal shared logic for running tests

This adds a Make include file which most selftests can then include to get the run_tests logic. On its own this has the advantage of some reduction in repetition, and also means the pass/fail message is defined in fewer places. However the key advantage is it will allow us to implement install

Re: [PATCH man-pages] bpf.2: new page documenting bpf(2)

On Tue, Mar 10, 2015 at 6:16 AM, Silvan Jegen wrote: > Hi Alexei > > Please find some comments and suggestions below. Thanks a lot for review! I think I've addressed all comments: man2/bpf.2 | 187 1 file changed, 100 insertions(+),

[PATCH -next] zsmalloc: Include linux/sched.h to fix build error

Fix: mm/zsmalloc.c: In function '__zs_compact': mm/zsmalloc.c:1747:2: error: implicit declaration of function 'cond_resched' seen when building mips:allmodconfig. Fixes: c4d204c38734 ("zsmalloc: support compaction") Cc: Minchan Kim Signed-off-by: Guenter Roeck --- mm/zsmalloc.c | 1 + 1 file

Re: [PATCH] Documentation: update the CONFIG_DEBUG_PAGEALLOC description

On 2015/3/2 15:28, Wang Long wrote: cc: vegard.nos...@gmail.com > The CONFIG_DEBUG_PAGEALLOC option now is located under "Kernel > hacking" / "Memory Debugging" / "Debug page memory allocations". > so we should update the description in kmemcheck.txt. > > Signed-off-by: Wang Long > --- >

Re: [PATCH 2/2 net-next] hyperv: Support batched notification

On Wed, Mar 11, 2015 at 2:50 AM, K. Y. Srinivasan wrote: Optimize notifying the host by deferring notification until there are no more packets to be sent. This will help in batching the requests on the host. Signed-off-by: K. Y. Srinivasan --- drivers/net/hyperv/hyperv_net.h |2 +-

Re: [PATCH v2] x86: entry_32.S: change ESPFIX test to not touch PT_OLDSS(%esp)

On Tue, Mar 10, 2015 at 12:57 AM, Ingo Molnar wrote: > > * Denys Vlasenko wrote: > >> Old code was trying to avoid having three branch insns, >> but instead it has a chain of six insns where each insn >> depends on previos one. >> >> And it was touching PT_OLDSS(%esp) unconditionally, even when

[PATCH 2/2] drm/bridge: Add IT6151 bridge driver

This patch adds a drm_bridge driver for the IT6151 MIPI to eDP bridge chip. Signed-off-by: CK Hu Signed-off-by: Jitao Shi --- drivers/gpu/drm/bridge/Kconfig | 10 + drivers/gpu/drm/bridge/Makefile | 1 + drivers/gpu/drm/bridge/it6151.c | 601

[PATCH 1/2] dt-bindings: drm/bridge: Add IT6151 bridge chip driver bindings.

Add devicetree bindings for IT6151 MIPI to eDP bridge chip driver. --- Documentation/devicetree/bindings/drm/bridge/it6151.txt | 15 +++ 1 file changed, 15 insertions(+) create mode 100644 Documentation/devicetree/bindings/drm/bridge/it6151.txt diff --git

[PATCH -next] of/platform: Fix sparc:allmodconfig build

sparc:allmodconfig fails to build with: drivers/built-in.o: In function `platform_bus_init': (.init.text+0x3684): undefined reference to `of_platform_register_reconfig_notifier' of_platform_register_reconfig_notifier is only declared if both OF_ADDRESS and OF_DYNAMIC are configured. Yet, the

[PATCH 6/8] ARM: time: Provide read_boot_clock64() and read_persistent_clock64()

From: Xunlei Pang As part of addressing "y2038 problem" for in-kernel uses, this patch converts read_boot_clock() to read_boot_clock64() and read_persistent_clock() to read_persistent_clock64() using timespec64 by converting clock_access_fn to use timespec64. Signed-off-by: Xunlei Pang ---

[PATCH 7/8] s390: time: Provide read_boot_clock64() and read_persistent_clock64()

From: Xunlei Pang As part of addressing "y2038 problem" for in-kernel uses, this patch converts read_boot_clock() to read_boot_clock64() and read_persistent_clock() to read_persistent_clock64() using timespec64. Since S390 is a 64bit architecture, also rename some timespec to timespec64 in

[PATCH 5/8] ARM: tegra: clock: Provide y2038-safe tegra_read_persistent_clock() replacement

From: Xunlei Pang As part of addressing "y2038 problem" for in-kernel uses, this patch adds the y2038-safe tegra_read_persistent_clock64() using timespec64. Because we rely on some subsequent changes to convert arm multiarch support, tegra_read_persistent_clock() will be removed then.

[PATCH 5/5] of/unittest: replace selftest with unittest

This patch replace the selftest with unittest. Signed-off-by: Wang Long --- Documentation/devicetree/bindings/unittest.txt | 44 +- drivers/of/unittest-data/tests-overlay.dtsi| 108 ++-- drivers/of/unittest.c | 702 - 3 files changed, 427

[PATCH 8/8] time: Remove read_boot_clock()

From: Xunlei Pang Now we have all the read_boot_clock64() for all implementations, it's time to remove read_boot_clock() completely from the kernel. Signed-off-by: Xunlei Pang --- read_persistent_clock() and update_persistent_clock() are way more complex, so we will deal with them gradually in

[PATCH 0/5] Update the OF unittest and some small fix

This series patches do some small fixes in drivers/of/unittest.c, and update the Documenttion. At last, replace selftest with unittest in the c and dtsi files. Wang Long (5): of/unittest: remove the duplicate of_changeset_init of/unittest: Fix the wrong expected value in

[PATCH 3/5] Documentation: update the of_selftest.txt

Since the directory "drivers/of/testcase-data" is renamed to "drivers/of/unittest-data". so we should update the path in the of_selftest.txt. When the kernel is built with OF_UNITTEST enabled, the output dtb is testcases.dtb instead of testcase.dtb, also update it (s/testcase/testcases/).

[PATCH 4/5] Documentation: rename of_selftest.txt to of_unittest.txt

Since the test of the devicetree's OF api use unittest as its name. so we should rename of_selftest.txt to of_unittest.txt. Signed-off-by: Wang Long --- Documentation/devicetree/of_selftest.txt | 198 --- Documentation/devicetree/of_unittest.txt | 198

[PATCH 2/5] of/unittest: Fix the wrong expected value in of_selftest_property_string

This patch fix the wrong expected value of of_property_match_string in of_selftest_property_string. Signed-off-by: Wang Long --- drivers/of/unittest.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/of/unittest.c b/drivers/of/unittest.c index 199fb23..00ddce7

[PATCH 1/5] of/unittest: remove the duplicate of_changeset_init

Remove the duplicate of_changeset_init. In of_selftest_changeset testcase, the "struct of_changeset chgset" is initialized twice, but only once is enough. so, drop the first initializtion code. Signed-off-by: Wang Long --- drivers/of/unittest.c | 1 - 1 file changed, 1 deletion(-) diff --git

[PATCH 0/8] Add y2038 safe replacements for read_boot_clock(), read_persistent_clock() and update_persistent_clock()

From: Xunlei Pang read_boot_clock(), read_persistent_clock() and update_persistent_clock() all use timespec which may have "y2038 problem", thus we are planning on converting all of them to use timespec64. The approach we're using is: 1) First of all, add the "__weak" implementaion of

Re: [PATCH 2/9] selftests: Add install target

On Tue, 2015-03-10 at 09:11 -0600, Shuah Khan wrote: > On 03/09/2015 04:29 PM, Shuah Khan wrote: > > On 03/09/2015 08:20 AM, Shuah Khan wrote: > >> On 03/05/2015 11:53 AM, Dave Jones wrote: > >>> On Tue, Mar 03, 2015 at 03:51:35PM +1100, Michael Ellerman wrote: > >>> > This adds make install

[PATCH 1/8] time: Add y2038 safe read_boot_clock64()

From: Xunlei Pang As part of addressing in-kernel y2038 issues, this patch adds read_boot_clock64() and replaces all the call sites of read_boot_clock() with this function. This is a __weak implementation, which simply calls the existing y2038 unsafe read_boot_clock(). This allows architecture

[PATCH 4/8] ARM: OMAP: 32k counter: Provide y2038-safe omap_read_persistent_clock() replacement

From: Xunlei Pang As part of addressing "y2038 problem" for in-kernel uses, this patch adds the y2038-safe omap_read_persistent_clock64() using timespec64. Because we rely on some subsequent changes to convert arm multiarch support, omap_read_persistent_clock() will be removed then. Also

[PATCH 2/8] time: Add y2038 safe read_persistent_clock64()

From: Xunlei Pang As part of addressing in-kernel y2038 issues, this patch adds read_persistent_clock64() and replaces all the call sites of read_persistent_clock() with this function. This is a __weak implementation, which simply calls the existing y2038 unsafe read_persistent_clock(). This

[PATCH 3/8] time: Add y2038 safe update_persistent_clock64()

From: Xunlei Pang As part of addressing in-kernel y2038 issues, this patch adds update_persistent_clock64() and replaces all the call sites of update_persistent_clock() with this function. This is a __weak implementation, which simply calls the existing y2038 unsafe update_persistent_clock().

Re: [PATCH 2/9] selftests: Add install target

On Wed, Mar 11, 2015 at 02:15:10PM +1100, Michael Ellerman wrote: > On Thu, 2015-03-05 at 13:53 -0500, Dave Jones wrote: > > $ ./all.sh > > -bash: ./all.sh: /bin/bash\n\n: bad interpreter: No such file or directory > > > > Removing the \n\n fixes it. > > > > > + echo "cd

Re: [PATCH 2/4] soc: Mediatek: Add SCPSYS power domain driver

Hi, On Tue, 2015-03-10 at 10:41 +0100, Sascha Hauer wrote: > On Mon, Mar 09, 2015 at 02:35:03PM -0700, Kevin Hilman wrote: > > Sascha Hauer writes: > > > > > Signed-off-by: Sascha Hauer > > > > A bit of a changelog here would be useful describing this driver, that > > it's only covering part

Re: [PATCH 2/9] selftests: Add install target

On Thu, 2015-03-05 at 13:53 -0500, Dave Jones wrote: > On Tue, Mar 03, 2015 at 03:51:35PM +1100, Michael Ellerman wrote: > > This adds make install support to selftests. The basic usage is: > > > > $ cd tools/testing/selftests > > $ make install > > > > That installs into

[PATCH v8 0/2] Add Spreadtrum Sharkl64 Platform support

This patchset adds Spreadtrum's Sharkl64 support in arm64 device tree. Changes from v7: - Added Mark Rutland's Acked-by - Rebased v4.0-rc1 Changes from v6: - Setted stdout-path with "serial1:115200n8" Changes from v5: - Added maintenance interrupt for gic

[PATCH v8 2/2] arm64: Add support for Spreadtrum's Sharkl64 Platform in Kconfig and defconfig

From: Zhizhou Zhang Adds support for Spreadtrum's SoC Platform in the arm64 Kconfig and defconfig files. Signed-off-by: Zhizhou Zhang Signed-off-by: Orson Zhai Signed-off-by: Chunyan Zhang --- arch/arm64/Kconfig | 5 + arch/arm64/configs/defconfig | 1 + 2 files changed, 6

[PATCH v8 1/2] arm64: dts: Add support for Spreadtrum SC9836 SoC in dts and Makefile

From: Zhizhou Zhang Adds the device tree support for Spreadtrum SC9836 SoC which is based on Sharkl64 platform. Sharkl64 platform contains the common nodes of Spreadtrum's arm64-based SoCs. Signed-off-by: Zhizhou Zhang Signed-off-by: Orson Zhai Signed-off-by: Chunyan Zhang Acked-by: Mark

Re: [PATCH v5 12/12] ARM: dts: sun6i: hummingbird: Enable the onboard WiFi module

On Wed, Mar 11, 2015 at 5:32 AM, Maxime Ripard wrote: > On Tue, Mar 10, 2015 at 07:59:24PM +0800, Chen-Yu Tsai wrote: >> The Hummingbird A31 has an AMPAK AP6210 WiFi+Bluetooth module. The >> WiFi part is a BCM43362 IC connected to MMC1 in the A31 SoC via SDIO. >> The IC also takes a power enable

Re: [PATCH v2 1/2] Documentation: update the of_selftest.txt

On 2015/3/10 23:16, Gaurav Minocha wrote: > Hi Rob, > > On Mar 10, 2015 7:51 AM, "Rob Herring" > wrote: >> >> On Tue, Mar 10, 2015 at 9:44 AM, Rob Herring > > wrote: >> > On Sun, Mar 8, 2015 at 9:35 PM, Wang Long > >

Re: [PATCH v2] video: mxsfb: Make sure axi clock is enabled when accessing registers

On Tue, Mar 10, 2015 at 02:02:37PM +0200, Tomi Valkeinen wrote: > On 04/03/15 09:06, Liu Ying wrote: > > The LCDIF engines embedded in i.MX6sl and i.MX6sx SoCs need the axi clock > > as the engine's system clock. The clock should be enabled when accessing > > LCDIF registers, otherwise the kernel

Re: node-hotplug: is memset 0 safe in try_offline_node()?

On 2015/3/11 9:12, Gu Zheng wrote: > Hi Xishi, > > What is the condition of this problem now? Hi Gu, I have no machine to do this test now. But I've tested the patch "just remove memset 0" more than 20 hours last week, it's OK. Thanks, Xie XiuQi > > Regards, > Gu > On 03/05/2015

Re: [PATCH] dma: Add Xilinx ZDMA device tree Binding Documentation

On Wed, Mar 11, 2015 at 5:31 AM, Sören Brinkmann wrote: > On Tue, 2015-03-10 at 07:46PM +0530, Punnaiah Choudary Kalluri wrote: >> Device-tree binding documentation for Xilinx ZDMA Engine >> >> Signed-off-by: Punnaiah Choudary Kalluri >> --- >> .../devicetree/bindings/dma/xilinx/zdma.txt

Re: [PATCH] dma: Add Xilinx ZDMA device tree Binding Documentation

On Wed, Mar 11, 2015 at 5:27 AM, Josh Cartwright wrote: > On Tue, Mar 10, 2015 at 07:46:23PM +0530, Punnaiah Choudary Kalluri wrote: >> Device-tree binding documentation for Xilinx ZDMA Engine >> >> Signed-off-by: Punnaiah Choudary Kalluri >> --- > > Hey Punnaiah- > > Was this intended to be

Re: [E1000-devel] [PATCH v3] ixgbe: make VLAN filter conditional

On 03/10/2015 05:59 PM, Hiroshi Shimamoto wrote: From: Hiroshi Shimamoto Disable hardware VLAN filtering if netdev->features VLAN flag is dropped. In SR-IOV case, there is a use case which needs to disable VLAN filter. For example, we need to make a network function with VF in virtualized

linux-next: manual merge of the tip tree with the usb-gadget-fixes tree

Hi all, Today's linux-next merge of the tip tree got a conflict in drivers/usb/isp1760/isp1760-core.c between commit 80b4a0f8feeb ("usb: isp1760: set IRQ flags properly") from the usb-gadget-fixes tree and commit d8bf368d0631 ("genirq: Remove the deprecated 'IRQF_DISABLED' request_irq() flag

Help-desk Service Center requires your immediate re-activation of your Email

Help-desk Service Center requires your immediate re-activation of your Email account. This is to upgrade email account to the new anti spam virus detector sever 2014. Inability to complete this procedure will render your account inactivate. Activate by completing the survey procedure. CLICK LINK:

Re: [PATCH v4 4/9] epoll: Add implementation for epoll_ctl_batch

On Tue, 03/10 09:59, Dan Rosenberg wrote: > On 03/09/2015 09:49 PM, Fam Zheng wrote: > > + if (!cmds || ncmds <= 0 || ncmds > EP_MAX_BATCH) > > + return -EINVAL; > > + cmd_size = sizeof(struct epoll_ctl_cmd) * ncmds; > > + /* TODO: optimize for small arguments like select/poll with

Re: [PATCH v2] selftests: kcmp build fails when invoked from kselftest target

On Tue, 2015-03-10 at 18:08 -0600, Shuah Khan wrote: > kcmp Makefile doesn't have an explicit build rule. As a result, > kcmp build fails, when it is run from top level Makefile target > kselftest. Without the explicit rule, make works only when it is > run in the current directory or from

[PATCH] kbuild: Don't pass LDFLAGS to selftest Makefile

The makefile in arch/x86/Makefile.um sets LDFLAGS and exports it, which is then propagated to the selftest Makefiles and leads to build errors there. The build errors occur because we are passing LDFLAGS to CC, but the option set in Makefile.um (-m elf_x86_64) is not understood by CC. We could fix

Re: [PATCH -next] hwmon: fix gpio-fan.c build

--- drivers/hwmon/Kconfig |1 + 1 file changed, 1 insertion(+) --- linux-next-20150310.orig/drivers/hwmon/Kconfig +++ linux-next-20150310/drivers/hwmon/Kconfig @@ -510,6 +510,7 @@ config SENSORS_G762 config SENSORS_GPIO_FAN tristate "GPIO fan" depends

RE: [PATCH 3/4] mm: move lazy free pages to inactive list

> -Original Message- > From: Minchan Kim [mailto:minc...@kernel.org] > Sent: Wednesday, March 11, 2015 9:21 AM > To: Andrew Morton > Cc: linux-kernel@vger.kernel.org; linux...@kvack.org; Michal Hocko; > Johannes Weiner; Mel Gorman; Rik van Riel; Shaohua Li; Wang, Yalin; Minchan > Kim >

[PATCH] pm: at91: pm_slowclock: fix the compilation error

When compiling the kernel in thumb2 (CONFIG_THUMB2_KERNEL option activated), we hit a compilation error. The error message is listed below: ---8< - Error: cannot use register index with PC-relative addressing -- `str r0,.saved_lpr' --->8 Add the .arm directive in the assembly files

Re: linux-next: build warnings after merge of the crypto tree

On Tue, Mar 10, 2015 at 07:00:26PM -0700, Tadeusz Struk wrote: > On 03/09/2015 11:03 PM, Herbert Xu wrote: > > This is a bit of a bummer. What happened is that net-next has > > killed the kiocb argument to sendmsg/recvmsg. However, this > > change is obviously not part of the crypto tree and

Re: linux-next: build warnings after merge of the crypto tree

On 03/09/2015 11:03 PM, Herbert Xu wrote: > This is a bit of a bummer. What happened is that net-next has > killed the kiocb argument to sendmsg/recvmsg. However, this > change is obviously not part of the crypto tree and algif_aead > only exists in the crypto tree. > > So Stephen could you fix

Re: [PATCH 45/45] include/uapi/asm-generic/ucontext.h: include signal.h and sigcontext.h

On Tue, Feb 17, 2015 at 10:10:42AM +0100, Arnd Bergmann wrote: > On Tuesday 17 February 2015 00:05:48 Mikko Rapeli wrote: > > #ifndef __ASM_GENERIC_UCONTEXT_H > > #define __ASM_GENERIC_UCONTEXT_H > > > > +#include > > +#include > > + > > struct ucontext { > > > > Including another

Re: [PATCHv3 5/5] usb: gadget: udc-core: independent registration of gadgets and gadget drivers

Hi, On Wed, Mar 11, 2015 at 02:21:38AM +0200, Ruslan Bilovol wrote: > >> @@ -469,6 +488,16 @@ int usb_gadget_unregister_driver(struct > >> usb_gadget_driver *driver) > >> break; > >> } > >> > >> + if (ret) { > >> + struct usb_gadget_driver

Re: [PATCH 43/45] include/uapi/linux/netfilter_bridge.h: include if.h

On Tue, Feb 17, 2015 at 01:02:50AM +0100, Jan Engelhardt wrote: > On Tuesday 2015-02-17 00:05, Mikko Rapeli wrote: > > >Fixes userspace compilation errors like: > > > >error: field ‘in’ has incomplete type > >struct in_addr in; > > > >+#include > > Patch 36/45 included linux/in.h instead of

[PATCH] phy: omap-usb2: Fix missing clk_prepare call when using old dt name

Current code does not call clk_prepare(phy->optclk) when using the old usb_otg_ss_refclk960m name. Fix it. Signed-off-by: Axel Lin --- drivers/phy/phy-omap-usb2.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/drivers/phy/phy-omap-usb2.c b/drivers/phy/phy-omap-usb2.c

Re: [PATCH 1/2] power: reset: Add generic SYSCON register mapped poweroff.

Hi, On Tue, Mar 10, 2015 at 04:21:09PM -0700, Moritz Fischer wrote: > Add a generic SYSCON register mapped poweroff mechanism. Driver looks mostly fine. > [...] > +#ifdef CONFIG_OF > +static const struct of_device_id syscon_poweroff_of_match[] = { > + { .compatible = "syscon-poweroff" }, >

Re: [PATCH 1/2] gpio / ACPI: Avoid unnecessary checks in __gpiod_get_index()

On 2015/3/11 6:08, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > If dev is NULL in __gpiod_get_index() and both ACPI and OF are > enabled, it will be checked twice before the code decides to give > up with DT/ACPI lookup, so avoid that. > > Also use the observation that ACPI_COMPANION()

Re: [PATCHv3 5/5] usb: gadget: udc-core: independent registration of gadgets and gadget drivers

On Wed, 11 Mar 2015, Ruslan Bilovol wrote: > Hi Alan, Hello. > > If you add the list_init and list_del_init above, this loop won't be > > needed. You can just call list_del. > > I disagree with this. This function is externally visible and we can't > guarantee that some buggy code will not

[PATCH 5/6] staging: sm750fb: Fix __iomem pointer types

This patch annotates pointers as referring to I/O mapped memory where they ought to be, removes now unnecessary ugly casts, eliminates an incorrect deref on I/O mapped memory by using iowrite16 instead, and updates the pointer arithmetic accordingly to take into account that the pointers are now

[PATCH 2/6] staging: sm750fb: Fix non-ANSI function declarations

Fixes Function declarations which expect no parameters to have a parameter list consisting of void. This fixes the following sparse warnings:- drivers/staging/sm750fb/sm750_hw.c:584:23: warning: non-ANSI function declaration of function 'hw_sm750le_deWait'

[PATCH 4/6] staging: sm750fb: Expose hw712_fillrect externally

This patch adds a reference to hw712_fillrect which is not used elsewhere in the driver, but appears to be an alternative to the hw_fillrect method. This patch fixes the following sparse warning:- drivers/staging/sm750fb/sm750_accel.c:95:5: warning: symbol 'hw712_fillrect' was not declared.

[PATCH 3/6] staging: sm750fb: Make internal functions static

This patch declares externally unavailable functions static. This fixes the following sparse warnings:- drivers/staging/sm750fb/ddk750_swi2c.c:223:6: warning: symbol 'swI2CStart' was not declared. Should it be static? drivers/staging/sm750fb/ddk750_swi2c.c:234:6: warning: symbol 'swI2CStop' was

[PATCH 6/6] staging: sm750fb: Spinlock and unlock in the same block

This patch combines spinlock locks and unlocks together in the same block rather than occurring in separate blocks preventing a possible deadlock. This fixes the following sparse warnings:- drivers/staging/sm750fb/sm750.c:218:22: warning: context imbalance in 'lynxfb_ops_fillrect' - different

Re: node-hotplug: is memset 0 safe in try_offline_node()?

Hi Xishi, What is the condition of this problem now? Regards, Gu On 03/05/2015 05:39 PM, Xishi Qiu wrote: > On 2015/3/5 16:26, Gu Zheng wrote: > >> Hi Xishi, >> Could you please try the following one? >> It postpones the reset of obsolete pgdat from try_offline_node() to >> hotadd_new_pgdat(),

[PATCH 1/6] staging: sm750fb: Use memset_io instead of memset

This patch uses memset_io instead of memset when using memset on __iomem qualified pointers. This fixes the following sparse warnings:- drivers/staging/sm750fb/sm750.c:489:17: warning: incorrect type in argument 1 (different address spaces) drivers/staging/sm750fb/sm750.c:490:17: warning:

Re: [PATCH RESEND v4 1/3] lib/plist: Provide plist_add_head() for nodes with the same prio

On Mon, Mar 9, 2015 at 3:32 AM, Xunlei Pang wrote: > From: Xunlei Pang > > If there're multiple nodes with the same prio as @node, currently > plist_add() will add @node behind all of them. Now we need to add > @node before all of these nodes for SMP RT scheduler. > > This patch adds a common

Re: [PATCH 41/45] include/uapi/sound/emu10k1.h: hide gpr_valid, tram_valid and code_valid in userspace

On Tue, Feb 17, 2015 at 07:27:38AM +0100, Takashi Iwai wrote: > At Tue, 17 Feb 2015 00:05:44 +0100, > Mikko Rapeli wrote: > > > > The DECLARE_BITMAP macro is not available in userspace headers. > > Fixes userspace compile error: > > error: expected specifier-qualifier-list before ‘DECLARE_BITMAP’

[PATCH 3/4] mm: move lazy free pages to inactive list

MADV_FREE is hint that it's okay to discard pages if there is memory pressure and we uses reclaimers(ie, kswapd and direct reclaim) to free them so there is no worth to remain them in active anonymous LRU so this patch moves them to inactive LRU list's head. This means that MADV_FREE-ed pages

[PATCH 1/4] mm: free swp_entry in madvise_free

When I test below piece of code with 12 processes(ie, 512M * 12 = 6G consume) on my (3G ram + 12 cpu + 8G swap, the madvise_free is siginficat slower (ie, 2x times) than madvise_dontneed. loop = 5; mmap(512M); while (loop--) { memset(512M); madvise(MADV_FREE or MADV_DONTNEED); }

[PATCH 4/4] mm: make every pte dirty on do_swap_page

Bascially, MADV_FREE relys on the pte dirty to decide whether it allows VM to discard the page. However, if there is swap-in, pte pointed out the page has no pte_dirty. So, MADV_FREE checks PageDirty and PageSwapCache for those pages to not discard it because swapped-in page could live on swap

  1   2   3   4   5   6   7   8   9   10   >