Re: [PATCH] thermal: cpu_cooling: fix out of bounds access in time_in_idle

On 19-12-15, 12:54, Javi Merino wrote: > In __cpufreq_cooling_register() we allocate the arrays for time_in_idle > and time_in_idle_timestamp to be as big as the number of cpus in this > cpufreq device. However, in get_load() we access this array using the > cpu number as index, which can result

Re: [PATCH] blackfin-cpufreq: Change return type of cpu_set_cclk() to that of clk_set_rate()

On 19-12-15, 09:23, SF Markus Elfring wrote: > >> From: Markus Elfring > >> Date: Fri, 18 Dec 2015 19:43:27 +0100 > >> > >> The return type "unsigned long" was used by the cpu_set_cclk() function > >> while the type "int" is provided by the clk_set_rate() function.

[PATCH] IRQ/Platform-MSI:Increase the maximum MSIs the MSI framework can support.

From: Ma Jun The current MSI framework can only support 256 platform MSIs. But on Hisilicon platform, some network related devices has about 500 wired interrupts. To support these devices, we need a new maximum value more than 256. Signed-off-by: Ma Jun

[PATCH 2/2] mm/compaction: speed up pageblock_pfn_to_page() when zone is contiguous

There is a performance drop report due to hugepage allocation and in there half of cpu time are spent on pageblock_pfn_to_page() in compaction [1]. In that workload, compaction is triggered to make hugepage but most of pageblocks are un-available for compaction due to pageblock type and skip bit

[PATCH 1/2] mm/compaction: fix invalid free_pfn and compact_cached_free_pfn

free_pfn and compact_cached_free_pfn are the pointer that remember restart position of freepage scanner. When they are reset or invalid, we set them to zone_end_pfn because freepage scanner works in reverse direction. But, because zone range is defined as [zone_start_pfn, zone_end_pfn),

Re: [PATCH] pinctrl: mediatek: convert to arch_initcall

On Fri, Dec 18, 2015 at 11:06 PM, Yingjoe Chen wrote: > On Fri, 2015-12-18 at 12:21 +0800, Daniel Kurtz wrote: >> Move pinctrl initialization earlier in boot so that real devices can find >> their pctldev without probe deferring. >> >> Signed-off-by: Daniel Kurtz

[PATCH v1 1/4] um: Fix ptrace GETREGS/SETREGS bugs

This fix two related bugs: * PTRACE_GETREGS doesn't get the right orig_ax (syscall) value * PTRACE_SETREGS can't set the orig_ax value (erased by initial value) Remove the now useless and error-prone get_syscall(). Signed-off-by: Mickaël Salaün Cc: Jeff Dike

linux-next: manual merge of the cgroup tree with the tip tree

Hi Tejun, Today's linux-next merge of the cgroup tree got a conflict in: init/Kconfig between commits: 257372262056 ("x86/intel_rdt: Add support for Cache Allocation detection") 5ad9144cdb9a ("x86,cgroup/intel_rdt : Add a cgroup interface to manage Intel cache allocation") from the tip

Re: IO errors after "block: remove bio_get_nr_vecs()"

On 2015-12-21 09:32, Linus Torvalds wrote: On Sun, Dec 20, 2015 at 5:50 PM, Artem S. Tashkinov wrote: P.S. I know Linus doesn't condone PAE but I still find it more preferrable than running a mixed environment with almost zero benefit in regard to performance and quite obvious performance

Re: [Propose] Isolate core_pattern in mnt namespace.

On 12/20/2015 05:47 PM, Eric W. Biederman wrote: Dongsheng Yang writes: On 12/20/2015 10:37 AM, Al Viro wrote: On Sun, Dec 20, 2015 at 10:14:29AM +0800, Dongsheng Yang wrote: On 12/17/2015 07:23 PM, Dongsheng Yang wrote: Hi guys, We are working on making

Re: [PATCH] clk: let clk_disable() return immediately if clk is NULL or error

2015-12-05 14:17 GMT+08:00 Masahiro Yamada : > The clk_disable() in the common clock framework (drivers/clk/clk.c) > returns immediately if the given clk is NULL or an error pointer. > It allows drivers to call clk_disable() (and clk_disable_unprepare()) > with a

Re: [PATCH v5 3/5] PCI: qcom: Add Qualcomm PCIe controller driver

On Fri, Dec 18, 2015 at 5:44 AM, kbuild test robot wrote: > Hi Stanimir, > > [auto build test WARNING on next-20151218] > [also build test WARNING on v4.4-rc5] > [cannot apply to pci/next robh/for-next v4.4-rc5 v4.4-rc4 v4.4-rc3] > > url: >

Re: [PATCH] NFC: added the rx delay parameter for nfcsim workqueue

Hi Saurabh, On Mon, Dec 21, 2015 at 12:29:30AM +0530, Saurabh Sengar wrote: > added the rx delay parameter as a device tunable parameter. > > Signed-off-by: Saurabh Sengar > --- > This is a follow up patch after the review comments by Samuel Ortiz > on the initial

Re: IO errors after "block: remove bio_get_nr_vecs()"

On 2015-12-20 23:44, Kent Overstreet wrote: On Sun, Dec 20, 2015 at 07:18:01PM +0100, Christoph Hellwig wrote: On Sun, Dec 20, 2015 at 09:51:14AM -0800, Linus Torvalds wrote: > Kent, Jens, Christoph et al, ie please see this bugzilla: >o > httpps://bugzilla.kernel.org/show_bug.cgi?id=109661

Re: IO errors after "block: remove bio_get_nr_vecs()"

On Mon, Dec 21, 2015 at 04:25:12AM +0500, Artem S. Tashkinov wrote: > On 2015-12-20 23:18, Christoph Hellwig wrote: > >On Sun, Dec 20, 2015 at 09:51:14AM -0800, Linus Torvalds wrote: > >>Kent, Jens, Christoph et al, > >> please see this bugzilla: > >> > >>

Re: [PATCH] ARM: dma-mapping: Just allocate one chunk at a time

Hi Robin, On Friday 18 December 2015 20:20:56 Robin Murphy wrote: > On 18/12/15 18:55, Doug Anderson wrote: > > On Fri, Dec 18, 2015 at 4:41 AM, Robin Murphy wrote: > >> On 17/12/15 22:31, Doug Anderson wrote: > >>> On Thu, Dec 17, 2015 at 12:30 PM, Douglas Anderson wrote: > The

SATA IO errors after ''block: fix segment split"

Hi, Both Andre and Diethard reported that the following kind of SATA write IO errors on 32bit(ARM/i386) with PAE after the commit 578270bfb(block: fix segment split): [ 103.736982] ata1.00: exception Emask 0x0 SAct 0x30 SErr 0x0 action 0x6 frozen [ 103.744476] ata1.00: failed command:

Re: [PATCH v2 4/5] pinctrl: mediatek: Add Pinctrl/GPIO/EINT driver for mt2701

Hi Biao and Joe, On Fri, Dec 18, 2015 at 11:13 PM, Yingjoe Chen wrote: > On Fri, 2015-12-11 at 17:07 +0800, Biao Huang wrote: >> Add mt2701 support using mediatek common pinctrl driver. >> MT2701 have some special pins need an extra setting register >> than other ICs,

Re: IO errors after "block: remove bio_get_nr_vecs()"

On Mon, Dec 21, 2015 at 10:25 AM, Artem S. Tashkinov wrote: > # cat > /sys/block/sda/queue/{max_hw_sectors_kb,max_sectors_kb,max_segments,max_segment_size} > 32767 > 32767 > 168 > 65536 Looks it is fine, then maybe it is related with BIOVEC_PHYS_MERGEABLE(),

[PATCH v5] arm64: run-time detection for aarch32 support

Kernel option COMPAT defines the ability of executing aarch32 binaries. Some platforms does not support aarch32 mode, and so cannot execute that binaries. But we cannot just disable COMPAT for them because the same kernel binary may be used by multiple platforms. In this patch,

Re: IO errors after "block: remove bio_get_nr_vecs()"

On Sun, Dec 20, 2015 at 8:43 PM, Artem S. Tashkinov wrote: > > In the past I happily ran an x86_64 bit kernel together with 32bit userland > for quite some time but then I hit a wall: VirtualBox expects its kernel > modules to have the same bitness as the application itself so

Re: [PATCH 4.4-rc5 v22 4/4] ARM: Allow IPI_CPU_BACKTRACE to exploit FIQ

Hi Daniel, [auto build test ERROR on v4.4-rc5] [also build test ERROR on next-20151218] [cannot apply to tip/irq/core] url: https://github.com/0day-ci/linux/commits/Daniel-Thompson/irq-arm-Use-FIQ-for-NMI-backtrace-when-possible/20151221-045854 config: arm-socfpga_defconfig (attached as

linux-next: manual merge of the orangefs tree with Linus' tree

Hi Mike, Today's linux-next merge of the orangefs tree got a conflict in: Makefile between commit: 1ec218373b8e ("Linux 4.4-rc2") from Linus' tree and commit: 575e946125f7 ("Orangefs: change pvfs2 filenames to orangefs") from the orangefs tree. You should really remove this

Linux 4.4-rc6

Things remain fairly normal. Last week rc5 was very small indeed, this week we have a slightly bigger rc6. The main difference is that rc6 had a network pull in it. But rc6 is still pretty small, and the patch looks pretty normal: just over 60% drivers, 16% core networking, 13% architecture

Re: linux-next: build failure after merge of the vfs tree

Hi Stephen, On Thu, 10 Dec 2015 11:18:47 +1100 Stephen Rothwell wrote: > > Hi Al, > > After merging the vfs tree, today's linux-next build (x86_64 allmodconfig) > failed like this: > > fs/orangefs/symlink.c:26:2: error: unknown field 'follow_link' specified in >

[PATCH v1 3/4] um: Add full asm/syscall.h support

Add subarchitecture-independent implementation of asm-generic/syscall.h allowing access to user system call parameters and results: * syscall_get_nr() * syscall_rollback() * syscall_get_error() * syscall_get_return_value() * syscall_set_return_value() * syscall_get_arguments() *

Re: [PATCH 2/3] thermal: Add Mediatek thermal controller support

Hi Sascha, One nit below that can be fixed up later, or now if you don't plan to spin this driver to address Eduardo's feedback... On Mon, Nov 30, 2015 at 7:42 PM, Sascha Hauer wrote: > This adds support for the Mediatek thermal controller found on MT8173 > and likely

linux-next: manual merge of the cgroup tree with the tip tree

Hi Tejun, Today's linux-next merge of the cgroup tree got a conflict in: include/linux/cgroup_subsys.h between commit: 5ad9144cdb9a ("x86,cgroup/intel_rdt : Add a cgroup interface to manage Intel cache allocation") from the tip tree and commit: b53202e63089 ("cgroup: kill

Re: module: preserve Elf information for livepatch modules

+++ Petr Mladek [17/12/15 17:26 +0100]: On Mon 2015-11-30 23:21:15, Jessica Yu wrote: For livepatch modules, copy Elf section, symbol, and string information from the load_info struct in the module loader. Livepatch uses special relocation sections in order to be able to patch modules that are

[PATCH 1/4] clocksource/vt8500: Use [read\write]l_relaxed()

From: Roman Volkov It is more preferred way to use relaxed read\write without barriers on ARM. http://permalink.gmane.org/gmane.linux.ports.arm.kernel/117658: "For accesses to the same device we don't actually need any barriers on ARM as this is guaranteed by the

Re: [PATCH v1 1/4] um: Fix ptrace GETREGS/SETREGS bugs

Am 21.12.2015 um 01:03 schrieb Mickaël Salaün: > This fix two related bugs: > * PTRACE_GETREGS doesn't get the right orig_ax (syscall) value > * PTRACE_SETREGS can't set the orig_ax value (erased by initial value) > > Remove the now useless and error-prone get_syscall(). > > Signed-off-by:

[PATCH v1 4/4] um: Add seccomp support

This brings SECCOMP_MODE_STRICT and SECCOMP_MODE_FILTER support through prctl(2) and seccomp(2) to User-mode Linux for i386 and x86_64 subarchitectures. secure_computing() is called first in handle_syscall() so that the syscall emulation will be aborted quickly if matching a seccomp rule. This

[PATCH] vfio: Enable VFIO device for powerpc

ec53500f "kvm: Add VFIO device" added a special KVM pseudo-device which is used to handle any necessary interactions between KVM and VFIO. Currently that device is built on x86 and ARM, but not powerpc, although powerpc does support both KVM and VFIO. This makes things awkward in userspace

Re: [PATCH 1/3] ata: sata_dwc_460ex: use "dmas" DT property to find dma channel

Måns Rullgård writes: > Andy Shevchenko writes: > >> On Sun, Dec 20, 2015 at 8:49 PM, Måns Rullgård wrote: >>> Julian Margetson writes: On 12/20/2015 1:11 PM, Måns Rullgård wrote: > Julian Margetson

Re: [PATCH 5/8 v6] thermal: rcar: enable to use thermal-zone on DT

Hi > > +thermal: thermal@e61f { > > + compatible ="renesas,thermal-r8a7790", > > + "renesas,rcar-gen2-thermal", > > + "renesas,rcar-thermal"; > > Isn't having both mutually exclusive? "rcar-thermal" is very basic version of "rcar-gen2", and

Re: [PATCH kernel] vfio: Add explicit alignments in vfio_iommu_spapr_tce_create

On Fri, Dec 18, 2015 at 12:35:47PM +1100, Alexey Kardashevskiy wrote: > The vfio_iommu_spapr_tce_create struct has 4x32bit and 2x64bit fields > which should have resulted in sizeof(fio_iommu_spapr_tce_create) equal > to 32 bytes. However due to the gcc's default alignment, the actual > size of

Re: [PATCH 1/3] ata: sata_dwc_460ex: use "dmas" DT property to find dma channel

Andy Shevchenko writes: > On Sun, Dec 20, 2015 at 8:49 PM, Måns Rullgård wrote: >> Julian Margetson writes: >>> On 12/20/2015 1:11 PM, Måns Rullgård wrote: Julian Margetson writes: > >>> [ 48.769671]

Re: IO errors after "block: remove bio_get_nr_vecs()"

On Mon, Dec 21, 2015 at 1:51 AM, Linus Torvalds wrote: > Kent, Jens, Christoph et al, > please see this bugzilla: > > https://bugzilla.kernel.org/show_bug.cgi?id=109661 > > where Artem Tashkinov bisected his problems with 4.3 down to commit > b54ffb73cadc

Re: [PATCH v2 1/2] KVM: x86: Use vector-hashing to deliver lowest-priority interrupts

On 2015/12/16 9:37, Feng Wu wrote: Use vector-hashing to deliver lowest-priority interrupts, As an example, modern Intel CPUs in server platform use this method to handle lowest-priority interrupts. Signed-off-by: Feng Wu --- arch/x86/kvm/irq_comm.c | 27

Re: [PATCH] ceph: Avoid to propagate the invalid page point

> On Dec 19, 2015, at 10:54, Minfei Huang wrote: > > The variant pagep will still get the invalid page point, although ceph > fails in function ceph_update_writeable_page. > > To fix this issue, Assigne the page to pagep until there is no failure > in function

linux-next: build failure after merge of the l2-mtd tree

Hi Brian, After merging the l2-mtd tree, today's linux-next build (powerpc ppc44x_defconfig) failed like this: drivers/mtd/nand/ndfc.c: In function 'ndfc_chip_init': drivers/mtd/nand/ndfc.c:177:2: error: 'ppdata' undeclared (first use in this function) ppdata.of_node = flash_np; ^ Caused

RE: linux-next: build failure after merge of the pinctrl tree

Hi Stephen Rothwell, This is the same error what we discussed on Friday mail-chain. Please see the attachment of my reply. Regards, Pramod > -Original Message- > From: Stephen Rothwell [mailto:s...@canb.auug.org.au] > Sent: 21 December 2015 10:28 > To: Linus Walleij > Cc:

Re: [PATCH v3 5/5] hisilicon/dts: Add hi655x pmic dts node

On 2015/12/21 11:01, chenfeng wrote: > Mark, > > On 2015/12/19 1:58, Mark Brown wrote: >> On Thu, Dec 17, 2015 at 11:27:27AM +0800, chenfeng wrote: >> >>> +- regulator-vset-regs: Voltage set register offset. >>> +- regulator-vset-mask: voltage set control mask. >>> +- regulator-n-vol: The

Re: IO errors after "block: remove bio_get_nr_vecs()"

On 2015-12-20 22:51, Linus Torvalds wrote: Kent, Jens, Christoph et al, please see this bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=109661 where Artem Tashkinov bisected his problems with 4.3 down to commit b54ffb73cadc ("block: remove bio_get_nr_vecs()") that you've all signed

Re: IO errors after "block: remove bio_get_nr_vecs()"

On 2015-12-20 23:18, Christoph Hellwig wrote: On Sun, Dec 20, 2015 at 09:51:14AM -0800, Linus Torvalds wrote: Kent, Jens, Christoph et al, please see this bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=109661 where Artem Tashkinov bisected his problems with 4.3 down to commit

Re: [PATCH 1/3] ata: sata_dwc_460ex: use "dmas" DT property to find dma channel

Andy Shevchenko writes: > On Sun, Dec 20, 2015 at 8:49 PM, Måns Rullgård wrote: >> Julian Margetson writes: >>> On 12/20/2015 1:11 PM, Måns Rullgård wrote: Julian Margetson writes: > >>> [ 48.769671]

Re: [PATCH 1/3] ata: sata_dwc_460ex: use "dmas" DT property to find dma channel

Andy Shevchenko writes: > On Sun, Dec 20, 2015 at 10:17 PM, Andy Shevchenko > wrote: >> On Sun, Dec 20, 2015 at 8:49 PM, Måns Rullgård wrote: >>> Julian Margetson writes: On 12/20/2015 1:11 PM, Måns

Re: IO errors after "block: remove bio_get_nr_vecs()"

On 2015-12-21 06:38, Ming Lei wrote: On Mon, Dec 21, 2015 at 1:51 AM, Linus Torvalds wrote: Kent, Jens, Christoph et al, please see this bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=109661 where Artem Tashkinov bisected his problems with 4.3 down to commit b54ffb73cadc ("block:

Re: [PATCH v2 2/2] KVM: x86: Add lowest-priority support for vt-d posted-interrupts

On 2015/12/16 9:37, Feng Wu wrote: Use vector-hashing to deliver lowest-priority interrupts for VT-d posted-interrupts. Signed-off-by: Feng Wu --- arch/x86/kvm/lapic.c | 67 arch/x86/kvm/lapic.h | 2 ++

Re: [PATCH v2 1/2] KVM: x86: Use vector-hashing to deliver lowest-priority interrupts

On 2015/12/21 9:50, Wu, Feng wrote: -Original Message- From: Yang Zhang [mailto:yang.zhang...@gmail.com] Sent: Monday, December 21, 2015 9:46 AM To: Wu, Feng ; pbonz...@redhat.com; rkrc...@redhat.com Cc: k...@vger.kernel.org; linux-kernel@vger.kernel.org Subject:

Re: IO errors after "block: remove bio_get_nr_vecs()"

On 2015-12-21 07:18, Ming Lei wrote: On Mon, Dec 21, 2015 at 9:50 AM, Artem S. Tashkinov wrote: BTW, I have posted very similar issue in the link: http://marc.info/?l=linux-ide=145066119623811=2 Artem, I noticed from bugzillar that the hardware is i386, just wondering if PAE is enabled? If

Re: [PATCH] extcon: max3355: kill unneeded #include's

On 2015년 12월 21일 03:31, Sergei Shtylyov wrote: > Some #include's weren't needed from the start, some are left overs from the > earlier driver versions... Kill 'em all! :-) I don't prefer following expression. I think you should write the description to maintain the formal style on the next. -

[PATCH v1 2/4] selftests/seccomp: Remove the need for HAVE_ARCH_TRACEHOOK

Some architectures do not implement PTRACE_GETREGSET nor PTRACE_SETREGSET (required by HAVE_ARCH_TRACEHOOK) but only implement PTRACE_GETREGS and PTRACE_SETREGS (e.g. User-mode Linux). This improve seccomp selftest portability for architectures without HAVE_ARCH_TRACEHOOK support by defining a

RE: [PATCH v2 1/2] KVM: x86: Use vector-hashing to deliver lowest-priority interrupts

> -Original Message- > From: Yang Zhang [mailto:yang.zhang...@gmail.com] > Sent: Monday, December 21, 2015 9:46 AM > To: Wu, Feng ; pbonz...@redhat.com; > rkrc...@redhat.com > Cc: k...@vger.kernel.org; linux-kernel@vger.kernel.org > Subject: Re: [PATCH v2 1/2] KVM:

[PATCH v1.1 4/6] drm/rockchip: vop: spilt scale regsters

There are two version scale control register found on vop, scale full version found on rk3288, support extension registers. and scale little version found on rk3036, only support common scale. Signed-off-by: Mark Yao --- Changes in v1.1 - fix scale calculation mistake.

Re: [BUG] perf test 21("Test object code reading") failure on ARM64

于 2015/12/20 8:25, Jan Stancek 写道: > On Sat, Dec 19, 2015 at 11:04:21AM +0800, xiakaixu wrote: >> >... >>> >>> Hi, >>> >>> What is your objdump version? >> >> Hi, >> >> Sorry for the late reply. >> >> # objdump --version >> GNU objdump (GNU Binutils) 2.25. >> >> I am sure that the system

Re: [PATCH v7 1/4] acpi: pci: Setup MSI domain for ACPI based pci devices

On Thursday, December 10, 2015 08:55:27 AM Suravee Suthikulpanit wrote: > This patch introduces pci_msi_register_fwnode_provider() for irqchip > to register a callback, to provide a way to determine appropriate MSI > domain for a pci device. > > It also introduces

Re: IO errors after "block: remove bio_get_nr_vecs()"

On Mon, Dec 21, 2015 at 06:50:21AM +0500, Artem S. Tashkinov wrote: > On 2015-12-21 06:38, Ming Lei wrote: > >On Mon, Dec 21, 2015 at 1:51 AM, Linus Torvalds wrote: > >>Kent, Jens, Christoph et al, > >> please see this bugzilla: > >> > >> https://bugzilla.kernel.org/show_bug.cgi?id=109661 > >> >

Re: IO errors after "block: remove bio_get_nr_vecs()"

Hello, Linus. On Sun, Dec 20, 2015 at 09:51:14AM -0800, Linus Torvalds wrote: ... > (Also Tejun - maybe you can see what's up - maybe that error message > tells you something) Hmmm... all it says is that something went wrong on the PCI side. > I'm not sure what's up with his machine, the disk

Re: linux-next: manual merge of the cgroup tree with the tip tree

On Mon, Dec 21, 2015 at 03:41:19PM +1100, Stephen Rothwell wrote: > Hi Tejun, > > Today's linux-next merge of the cgroup tree got a conflict in: > > init/Kconfig > > between commits: > > 257372262056 ("x86/intel_rdt: Add support for Cache Allocation detection") > 5ad9144cdb9a

Re: linux-next: build failure after merge of the gpio tree

Hi Linus, On Wed, 16 Dec 2015 14:37:55 +1100 Stephen Rothwell wrote: > > After merging the gpio tree, today's linux-next build (arm > multi_v7_defconfig) failed like this: > > drivers/pinctrl/bcm/pinctrl-nsp-gpio.c: In function 'nsp_gpio_probe': >

Re: IO errors after "block: remove bio_get_nr_vecs()"

On Sun, Dec 20, 2015 at 8:47 PM, Linus Torvalds wrote: > > That said, we obviously need to figure out this current problem > regardless first.. ... although maybe it *would* be interesting to hear what happens if you just compile a 64-bit kernel instead? Do you

RE: [PATCH v11] PCI: Xilinx-NWL-PCIe: Added support for Xilinx NWL PCIe Host Controller

Hi Bjorn, can you comment on this. Marc has also replied for query on irq_dispose_mapping(). > Subject: RE: [PATCH v11] PCI: Xilinx-NWL-PCIe: Added support for Xilinx NWL > PCIe Host Controller > > > Subject: Re: [PATCH v11] PCI: Xilinx-NWL-PCIe: Added support for > > Xilinx NWL PCIe Host

[PATCH] PM / sleep: console flush during suspend if no_console_suspend enabled

On multicore CPUs, sometimes debug console logs are not flushed if you have VT consoles also enabled. Reason being console_lock is taken by secondary/nonboot cpus which are disabled as part of suspend.This patch flushes the console before disabling nonboot cpus Signed-off-by: Bibek Basu

Re: [RFC PATCH v1 0/2] Introduce Innosilicon HDMI driver on Rockchip platforms

Hi Mark On 12/21/2015 03:25 PM, Mark yao wrote: Hi Yakir I want to convert drm/rockchip to support atomic api, I'd like you can do some modify to adapt it. Sure, would update as soon as possible. Thanks, - Yakir - Mark On 2015年11月11日 15:45, Yakir Yang wrote: Hi guys: Here are a

[PATCH] trace-cmd: Print relate stacktrace at once

From: Namhyung Kim Currently trace-cmd prints ring buffer events in a strict time order. But it sometimes annoying that stacktrace from the same cpu can be intermixed with events from other cpu. This patch looks next event when print last record and prints it also if it's a

[PATCH 1/5] watchdog: Create watchdog device in watchdog_dev.c

The watchdog character device is currently created in watchdog_dev.c, and the watchdog device in watchdog_core.c. This results in cross-dependencies, since device creation needs to know the watchdog character device number as well as the watchdog class, both of which reside in watchdog_dev.c.

[PATCH 4/5] watchdog: da9055_wdt: Drop reference counting

Reference counting is now implemented in the watchdog core and no longer required in watchdog drivers. Signed-off-by: Guenter Roeck --- drivers/watchdog/da9055_wdt.c | 24 1 file changed, 24 deletions(-) diff --git a/drivers/watchdog/da9055_wdt.c

[PATCH 0/5] watchdog: Replace driver based refcounting

All variables required by the watchdog core to manage a watchdog are currently stored in struct watchdog_device. The lifetime of those variables is determined by the watchdog driver. However, the lifetime of variables used by the watchdog core differs from the lifetime of struct watchdog_device.

[PATCH 2/5] watchdog: Separate and maintain variables based on variable lifetime

All variables required by the watchdog core to manage a watchdog are currently stored in struct watchdog_device. The lifetime of those variables is determined by the watchdog driver. However, the lifetime of variables used by the watchdog core differs from the lifetime of struct watchdog_device.

[PATCH 5/5] hwmon: (sch56xx) Drop watchdog driver data reference count callbacks

Reference counting is now implemented in the watchdog core and no longer required in watchdog drivers. Signed-off-by: Guenter Roeck --- drivers/hwmon/sch56xx-common.c | 30 -- 1 file changed, 30 deletions(-) diff --git

[PATCH 3/5] watchdog: da9052_wdt: Drop reference counting

Reference counting is now implemented in the watchdog core and no longer required in watchdog drivers. Signed-off-by: Guenter Roeck --- drivers/watchdog/da9052_wdt.c | 24 1 file changed, 24 deletions(-) diff --git a/drivers/watchdog/da9052_wdt.c

Re: [PATCH V2] ALSA: oss: consolidate kmalloc/memset 0 call to kzalloc

On Sat, 19 Dec 2015 15:23:13 +0100, Nicholas Mc Guire wrote: > > This is an API consolidation only. The use of kmalloc + memset to 0 > is equivalent to kzalloc. > > Signed-off-by: Nicholas Mc Guire Applied, thanks. Takashi > --- > > V2: somehow managed to insert exactly

Re: WARNING in crypto_wait_for_test

Am Freitag, 18. Dezember 2015, 19:16:57 schrieb Herbert Xu: Hi Herbert, > On Fri, Dec 18, 2015 at 04:49:17PM +0800, Herbert Xu wrote: > > OK turns out I was looking at the wrong WARN_ON line. > > > > This particular bug is a legacy of the geniv construct we have > > for ablkcipher. > > > > It

[PATCH] staging: wilc1000: fix double mutex_unlock on failure path in wilc_wlan_cleanup()

If hif_read_reg() or hif_write_reg() fail in wilc_wlan_cleanup(), it calls release_bus() and continues execution. But it leads to double release_bus() call that means double unlock of g_linux_wlan->hif_cs mutex. Found by Linux Driver Verification project (linuxtesting.org). Signed-off-by: Alexey

Re: [PATCH] ARM: uniphier: select PINCTRL

On Fri, Dec 18, 2015 at 03:03:59PM +0900, Masahiro Yamada wrote: > Please let me gently ping in case the maintainers might be away from keyboard > during the Christmas days. > > I want this trivial one for the next merge window. Applied now. Thanks for the ping. -Olof -- To unsubscribe from

Re: [PATCH] ARM: multi_v7_defconfig: enable TPS65217 regulator

On Wed, Nov 11, 2015 at 12:39:13PM +0530, Afzal Mohammed wrote: > Enable TPS65217 regulator to have rootfs in MMC for Beagle Bone's. > > Suggested-by: Kishon Vijay Abraham I > Signed-off-by: Afzal Mohammed > --- Applied, thanks. -Olof -- To unsubscribe

Re: [PATCH 4.4-rc5 v22 4/4] ARM: Allow IPI_CPU_BACKTRACE to exploit FIQ

Hi Daniel, [auto build test ERROR on v4.4-rc5] [also build test ERROR on next-20151218] [cannot apply to tip/irq/core] url: https://github.com/0day-ci/linux/commits/Daniel-Thompson/irq-arm-Use-FIQ-for-NMI-backtrace-when-possible/20151221-045854 config: arm-iop-adma (attached as .config)

Re: [PATCH v2 0/8] Raspberry Pi 2 support.

On Fri, Dec 18, 2015 at 11:08:26AM +0100, Alexander Aring wrote: ... > Uncompressing Linux... done, booting the kernel. > [0.00] Booting Linux on physical CPU 0x0 > [0.00] Initializing cgroup subsys cpuset > [0.00] Initializing cgroup subsys cpu > [0.00]

[PATCH v4 2/5] thermal: rockchip: fix a impossible condition caused by the warning

As the Dan report the smatch check the thermal driver warning: drivers/thermal/rockchip_thermal.c:551 rockchip_configure_from_dt() warn: impossible condition '(thermal->tshut_temp > ((~0 >> 1))) => (s32min-s32max > s32max)' Although The shut_temp read from DT is u32,the temperature is currently

Re: [PATCH v3 7/8] clk: rockchip: fix usbphy-related clocks

Hi, On Saturday 19 December 2015 10:51 PM, Heiko Stübner wrote: > Hi Kishon, > > Am Dienstag, 15. Dezember 2015, 16:22:32 schrieb Kishon Vijay Abraham I: >> On Friday 20 November 2015 02:52 AM, Heiko Stuebner wrote: >>> The otgphy clocks really only drive the phy blocks. These in turn >>>

Re: [PATCH 1/2] x86/mm/pat: Change untrack_pfn() to handle unmapped vma

Toshi, On Wed, 9 Dec 2015, Toshi Kani wrote: > diff --git a/arch/x86/mm/pat.c b/arch/x86/mm/pat.c > index 188e3e0..f3e391e 100644 > --- a/arch/x86/mm/pat.c > +++ b/arch/x86/mm/pat.c > @@ -966,8 +966,14 @@ int track_pfn_insert(struct vm_area_struct *vma, > pgprot_t *prot, > > /* > *

[tip:irq/core] genirq/msi: Export functions to allow MSI domains in modules

Commit-ID: a4289dc2ec3a5821076a78ee9678909b4eff297e Gitweb: http://git.kernel.org/tip/a4289dc2ec3a5821076a78ee9678909b4eff297e Author: Jake Oshins AuthorDate: Thu, 10 Dec 2015 17:52:59 + Committer: Thomas Gleixner CommitDate: Sun, 20 Dec

firmware_class warnings on resume

I hit this warning fairly frequently when resuming 4.4-rc5: ret = usermodehelper_read_trylock(); if (WARN_ON(ret)) { dev_err(device, "firmware: %s will not be loaded\n", name); goto out; } It seems like it could be improved in two

Re: Indent issus in kernel module development

I tried it. Not worked unfortunately,. ```bash $ ~/share/linux/scripts/checkpatch.pl --fix --types=spacing testcompletion.c total: 0 errors, 0 warnings, 0 lines checked testcompletion.c has no obvious style problems and is ready for submission. NOTE: Used message types: SPACING ``` 2015-12-19

Re: [PATCH] posix-clock: Use an unsigned data type for a variable

On Sun, 20 Dec 2015, SF Markus Elfring wrote: > >> Reuse the type from this poll call instead. > > > > Why use uint when the function return type it unsigned int? > > Do you prefer to express the type modifier once more there? I don't know what the sentence means, but I think that the type

[GIT PULL] RTC fixes for 4.4 #2

Hi Linus, Please pull those late fixes for the RTC subsystem for 4.4. The following changes since commit 3abb1ada21a4fb5b2920457a2e5c8483abb09a45: rtc: ds1307: fix alarm reading at probe time (2015-11-26 18:11:26 +0100) are available in the git repository at:

Re: [PATCH v3 0/5] Fix a trivial typo and support rk3228/rk3399 SoCs for thermal driver.

在 2015年12月18日 04:09, Eduardo Valentin 写道: Hello, On Thu, Dec 03, 2015 at 04:48:38PM +0800, Caesar Wang wrote: This series pacthes to support the next soc for this thermal driver. I don't add the dts thermal data since these SoCs have *_not_* land in this mainline. I believe these SoCs dts

[PATCH v2 1/4] x86, vdso, pvclock: Simplify and speed up the vdso pvclock reader

From: Andy Lutomirski The pvclock vdso code was too abstracted to understand easily and excessively paranoid. Simplify it for a huge speedup. This opens the door for additional simplifications, as the vdso no longer accesses the pvti for any vcpu other than vcpu 0.

[PATCH v2 0/4] x86: KVM vdso and clock improvements

x86: KVM vdso and clock improvements NB: patch 1 doesn't really belong here, but it makes this a lot easier for me to test. Patch 1, if it's okay at all, should go though the kvm tree. The rest should probably go through tip:x86/vdso once they're reviewed. I'll do a followup to enable vdso

[PATCH 3/4] s390/cio: add NULL test

Add NULL test on call to kzalloc. The semantic match that finds this problem is as follows: (http://coccinelle.lip6.fr/) // @@ expression x; identifier fld; @@ * x = kzalloc(...); ... when != x == NULL x->fld // Signed-off-by: Julia Lawall ---

[PATCH 4/4] ASoC: Intel: add NULL test

Add NULL test on call to devm_kzalloc. The semantic match that finds this problem is as follows: (http://coccinelle.lip6.fr/) // @@ expression x; identifier fld; @@ * x = devm_kzalloc(...); ... when != x == NULL x->fld // Signed-off-by: Julia Lawall ---

[PATCH 0/4] add NULL test

Add NULL tests on various calls to kzalloc and devm_kzalloc. The semantic match that finds these problems is as follows: (http://coccinelle.lip6.fr/) // @@ expression x,y; identifier fld; @@ ( x = \(vmalloc\|kmalloc\|kzalloc\|kcalloc\|kmem_cache_alloc\|krealloc\| kmemdup\|kstrdup\|

[tip:x86/apic] x86/irq: Export functions to allow MSI domains in modules

Commit-ID: c8f3e518d3444ee9200a4987421fcee60f768f11 Gitweb: http://git.kernel.org/tip/c8f3e518d3444ee9200a4987421fcee60f768f11 Author: Jake Oshins AuthorDate: Thu, 10 Dec 2015 17:52:59 + Committer: Thomas Gleixner CommitDate: Sun, 20 Dec

Re: [PATCH v5] rtc: support DS1302 RTC on ICP DAS LP-8x4x

On Sat, 2015-12-19 at 21:38 -0600, Rob Herring wrote: > On Tue, Dec 15, 2015 at 08:45:23PM +0300, Sergei Ianovich wrote: > > Nothing in this is specific to ICP, so the subject should be updated. > > > Signed-off-by: Sergei Ianovich > > CC: Alexandre Belloni

RE: [char-misc-next v2 7/7] watchdog: mei_wdt: re-register device on event

> > > > That breaks the existing behaviour of hot pluggable watchdog interfaces > > > and is different to just about any other device in the kernel. Today with > > > any desktop or server distribution you can already trivially arrange for > > > watchdog daemons to start at the point a watchdog is

Re: [PATCH] posix-clock: Use an unsigned data type for a variable

Reuse the type from this poll call instead. >>> >>> Why use uint when the function return type it unsigned int? >> >> Do you prefer to express the type modifier once more there? > > I don't know what the sentence means, Can it be a matter of taste if the key word "unsigned" should be

Re: [PATCH v5 2/3] tty: Add software emulated RS485 support for 8250

2015-12-20 19:41 GMT+03:00 Andy Shevchenko : > On Sat, Dec 12, 2015 at 1:23 PM, Matwey V. Kornilov wrote: >> Implementation of software emulation of RS485 direction handling is based >> on omap_serial driver. >> Before and after transmission RTS is

Re: [PATCH v5 2/3] tty: Add software emulated RS485 support for 8250

On Sun, Dec 20, 2015 at 8:11 PM, Matwey V. Kornilov wrote: > 2015-12-20 19:41 GMT+03:00 Andy Shevchenko : >> On Sat, Dec 12, 2015 at 1:23 PM, Matwey V. Kornilov >> wrote: >>> Implementation of software emulation of RS485 direction

Re: [char-misc-next v2 6/7] watchdog: mei_wdt: register wd device only if required

On 12/20/2015 04:23 AM, Winkler, Tomas wrote: On 12/17/2015 06:49 AM, Tomas Winkler wrote: From: Alexander Usyskin For Intel Broadwell and newer platforms, the ME device can inform the host whether the watchdog functionality is activated or not. If the watchdog

<    1   2   3   4   5   6   >