Re: [PATCH v2 06/14] USB: ch341: reinitialize chip on reconfiguration

Grigori Goronzy wrote: > Changing the LCR register after initialization does not seem to be > reliable on all chips (particularly not on CH341A). Restructure > initialization and configuration to always reinit the chip on > configuration changes instead and pass the LCR register value directly >

Re: [PATCH 5/5] max44000: Initial triggered buffer support

On 07/04/16 17:21, Crestez Dan Leonard wrote: > Signed-off-by: Crestez Dan Leonard > --- > drivers/iio/light/max44000.c | 63 > > 1 file changed, 63 insertions(+) > > diff --git a/drivers/iio/light/max44000.c

Re: [PATCH 3/9] iio: adc: qcom-spmi-vadc: use regmap to retrieve struct device

On 06/04/16 06:17, Alison Schofield wrote: > Driver includes struct regmap and struct device in its global data. > Remove the struct device and use regmap API to retrieve device info. > > Patch created using Coccinelle plus manual edits. > > Signed-off-by: Alison Schofield

Re: [PATCH 13/17] staging: lustre: lloop: Fix build failure on ppc64

> This patch was shown not to work. I just haven't removed it from opensuse yet. Its been running in our production tree as well for some time. Guess that change is a noop. In any case we have been discussing redoing the lloop driver anyways. Just need to find the cycles. > -- > Jeff Mahoney

Re: [PATCH 1/1] iio: adc: Add driver for the TI INA3221 Triple Current/Voltage Monitor

On 04/10/2016 04:57 AM, Jonathan Cameron wrote: On 08/04/16 19:19, Andrew F. Davis wrote: The INA3221 is a three-channel, high-side current and bus voltage monitor with an I2C and SMBUS compatible interface. Signed-off-by: Andrew F. Davis Hi Andrew, My immediate thought on this

Re: [PATCH v3 13/19] drm: sun4i: Add DT bindings documentation

Hi Rob, On Tue, Mar 29, 2016 at 01:50:35PM -0500, Rob Herring wrote: > On Tue, Mar 29, 2016 at 12:33:14PM +0200, Maxime Ripard wrote: > > Hi Rob, > > > > On Fri, Mar 25, 2016 at 09:11:18AM -0500, Rob Herring wrote: > > > On Wed, Mar 23, 2016 at 05:38:36PM +0100, Maxime Ripard wrote: > > > > The

Re: [PATCH v3 01/19] clk: composite: Add unregister function

Hi Stephen, Mike, On Wed, Mar 23, 2016 at 05:38:24PM +0100, Maxime Ripard wrote: > The composite clock didn't have any unregistration function, which forced > us to use clk_unregister directly on it. > > While it was already not great from an API point of view, it also meant > that we were

Re: [PATCH] Bluetooth: Deinline large functions

On Sun, 2016-04-10 at 18:24 +0200, Denys Vlasenko wrote: > Fastest existing Bluetooth standard's top speed is 2.4 MB/s. > It is way off from being CPU limited, no need to squeeze > last few cycles by excessive inlining. > > This patch delinlines the following functions: > >

[PATCH 11/17] staging: lustre: osc: osc_extent_wait() shouldn't be interruptible

From: Jinshan Xiong Otherwise it will hit the assertion at cl_lock.c: cl_lock.c:1967:discard_cb()) ASSERTION( (!(page->cp_type == CPT_CACHEABLE) || (!PageWriteback(cl_page_vmpage(env, page ) failed: This is because in osc_lock_flush() we have to make sure the

[PATCH 14/17] staging: lustre: lov: return minimal FIEMAP for released files

From: Bruno Faccini Since st_blocks = NULL is returned for released files, FIEMAP should at least return a minimal mapping to make users aware that file contains data but it is not immediately available. This will make coreutils and tools such tar happy and have them

[PATCH 07/17] staging: lustre: llite: error setting max_cache_mb at mount time

From: Jinshan Xiong The root cause is that when max_cache_mb conf parameter is applied, the client isn't connected to the OST yet so that sbi->ll_dt_exp is NULL. However, it's not necessary to shrink the cache memory in this case so success should be returned.

Re: [PATCH] platform:x86 decouple telemetry driver from the optional IPC resources

On Thu, Mar 31, 2016 at 10:28 PM, Aubrey Li wrote: > Currently the optional IPC resources prevent telemetry driver from > probing if these resources are not in ACPI table. This patch decouples > telemetry driver from these optional resources, so that telemetry driver >

Re: [PATCH 3/5] max44000: Support controlling LED current output

On 07/04/16 17:21, Crestez Dan Leonard wrote: > This is exposed as an output channel with "led" as an extend_name. > > Other sensors also have support for controlling an external LED. It's > not clear that simply exposing an undecorated output channel is the > correct approach. Agreed that this

[PATCH 01/17] staging: lustre: osc: fix race issues thanks to oap_lock

From: Sebastien Buisson Fix 'data race condition' defects found by Coverity version 6.5.0: Data race condition (MISSING_LOCK) Accessing variable without holding lock. Elsewhere, this variable is accessed with lock held. This patch is dedicated to code fragments involving

[PATCH 05/17] staging: lustre: llite: variable rename in namei.c

From: Andrew Perepechko With the patch 6648 a fee variables were renamed. We do these renames in broken out patch to the fix obvious. Signed-off-by: Andrew Perepechko Reviewed-by: Alexander Boyko

[PATCH 06/17] staging: lustre: llite: speedup in unlink/rmdir

From: Andrew Perepechko Assume dchild argument is fully initialized in ->unlink and ->rmdir callbacks, so additional lookup for ELC is not needed. Signed-off-by: Andrew Perepechko Reviewed-by: Alexander Boyko

[PATCH 08/17] staging: lustre: obd: MDT mount fails on MDS w/o MGS on it

From: Bobi Jam If we specify multiple --mgsnode for a MDT, when we start MDS upon it while MGS is no the other node, the MGC import connection will always select the local nid (which is one of the candidate mgsnode) since it think its the closest connection. This patch

Re: [PATCH] platform:x86 decouple telemetry driver from the optional IPC resources

On 2016/4/10 21:17, Andy Shevchenko wrote: > On Thu, Mar 31, 2016 at 10:28 PM, Aubrey Li wrote: >> Currently the optional IPC resources prevent telemetry driver from >> probing if these resources are not in ACPI table. This patch decouples >> telemetry driver from these

Re: [PATCH] nvme/host: Add missing blk_integrity tag_size + flags assignments

Looks fine, Reviewed-by: Sagi Grimberg

Re: [PATCH v2] staging: iio: ad7606: use iio_device_{claim|release}_direct_mode()

On 06/04/16 22:06, Lars-Peter Clausen wrote: > On 04/06/2016 06:11 AM, Alison Schofield wrote: >> Replace the code that guarantees the device stays in direct mode with >> iio_device_{claim|release}_direct_mode() which does same. >> >> Signed-off-by: Alison Schofield > >

Re: [PATCH 1/3] iio: core: Add devm_ APIs for iio_channel_{get,release}

On 06/04/16 15:58, Laxman Dewangan wrote: > Hi Daniel, > > > On Wednesday 06 April 2016 07:19 PM, Daniel Baluta wrote: >> On Wed, Apr 6, 2016 at 1:31 PM, Laxman Dewangan wrote: >>> Some of kernel driver uses the IIO framework to get the sensor >>> value via ADC or IIO HW

Re: [PATCH v2 27/30] iio: use parity32 in adxrs450

On 06/04/16 11:16, zengzhao...@163.com wrote: > From: Zhaoxiu Zeng > > Signed-off-by: Zhaoxiu Zeng Applied to the togreg branch of iio.git as you seem to have addressed Lars' comments. Thanks, Jonathan > --- > drivers/iio/gyro/adxrs450.c | 4

Re: [PATCH 08/27] staging: lustre: avoid to use bio->bi_vcnt directly

> The lloop driver should be removed entirely - use the loop driver > instead. I talked with Andreas last week at our annual Lustre users group meeting about this. The reason I was told for existance is that some users were using files on a Lustre file system with the loop back device. The

Re: [PATCH 1/2] char: PC rtc: replace blacklist with whitelist

Arnd, On 02/03/2016 at 11:22:04 +0100, Geert Uytterhoeven wrote : > On Wed, Mar 2, 2016 at 10:48 AM, Arnd Bergmann wrote: > > Every new architecture has to add itself to the growing list of those > > that do not support the legacy PC RTC driver. > > > > This replaces the long list

Re: [PATCH 13/17] staging: lustre: lloop: Fix build failure on ppc64

> > > This patch was shown not to work. I just haven't removed it from opensuse > > > yet. > > > > Its been running in our production tree as well for some time. Guess that > > change is a noop. In any case we have been discussing redoing the lloop > > driver anyways. Just need to find the

Re: [patch] power: ipaq-micro-battery: freeing the wrong variable

Hi, On Fri, Mar 18, 2016 at 12:00:51PM +0300, Dan Carpenter wrote: > We accidentally free "micro_ac_power" which is an error pointer and it > leads to an oops. We intended to free "micro_batt_power". Thanks, queued. -- Sebastian signature.asc Description: PGP signature

Re: [PATCH] sbs-battery: fix power status when battery charging near dry

Hi, On Wed, Apr 06, 2016 at 10:32:25AM +0800, YH Huang wrote: > POWER_SUPPLY_STATUS_NOT_CHARGING is used for AC connected, but > battery not charging (e.g. because battery temperature is out > of acceptable range). > > When battery is charging near dry and BATTERY_FULL_DISCHARGED is set, > it is

[PATCH 10/17] staging: lustre: llite: Truncate to restore file

From: Jinshan Xiong Truncate up is safe so it won't trigger restore. Copy optimization for truncate down - only copy the part under truncate length. If a file is truncated to zero usually it'll be followed by write so I choose to restore the file and set correct stripe

[PATCH 00/17] staging : lustre : rest of missing patches from 2.5.0 release

This is the last collection of missing fixes present in the Lustre 2.5.0 release. Once these are merged the upstream client will be equal to the pre-2.6 lustre version since the major of clio cleanups from that time frame have already landed. Andrew Perepechko (3): staging: lustre: llite:

[PATCH 15/17] staging: lustre: lov: Don't wait for active target with OBD_STATFS_NODELAY

From: Andriy Skulysh Patch for LU-631 which was landed before the upstream merge broke OBD_STATFS_NODELAY behaviour. It adds unnecessary delay while running df command with inactive OSTs. We shouldn't try to recover connection to OST in this case. Signed-off-by:

[PATCH 12/17] staging: lustre: lprocfs: implement log2 using bitops

From: Andrew Perepechko This patch implements log2 using fls. Signed-off-by: Andrew Perepechko Reviewed-by: Alexander Boyko Reviewed-by: alexander_zarochent...@xyratex.com Reviewed-by: Vitaly Fertman

[PATCH 16/17] staging: lustre: hsm: permission checks for HSM ioctl operations

From: John L. Hammond In the LL_IOC_HSM_CT_START case of ll_dir_ioctl() require CAP_SYS_ADMIN, since the local handler for this ioctl may modify the global KUC table. Signed-off-by: John L. Hammond Intel-bug-id:

[PATCH 13/17] staging: lustre: lloop: Fix build failure on ppc64

From: Jeff Mahoney On ppc64 with 64k pages, we get a build failure in lloop: drivers/staging/lustre/lustre/llite/lloop.c:527:2: note: in expansion of macro 'CLASSERT' CLASSERT(PAGE_CACHE_SIZE < (1 << (sizeof(unsigned short) * 8))); There's no need to change the queue's logical

Re: [PATCH 2/5] max44000: Initial support for proximity reading

On 07/04/16 17:21, Crestez Dan Leonard wrote: > The proximity sensor relies on sending pulses to an external IR led and > it is disabled by default on powerup. The driver will enable it with a > default power setting. > > Signed-off-by: Crestez Dan Leonard One trivial

[PATCH 17/17] staging: lustre: hsm: don't use real suppgid

From: John L. Hammond In the MDC HSM handlers that do not pack a real suppgid, use -1 rather than 0 for the suppgid in mdt_body. Signed-off-by: John L. Hammond Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-3866 Reviewed-on:

Re: [PATCH 4/5] max44000: Expose ambient sensor scaling

On 07/04/16 17:21, Crestez Dan Leonard wrote: > This patch exposes ALSTIM as illuminance_integration_time and ALSPGA as > illuminance_scale. > > Changing ALSTIM also changes the number of bits available in the data > register. Hmm.. This usually means we have oversampling going on rather than

[PATCH trivial] include : linux: hugetlb: Clean up code

From: Chen Gang Macro HUGETLBFS_SB is clearer enough, so one statement is clearer than 3 lines statements. Remove redundant return statements for non-return functions, which can save lines, at least. Signed-off-by: Chen Gang ---

[PATCH] include/linux/hugetlb.h: Use bool instead of int for hugepage_migration_supported()

From: Chen Gang It is used as a pure bool function within kernel source wide. Signed-off-by: Chen Gang --- include/linux/hugetlb.h | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/include/linux/hugetlb.h

Re: [regression] cross core scheduling frequency drop bisected to 0c313cb20732

On Sun, 2016-04-10 at 11:35 +0200, Mike Galbraith wrote: > On Sun, 2016-04-10 at 05:44 +0200, Rafael J. Wysocki wrote: > > On Sat, Apr 9, 2016 at 6:39 PM, Mike Galbraith < > > umgwanakikb...@gmail.com> wrote: > > > > > > Hm, setting gov=performance, and taking the average of 3 30 second > > >

Re: [PATCH v2 27/30] iio: use parity32 in adxrs450

On 10/04/16 15:41, Lars-Peter Clausen wrote: > On 04/10/2016 04:37 PM, Jonathan Cameron wrote: >> On 06/04/16 11:16, zengzhao...@163.com wrote: >>> From: Zhaoxiu Zeng >>> >>> Signed-off-by: Zhaoxiu Zeng >> Applied to the togreg branch of iio.git as

Re: [PATCH v2 27/30] iio: use parity32 in adxrs450

On 10/04/16 16:13, Jonathan Cameron wrote: > On 10/04/16 15:41, Lars-Peter Clausen wrote: >> On 04/10/2016 04:37 PM, Jonathan Cameron wrote: >>> On 06/04/16 11:16, zengzhao...@163.com wrote: From: Zhaoxiu Zeng Signed-off-by: Zhaoxiu Zeng

Re: [PATCH v5 0/2] power: reset: support for Atmel alternative Shutdown Controller

Hi, On Wed, Mar 16, 2016 at 02:19:48PM +0100, Nicolas Ferre wrote: > This is a series to add driver for a new Atmel Shutdown Controller. This new > IP > is extensible and some features will be added later (see the TODO section). > Its extensible nature led to write a new binding so that wake-up

Re: [patch] power/max8925: freeing wrong variable

Hi, On Fri, Mar 18, 2016 at 08:40:16AM +0300, Dan Carpenter wrote: > We were freeing "info->battery" instead of "info->usb", which leads to > an OOps and a resource leak. > > The labels were wonky, "out_battery" did release the battery but out_usb > did not release usb. I was introducing a call

Re: [PATCH] Bluetooth: Deinline large functions

On Sun, Apr 10, 2016 at 6:59 PM, Joe Perches wrote: > On Sun, 2016-04-10 at 18:24 +0200, Denys Vlasenko wrote: >> Fastest existing Bluetooth standard's top speed is 2.4 MB/s. >> It is way off from being CPU limited, no need to squeeze >> last few cycles by excessive inlining. >>

Re: [PATCH 13/17] staging: lustre: lloop: Fix build failure on ppc64

This patch was shown not to work. I just haven't removed it from opensuse yet. -Jeff -- Jeff Mahoney (apologies for the top post -- from my mobile) > On Apr 10, 2016, at 9:13 AM, James Simmons wrote: > > From: Jeff Mahoney > > On ppc64 with 64k pages,

Re: [PATCH 1/9] iio: adc: exynos_adc: use regmap to retrieve struct device

On 07/04/16 06:33, Marek Szyprowski wrote: > Hello, > > On 2016-04-06 22:33, Alison Schofield wrote: >> On Wed, Apr 06, 2016 at 09:03:00AM +0200, Marek Szyprowski wrote: >>> Hello, >>> >>> On 2016-04-06 07:15, Alison Schofield wrote: Driver includes struct regmap and struct device in its

Re: [PATCH 2/9] iio: adc: qcom-spmi-iadc: use regmap to retrieve struct device

On 06/04/16 06:16, Alison Schofield wrote: > Driver includes struct regmap and struct device in its global data. > Remove the struct device and use regmap API to retrieve device info. > > Patch created using Coccinelle plus manual edits. > > Signed-off-by: Alison Schofield

Re: [PATCH 5/9] iio: accel: mma7455: use regmap to retrieve struct device

On 06/04/16 08:35, Joachim Eastwood wrote: > Hi Alison, > > On 6 April 2016 at 07:18, Alison Schofield wrote: >> Driver includes struct regmap and struct device in its global data. >> Remove the struct device and use regmap API to retrieve device info. >> >> Patch created

Re: [RFC PATCH 0/3] restartable sequences v2: fast user-space percpu critical sections

- On Apr 8, 2016, at 5:25 PM, Linus Torvalds torva...@linux-foundation.org wrote: > On Fri, Apr 8, 2016 at 10:46 AM, Mathieu Desnoyers > wrote: >> >> By the way, the debugger can always decide to single-step through the >> first iteration of the rseq, and

Re: [PATCH 1/3] iio: core: Add devm_ APIs for iio_channel_{get,release}

On 06/04/16 11:31, Laxman Dewangan wrote: > Some of kernel driver uses the IIO framework to get the sensor > value via ADC or IIO HW driver. The client driver get iio channel > by iio_channel_get() and release it by calling iio_channel_release(). > > Add resource managed version (devm_*) of these

Re: [PATCH] iio: ak8975: fix maybe-uninitialized warning

On 05/04/16 14:03, Richard Leitner wrote: > If i2c_device_id *id is NULL and acpi_match_device returns NULL too, > then chipset may be unitialized when accessing _def_array[chipset] in > ak8975_probe. Therefore initialize chipset to AK_MAX_TYPE, which will > return an error when not changed. > >

Re: [PATCH] powerpc: introduce {cmp}xchg for u8 and u16

On 2016年04月08日 15:47, Peter Zijlstra wrote: > On Fri, Apr 08, 2016 at 02:41:46PM +0800, Pan Xinhui wrote: >> From: pan xinhui >> >> Implement xchg{u8,u16}{local,relaxed}, and >> cmpxchg{u8,u16}{,local,acquire,relaxed}. >> >> Atomic operation on 8-bit and 16-bit

Re: [PATCH v2 1/2] ti-adc081c: Add support for adc101c* and adc121c*

On 04/04/16 19:21, Crestez Dan Leonard wrote: > These chips has an almost identical interface but a deal with a > different number of value bits. Datasheet links for comparison: > > * http://www.ti.com/lit/ds/symlink/adc081c021.pdf > * http://www.ti.com/lit/ds/symlink/adc101c021.pdf > *

Re: [PATCH v3] iio: imu: Add initial support for Bosch BMI160

On 06/04/16 15:58, Daniel Baluta wrote: > BMI160 is an Inertial Measurement Unit (IMU) which provides acceleration > and angular rate measurement. It also offers a secondary I2C interface > for connecting a magnetometer sensor (usually BMM160). > > Current driver offers support for accelerometer

Re: [PATCH 08/27] staging: lustre: avoid to use bio->bi_vcnt directly

On Sun, Apr 10, 2016 at 03:37:42PM +0100, James Simmons wrote: > > > The lloop driver should be removed entirely - use the loop driver > > instead. > > I talked with Andreas last week at our annual Lustre users group meeting > about this. The reason I was told for existance is that some users

Re: [PATCH] nvme/host: Add missing blk_integrity tag_size + flags assignments

Does NVMe really force ATO=1? Sorry, didn't have much time to spend with that part of the spec.

Re: [PATCH v2 27/30] iio: use parity32 in adxrs450

On 04/10/2016 04:37 PM, Jonathan Cameron wrote: > On 06/04/16 11:16, zengzhao...@163.com wrote: >> From: Zhaoxiu Zeng >> >> Signed-off-by: Zhaoxiu Zeng > Applied to the togreg branch of iio.git as you seem to have addressed > Lars' comments. The

Re: [PATCH 08/27] staging: lustre: avoid to use bio->bi_vcnt directly

> On Sun, Apr 10, 2016 at 03:37:42PM +0100, James Simmons wrote: > > > > > The lloop driver should be removed entirely - use the loop driver > > > instead. > > > > I talked with Andreas last week at our annual Lustre users group meeting > > about this. The reason I was told for existance is

[PATCH] Bluetooth: Deinline large functions

Fastest existing Bluetooth standard's top speed is 2.4 MB/s. It is way off from being CPU limited, no need to squeeze last few cycles by excessive inlining. This patch delinlines the following functions: hci_conn_hash_lookup_handle: 345 bytes, 39 calls hci_conn_hash_lookup_ba: 372 bytes, 36

[PATCH 04/17] staging: lustre: ldlm: refine LU-2665 patch for POSIX compliance

From: Bruno Faccini Follow-on to patch introduced to fix LU-2665 ticket (Gerrit Change at http://review.whamcloud.com/6415 with Change-Id: I8faa331712abeadee46eabe111ee1c23a05840d5). Original patch introduced regressions against POSIX test suite (fcntl.18/fcntl.35 tests

Re: [PATCH] staging: iio: ad7606: use iio_device_{claim|release}_direct_mode()

On 06/04/16 19:06, Lars-Peter Clausen wrote: > On 04/03/2016 11:09 AM, Jonathan Cameron wrote: >> On 01/04/16 17:53, Alison Schofield wrote: >>> Two instances are moved to the new claim/release API: >>> >>> In the first instance, the driver was using mlock followed by >>> iio_buffer_enabled().

Re: [PATCH v6 08/24] iio: imu: inv_mpu6050: convert to use an explicit i2c mux core

On 03/04/16 12:51, Peter Rosin wrote: > On 2016-04-03 12:51, Jonathan Cameron wrote: >> On 03/04/16 09:52, Peter Rosin wrote: >>> From: Peter Rosin >>> >>> Allocate an explicit i2c mux core to handle parent and child adapters >>> etc. Update the select/deselect ops to be in terms

Re: [PATCH v2 2/2] ti-adc081c: Initial triggered buffer support

On 04/04/16 19:21, Crestez Dan Leonard wrote: > Using this requires software triggers like CONFIG_IIO_HRTIMER_TRIGGER. > > The device can be configured to do internal periodic sampling but does not > offer some sort of interrupt on data ready. Interrupts can only trigger when > values get out of

[RFC] proc: meminfo: Replace kB with KiB in output

Hi! I was helping somebody write some documentation about meminfo and I started explaining that memory values are mostly multiples of 1024 and that binary prefixes are preferred. The output of /proc/meminfo is hardcoded to be in 'kB' which should mean 1000 bytes (one kilobytes). But judging by

[PATCH] proc: meminfo: Replace kB with KiB in output

Current values are based on multiples of 1024 (powers of 2) which means that the values in meminfo are not kilobytes (1000 bytes) but kibibytes (1024 bytes). The correct prefix for that would be 'Ki' so the output should be 'KiB'. Signed-off-by: Alexandru Juncu ---

Re: [PATCH 13/17] staging: lustre: lloop: Fix build failure on ppc64

On Sun, Apr 10, 2016 at 03:04:51PM +0100, James Simmons wrote: > > > This patch was shown not to work. I just haven't removed it from opensuse > > yet. > > Its been running in our production tree as well for some time. Guess that > change is a noop. In any case we have been discussing redoing

Re: [regression] cross core scheduling frequency drop bisected to 0c313cb20732

On Sat, 2016-04-09 at 14:31 +0200, Rafael J. Wysocki wrote: > On Sat, Apr 9, 2016 at 1:07 PM, Peter Zijlstra > wrote: > > On Fri, Apr 08, 2016 at 10:59:59PM +0200, Rafael J. Wysocki wrote: > > > On Friday, April 08, 2016 08:50:54 AM Mike Galbraith wrote: > > > > On Fri,

Commit 'sched/cpuacct: Split usage accounting into user_usage and sys_usage' causing crashes

Hi, your commit 'sched/cpuacct: Split usage accounting into user_usage and sys_usage' in -next causes crashes with several of my qemu tests (mac99, q3beige). Reverting the patch fixes the problem. Details and complete logs are available at http://kerneltests.org/builders/qemu-ppc-next

Schönen Tag

Schönen Tag Dies ist die Santander Consumer Finance, wir Darlehen Zinssatz von 2% für beide Unternehmen Darlehen und persönliche Darlehen bieten für Ihr Projekt und die individuellen Bedürfnisse Füllen Sie das Formular aus, wenn interessiert Vollständiger Name: Geschlecht: Land:

[PULL REQUEST] i2c for 4.6

Linus, some bugfixes from I2C: * fix a uevent triggered boot problem by removing a useless debug print * fix sysfs-attributes of the new i2c-demux-pinctrl driver to follow standard kernel behaviour * fix a potential division-by-zero error (needed two takes) Please pull. Wolfram The

Re: [PATCH 2/2] tty: Remove stale parameter comment

On 04/10/2016, 05:36 AM, Peter Hurley wrote: > noctty was removed as a parameter by commit 216513411937586 It is actually 11e1d4aa4da. > ("tty: Consolidate noctty check in tty_open()"). > > Signed-off-by: Peter Hurley > --- > drivers/tty/tty_io.c | 1 - > 1 file

Re: [PATCH v2] iio: max5487: Add support for Maxim digital potentiometers

Hi Cristina, On 9 April 2016 at 10:24, Cristina Moraru wrote: > Add implementation for Maxim MAX5487, MAX5488, MAX5489 > digital potentiometers. > > Datasheet: > http://datasheets.maximintegrated.com/en/ds/MAX5487-MAX5489.pdf > > Signed-off-by: Cristina Moraru

Re: sched: tweak select_idle_sibling to look for idle threads

On Sun, 2016-04-10 at 08:35 -0400, Chris Mason wrote: > What are you testing with? If it's two sockets or less I may be able to > find one to reproduce with. i4790 desktop box. -Mike

Re: [PATCH 1/5] max44000: Initial commit

On 07/04/16 20:48, Peter Meerwald-Stadler wrote: > >> This just adds support for reporting illuminance with default settings. >> >> All default registers are written on probe because the device otherwise >> lacks a reset function. > > comments below Mostly fine, but a few corners need cleaning

Re: [PATCH v2] iio: max5487: Add support for Maxim digital potentiometers

On 10 April 2016 at 14:47, Joachim Eastwood wrote: > Hi Cristina, > > On 9 April 2016 at 10:24, Cristina Moraru wrote: >> Add implementation for Maxim MAX5487, MAX5488, MAX5489 >> digital potentiometers. >> >> Datasheet: >>

Re: [PATCH 1/2] ARM: exynos_defconfig: Enable CPUFreq governors as modules

On Fri, Apr 08, 2016 at 03:02:09PM -0400, Javier Martinez Canillas wrote: > Currently only the ondemand and performance CPUFreq policy governors are > enabled in the Exynos defconfig. But the other governors are also useful > for some cases, enable them to allow users change the default if needed.

[GIT PULL] MMC fixes for v.4.6 rc3

Hi Linus, Here are a couple of mmc fixes intended for v4.6 rc3 (or rc4 as I guess it's late for rc3). It's based on v4.6 rc1. Details are as usual found in the signed tag. Please pull this in! Kind regards Ulf Hansson The following changes since commit f55532a0c0b8bb6148f4e07853b876ef73bc69ca:

Re: [PATCH v2] iio: potentiometer: add driver for Maxim Integrated DS1803

On 09/04/16 12:12, Slawomir Stepien wrote: > On Apr 08, 2016 23:27, Slawomir Stepien wrote: >> +static int ds1803_read_raw(struct iio_dev *indio_dev, >> +struct iio_chan_spec const *chan, >> +int *val, int *val2, long mask) >> +{ >> +struct

Re: AP firmware for TI wl1251 wifi chip (wl1251-fw-ap.bin)

Hi! > > > wl1251 does not support AP mode, so there is no firmware for it in > > > the tree. > > > > > > Regards, > > > Yaniv > > > > Hi Yaniv! I read on some TI whitepaper, that wl1251 hardware supports > > some Soft-AP mode. So I expect that either special FW is needed for it > > or somehow

Re: sched: tweak select_idle_sibling to look for idle threads

On Sun, Apr 10, 2016 at 12:04:21PM +0200, Mike Galbraith wrote: > On Sat, 2016-04-09 at 15:05 -0400, Chris Mason wrote: > > > This does preserve the existing logic to prefer idle cores over idle > > CPU threads, and includes some tests to try and avoid the idle scan when > > we're > > actually

Re: [PATCH] sched/deadline/rtmutex: Fix a PI crash for deadline tasks

On 2016/04/09 at 21:29, Peter Zijlstra wrote: > On Sat, Apr 09, 2016 at 11:25:39AM +0800, Xunlei Pang wrote: > >>> In any case, I just realized we do not in fact provide this guarantee >>> (of pointing to a blocked task) that needs a bit more work. >> Current patch calls rt_mutex_adjust_prio()

Re: [PATCH] fujitsu-laptop: Support radio LED

Hi Darren Thanks for the ping. On Sat, Apr 09, 2016 at 07:30:20PM -0700, Darren Hart wrote: > On Thu, Mar 24, 2016 at 10:05:14PM +1030, Jonathan Woithe wrote: > > This is a quick reply with preliminary information. I'll follow up in the > > next few days with further details. > > > > On Tue,

Re: [PATCH v2] iio: potentiometer: add driver for Maxim Integrated DS1803

On 08/04/16 22:27, Slawomir Stepien wrote: > The following functions are supported: > - write, read potentiometer value > - potentiometer scale > > Datasheet: https://datasheets.maximintegrated.com/en/ds/DS1803.pdf > > Signed-off-by: Slawomir Stepien Looks good to me, but as

[PATCH] ath9k: remove duplicate assignment of variable ah

From: Colin Ian King ah is written twice with the same value, remove one of the redundant assignments to ah. Signed-off-by: Colin Ian King --- drivers/net/wireless/ath/ath9k/init.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

Re: [PATCH v3] iio: potentiometer: add driver for Maxim Integrated DS1803

On 10/04/16 12:23, Slawomir Stepien wrote: > The following functions are supported: > - write, read potentiometer value > - potentiometer scale > > Datasheet: https://datasheets.maximintegrated.com/en/ds/DS1803.pdf > > Signed-off-by: Slawomir Stepien Applied to the togreg

Re: [PATCH 2/2] ARM: multi_v7_defconfig: Enable CPUFreq governors as modules

On Fri, Apr 08, 2016 at 03:02:10PM -0400, Javier Martinez Canillas wrote: > Currently only the ondemand and performance CPUFreq policy governors are > enabled in multi_v7 defconfig. But the other governors are also useful > for some cases, enable them to allow users change the default if needed. >

Re: [regression] cross core scheduling frequency drop bisected to 0c313cb20732

On Sun, 2016-04-10 at 05:44 +0200, Rafael J. Wysocki wrote: > On Sat, Apr 9, 2016 at 6:39 PM, Mike Galbraith < > umgwanakikb...@gmail.com> wrote: > > > > Hm, setting gov=performance, and taking the average of 3 30 second > > interval PkgWatt samples as pipe-test runs.. > > > > 714KHz/28.03Ws =

Re: [PATCH] staging: wilc1000: rework comments in wilc_sdio.c

Hi Mohammed, On Sun, Apr 10, 2016 at 5:11 AM, wrote: > From: Mohammed Billoo > > Remove unnecessary comments (highlighting sections of functions), make > multiline comments into single line comments, and ensure that multiline > comments

RE: [regression] cross core scheduling frequency drop bisected to 0c313cb20732

On 2106.04.09 20:45 Rafael J. Wysocki wrote: >On Sat, Apr 9, 2016 at 6:39 PM, Mike Galbraith wrote: >> >> Hm, setting gov=performance, and taking the average of 3 30 second >> interval PkgWatt samples as pipe-test runs.. >> >> 714KHz/28.03Ws = 25.46 >> 877KHz/30.28Ws = 28.96 >> >> ..for pipe-test,

[PATCHv2] wlcore: spi: add wl18xx support

Add support for using with both wl12xx and wl18xx. - all wilink family needs special init command for entering wspi mode. extra clock cycles should be sent after the spi init command while the cs pin is high. - switch to controling the cs pin from the spi driver for achieveing the above. -

Re: [PATCH 1/2] mfd: max77693: Allow building as a module

On Fri, Apr 08, 2016 at 08:17:21AM +0100, Lee Jones wrote: > > Yes, this can be taken as is. Only second patch (changing defconfig) > > depends on this. I can take the second patch through samsung tree but > > that would require a tag/branch with this... which looks like an > > overkill. So maybe

Re: [PATCH 2/2] asus-laptop: remove unused variable

On Sat, Apr 09, 2016 at 08:21:21PM -0700, Darren Hart wrote: > On Thu, Apr 07, 2016 at 11:20:01PM +0300, Giedrius Statkevičius wrote: > > `out' was assigned value but it was never used so remove it > > > > Signed-off-by: Giedrius Statkevičius > > --- > >

[PATCH kernel.org] change 3.12 EOL

From: Jiri Slaby Since SLE12-SP1 is based upon 3.12 and its EOL is in 2017, move the EOL of 3.12 to 2017 too. Signed-off-by: Jiri Slaby --- content/releases.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/releases.rst

Re: sched: tweak select_idle_sibling to look for idle threads

On Sat, 2016-04-09 at 15:05 -0400, Chris Mason wrote: > This does preserve the existing logic to prefer idle cores over idle > CPU threads, and includes some tests to try and avoid the idle scan when we're > actually better off sharing a non-idle CPU with someone else. My box says the "oh

[PATCH] thunderbolt: Fix double free of drom buffer

If tb_drom_read fails sw->drom is freed but not set to NULL. sw->drom is then freed again in the error path of sw_switch_alloc. The bug can be triggered by unplugging a thunderbolt device shortly after it is detected by the thunderbolt driver. Signed-off-by: Andreas Noever

[PATCH v3] iio: potentiometer: add driver for Maxim Integrated DS1803

The following functions are supported: - write, read potentiometer value - potentiometer scale Datasheet: https://datasheets.maximintegrated.com/en/ds/DS1803.pdf Signed-off-by: Slawomir Stepien --- Changes since v2: - Use array of u8 as a result type for i2c_master_recv() call

Re: [PATCH v2] iio: max5487: Add support for Maxim digital potentiometers

On 09/04/16 09:24, Cristina Moraru wrote: > Add implementation for Maxim MAX5487, MAX5488, MAX5489 > digital potentiometers. > > Datasheet: > http://datasheets.maximintegrated.com/en/ds/MAX5487-MAX5489.pdf > > Signed-off-by: Cristina Moraru > CC: Daniel Baluta

Re: [PATCH 1/1] iio: adc: Add driver for the TI INA3221 Triple Current/Voltage Monitor

On 08/04/16 19:19, Andrew F. Davis wrote: > The INA3221 is a three-channel, high-side current and bus voltage monitor > with an I2C and SMBUS compatible interface. > > Signed-off-by: Andrew F. Davis Hi Andrew, My immediate thought on this one is whether it would be better off in

[PATCH 02/17] staging: lustre: clio: incorrect assertions in 'enable-invariants'

From: Niu Yawei Fixed several incorrect assumptions in 'enable-invariants'. Signed-off-by: Niu Yawei Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-3521 Reviewed-on: http://review.whamcloud.com/6832 Reviewed-by: Bobi Jam

[PATCH 09/17] staging: lustre: ptlrpc: return a meaningful status from ptlrpcd_init()

From: Swapnil Pimpale This patch has the following: 1) Fix for the return value from ptlrpcd_init(). It will now return a correct status instead of returning zero always. 2) ptlrpcd_addref() should not increment ptlrpcd_users on error. 3) Added code in a mdc_setup() and

  1   2   3   4   5   6   7   8   9   10   >