Re: [PATCH] driver core: Ensure proper suspend/resume ordering

On Mon, 21 Sep 2015, Thierry Reding wrote: > > > Force-removing drivers that depend on a device that's being unbound > > > would be a possibility to solve the problem where consumers depend on a > > > device that could physically go away. It might also be the right thing > > > to do in any case.

[PATCH perf/core] perf tools: Add include/err.h into MANIFEST

Otherwise the tarpkg is incomplete (tarpkg tests fails). Link: http://lkml.kernel.org/n/tip-z2s0apjs7kyinererbnnm...@git.kernel.org Signed-off-by: Jiri Olsa --- tools/perf/MANIFEST | 1 + 1 file changed, 1 insertion(+) diff --git a/tools/perf/MANIFEST b/tools/perf/MANIFEST

Re: [RFC v7 13/41] richacl: Check if an acl is equivalent to a file mode

On Mon, Sep 21, 2015 at 09:59:07AM -0400, Austin S Hemmelgarn wrote: > On 2015-09-17 20:56, J. Bruce Fields wrote: > >On Thu, Sep 17, 2015 at 02:22:19PM -0400, bfields wrote: > >>On Sat, Sep 05, 2015 at 12:27:08PM +0200, Andreas Gruenbacher wrote: > >>>ACLs are considered equivalent to file modes

Re: [PATCH 00/16] usb: gadget: amd5536udc: fix memory leaks

On Mon, Sep 21, 2015 at 06:18:04PM +0530, Sudip Mukherjee wrote: > On Sun, Sep 20, 2015 at 11:17:36AM -0500, Felipe Balbi wrote: > > On Sun, Sep 20, 2015 at 01:42:42PM +0530, Sudip Mukherjee wrote: > > > On Sat, Sep 19, 2015 at 09:24:38AM +0530, Sudip Mukherjee wrote: > > > > On Fri, Sep 18, 2015

Re: EXT4: new warnings from 4.3.0-rc2

Thanks Ortwin. On 09/21/15 14:27, Ortwin Glück wrote: >> [2.481399] EXT4-fs (sda2): couldn't mount as ext3 due to feature >> incompatibilities >> [2.482426] EXT4-fs (sda2): couldn't mount as ext2 due to feature >> incompatibilities > > As the kernel doesn't know which FS your root is,

Re: [RFC PATCH 0/3] fix *pbl format support

Hi Rasmus, On 09/16/2015 10:35 PM, Rasmus Villemoes wrote: > > I just remembered: I noticed a while ago that the qualifier member is > only used inside format_decode (in the end, the information is folded > into the type member), so one might as well use a local variable for > that. This gives

[PATCH 07/14] RFC: usb/host/fotg210: Remove a macro from snprintf

This patch removes a macro from a call to snprintf() and moves it's content to just before the call to snprintf() assigning a value to a new variable named tmp. The goal of this patch is to make the code easier to understand. Signed-off-by: Peter Senna Tschudin ---

RE: [PATCH 1/3] ASoC: codecs: Add da7219 codec driver

On September 19, 2015 18:44, Mark Brown wrote: > > + do { > > + statusa = snd_soc_read(codec, DA7219_ACCDET_STATUS_A); > > + if (statusa & DA7219_MICBIAS_UP_STS_MASK) > > + micbias_up = true; > > + } while (!micbias_up); > > This could go into an

Re: [RFC] Perf: Trigger and dump sample info to perf.data from user space ring buffer

On Mon, Sep 21, 2015 at 09:54:39PM +0800, Yunlong Song wrote: > [Problem Background] > > We want to run perf in daemon mode and collect the traces when the exception > (e.g., machine crashes, app performance goes down) appears. Perf may run for a > long time (from days to weeks or even months),

Re: [RFC PATCH 0/2] kvmclock: fix ABI breakage from PVCLOCK_COUNTS_FROM_ZERO.

2015-09-20 19:57-0300, Marcelo Tosatti: > On Fri, Sep 18, 2015 at 05:54:28PM +0200, Radim Krčmář wrote: >> This patch series will be disabling PVCLOCK_COUNTS_FROM_ZERO flag and is >> RFC because I haven't explored many potential problems or tested it. > > The justification to disable

[PATCH 1/4] sound/onyx: remove redundant case entry

Case ti->tag == 0 can be included in the last return, remove it. No functional change. Signed-off-by: Yaowei Bai --- sound/aoa/codecs/onyx.c | 1 - 1 file changed, 1 deletion(-) diff --git a/sound/aoa/codecs/onyx.c b/sound/aoa/codecs/onyx.c index a04edff..a407e1f 100644

[PATCH v6 22/22] of/platform: Defer probes of registered devices

Instead of trying to match and probe platform and AMBA devices right after each is registered, delay their probes until device_initcall_sync. This means that devices will start probing once all built-in drivers have registered, and after all platform and AMBA devices from the DT have been

[PATCH v6 18/22] dma: of: Probe DMA controllers on demand

When looking up a DMA controller through its OF node, probe it if it hasn't already. The goal is to reduce deferred probes to a minimum, as it makes it very cumbersome to find out why a device failed to probe, and can introduce very big delays in when a critical device is probed. Signed-off-by:

[PATCH v6 0/22] On-demand device probing

with Tegra, iMX.6, Exynos, Rockchip and OMAP SoCs, and these patches were enough to eliminate all the deferred probes (except one in PandaBoard because omap_dma_system doesn't have a firmware node as of yet). Have submitted a branch [5][6][7] with these patches on top of today's linux-next

[PATCH v6 15/22] clk: Probe clk providers on demand

When looking up a clock through its OF node, probe it if it hasn't already. The goal is to reduce deferred probes to a minimum, as it makes it very cumbersome to find out why a device failed to probe, and can introduce very big delays in when a critical device is probed. Signed-off-by: Tomeu

[PATCH v6 14/22] usb: phy: Probe phy devices on demand

When looking up a phy through its OF node, probe it if it hasn't already. The goal is to reduce deferred probes to a minimum, as it makes it very cumbersome to find out why a device failed to probe, and can introduce very big delays in when a critical device is probed. Signed-off-by: Tomeu

[PATCH v6 21/22] driver core: Start processing deferred probes earlier

Some initcalls in the late level assume that some devices will have already probed without explicitly checking for that. After the recent move to defer most device probes when they are registered, pressure increased in the late initcall level. By starting the processing of the deferred queue in

[PATCH v6 20/22] driver core: Allow deferring probes until late init

Add a field to struct device that instructs the device-driver core to defer the probe of this device until the late_initcall level. By letting all built-in drivers to register before starting to probe, we can avoid any deferred probes by probing dependencies on demand. Signed-off-by: Tomeu

[PATCH v6 17/22] phy: core: Probe phy providers on demand

When looking up a phy provider through its OF node, probe it if it hasn't already. The goal is to reduce deferred probes to a minimum, as it makes it very cumbersome to find out why a device failed to probe, and can introduce very big delays in when a critical device is probed. Signed-off-by:

[PATCH v6 02/22] ARM: amba: Move reading of periphid to amba_match()

Reading the periphid when the Primecell device is registered means that the apb pclk must be available by then or the device won't be registered at all. By reading the periphid in amba_match() we can return -EPROBE_DEFER if the apb pclk isn't there yet and the device will be retried later.

Re: PCIe bus (re-)numbering

2015-09-21 9:49 GMT+02:00 Ruud : >> /sbin/setpci -s $NAME 0x1a.b=0 >> N=`find /sys/devices/pci:"$BUS"/"$NAME"/remove -name "remove"` >> echo $N >> echo -n 1 > "$N" >> sleep 1s >> done >> done >> > > Thanks for the script! > >> >>> >>>

Re: [PATCH] fs: fix data race on mnt.mnt_flags

On Mon, Sep 21, 2015 at 02:16:47PM +0200, Dmitry Vyukov wrote: > do_remount() does: > > mnt_flags |= mnt->mnt.mnt_flags & ~MNT_USER_SETTABLE_MASK; > mnt->mnt.mnt_flags = mnt_flags; > > This can easily be compiled as: > > mnt->mnt.mnt_flags &= ~MNT_USER_SETTABLE_MASK; > mnt->mnt.mnt_flags |=

[PATCH v6 16/22] pinctrl: Probe pinctrl devices on demand

When looking up a pin controller through its OF node, probe it if it hasn't already. The goal is to reduce deferred probes to a minimum, as it makes it very cumbersome to find out why a device failed to probe, and can introduce very big delays in when a critical device is probed. Signed-off-by:

[PATCH] bq2415x_charger: Fix null pointer dereference

Commit b68c3161430a (bq2415x_charger: Allow to load and use driver even if notify device is not registered yet) introduced null pointer dereference in case bq is NULL. This patch fixes it. Signed-off-by: Pali Rohár Reported-by: Dan Carpenter ---

Re: [PATCH v4] tools lib traceevent: str addresses in heterogeneous arch environments

On Mon, 21 Sep 2015 15:26:23 +0100 Kapileshwar Singh wrote: > When a trace recorded on a 32-bit device is processed with a 64-bit > binary, the higher 32-bits of the address need to ignored > > The lack of this results in the output of the 64-bit pointer > value to

[PATCH 10/14] RFC: usb/host/fotg210: Add function scan_frame_queue()

checkpatch complains about too many leading tabs because the if statement starts after 6 tabs: scan_iosoc() -> for() -> while() -> switch() -> if() -> for() -> if() There is also a goto statement going backwards in case of failure. This patch creates a new inline function named

[PATCH 02/14] RFC: usb/host/fotg210: remove KERN_WARNING from pr_info

This patch remove KERN_WARNING from a call to pr_info(). Signed-off-by: Peter Senna Tschudin --- drivers/usb/host/fotg210-hcd.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/usb/host/fotg210-hcd.c b/drivers/usb/host/fotg210-hcd.c index

[PATCH 14/14] RFC: usb/host/faraday-hcd: Import FUSBH200 parameters

This patch adds FUSBH200 parameters to faraday-hcd.h. Signed-off-by: Peter Senna Tschudin --- drivers/usb/host/faraday-hcd.h | 50 +- 1 file changed, 49 insertions(+), 1 deletion(-) diff --git a/drivers/usb/host/faraday-hcd.h

[PATCH 06/14] RFC: usb/host/fotg210: replace msleep by usleep_range

msleep under 20ms can result in sleeping up to 20ms, which may not be intended. Replace msleep(5) by usleep_range(5000, 6000). Signed-off-by: Peter Senna Tschudin --- drivers/usb/host/fotg210-hcd.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 13/14] RFC: usb/host/faraday-hcd: Move #defines outside struct

For making the code more readable and to facilitate supporting multiple hardware versions, move #defines to outside the struct declaration. This patch also renames fhcd2xx_regs to fotg210_regs as this struct is specific to fotg210. Signed-off-by: Peter Senna Tschudin ---

[PATCH 05/14] RFC: usb/host/fotg210: change kmalloc by kmalloc_array

This patch change: kmalloc(DBG_SCHED_LIMIT * sizeof(*seen), GFP_ATOMIC) by: kmalloc_array(DBG_SCHED_LIMIT, sizeof(*seen), GFP_ATOMIC) as kmalloc_array() should be used for allocating arrays. Signed-off-by: Peter Senna Tschudin --- drivers/usb/host/fotg210-hcd.c | 2 +-

Re: [PATCH v9 12/18] vfio: Register/unregister irq_bypass_producer

On 21/09/2015 10:56, Wu, Feng wrote: > Hi Paolo & Alex, > > I find that there is a build error in the following two cases: > - KVM is configured as 'M' and VFIO as 'Y' > The reason is the build of irqbypass manager is triggered in > arch/x86/kvm/Makefile, and VFIO is built before KVM, hence >

[PATCH v3 01/12] pwm: introduce default period and polarity concepts

When requested by a user, the PWM is assigned a default period and polarity extracted from the DT, the platform data or statically set by the driver. Those default values are currently stored in the period and polarity fields of the pwm_device struct, but they will be stored somewhere else once we

[PATCH v3 02/12] pwm: define a new pwm_state struct

The PWM state, represented by its period, duty_cycle and polarity, is currently directly stored in the PWM device. Declare a pwm_state structure embedding those field so that we can later use this struct to atomically update all the PWM parameters at once. Signed-off-by: Boris Brezillon

[PATCH v3 08/12] pwm: add information about polarity, duty cycle and period to debugfs

From: Heiko Stübner The pwm-states make it possible to also output the polarity, duty cycle and period information in the debugfs pwm summary-outout. This makes it easier to gather overview information about pwms without needing to walk through the sysfs attributes of every pwm.

[PATCH v3 12/12] regulator: pwm: properly initialize the ->state field

The ->state field is currently initialized to 0, thus referencing the voltage selector at index 0, which might not reflect the current voltage value. If possible, retrieve the current voltage selector from the PWM state, else return -EINVAL. Signed-off-by: Boris Brezillon

Re: [PATCH] pramdisk: new block disk driver to perform persistent storage

On 2015/9/19 0:18, Ross Zwisler wrote: On Fri, Sep 18, 2015 at 03:46:30PM +0800, Lin Yongting wrote: In embed devices, user space applications will use reserved memory (i.e. persistent memory) to store business data, the data is kept in this memory region after system rebooting or panic.

[PATCH v3 11/12] regulator: pwm: implement ->enable(), ->disable() and ->is_enabled methods

Implement the ->enable(), ->disable() and ->is_enabled methods and remove the PWM call in ->set_voltage_sel(). This is particularly important for critical regulators tagged as always-on, because not claiming the PWM (and its dependencies) might lead to unpredictable behavior (like a system hang

[PATCH v3 10/12] pwm: rockchip: add support for atomic update

Implement the ->apply() function to add support for atomic update. Signed-off-by: Boris Brezillon --- drivers/pwm/pwm-rockchip.c | 53 +- 1 file changed, 29 insertions(+), 24 deletions(-) diff --git

[PATCH v3 09/12] pwm: rockchip: add initial state retrieval

Implement the ->reset_state() function to expose initial state. Signed-off-by: Boris Brezillon --- drivers/pwm/pwm-rockchip.c | 66 ++ 1 file changed, 66 insertions(+) diff --git a/drivers/pwm/pwm-rockchip.c

[PATCH v3 06/12] pwm: add the PWM initial state retrieval infra

Add a ->reset_state() function to the pwm_ops struct to let PWM drivers initialize the PWM state attached to a PWM device. Signed-off-by: Boris Brezillon --- drivers/pwm/core.c | 3 +++ include/linux/pwm.h | 4 2 files changed, 7 insertions(+) diff

Re: [PATCH] pramdisk: new block disk driver to perform persistent storage

On 2015/9/19 0:41, Dan Williams wrote: On Fri, Sep 18, 2015 at 9:18 AM, Ross Zwisler wrote: On Fri, Sep 18, 2015 at 03:46:30PM +0800, Lin Yongting wrote: In embed devices, user space applications will use reserved memory (i.e. persistent memory) to store

[PATCH v3 05/12] pwm: declare a default PWM state

Prepare the addition of the PWM initial state retrieval by adding a default state where all the parameters retrieved from DT, platform data or statically forced by the hardware will be stored. Once done we will be able to store the initial state in the ->state field without risking to loose the

Re: [PATCH v2] mmc/sdhci-acpi: enable sdhci-acpi device to suspend/resume asynchronously

On Mon, 2015-09-21 at 14:51 +0800, Fu, Zhonghui wrote: > Now, PM core supports asynchronous suspend/resume mode for devices > during system suspend/resume, and the power state transition of one > device may be completed in separate kernel thread. PM core ensures > all power state transition timing

[PATCH v3 07/12] pwm: add the core infrastructure to allow atomic update

Add an ->apply() method to the pwm_ops struct to allow PWM drivers to implement atomic update. This method will be preferred over the ->enable(), ->disable() and ->config() methods if available. Add the pwm_get_state(), pwm_get_default_state() and pwm_apply_state() functions for PWM users to be

[PATCH v3 03/12] pwm: move the enabled/disabled info to pwm_state struct

Prepare the transition to PWM atomic update by moving the enabled/disabled state into the pwm_state struct. This way we can easily update the whole PWM state by copying the new state in the ->state field. Signed-off-by: Boris Brezillon --- drivers/pwm/core.c

[PATCH v3 04/12] backlight: pwm_bl: remove useless call to pwm_set_period

The PWM period will be set when calling pwm_config. Remove this useless call to pwm_set_period, which might mess up with the initial PWM state once we have added proper support for PWM init state retrieval. Signed-off-by: Boris Brezillon ---

[PATCH v3 00/12] pwm: add support for atomic update

Hello, This series adds support for atomic PWM update, or IOW, the capability to update all the parameters of a PWM device (enabled/disabled, period, duty and polarity) in one go. Best Regards, Boris Changes since v2: - rebased on top of 4.3-rc2 - reintroduced pwm-regulator patches Changes

[PATCH v2 5/6] virtio-gpu: add basic prime support

From: Dave Airlie This is enough to enable DRI3. Signed-off-by: Dave Airlie Signed-off-by: Gerd Hoffmann --- drivers/gpu/drm/virtio/Makefile| 2 +- drivers/gpu/drm/virtio/virtgpu_drv.c | 13 +-

[PATCH v2 6/6] virtio-gpu: mark as a render gpu

From: Dave Airlie Also add DRM_RENDER_ALLOW to the ioctls. Signed-off-by: Gerd Hoffmann --- drivers/gpu/drm/virtio/virtgpu_drv.c | 2 +- drivers/gpu/drm/virtio/virtgpu_ioctl.c | 18 +- 2 files changed, 10 insertions(+), 10 deletions(-)

[PATCH v2 2/6] virtio-gpu: add & use virtio_gpu_queue_fenced_ctrl_buffer

Add helper function to handle the submission of fenced control requests. Make sure we initialize the fence while holding the virtqueue lock, so requests can't be reordered. Signed-off-by: Gerd Hoffmann --- drivers/gpu/drm/virtio/virtgpu_fence.c | 2 +-

[PATCH v2 4/6] virtio-gpu: add 3d/virgl support

Add the bits needed for opengl rendering support: query capabilities, new virtio commands, drm ioctls. Signed-off-by: Dave Airlie Signed-off-by: Gerd Hoffmann --- drivers/gpu/drm/virtio/Makefile| 3 +- drivers/gpu/drm/virtio/virtgpu_drv.c |

[PATCH v2 3/6] virtio-gpu: wait for cursor updates finish

Signed-off-by: Gerd Hoffmann --- drivers/gpu/drm/virtio/virtgpu_display.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/gpu/drm/virtio/virtgpu_display.c b/drivers/gpu/drm/virtio/virtgpu_display.c index 4e160ef..97e5274 100644 ---

[PATCH v2 1/6] virtio-gpu: add virtio_gpu_queue_ctrl_buffer_locked

Add virtio_gpu_queue_ctrl_buffer_locked function, which does the same as virtio_gpu_queue_ctrl_buffer but does not take the virtqueue lock. The caller must hold the lock instead. Signed-off-by: Gerd Hoffmann --- drivers/gpu/drm/virtio/virtgpu_vq.c | 17 + 1

Re: [PATCH] CHROMIUM: drm: bridge/dw_hdmi: Eliminate unused cable_plugin

On Wed, Sep 16, 2015 at 01:41:38PM -0700, Douglas Anderson wrote: > There's a member in 'struct dw_hdmi' called cable_plugin. It's never > set to anything anywhere so thus is always false. There's a bit of code > checking it, but since it's always false this must be dead code. > Eliminate it. >

Re: [PATCH] iio: gyro: ssp_gyro_sensor: Use devm_iio_device_register

On 21 September 2015 09:18:39 BST, Karol Wrona wrote: >On 09/20/2015 09:18 PM, Jonathan Cameron wrote: >> On 14/09/15 17:08, Vaishali Thakkar wrote: >>> Use resourced managed function devm_iio_device_register to >>> make error path simpler. To be compatible with the change,

[RFC v2] kdbus: use LSM hooks to restrict ability to send file descriptors

The goal of this patch is to reproduce on kdbus the same behavior that is expressed by Unix Domain Sockets when it comes to restricting ability to pass opened file descriptors. Signed-off-by: Paul Osmialowski --- ipc/kdbus/message.c | 31 ++-

Re: [PATCH V3] mmc: block: Add new ioctl to send multi commands

On 16/09/15 18:54, Gwendal Grignou wrote: [snip] >> +static int mmc_blk_ioctl_multi_cmd(struct block_device *bdev, >> + struct mmc_ioc_multi_cmd __user *user) >> +{ >> + struct mmc_blk_ioc_data **idata = NULL; >> + struct mmc_ioc_cmd __user *cmds =

Potential data race in __scsi_init_queue/ata_sg_setup

Hello, We are working on a data race detector for kernel, KernelThreadSanitizer (KTSAN. I am getting the following reports (on 4.2 rc2) between __scsi_init_queue and ata_sg_setup. The reports suggest that dev->dma_parms->max_segment_size is being used before it is initialized. I would expect that

[PATCH v2] x86: Introduce Numachip2 timer mechanisms

Add 1GHz 64-bit Numachip2 clocksource timer support for accurate system-wide timekeeping, as core TSCs are unsynchronised. Additionally, add a per-core clockevent mechanism that interrupts via the platform IPI vector after a programmed period. v2: Fix whitespace and wrapping issue

[PATCH] fuse: break infinite loop in fuse_fill_write_pages()

I got a report about unkillable task eating CPU. Thge further investigation shows, that the problem is in the fuse_fill_write_pages() function. If iov's first segment has zero length, we get an infinite loop, because we never reach iov_iter_advance() call. Fix this by calling iov_iter_advance()

[PATCH v2 4/6] pinctrl: dt-binding: document berlin4ct SoC pinctrl

Add berlin4ct to existing berlin pinctrl device tree binding. Signed-off-by: Jisheng Zhang --- Documentation/devicetree/bindings/pinctrl/berlin,pinctrl.txt | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git

Re: Potential data race in __scsi_init_queue/ata_sg_setup

Here is another data race in add_disk, maybe it is related. ThreadSanitizer: data-race in sysfs_create_dir_ns Write at 0x88048374eca8 of size 8 by thread 829 on CPU 4: [] sysfs_create_dir_ns+0x7b/0xd0 fs/sysfs/dir.c:63 [< inline >] create_dir lib/kobject.c:71 []

Re: [Open-FCoE] [PATCH] fcoe:Fix incorrect use of non wrapper version of skb_buff helper function in fcoe_percpu_recieve_thread

On Sun, Sep 20, 2015 at 06:22:39PM -0400, Nicholas Krause wrote: > This fixes the incorrect use of the non wrapper version of the > function skb_dequeue in fcoe_percpu_receive_thread to use the > wrapper version as we need to protect avoid other users from > concurrently access on the sk_buff_head

[PATCH 4/5] locking/rwsem: Use acquire/release semantics

As such, weakly ordered archs can benefit from more relaxed use of barriers when locking/unlocking. Signed-off-by: Davidlohr Bueso --- include/asm-generic/rwsem.h | 14 +++--- kernel/locking/rwsem-xadd.c | 5 +++-- 2 files changed, 10 insertions(+), 9 deletions(-) diff

[PATCH 2/5] locking/mutex: Use acquire/release semantics

As such, weakly ordered archs can benefit from more relaxed use of barriers when issuing atomics. Signed-off-by: Davidlohr Bueso --- include/asm-generic/mutex-dec.h | 8 include/asm-generic/mutex-xchg.h | 10 +- kernel/locking/mutex.c | 9 +

[PATCH 0/5] locking: Use acquire/release semantics

Changes from v2: o Rename patch titles (per Linus), slight changelog rephrasing. Hi, This series continues porting users to Will's new _{acquire|release|relaxed} optimizations for weakly ordered archs -- and in practice, arm64 being the only actual user we have, thus could use a _lot_ more

Re: [PATCH 4/5] locking/rwsem: Use acquire/release semantics

On Mon, Sep 21, 2015 at 1:17 PM, Davidlohr Bueso wrote: > @@ -114,7 +114,7 @@ static inline void __downgrade_write(struct rw_semaphore > *sem) > { > long tmp; > > - tmp = atomic_long_add_return(-RWSEM_WAITING_BIAS, > + tmp =

ARM64 readahead: fault retry breaks mmap file read random detection

Description from commit 45cac65b0fcd ("readahead: fault retry breaks mmap file read random detection") .fault now can retry. The retry can break state machine of .fault. In filemap_fault, if page is miss, ra->mmap_miss is increased. In the second try, since the page is in page cache now,

[PATCH 3/5] locking/rtmutex: Use acquire/release semantics

As such, weakly ordered archs can benefit from more relaxed use of barriers when locking/unlocking. Signed-off-by: Davidlohr Bueso --- kernel/locking/rtmutex.c | 30 +- 1 file changed, 21 insertions(+), 9 deletions(-) diff --git

[PATCH 5/5] locking/mcs: Use acquire/release semantics

As such, weakly ordered archs can benefit from more relaxed use of barriers when locking/unlocking. Signed-off-by: Davidlohr Bueso --- kernel/locking/mcs_spinlock.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/kernel/locking/mcs_spinlock.h

[PATCH 1/5] asm-generic: Add _{relaxed|acquire|release}() variants for inc/dec atomics

Similar to what we have for regular add/sub calls. For now, no actual arch implements them, so everyone falls back to the default atomics... iow, nothing changes. These will be used in future primitives. Signed-off-by: Davidlohr Bueso --- include/asm-generic/atomic-long.h | 29

Re: [RFC PATCH] PM / Runtime: runtime: Add sysfs option for forcing runtime suspend

On Mon 2015-09-21 10:38:46, Alan Stern wrote: > On Mon, 21 Sep 2015, Pavel Machek wrote: > > > > > In fact, then, what you need seems to be the feature discussed by Alan > > > > and me some time ago allowing remote wakeup do be disabled for runtime > > > > PM from user space as that in

Re: [PATCH] fs-writeback: drop wb->list_lock during blk_finish_plug()

On Mon, 21 Sep 2015 11:24:29 +0200 Jan Kara wrote: > On Sat 19-09-15 08:17:14, Dave Chinner wrote: > > On Thu, Sep 17, 2015 at 11:04:03PM -0700, Linus Torvalds wrote: > > > On Thu, Sep 17, 2015 at 10:40 PM, Dave Chinner > > > wrote: > > > > PS: just hit

[PATCH] mtd: provide proper 32/64-bit compat_ioctl() support for BLKPG

After a bit of poking around wondering why my 32-bit user-space can't seem to send a proper ioctl(BLKPG) to an MTD on my 64-bit kernel (ARM64), I noticed that struct blkpg_ioctl_arg is actually pretty unsuitable for use in the ioctl() ABI, due to its use of raw pointers, and its lack of

Re: possible reason: unannotated irqs-off

On 09/21/2015 11:44 AM, Murali Karicheri wrote: Russell, On 09/18/2015 01:02 PM, Russell King - ARM Linux wrote: On Fri, Sep 18, 2015 at 12:02:15PM -0400, Murali Karicheri wrote: While chasing a fix for a deadlock in netcp driver with debug options enabled, i bumped on another warning shown

Re: [RFC v7 14/41] richacl: Create-time inheritance

2015-09-18 19:58 GMT+02:00 J. Bruce Fields : > On Sat, Sep 05, 2015 at 12:27:09PM +0200, Andreas Gruenbacher wrote: >> + if (dir_ace->e_flags & >> RICHACE_NO_PROPAGATE_INHERIT_ACE) >> + ace->e_flags &=

3.5%loan offer

3.5% WONGA.pdf Description: Adobe PDF document

Re: [PATCH 2/3] drivers:hv: Export the API to invoke a hypercall on Hyper-V

On Mon, Sep 21, 2015 at 05:36:06PM +, KY Srinivasan wrote: > > > > -Original Message- > > From: Greg KH [mailto:gre...@linuxfoundation.org] > > Sent: Monday, September 21, 2015 9:41 AM > > To: KY Srinivasan > > Cc: linux-kernel@vger.kernel.org;

Re: [rcu] kernel BUG at include/linux/pagemap.h:149!

On Mon, Sep 21, 2015 at 09:30:49PM +0200, Frederic Weisbecker wrote: > On Fri, Sep 11, 2015 at 10:19:47AM +0800, Boqun Feng wrote: > > Subject: [PATCH 01/27] rcu: Don't disable preemption for Tiny and Tree RCU > > readers > > > > Because preempt_disable() maps to barrier() for non-debug builds,

[PATCH] Re: [4.3-rc1 regression] modular 8250 doesn't load

In article <20150914211827.ga3...@kroah.com> (earth.lists.linux-kernel) you wrote: > On Mon, Sep 14, 2015 at 02:12:43PM -0700, Greg Kroah-Hartman wrote: > > On Mon, Sep 14, 2015 at 10:42:24PM +0200, Mikael Pettersson wrote: > > > Greg Kroah-Hartman writes: uart_insert_char is EXPORT_SYMBOL_GPL, >

[PATCH] netlink: Replace rhash_portid with load_acquire protected boolean

Hello, Here's an updated version of Herbert's patch which always uses load_acquire through a helper. Thanks. - 8< - The commit 1f770c0a09da855a2b51af6d19de97fb955eca85 ("netlink: Fix autobind race condition that leads to zero port ID") created some new races that can occur due to

Re: [PATCH 1/3] ASoC: codecs: Add da7219 codec driver

On Mon, Sep 21, 2015 at 03:08:03PM +, Opensource [Adam Thomson] wrote: > On September 19, 2015 18:44, Mark Brown wrote: > > This is obviously a massive reconfiguration of the device. I'm not > > seeing anything here which prevents userspace coming in and change the > > configuration while

Re: [PATCH] inotify: hide internal kernel bits from fdinfo

Acked-by: Eric Paris On Mon, 2015-09-21 at 11:45 -0700, Dave Hansen wrote: > From: Dave Hansen > > There was a report that my patch: > > inotify: actually check for invalid bits in > sys_inotify_add_watch() > > broke CRIU. > > The reason

Re: [PATCH 1/7] phy: fix of_mdio_find_bus() device refcount leak

On Mon, Sep 21, 2015 at 12:01:59PM -0700, David Miller wrote: > From: Russell King > Date: Fri, 18 Sep 2015 10:54:55 +0100 > > > Update the comment, and arrange for the only user of this function > > to drop this refcount when disposing of a reference to it. > >

Re: [v7 PATCH 1/2] iio: light: Add support for UPISEMI uS5182d als and proximity sensor

On 16/09/15 09:14, Adriana Reus wrote: > Add support for UPISEMI us5182d als and proximity sensor. > Supports raw readings. > Data sheet for this device can be found here: > http://www.upi-semi.com/temp/uS5182D-DS-P0103-temp.pdf > > Signed-off-by: Adriana Reus Applied to

Applied "regulator: core: Remove regulator_list" to the regulator tree

The patch regulator: core: Remove regulator_list has been applied to the regulator tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent

Re: [PATCH v6 08/22] regulator: core: Probe regulators on demand

On Mon, Sep 21, 2015 at 04:02:48PM +0200, Tomeu Vizoso wrote: > When looking up a regulator through its OF node, probe it if it hasn't > already. Acked-by: Mark Brown signature.asc Description: Digital signature

Re: [PATCH 2/3] mfd: tps65912: Rewrite driver adding DT support and using regmap

On 09/21/2015 02:26 PM, Mark Brown wrote: On Mon, Sep 21, 2015 at 11:42:13AM -0500, Andrew F. Davis wrote: I know this is hard to review, and so I would like to apologize in advance, but the regulator and GPIO changes depend on the new driver core, as do the i2c/spi components. I really don't

Re: [PATCH v9 12/18] vfio: Register/unregister irq_bypass_producer

Hi, On 09/21/2015 03:02 PM, Paolo Bonzini wrote: > > > On 21/09/2015 14:53, Wu, Feng wrote: >> I think the point is that we cannot trigger the build of irqbypass >> manager inside KVM or VFIO, we need trigger the build at a high >> level and it should be built before VFIO and KVM.

Re: [PATCH 2/3] mfd: tps65912: Rewrite driver adding DT support and using regmap

On Mon, Sep 21, 2015 at 02:46:50PM -0500, Andrew F. Davis wrote: > On 09/21/2015 02:26 PM, Mark Brown wrote: > >So split that interface change between the MFD and the function drivers > >out into a separate change - you've got way more than just an interface > >change in here (and you've not

Re: [PATCH] inotify: hide internal kernel bits from fdinfo

2015-09-21 21:45 GMT+03:00 Dave Hansen : > > From: Dave Hansen > > There was a report that my patch: > > inotify: actually check for invalid bits in sys_inotify_add_watch() > > broke CRIU. > > The reason is that CRIU looks up raw flags in

Re: [RFC PATCH 0/2] kvmclock: fix ABI breakage from PVCLOCK_COUNTS_FROM_ZERO.

2015-09-21 12:52-0300, Marcelo Tosatti: > On Mon, Sep 21, 2015 at 05:12:10PM +0200, Radim Krčmář wrote: >> 2015-09-20 19:57-0300, Marcelo Tosatti: >>> Is it counting from zero that breaks SLES10? >> >> Not by itself, treating MSR_KVM_SYSTEM_TIME as one-shot initializer did. >> The guest wants to

Re: [PATCH 2/3] mfd: tps65912: Rewrite driver adding DT support and using regmap

On 09/21/2015 02:54 PM, Mark Brown wrote: On Mon, Sep 21, 2015 at 02:46:50PM -0500, Andrew F. Davis wrote: On 09/21/2015 02:26 PM, Mark Brown wrote: So split that interface change between the MFD and the function drivers out into a separate change - you've got way more than just an interface

Re: [PATCH v4 0/16] Add Analogix Core Display Port Driver

Hi Thierry, Thanks for your suggest :) On 09/21/2015 05:15 PM, Thierry Reding wrote: On Mon, Sep 21, 2015 at 04:45:44PM +0800, Yakir Yang wrote: Hi Heiko, On 09/02/2015 10:15 AM, Yakir Yang wrote: Hi Heiko, 在 09/02/2015 05:47 AM, Heiko Stuebner 写道: Hi Yakir, Am Dienstag, 1. September

[PATCH v3 3/4] iio: bmc150: Split the driver into core and i2c

Signed-off-by: Markus Pargmann --- drivers/iio/accel/Kconfig | 9 +- drivers/iio/accel/Makefile | 3 +- .../accel/{bmc150-accel.c => bmc150-accel-core.c} | 85 - drivers/iio/accel/bmc150-accel-i2c.c

[PATCH 03/10] mm, page_alloc: Remove unnecessary taking of a seqlock when cpusets are disabled

There is a seqcounter that protects against spurious allocation failures when a task is changing the allowed nodes in a cpuset. There is no need to check the seqcounter until a cpuset exists. Signed-off-by: Mel Gorman Acked-by: Christoph Lameter

[PATCH v3 2/4] iio: bcm150: Remove i2c_client from private data

i2c_client struct is now only used for debugging output. We can use the device struct as well so we can remove all struct i2c_client usage. Signed-off-by: Markus Pargmann Acked-by: Jonathan Cameron --- drivers/iio/accel/bmc150-accel.c | 116

[PATCH 04/10] mm, page_alloc: Use masks and shifts when converting GFP flags to migrate types

This patch redefines which GFP bits are used for specifying mobility and the order of the migrate types. Once redefined it's possible to convert GFP flags to a migrate type with a simple mask and shift. The only downside is that readers of OOM kill messages and allocation failures may have been

[PATCH 00/10] Remove zonelist cache and high-order watermark checking v4

Changelog since V3 o Rebase to 4.3-rc1 o Consistent style for __GFP_WAIT (joonsoo) o Restored cpuset static checking behaviour (vbabka) o Fix cpusets check in allocator fastpath (vbabka) o Applied acks Changelog since V2 o

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