[PATCH net-next 4/8] net: dsa: mv88e6xxx: do not increment bus refcount

The MDIO device probe and remove functions are respectively incrementing and decrementing the bus refcount themselves. Since these bus level actions are out of the device scope, remove them. Signed-off-by: Vivien Didelot --- drivers/net/dsa/mv88e6xxx.c | 3

Re: [PATCH v5 08/11] powerpc/powernv: Add platform support for stop instruction

On Wed, 2016-06-08 at 22:31 +0530, Shreyas B Prabhu wrote: > Hi Ben, > > Sorry for the delayed response. > > On 06/06/2016 03:58 AM, Benjamin Herrenschmidt wrote: > > > > On Thu, 2016-06-02 at 07:38 -0500, Shreyas B. Prabhu wrote: > > > > > > @@ -61,8 +72,13 @@ save_sprs_to_stack: > > >    

Re: [PATCH] proc_oom_score: remove tasklist_lock and pid_alive()

On Wed, 8 Jun 2016, Oleg Nesterov wrote: > This was needed before to ensure that ->signal != 0 and do_each_thread() > is safe, see the commit b95c35e76b29b for details. > > Today tsk->signal can't go away and for_each_thread(tsk) is always safe. > > Signed-off-by: Oleg Nesterov

[PATCH v5 0/4] tpm: Command duration logging and chip-specific override

v5: Use msecs_to_jiffies() instead of * HZ / 1000. v4: Rework tpm_get_timeouts() to allow overriding both timeouts and durations via a single callback. This series - improves TPM command error reporting - adds optional logging of TPM command durations - allows chip-specific override of command

[PATCH v5 3/4] tpm: Allow TPM chip drivers to override reported command durations

Some TPM chips report bogus command durations in their capabilities, just as others report incorrect timeouts. Rework tpm_get_timeouts() to allow chip drivers to override either via a single callback. Also clean up handling of TPMs that report milliseconds instead of microseconds. Signed-off-by:

[PATCH v5 2/4] tpm: Add optional logging of TPM command durations

Some TPMs violate their own advertised command durations. This is much easier to debug with data about how long each command actually takes to complete. Add debug messages that can be enabled by running echo -n 'module tpm +p' >/sys/kernel/debug/dynamic_debug/control on a kernel configured

[PATCH] ARM: mm: fix location of _etext

The _etext position is defined to be the end of the kernel text code, and should not include any part of the data segments. This interferes with things that might check memory ranges and expect executable code up to _etext. Signed-off-by: Kees Cook --- arm64 needs this

Re: [PATCH 3/3] ARM: configs: keystone: Enable PINCTRL_SINGLE Config

Franklin, On 6/6/2016 9:00 AM, Santosh Shilimkar wrote: On 6/5/2016 9:56 PM, Keerthy wrote: [...] Santosh, I posted a consolidated series for k2l. Thanks. Will pick that up. Franklin, Could you re-post k2g series on top of the series i posted today. I have update the keystone 4.8

Re: Regression in "kbuild: fix if_change and friends to consider argument order"

Em Ter, 2016-06-07 às 23:52 +0200, Michal Marek escreveu: > On Tue, Jun 07, 2016 at 02:10:28PM +, Zanoni, Paulo R wrote: > >  > > From b36fad65d61fffe4b662d4bfb1ed673c455a36a2 Mon Sep 17 00:00:00 > 2001 > From: Michal Marek > Date: Tue, 7 Jun 2016 11:57:02 +0200 > Subject:

[RESEND PATCH V2 0/2] Add Broadcom USB PHY driver for Broadcom STB SoCs

Add Broadcom USB PHY driver for Broadcom STB SoCs. This driver in combination with the generic ohci, ehci and xhci platform drivers will enable USB1.1, USB2.0 and USB3.0 support. NOTE: An unrelated patch is in the pipline to move the file drivers/soc/brcmstb/common.c to

[RESEND PATCH V2 1/2] soc: brcmstb: Add Product ID and Family ID helper functions

Signed-off-by: Al Cooper --- drivers/soc/brcmstb/common.c| 12 include/linux/soc/brcmstb/brcmstb.h | 10 ++ 2 files changed, 22 insertions(+) diff --git a/drivers/soc/brcmstb/common.c b/drivers/soc/brcmstb/common.c index 94e7335..454f4c2 100644

[PATCH 2/9] mm: implement new pkey_mprotect() system call

From: Dave Hansen pkey_mprotect() is just like mprotect, except it also takes a protection key as an argument. On systems that do not support protection keys, it still works, but requires that key=0. Otherwise it does exactly what mprotect does. I expect it to get

[PATCH 4/9] x86: wire up mprotect_key() system call

From: Dave Hansen This is all that we need to get the new system call itself working on x86. Signed-off-by: Dave Hansen Cc: linux-...@vger.kernel.org Cc: linux...@kvack.org Cc: x...@kernel.org Cc: torva...@linux-foundation.org Cc:

[PATCH 9/9] x86, pkeys: add self-tests

From: Dave Hansen This code should be a good demonstration of how to use the new system calls as well as how to use protection keys in general. This code shows how to: 1. Manipulate the Protection Keys Rights User (PKRU) register with sys_pkey_get/set() 2. Set a

[PATCH 1/9] x86, pkeys: add fault handling for PF_PK page fault bit

From: Dave Hansen PF_PK means that a memory access violated the protection key access restrictions. It is unconditionally an access_error() because the permissions set on the VMA don't matter (the PKRU value overrides it), and we never "resolve" PK faults (like how

Re: [PATCH v12 01/15] PCI: Let pci_mmap_page_range() take extra resource pointer

On Wed, Jun 8, 2016 at 3:35 PM, Yinghai Lu wrote: > At the same time, can you kill __pci_mmap_set_pgprot() for powerpc. Can you please put your two patches and this attached one into to pci/next? Then I could send updated PCI: Let pci_mmap_page_range() take resource

[PATCH 1/2] clk: hi6220: Add RTC clock for pl031

From: Zhangfei Gao Adds clk support for the pl031 RTC on hi6220 Cc: Michael Turquette Cc: Stephen Boyd Cc: Rob Herring Cc: Pawel Moll Cc: Wei Xu Cc: Guodong

[PATCH 2/2] arm64: dts: hi6220: Add pl031 RTC support

From: Zhangfei Gao Add pl031 rtc0 and rtc1 support to hi6220 dtsi Cc: Michael Turquette Cc: Stephen Boyd Cc: Rob Herring Cc: Pawel Moll Cc: Wei Xu Cc:

[PATCH 0/2] Add pl031 RTC support for Hi6220/HiKey

This patchset enables the pl031 RTC on the Hi6220 SoC. I wanted to submit it out for review and consideration to be merged. Please let me know how best these two patches should go upstream (independently via separate maintainers trees, or acked and through one?). thanks -john Cc: Michael

Re: [PATCH] drm/exynos: don't use HW trigger for Exynos5420/5422/5800

Hello Inki, Thanks for your feedback. On 06/08/2016 07:09 PM, Inki Dae wrote: > Hi Javier, > > 2016년 06월 02일 23:20에 Javier Martinez Canillas 이(가) 쓴 글: >> Commit a6f75aa161c5 ("drm/exynos: fimd: add HW trigger support") added >> hardware trigger support to the FIMD controller driver. But this

Re: [PATCH] net: stmmac: dwmac-rk: keep PHY up for WoL

On Wed, Jun 08, 2016 at 03:25:38PM -0700, Vincent Palatin wrote: > On Tue, Jun 7, 2016 at 12:23 AM, Giuseppe CAVALLARO > wrote: > > Hello > > > > On 6/3/2016 7:29 PM, Vincent Palatin wrote: > >> > >> Do not shutdown the PHY if Wake-on-Lan is enabled, else it cannot wake >

[PATCH v2 2/5] clockevents: Add timed freeze

From: Derek Basehore Adds a new feature to clockevents to schedule wakeups on a CPU during freeze. These won't fully wake up the system, but allow simple platform callbacks that don't require device support to be run during freeze with little power impact. This

[PATCH v2 5/5] intel_idle: Add S0ix validation

From: Derek Basehore This adds validation of S0ix entry and enables it on Skylake. Using the new timed_freeze function, we program the CPU to wake up X seconds after entering freeze. After X seconds, it will wake the CPU to check the S0ix residency counters and make sure

[PATCH v2 3/5] x86, apic: Add timed freeze support

From: Derek Basehore This adds support to the clock event devices created by apic to use timed freeze. The apic is able to run a timer during freeze with near izero impact on modern CPUs such as skylake. This will allow S0ix, suspend-to-idle, to be validated on Intel CPUs

[PATCH net-next 1/8] net: dsa: mv88e6xxx: fix style issues

This patch fixes 5 style problems reported by checkpatch: WARNING: suspect code indent for conditional statements (8, 24) #492: FILE: drivers/net/dsa/mv88e6xxx.c:492: + if (phydev->link) + reg |= PORT_PCS_CTRL_LINK_UP; CHECK: Logical continuations should

[PATCH net-next 2/8] net: dsa: mv88e6xxx: remove redundant assignments

The chip->ds and ds->slave_mii_bus assignments are common to both legacy and new MDIO probing and are already done in the later setup code. Remove the duplicated assignments from the MDIO probing code. Signed-off-by: Vivien Didelot ---

[PATCH net-next 6/8] net: dsa: mv88e6xxx: add chip detection helper

Extract the common code to read the switch ID and allocate the private chip data, found in both legacy and new MDIO probe functions, into its own mv88e6xxx_detect helper to reduce boiler plate. Signed-off-by: Vivien Didelot --- drivers/net/dsa/mv88e6xxx.c |

[PATCH net-next 5/8] net: dsa: mv88e6xxx: add switch register helpers

Extract the allocation and registration code related to the dsa_switch structure in a mv88e6xxx_register_switch helper function. For symmetry in the code, add a mv88e6xxx_unregister_switch function. Signed-off-by: Vivien Didelot ---

[PATCH net-next 7/8] net: dsa: mv88e6xxx: explicit compatible devices

Thanks to the new device probing, we can explicit the exact switch model in the device tree. Name the driver "mv88e6xxx" and list all its compatible supported chips. In the meantime, rename the of_device_id table to avoid confusion with a later introduce matching function. Signed-off-by: Vivien

[PATCH net-next 8/8] net: dsa: mv88e6xxx: fail on mismatching probe

Now that we have access at probe time to the chip info described in the device tree, check if the probed device matches the device node, otherwise warn the user and fail. Signed-off-by: Vivien Didelot --- drivers/net/dsa/mv88e6xxx.c | 26

[PATCH net-next 3/8] net: dsa: mv88e6xxx: use already declared variables

In the MDIO probing function, dev is already assigned to >dev and np is already assigned to mdiodev->dev.of_node, so use them. Signed-off-by: Vivien Didelot --- drivers/net/dsa/mv88e6xxx.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff

[PATCH v2 0/5] Add suspend-to-idle validation for Intel SoCs

From: Derek Basehore This patch set adds support for catching errors when entering freeze on Intel Skylake SoCs. Support for this can be added to newer SoCs in later patches. Verification is done by waking up the CPU up to 1000 seconds later based on base 10 exponential

Re: [PATCH] net: stmmac: dwmac-rk: keep PHY up for WoL

On Tue, Jun 7, 2016 at 12:23 AM, Giuseppe CAVALLARO wrote: > Hello > > On 6/3/2016 7:29 PM, Vincent Palatin wrote: >> >> Do not shutdown the PHY if Wake-on-Lan is enabled, else it cannot wake >> us up. >> > > I do not understand why you need that. > This is done inside the

[PATCH v3 5/7] mips: use the new LED disk activity trigger

- platform: rename 'ide-disk' to 'disk-activity' - defconfig: rename 'LEDS_TRIGGER_IDE_DISK' to 'LEDS_TRIGGER_DISK' Signed-off-by: Stephan Linz --- arch/mips/configs/malta_qemu_32r6_defconfig | 2 +- arch/mips/configs/maltaaprp_defconfig | 2 +-

[PATCH v3 4/7] arm: use the new LED disk activity trigger

- dts: rename 'ide-disk' to 'disk-activity' - platform: rename 'ide-disk' to 'disk-activity' - defconfig: rename 'LEDS_TRIGGER_IDE_DISK' to 'LEDS_TRIGGER_DISK' Signed-off-by: Stephan Linz --- arch/arm/boot/dts/am57xx-beagle-x15.dts | 2 +-

Re: [PATCH V6 5/8] vfio: platform: call _RST method when using ACPI

On Sun, May 29, 2016 at 12:01 AM, Sinan Kaya wrote: > The device tree code checks for the presence of a reset driver and calls > the of_reset function pointer by looking up the reset driver as a module. > > ACPI defines _RST method to perform device level reset. After the

Re: [PATCH v12 01/15] PCI: Let pci_mmap_page_range() take extra resource pointer

On Wed, Jun 8, 2016 at 2:03 PM, Bjorn Helgaas wrote: > > Microblaze does look up the resource in pci_mmap_page_range(), but it > never actually uses it. It *looks* like it uses it, but that code is > actually dead and I think we should apply the first patch below. Good one.

[PATCH] staging: lustre: llite: remove lloop device

The lloop device was original developed to work around the lack of direct I/O for the default loop back device. Also the lloop device greatly out performed the default loop back device. The lloop hasn't been worked on for some time and now it no longer out performs the loop device and loop now

Re: [PATCH 06/10] mm, oom: kill all tasks sharing the mm

On Wed, 8 Jun 2016, Michal Hocko wrote: > > Why is the patch asking users to report oom killing of a process that > > raced with setting /proc/pid/oom_score_adj to OOM_SCORE_ADJ_MIN? What is > > possibly actionable about it? > > Well, the primary point is to know whether such races happen in

Re: [PATCH v2 4/4] dell-wmi: Rework code for generating sparse keymap and processing WMI events

On Wed, Jun 08, 2016 at 01:32:27AM +0200, Pali Rohár wrote: > This patch unify procedure for generating sparse keymap and unify also big > switch code for processing WMI events of different types. After this patch > dell-wmi driver does not differ between "old" and "new" hotkey type. > > It

Re: + thp-extract-khugepaged-from-mm-huge_memoryc-fix.patch added to -mm tree

On Wed, Jun 08, 2016 at 02:55:01PM -0700, a...@linux-foundation.org wrote: > > The patch titled > Subject: thp-extract-khugepaged-from-mm-huge_memoryc-fix > has been added to the -mm tree. Its filename is > thp-extract-khugepaged-from-mm-huge_memoryc-fix.patch > > This patch should

Re: [PATCH] pinctrl: Always recurse into bcm folder

Looks good. On 16-06-08 02:44 PM, Florian Fainelli wrote: drivers/pinctrl/bcm/Makefile properly builds individual drivers based on their respective Kconfig symbols. ARCH_BCM is currently a menuconfig option from arch/arm/mach-bcm/Kconfig, which is fine, but prevents ARM64 platforms which do not

Re: [PATCH] LSM: module hierarchy in /proc/.../attr

Hi, [auto build test ERROR on security/next] [also build test ERROR on v4.7-rc2 next-20160608] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Casey-Schaufler/LSM-module-hierarchy-in-proc-attr

Re: [PATCH] drm/exynos: don't use HW trigger for Exynos5420/5422/5800

Hi Javier, 2016년 06월 02일 23:20에 Javier Martinez Canillas 이(가) 쓴 글: > Commit a6f75aa161c5 ("drm/exynos: fimd: add HW trigger support") added > hardware trigger support to the FIMD controller driver. But this broke > the display in at least the Exynos5800 Peach Pi Chromebook. > > So until the

[PATCH] fs/timerfd: reject ALARM timerfds without CAP_WAKE_ALARM

From: Eric Caruso timerfd gives processes a way to set wake alarms, but unlike timers made using timer_create, timerfds don't check whether the process has CAP_WAKE_ALARM before setting alarm-time timers. CAP_WAKE_ALARM is supposed to gate this behavior and so it makes sense

Re: [PATCH] nfit: add Microsoft NVDIMM DSM command set to white list

On Wed, Jun 8, 2016 at 2:47 PM, Stuart Hayes wrote: > > > On 5/26/2016 11:38 AM, Stuart Hayes wrote: >> >> Add the Microsoft _DSM command set to the white list of NVDIMM command >> sets. >> >> This command set is documented at >>

[PATCH] cpufreq: governor: Drop gov_cancel_work()

From: Rafael J. Wysocki There's no reason for gov_cancel_work() to exist at all, as it only has one caller and the only thing done by that caller is to invoke gov_cancel_work(). Accordingly, drop gov_cancel_work() and move its contents to the caller. Signed-off-by:

Re: [PATCH v5 3/3] sched/cputime: Add steal time support to full dynticks CPU time accounting

2016-06-09 3:05 GMT+08:00 Rik van Riel : > On Wed, 2016-06-08 at 11:05 +0800, Wanpeng Li wrote: >> >> @@ -681,12 +681,17 @@ static cputime_t vtime_delta(struct task_struct >> *tsk) >> static cputime_t get_vtime_delta(struct task_struct *tsk) >> { >> unsigned long now =

Re: [PATCH] Add .set_antenna callback in ath6kl driver to remove wireless core warns

Hi Prasun, On Thu, Jun 9, 2016 at 1:20 AM, Prasun Maiti wrote: > I am not sure it works fine. Like ath6kl driver send another cmd to > firmare, I have just filled up the cmd buffer with "tx_ant", and > "rx_ant" values, then use "ath6kl_wmi_cmd_send()" api to send the cmd

Re: [PATCH v3] mailbox: pcc: Support HW-Reduced Communication Subspace type 2

On 6/8/2016 10:24 AM, Hoan Tran wrote: > Hi Ashwin, > > On Wed, Jun 8, 2016 at 5:18 AM, Ashwin Chaugule > wrote: >> + Prashanth (Can you please have a look as well?) >> >> On 31 May 2016 at 15:35, Hoan Tran wrote: >>> Hi Ashwin, >> Hi, >> >> Sorry

Re: [PATCH v3] mailbox: pcc: Support HW-Reduced Communication Subspace type 2

Hi Prashanth, On Wed, Jun 8, 2016 at 5:32 PM, Prakash, Prashanth wrote: > > > On 6/8/2016 10:24 AM, Hoan Tran wrote: >> Hi Ashwin, >> >> On Wed, Jun 8, 2016 at 5:18 AM, Ashwin Chaugule >> wrote: >>> + Prashanth (Can you please have a look as

[PATCH net-next 0/8] net: dsa: mv88e6xxx: misc probe improvements

This patchset cleans a bit both legacy and the new MDIO probing functions by extracting common code and adding helpers. Then, thanks to the new probing model allowing switch chips to be true Linux devices, a device node can explicit the switch model in the tree and thus allows a more robust

Re: [RFC][PATCH 3/5] PM core: Make async suspend/resume of devices use device links

On Thu, Jan 14, 2016 at 02:55:25AM +0100, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > Make the device suspend/resume part of the core system > suspend/resume code use device links to ensure that supplier > and consumer devices will be suspended and resumed

Re: [PATCHv9 2/2] selftest/x86: add mremap vdso test

On 05/21/2016 11:27 PM, Ingo Molnar wrote: Will look at applying this after the merge window. Ping? Thanks, Dmitry Safonov

[PATCH v2 00/15] mtd: nand: allow vendor specific detection/initialization

Hello, This patch series is a step forward in supporting vendor-specific functionalities. This series is mainly moving vendor-specific initialization or detection code out of the core, but also introduces an infrastructure allowing support for vendor-specific features. While those features might

[PATCH v2 05/15] mtd: nand: add manufacturer specific initialization/detection steps

A lot of NANDs are implementing generic features in a non-generic way, or are providing advanced auto-detection logic where the NAND ID bytes meaning changes with the NAND generation. Providing this vendor specific initialization step will allow us to get rid of the full ids in the nand_ids table

[PATCH v2 02/15] mtd: nand: store nand ID in struct nand_chip

Store the NAND ID in struct nand_chip to avoid passing id_data and id_len as function parameters. Signed-off-by: Boris Brezillon --- drivers/mtd/nand/nand_base.c | 55 include/linux/mtd/nand.h | 13 +++

[PATCH v2 01/15] mtd: nand: get rid of the mtd parameter in all auto-detection functions

Now that struct nand_chip embeds an mtd_info object we can get rid of the mtd parameter and extract it from the chip parameter with the nand_to_mtd() helper. Signed-off-by: Boris Brezillon --- drivers/mtd/nand/nand_base.c | 56

[PATCH v2 04/15] mtd: nand: rename nand_get_flash_type() into nand_detect()

The only caller of nand_get_flash_type() (nand_scan_ident()) actually don't use the returned nand_flash_dev pointer except for converting it to to an error code. Rename this function nand_detect() and make it return an integer. Signed-off-by: Boris Brezillon

[PATCH v2 13/15] mtd: nand: samsung: retrieve ECC requirements from extended ID

From: Hans de Goede On some nand controllers with hw-ecc the controller code wants to know the ecc strength and size and having these as 0, 0 is not accepted. Specifying these in devicetree is possible but undesirable as the nand may be different in different production

Re: [PATCH 1/2] mfd: sm-usb-dig: Add support for the TI SM-USB-DIG

On Tue, 31 May 2016, Andrew F. Davis wrote: > The TI SM-USB-DIG is a USB to SPI/I2C/1Wire/GPIO adapter. > Add MFD core support. > > Signed-off-by: Andrew F. Davis > --- > The SPI, GPIO, and 1Wire drivers are WIP. > > drivers/mfd/Kconfig| 8 +++ >

Re: [Intel-gfx] 4.7-rc0: redshift stopped working on intel display

Hi! > Could you try to apply the following patch [1], hopefully this fixes > the issue for you. > > [1] https://patchwork.freedesktop.org/patch/89111/ I updated the kernel, applied the patch and yes, that helped. Thanks!

[PATCH 1/6] virtio_net: add _UAPI prefix to virtio_net header guards

This gives better namespacing and prevents conflicts with no-uapi version of virtio_net header that will be introduced in the following patch. Signed-off-by: Mike Rapoport --- include/uapi/linux/virtio_net.h | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)

Re: [PATCH] kernel/sysrq: reset watchdog on all CPUs while processing sysrq-w

* Andrey Ryabinin wrote: > Lengthy output of sysrq-w may take a lot of time on slow serial console. > Currently we reset NMI-watchdog on the current CPU to avoid softlockup. > Sometimes this doesn't work since watchdog might trigger on the other > CPU which is waiting

Re: NVMe over Fabrics target implementation

*) Extensible to multiple types of backend drivers. nvme-target needs a way to absorb new backend drivers, that does not effect existing configfs group layout or attributes. Looking at the nvmet/configfs layout as-is, there are no multiple backend types defined, nor a way to control backend

[PATCH 2/6] virtio_net: introduce virtio_net_hdr_{from,to}_skb

The code for conversion between virtio_net_hdr and skb GSO info is duplicated at several places. Let's put it to a common place to allow reuse. Signed-off-by: Mike Rapoport --- include/linux/virtio_net.h | 101 + 1 file

Re: [RFC][PATCH 2/6] staging: android: ion: Switch to using an idr to manage heaps

On Mon, Jun 06, 2016 at 11:23:29AM -0700, Laura Abbott wrote: > From: Laura Abbott > > > In anticipation of dynamic registration of heaps, switch to using > an idr for heaps. The idr makes it easier to control the assignment > and management + lookup of heap numbers.

Re: [PATCH 2/2] sched/debug: fix deadlock when enabling sched events

On Wed, Jun 08, 2016 at 09:56:12AM +0200, Ingo Molnar wrote: > > * Josh Poimboeuf wrote: > > > --- a/kernel/sched/fair.c > > +++ b/kernel/sched/fair.c > > @@ -789,6 +789,13 @@ static void update_curr_fair(struct rq *rq) > > update_curr(cfs_rq_of(>curr->se)); > > } > >

Re: [PATCH V8 7/9] acpi: Add generic MCFG table handling

On Wed, Jun 08, 2016 at 02:21:30PM +0200, Tomasz Nowicki wrote: > On 08.06.2016 03:56, Bjorn Helgaas wrote: > >On Mon, May 30, 2016 at 05:14:20PM +0200, Tomasz Nowicki wrote: > >>In order to handle PCI config space regions properly in ACPI, new MCFG > >>interface is defined which does sanity

Re: [PATCH 3/3] x86, mpx, selftests: add MPX self test

These patches look good to me, but it would be nice to get rid of uglies like: > +/* > + * Written by Dave Hansen > + * > + * run like this: > + pid=31390; BDIR="$(cat /proc/$pid/smaps | grep -B1 2097152 | head -1 | awk > -F- '{print $1}')"; ./mpx-dig $pid 0x$BDIR > + >

[PATCH v2 5/7] drm: rockchip: use common iommu api to attach iommu

Rockchip DRM used the arm special API, arm_iommu_*(), to attach iommu for ARM32 SoCs. This patch convert to common iommu API so it would support ARM64 like RK3399. The general idea is domain_alloc(), attach_device() and arch_setup_dma_ops() to set dma_ops manually for DRM at the last.

Re: [PATCH] vme: Update documentation to match api

On 05/06/16 21:35, Martyn Welch wrote: > The vme_register_driver() api changed in commit 5d6abf379d73 ("staging: > vme: make match() driver specific to improve non-VME64x support") but the > documentation wasn't updated. Update the documentation to match the API. > > Signed-off-by: Martyn Welch

Re: [PATCH v10 1/7] regulator: fixed: add support for ACPI interface

On Tue, Jun 07, 2016 at 09:42:48PM -0700, Greg Kroah-Hartman wrote: > On Thu, Jun 02, 2016 at 09:37:23AM +0800, Lu Baolu wrote: > > Add support to retrieve fixed voltage configure information through > > ACPI interface. This is needed for Intel Bay Trail devices, where a > > GPIO is used to

[PATCH] staging: slicoss: replacement of goto statements

From: Jaime Arrocha Replaced deprecated goto statements. Signed-off-by: Jaime Arrocha --- drivers/staging/slicoss/slicoss.c | 22 +++--- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/drivers/staging/slicoss/slicoss.c

Re: [PATCH v2 3/3] tracing: make "string" the default type for [ku]probe event $comm

On Tue, 7 Jun 2016 22:41:33 +0900 Namhyung Kim wrote: > > This is not general, but easy to review :) > > +1 I'll wait for v3 then :-) -- Steve

Re: [PATCH v3 4/6] watchdog: add watchdog pretimeout framework

Hi Guenter, On 08.06.2016 00:43, Guenter Roeck wrote: > On Tue, Jun 07, 2016 at 08:38:45PM +0300, Vladimir Zapolskiy wrote: >> The change adds a simple watchdog pretimeout framework infrastructure, >> its purpose is to allow users to select a desired handling of watchdog >> pretimeout events,

Re: [PATCH V8 7/9] acpi: Add generic MCFG table handling

On 08.06.2016 15:17, Bjorn Helgaas wrote: On Wed, Jun 08, 2016 at 02:21:30PM +0200, Tomasz Nowicki wrote: On 08.06.2016 03:56, Bjorn Helgaas wrote: On Mon, May 30, 2016 at 05:14:20PM +0200, Tomasz Nowicki wrote: In order to handle PCI config space regions properly in ACPI, new MCFG interface

Re: [PATCH V2] watchdog: f71808e_wdt: Add F81866 support

On 06/07/2016 11:57 PM, Ji-Ze Hong (Peter Hong) wrote: Adds watchdog enable support for Fintek F81866 Super-IO chip to Fintek wdt driver (f71808e_wdt) Tested and verified on iBASE MI802 Industrial PC Datasheet references:

Re: [PATCH v3 1/6] watchdog: add set_pretimeout interface

Hi Wolfram, On 08.06.2016 09:34, Wolfram Sang wrote: > On Tue, Jun 07, 2016 at 08:38:42PM +0300, Vladimir Zapolskiy wrote: >> From: Robin Gong >> >> Add set_pretimeout since our watchdog driver has those interfaces and >> obviously, the new common watchdog framework didn't

Re: [PATCH v3 04/30] staging: unisys: visorbus: remove unused module parameters

On Wed, Jun 08, 2016 at 02:13:47AM +, Binder, David Anthony wrote: > > -Original Message- > > From: Neil Horman [mailto:nhor...@redhat.com] > > Sent: Tuesday, June 07, 2016 9:23 AM > > To: Kershner, David A > > Cc: cor...@lwn.net; t...@linutronix.de;

[PATCH 4/6] tuntap: use common code for virtio_net_hdr and skb GSO conversion

Replace open coded conversion between virtio_net_hdr to skb GSO info with virtio_net_hdr_{from,to}_skb Signed-off-by: Mike Rapoport --- drivers/net/tun.c | 97 --- 1 file changed, 21 insertions(+), 76 deletions(-)

[PATCH 5/6] virtio_net: use common code for virtio_net_hdr and skb GSO conversion

Replace open coded conversion between virtio_net_hdr to skb GSO info with virtio_net_hdr_{from,to}_skb Signed-off-by: Mike Rapoport --- drivers/net/virtio_net.c | 78 +++- 1 file changed, 10 insertions(+), 68 deletions(-)

Re: [PATCH 2/2] sched/debug: fix deadlock when enabling sched events

* Josh Poimboeuf wrote: > On Wed, Jun 08, 2016 at 09:56:12AM +0200, Ingo Molnar wrote: > > > > * Josh Poimboeuf wrote: > > > > > --- a/kernel/sched/fair.c > > > +++ b/kernel/sched/fair.c > > > @@ -789,6 +789,13 @@ static void update_curr_fair(struct

Re: [PATCH] watchdog: max77620: Add support for watchdog timer

On 06/08/2016 01:58 AM, Laxman Dewangan wrote: Hi Guenter, Thanks for quick review. I will take care of most of comment. I have one query fr following comment. Thanks, Laxman On Tuesday 07 June 2016 11:26 PM, Guenter Roeck wrote: Hi, On Mon, Jun 06, 2016 at 05:22:44PM +0530, Laxman Dewangan

Re: [PATCH 09/10] mm: only count actual rotations as LRU reclaim cost

On Mon 06-06-16 15:48:35, Johannes Weiner wrote: > Noting a reference on an active file page but still deactivating it > represents a smaller cost of reclaim than noting a referenced > anonymous page and actually physically rotating it back to the head. > The file page *might* refault later on,

Re: [PATCH V8 5/9] pci, acpi: add acpi hook to assign domain number.

On Wed, Jun 08, 2016 at 12:21:19PM +0200, Tomasz Nowicki wrote: > On 08.06.2016 02:15, Bjorn Helgaas wrote: > >On Mon, May 30, 2016 at 05:14:18PM +0200, Tomasz Nowicki wrote: > >>PCI core code provides a config option (CONFIG_PCI_DOMAINS_GENERIC) > >>that allows assigning the PCI bus domain number

Re: dell-smm-hwmon: security problems

On 06/08/2016 02:57 AM, Pali Rohár wrote: Hello! Mario wrote me about two I think security problems in dell-smm-hwmon driver and I would like to ask you, how to fix them. 1) File /proc/i8k (exists only when kernel is compiled with CONFIG_I8K) exports DMI_PRODUCT_SERIAL and it can be read by

Re: 274ad65c9d02 ("drm/radeon: hard reset r600 and newer GPU when hibernating.")

On Wed, Jun 08, 2016 at 01:50:28PM +0200, Christian König wrote: > What's the output of mplayer? Mplayer usually uses video acceleration when > it is available. Something like this? libavformat version 56.23.105 (internal) libavformat file format detected. [lavf] stream 0: video (h264), -vid 0

[PATCH v2 0/7] fix bugs; enable iommu for ARM64

This series patches mainly for ARM64 supporting. To do this, it first add virtual iommu slave device which DRM can attach to, convert DRM driver to use common iommu API instead of the ARM32 functions, and then use DMA API in iommu driver to map, to flush cache. The v2 patches make a lot changes

[PATCH v2 1/7] iommu/rockchip: fix devm_{request,free}_irq parameter

From: Simon Xue Even though the iommu shares irq with its master, using the *dev of iommu instead of master's *dev for devm_{request,free}_irq makes things clear. Signed-off-by: Simon Xue Signed-off-by: Shunqian Zheng ---

[PATCH v2] futex: Calculate the futex key based on a tail page for file-based futexes

Mike Galbraith reported that the LTP test case futex_wake04 was broken by commit 65d8fc777f6d ("futex: Remove requirement for lock_page() in get_futex_key()"). This test case uses futexes backed by hugetlbfs pages and so there is an associated inode with a futex stored on such pages. The problem

[PATCH v2 6/7] iommu/rockchip: use DMA API to map, to flush cache

Use DMA API instead of architecture internal functions like __cpuc_flush_dcache_area() etc. To support the virtual device like DRM the virtual slave iommu added in the previous patch, attaching to which the DRM can use it own domain->dev for dma_map_*(), dma_sync_*() even VOP is disabled. With

[PATCH v2 7/7] iommu/rockchip: enable rockchip iommu on ARM64 platform

From: Simon Xue Signed-off-by: Simon Xue Signed-off-by: Shunqian Zheng --- drivers/iommu/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/iommu/Kconfig b/drivers/iommu/Kconfig index

[PATCH v2 2/7] iommu/rockchip: add map_sg callback for rk_iommu_ops

From: Simon Xue The iommu_dma_alloc() in iommu/dma-iommu.c calls iommu_map_sg() that requires the callback iommu_ops .map_sg(). Adding the default_iommu_map_sg() to rockchip iommu accordingly. Signed-off-by: Simon Xue Signed-off-by: Shunqian Zheng

[PATCH v2 3/7] iommu/rockchip: support virtual iommu slave device

An virtual master device like DRM need to attach to iommu domain to share the domain with VOP(the one with actual iommu slave). We currently check the group is NULL to indicate a virtual master, which is not true since we decide to use the common iommu api to attach device in DRM. With this

[PATCH v2 4/7] ARM: dts: rockchip: add virtual iommu for display

An virtual iommu without reg or interrupts for display. Adding this according to iommu driver changes. Signed-off-by: Shunqian Zheng --- arch/arm/boot/dts/rk3288.dtsi | 6 ++ 1 file changed, 6 insertions(+) diff --git a/arch/arm/boot/dts/rk3288.dtsi

Re: [PATCH] watchdog: max77620: Add support for watchdog timer

On Wednesday 08 June 2016 06:45 PM, Guenter Roeck wrote: On 06/08/2016 01:58 AM, Laxman Dewangan wrote: Hi Guenter, Thanks for quick review. I will take care of most of comment. I have one query fr following comment. Thanks, Laxman On Tuesday 07 June 2016 11:26 PM, Guenter Roeck wrote: Hi,

Re: [PATCH V2] watchdog: max77620: Add support for watchdog timer

Hi, On 06/08/2016 03:17 AM, Laxman Dewangan wrote: Maxim PMIC MAX77620 is Power management IC which have multiple sub blocks like regulators (DCDC/LDOs), GPIO, RTC, Clock, Watchdog timer etc. Add the driver for watchdog timer under watchdog framework. The driver implements the watchdog

Re: [PATCH 2/2] gpio: Support cascaded GPIO chip lookup for OF

Hi Rob, > On Jun 8, 2016, at 00:00 , Rob Herring wrote: > > +Mark R > > On Fri, Jun 3, 2016 at 3:26 PM, Pantelis Antoniou > wrote: >> In certain cases it makes sense to create cascaded GPIO which >> are not real GPIOs, merely point to the

Re: [PATCH 1/2] x86/entry: Avoid interrupt flag save and restore

> So I believe it would be cleaner to name the irqs-off code paths explicitly: > __guest_enter_irqsoff(), and propagate that naming into other parts as well? Ok, I'll send v2 with both the KVM cleanups and the entry optimizations. It should be four patches putting all things together. Thanks

<    1   2   3   4   5   6   7   8   9   10   >