Re: [4.4-rc1][Regression] drm/i915: Check live status before reading edid

On 03/02/2016 04:58 PM, Joseph Salisbury wrote: > On 02/29/2016 04:33 AM, Jani Nikula wrote: >> On Wed, 24 Feb 2016, Joseph Salisbury wrote: >>> Hi Sonika, >>> >>> A kernel bug report was opened against Ubuntu [0]. After a kernel >>> bisect, it was found that

Re: [4.4-rc1][Regression] drm/i915: Check live status before reading edid

On 03/02/2016 04:58 PM, Joseph Salisbury wrote: > On 02/29/2016 04:33 AM, Jani Nikula wrote: >> On Wed, 24 Feb 2016, Joseph Salisbury wrote: >>> Hi Sonika, >>> >>> A kernel bug report was opened against Ubuntu [0]. After a kernel >>> bisect, it was found that reverting the following commit

Re: [PATCH 03/31] Add alpha-specific parity functions

On 03/26/2016 10:43 PM, zhaoxiu.zeng wrote: From: Zeng Zhaoxiu Signed-off-by: Zeng Zhaoxiu --- arch/alpha/include/asm/bitops.h | 27 +++ 1 file changed, 27 insertions(+) Acked-by: Richard Henderson

Re: [PATCH 03/31] Add alpha-specific parity functions

On 03/26/2016 10:43 PM, zhaoxiu.zeng wrote: From: Zeng Zhaoxiu Signed-off-by: Zeng Zhaoxiu --- arch/alpha/include/asm/bitops.h | 27 +++ 1 file changed, 27 insertions(+) Acked-by: Richard Henderson r~

Re: [PATCH 2/3] swiotlb: prefix dma_to_phys and phys_to_dma functions

On Fri, Mar 18, 2016 at 11:00 AM, Sinan Kaya wrote: > On 3/18/2016 8:12 AM, Robin Murphy wrote: >> Since we know for sure that swiotlb_to_phys is a no-op on arm64, it might be >> cleaner to simply not reference it at all. I suppose we could have some >> private local

Re: [PATCH 2/3] swiotlb: prefix dma_to_phys and phys_to_dma functions

On Fri, Mar 18, 2016 at 11:00 AM, Sinan Kaya wrote: > On 3/18/2016 8:12 AM, Robin Murphy wrote: >> Since we know for sure that swiotlb_to_phys is a no-op on arm64, it might be >> cleaner to simply not reference it at all. I suppose we could have some >> private local wrappers, e.g.: >> >>

Re: [RFC PATCH 4/4] drivers: change au0828, uvcvideo, snd-usb-audio to use Media Device Allocator

Em Fri, 25 Mar 2016 22:38:45 -0600 Shuah Khan escreveu: > Change au0828, uvcvideo, snd-usb-audio to use Media Device Allocator and > new Media Controller API media_device_unregister_put(). > > Signed-off-by: Shuah Khan > --- >

Re: [RFC PATCH 3/4] media: Add refcount to keep track of media device registrations

Em Fri, 25 Mar 2016 22:38:44 -0600 Shuah Khan escreveu: > Add refcount to keep track of media device registrations to avoid release > of media device when one of the drivers does unregister when media device > belongs to more than one driver. Also add a new interfaces to

Re: [RFC PATCH 4/4] drivers: change au0828, uvcvideo, snd-usb-audio to use Media Device Allocator

Em Fri, 25 Mar 2016 22:38:45 -0600 Shuah Khan escreveu: > Change au0828, uvcvideo, snd-usb-audio to use Media Device Allocator and > new Media Controller API media_device_unregister_put(). > > Signed-off-by: Shuah Khan > --- > drivers/media/usb/au0828/au0828-core.c | 7 +-- >

Re: [RFC PATCH 3/4] media: Add refcount to keep track of media device registrations

Em Fri, 25 Mar 2016 22:38:44 -0600 Shuah Khan escreveu: > Add refcount to keep track of media device registrations to avoid release > of media device when one of the drivers does unregister when media device > belongs to more than one driver. Also add a new interfaces to unregister > a media

Re: [RFC PATCH 1/4] media: Add Media Device Allocator API

Hi Shuah, I reviewed the entire patch series, but I'm adding the comments only here, as the other patches are coherent with this one. Em Fri, 25 Mar 2016 22:38:42 -0600 Shuah Khan escreveu: > Add Media Device Allocator API to manage Media Device life time problems. >

Re: [RFC PATCH 2/4] media: Add Media Device Allocator API documentation

Em Fri, 25 Mar 2016 22:38:43 -0600 Shuah Khan escreveu: > Add Media Device Allocator API documentation. Please merge this with the previous patch. > > Signed-off-by: Shuah Khan > --- > include/media/media-dev-allocator.h | 32

Re: [RFC PATCH 1/4] media: Add Media Device Allocator API

Hi Shuah, I reviewed the entire patch series, but I'm adding the comments only here, as the other patches are coherent with this one. Em Fri, 25 Mar 2016 22:38:42 -0600 Shuah Khan escreveu: > Add Media Device Allocator API to manage Media Device life time problems. > There are known problems

Re: [RFC PATCH 2/4] media: Add Media Device Allocator API documentation

Em Fri, 25 Mar 2016 22:38:43 -0600 Shuah Khan escreveu: > Add Media Device Allocator API documentation. Please merge this with the previous patch. > > Signed-off-by: Shuah Khan > --- > include/media/media-dev-allocator.h | 32 > 1 file changed, 32

Re: [PATCH] intel_menlow: set cdev after null device check to avoid null pointer dereference

On Mon, Mar 28, 2016 at 05:18:39PM +0100, Colin King wrote: > From: Colin Ian King > > intel_menlow_memory_remove sanity checks to see if device is null, however, > this check is performed after we have already passed device into a call > to acpi_driver_data. If device

Re: [PATCH] intel_menlow: set cdev after null device check to avoid null pointer dereference

On Mon, Mar 28, 2016 at 05:18:39PM +0100, Colin King wrote: > From: Colin Ian King > > intel_menlow_memory_remove sanity checks to see if device is null, however, > this check is performed after we have already passed device into a call > to acpi_driver_data. If device is null, then

[PATCH] x86/thread_info: Merge two !__ASSEMBLY__ sections

From: Borislav Petkov We have #ifndef __ASSEMBLY__ ... #endif #ifndef __ASSEMBLY__ ... #endif Merge the two. No functionality change. Signed-off-by: Borislav Petkov --- arch/x86/include/asm/thread_info.h | 6 ++ 1 file changed, 2 insertions(+),

[PATCH] x86/thread_info: Merge two !__ASSEMBLY__ sections

From: Borislav Petkov We have #ifndef __ASSEMBLY__ ... #endif #ifndef __ASSEMBLY__ ... #endif Merge the two. No functionality change. Signed-off-by: Borislav Petkov --- arch/x86/include/asm/thread_info.h | 6 ++ 1 file changed, 2 insertions(+), 4 deletions(-) diff --git

Re: [PATCH v1 0/2] genirq: support multiple IRQ notifier.

On Fri, Mar 25, 2016 at 12:32:43PM -0700, Christoph Hellwig wrote: > On Fri, Mar 25, 2016 at 08:51:51AM -0700, Weongyo Jeong wrote: > > Each irq_desc only supports one IRQ affinity notifier at current > > implementation so when we try to register another notifier, it silently > > unregister

Re: [PATCH v1 0/2] genirq: support multiple IRQ notifier.

On Fri, Mar 25, 2016 at 12:32:43PM -0700, Christoph Hellwig wrote: > On Fri, Mar 25, 2016 at 08:51:51AM -0700, Weongyo Jeong wrote: > > Each irq_desc only supports one IRQ affinity notifier at current > > implementation so when we try to register another notifier, it silently > > unregister

Re: [PATCH v6 7/7][Resend] cpufreq: schedutil: New governor based on scheduler utilization data

On 03/26/2016 06:36 PM, Rafael J. Wysocki wrote: +static int sugov_limits(struct cpufreq_policy *policy) >>> +{ >>> + struct sugov_policy *sg_policy = policy->governor_data; >>> + >>> + if (!policy->fast_switch_enabled) { >>> +

Re: [PATCH v6 7/7][Resend] cpufreq: schedutil: New governor based on scheduler utilization data

On 03/26/2016 06:36 PM, Rafael J. Wysocki wrote: +static int sugov_limits(struct cpufreq_policy *policy) >>> +{ >>> + struct sugov_policy *sg_policy = policy->governor_data; >>> + >>> + if (!policy->fast_switch_enabled) { >>> +

Re: [PATCH v5] iio: potentiometer: add driver for Microchip MCP413X/414X/415X/416X/423X/424X/425X/426X

On 28 March 2016 at 16:58, Jonathan Cameron wrote: > On 23/03/16 08:57, Slawomir Stepien wrote: >> The following functionalities are supported: >> - write, read from volatile memory >> >> Datasheet: http://ww1.microchip.com/downloads/en/DeviceDoc/22060b.pdf >> >> Signed-off-by:

Re: [PATCH v5] iio: potentiometer: add driver for Microchip MCP413X/414X/415X/416X/423X/424X/425X/426X

On 28 March 2016 at 16:58, Jonathan Cameron wrote: > On 23/03/16 08:57, Slawomir Stepien wrote: >> The following functionalities are supported: >> - write, read from volatile memory >> >> Datasheet: http://ww1.microchip.com/downloads/en/DeviceDoc/22060b.pdf >> >> Signed-off-by: Slawomir Stepien

Re: [PATCH 09/17] watchdog: qcom: add kpss-standalone to device tree binding

On Mon, Mar 28, 2016 at 12:02:47PM -0500, Matthew McClintock wrote: > On Mar 25, 2016, at 9:15 AM, Rob Herring wrote: > > > > On Wed, Mar 23, 2016 at 05:05:04PM -0500, Matthew McClintock wrote: > >> Update the compatible string to add new device tree binding > >> > >> CC:

Re: [PATCH 09/17] watchdog: qcom: add kpss-standalone to device tree binding

On Mon, Mar 28, 2016 at 12:02:47PM -0500, Matthew McClintock wrote: > On Mar 25, 2016, at 9:15 AM, Rob Herring wrote: > > > > On Wed, Mar 23, 2016 at 05:05:04PM -0500, Matthew McClintock wrote: > >> Update the compatible string to add new device tree binding > >> > >> CC:

Re: [PATCH 07/17] watchdog: qcom: add option for standalone watchdog not in timer block

On Mon, Mar 28, 2016 at 11:55:28AM -0500, Matthew McClintock wrote: > > > On Mar 25, 2016, at 11:23 AM, Guenter Roeck wrote: > > > >> -#define WDT_RST 0x38 > >> -#define WDT_EN0x40 > >> -#define WDT_BITE_TIME 0x5C > >> +enum wdt_reg { > >> +

Re: [PATCH 07/17] watchdog: qcom: add option for standalone watchdog not in timer block

On Mon, Mar 28, 2016 at 11:55:28AM -0500, Matthew McClintock wrote: > > > On Mar 25, 2016, at 11:23 AM, Guenter Roeck wrote: > > > >> -#define WDT_RST 0x38 > >> -#define WDT_EN0x40 > >> -#define WDT_BITE_TIME 0x5C > >> +enum wdt_reg { > >> + WDT_RST, > >> + WDT_EN, >

Re: [RESEND PATCH 0/3 v4] powercap, intel_rapl, implement time window checks

+Jacob On Mon, 2016-03-21 at 08:27 -0400, Prarit Bhargava wrote: > This was submitted back in December and not picked up after review. > > P. > > -8< > The Intel ASDM provides a maximum time window that can be specified > when > setting a time window in the RAPL driver.  While the ASDM

Re: [RESEND PATCH 0/3 v4] powercap, intel_rapl, implement time window checks

+Jacob On Mon, 2016-03-21 at 08:27 -0400, Prarit Bhargava wrote: > This was submitted back in December and not picked up after review. > > P. > > -8< > The Intel ASDM provides a maximum time window that can be specified > when > setting a time window in the RAPL driver.  While the ASDM

Re: [RFC PATCH 0/4] ACPI based PCI host driver with generic ECAM

On Mon, Mar 28, 2016 at 7:12 PM, Sinan Kaya wrote: > Hi, > > On 3/23/2016 6:22 AM, Gabriele Paoloni wrote: >> I had a look at your patchset and also in your git repo at the other >> patches that you ported over from Tomasz; it seems that now we miss >> a quirk mechanism to

Re: [RFC PATCH 0/4] ACPI based PCI host driver with generic ECAM

On Mon, Mar 28, 2016 at 7:12 PM, Sinan Kaya wrote: > Hi, > > On 3/23/2016 6:22 AM, Gabriele Paoloni wrote: >> I had a look at your patchset and also in your git repo at the other >> patches that you ported over from Tomasz; it seems that now we miss >> a quirk mechanism to enable controller that

Re: [PATCHv4 00/25] THP-enabled tmpfs/shmem

On Fri, Mar 25, 2016 at 05:00:50PM -0700, Hugh Dickins wrote: > On Fri, 25 Mar 2016, Kirill A. Shutemov wrote: > > On Thu, Mar 24, 2016 at 12:08:55PM -0700, Hugh Dickins wrote: > > > On Thu, 24 Mar 2016, Kirill A. Shutemov wrote: > > > > On Wed, Mar 23, 2016 at 01:09:05PM -0700, Hugh Dickins

Re: [PATCHv4 00/25] THP-enabled tmpfs/shmem

On Fri, Mar 25, 2016 at 05:00:50PM -0700, Hugh Dickins wrote: > On Fri, 25 Mar 2016, Kirill A. Shutemov wrote: > > On Thu, Mar 24, 2016 at 12:08:55PM -0700, Hugh Dickins wrote: > > > On Thu, 24 Mar 2016, Kirill A. Shutemov wrote: > > > > On Wed, Mar 23, 2016 at 01:09:05PM -0700, Hugh Dickins

[PATCH] ACPICA: Remove unnecessary "\n" from an ACPI_INFO boot message

A "\n" at the end of bellow ACPI_INFO message is causing a blank line in the kernel log: ACPI_INFO(("%u ACPI AML tables successfully acquired and loaded\n", tables_loaded)); This patch removes the "\n". Kernel log before this patch: ACPI: Core revision 20160108 ACPI: 2 ACPI

[PATCH] ACPICA: Remove unnecessary "\n" from an ACPI_INFO boot message

A "\n" at the end of bellow ACPI_INFO message is causing a blank line in the kernel log: ACPI_INFO(("%u ACPI AML tables successfully acquired and loaded\n", tables_loaded)); This patch removes the "\n". Kernel log before this patch: ACPI: Core revision 20160108 ACPI: 2 ACPI

Re: [PATCH v3] dell-rbtn: Ignore ACPI notifications if device is suspended

2016-03-28 19:33 GMT+02:00 Darren Hart : > On Thu, Mar 24, 2016 at 12:24:56PM +0100, Gabriele Mazzotta wrote: >> 2016-03-24 10:39 GMT+01:00 Pali Rohár : >> > On Monday 21 March 2016 16:13:34 Gabriele Mazzotta wrote: >> >> 2016-03-21 13:17 GMT+01:00 Pali

Re: [PATCH v3] dell-rbtn: Ignore ACPI notifications if device is suspended

2016-03-28 19:33 GMT+02:00 Darren Hart : > On Thu, Mar 24, 2016 at 12:24:56PM +0100, Gabriele Mazzotta wrote: >> 2016-03-24 10:39 GMT+01:00 Pali Rohár : >> > On Monday 21 March 2016 16:13:34 Gabriele Mazzotta wrote: >> >> 2016-03-21 13:17 GMT+01:00 Pali Rohár : >> >> > On Friday 18 March 2016

Re: [PATCH] pps: kc: fix non-tickless system config dependency

Hi Andrew, Could you take this patch, please? Thanks, Maciej On 21.03.2016 15:38, Rodolfo Giometti wrote: > On Mon, Mar 21, 2016 at 03:28:26PM +0100, Maciej S. Szmigiero wrote: >> Hi Rodolfo, >> >> On 06.03.2016 20:13, Rodolfo Giometti wrote: >>> On Sat, Mar 05, 2016 at 06:37:39PM +0100, Maciej

Re: [PATCH] pps: kc: fix non-tickless system config dependency

Hi Andrew, Could you take this patch, please? Thanks, Maciej On 21.03.2016 15:38, Rodolfo Giometti wrote: > On Mon, Mar 21, 2016 at 03:28:26PM +0100, Maciej S. Szmigiero wrote: >> Hi Rodolfo, >> >> On 06.03.2016 20:13, Rodolfo Giometti wrote: >>> On Sat, Mar 05, 2016 at 06:37:39PM +0100, Maciej

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

On Tue, Mar 22, 2016 at 02:30:51PM +0100, Michał Kępień wrote: ... > > > First of all, this patch raises a couple of checkpatch warnings. > > > > The code on the whole reads well so I would be happy with it as is. Making > > it (and the existing code) fully compliant with checkpatch results in

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

On Tue, Mar 22, 2016 at 02:30:51PM +0100, Michał Kępień wrote: ... > > > First of all, this patch raises a couple of checkpatch warnings. > > > > The code on the whole reads well so I would be happy with it as is. Making > > it (and the existing code) fully compliant with checkpatch results in

[PATCH 5/5] perf, tools, report: Add srcline_from/to branch sort keys

From: Andi Kleen Add srcline_from and srcline_to branch sort keys that allow to show the source lines of a branch. That makes it much easier to track down where particular branches happen in the program, for example to examine branch mispredictions, or to associate it with

[PATCH 5/5] perf, tools, report: Add srcline_from/to branch sort keys

From: Andi Kleen Add srcline_from and srcline_to branch sort keys that allow to show the source lines of a branch. That makes it much easier to track down where particular branches happen in the program, for example to examine branch mispredictions, or to associate it with cycle counts: % perf

[PATCH 2/5] perf, tools: Add probing for udev86

From: Andi Kleen Add autoprobing for the udev86 disassembler library. Signed-off-by: Andi Kleen --- tools/build/Makefile.feature | 6 -- tools/build/feature/Makefile | 8 ++-- tools/build/feature/test-all.c| 5 +

[PATCH 2/5] perf, tools: Add probing for udev86

From: Andi Kleen Add autoprobing for the udev86 disassembler library. Signed-off-by: Andi Kleen --- tools/build/Makefile.feature | 6 -- tools/build/feature/Makefile | 8 ++-- tools/build/feature/test-all.c| 5 + tools/build/feature/test-udis86.c | 8

[PATCH 1/5] perf, tools: Add support for skipping itrace instructions

From: Andi Kleen When using perf script to look at PT traces it is often useful to ignore the initialization code at the beginning. On larger traces which may have many millions of instructions in initialization code doing that in a pipeline can be very slow, with perf

[PATCH 4/5] perf, tools, script: Add brstackasm output for branch stacks

From: Andi Kleen Implement printing full disassembled sequences for branch stacks in perf script. This allows to directly print hot paths for individual samples, together with branch misprediction and even cycle count information. % perf record -b ... % perf script -F

[PATCH 1/5] perf, tools: Add support for skipping itrace instructions

From: Andi Kleen When using perf script to look at PT traces it is often useful to ignore the initialization code at the beginning. On larger traces which may have many millions of instructions in initialization code doing that in a pipeline can be very slow, with perf script spending a lot of

[PATCH 4/5] perf, tools, script: Add brstackasm output for branch stacks

From: Andi Kleen Implement printing full disassembled sequences for branch stacks in perf script. This allows to directly print hot paths for individual samples, together with branch misprediction and even cycle count information. % perf record -b ... % perf script -F brstackasm ...

[PATCH 3/5] perf, tools, script: Add support for printing assembler

From: Andi Kleen When dumping PT traces with perf script it is very useful to see the assembler for each sample, so that it is easily possible to follow the control flow. As using objdump is difficult and inefficient from perf script this patch uses the udis86 library to

[PATCH 3/5] perf, tools, script: Add support for printing assembler

From: Andi Kleen When dumping PT traces with perf script it is very useful to see the assembler for each sample, so that it is easily possible to follow the control flow. As using objdump is difficult and inefficient from perf script this patch uses the udis86 library to implement assembler

Re : Re: Ihre Finanzierung/Kredit/Darlehen

Guten Tag Sie benötigen Hilfe finanziell für Ihr Projekt? Kraftfahrzeug? Haus? Unternehmen? Schuld? Rechnung? auf der Suche einer ehrlichen Person, nach Wort und Ernst wir sind dort, um Sie zu dienen, um Ihnen zu stellen an der Bequemlichkeit Sie könnten mit unserer Hilfe für die Erlangung

Re : Re: Ihre Finanzierung/Kredit/Darlehen

Guten Tag Sie benötigen Hilfe finanziell für Ihr Projekt? Kraftfahrzeug? Haus? Unternehmen? Schuld? Rechnung? auf der Suche einer ehrlichen Person, nach Wort und Ernst wir sind dort, um Sie zu dienen, um Ihnen zu stellen an der Bequemlichkeit Sie könnten mit unserer Hilfe für die Erlangung

Re: [PATCH v2 1/2] x86/mm: TLB_REMOTE_SEND_IPI should count pages

The commit message should have said: Fixes: 5b74283ab251b9db55cbbe31d19ca72482103290 (and not what it currently says). Let me know whether to submit v3. Nadav On 3/26/16, 1:25 AM, "Nadav Amit" wrote: >TLB_REMOTE_SEND_IPI was recently introduced, but it counts bytes instead

Re: [PATCH v2 1/2] x86/mm: TLB_REMOTE_SEND_IPI should count pages

The commit message should have said: Fixes: 5b74283ab251b9db55cbbe31d19ca72482103290 (and not what it currently says). Let me know whether to submit v3. Nadav On 3/26/16, 1:25 AM, "Nadav Amit" wrote: >TLB_REMOTE_SEND_IPI was recently introduced, but it counts bytes instead >of pages. In

Re: [PATCH v2 1/1] iio: accel: bmc150: use common definition for regmap conf

Hi Irina, [auto build test ERROR on iio/togreg] [also build test ERROR on v4.6-rc1 next-20160327] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url:

Re: [PATCH 1/1] iio: accel: bmc150: fix endianness when reading axes

On Mon, 28 Mar 2016, Irina Tirdea wrote: > For big endian platforms, reading the axes will return > invalid values. > > The device stores each axis value in a 16 bit little > endian register. The driver uses regmap_read_bulk to get > the axis value, resulting in a 16 bit little endian value. >

Re: [PATCH v2 1/1] iio: accel: bmc150: use common definition for regmap conf

Hi Irina, [auto build test ERROR on iio/togreg] [also build test ERROR on v4.6-rc1 next-20160327] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url:

Re: [PATCH 1/1] iio: accel: bmc150: fix endianness when reading axes

On Mon, 28 Mar 2016, Irina Tirdea wrote: > For big endian platforms, reading the axes will return > invalid values. > > The device stores each axis value in a 16 bit little > endian register. The driver uses regmap_read_bulk to get > the axis value, resulting in a 16 bit little endian value. >

[PATCH] f2fs: fix stale nids in an indirect node block

In truncate_inode_blocks, we can get some stale node block addresses in the following scenario. 1. ipage = get_node_page(ino) 2. unlock_page(ipage) 3. trundate_dnode() - invalidates all the data indices - truncate node block 4. lock_page(ipage) and then failed, goto restart 5. -ENOMEM or -EIO

[PATCH] f2fs: fix stale nids in an indirect node block

In truncate_inode_blocks, we can get some stale node block addresses in the following scenario. 1. ipage = get_node_page(ino) 2. unlock_page(ipage) 3. trundate_dnode() - invalidates all the data indices - truncate node block 4. lock_page(ipage) and then failed, goto restart 5. -ENOMEM or -EIO

Re: [PATCH v3] dell-rbtn: Ignore ACPI notifications if device is suspended

On Thu, Mar 24, 2016 at 12:24:56PM +0100, Gabriele Mazzotta wrote: > 2016-03-24 10:39 GMT+01:00 Pali Rohár : > > On Monday 21 March 2016 16:13:34 Gabriele Mazzotta wrote: > >> 2016-03-21 13:17 GMT+01:00 Pali Rohár : > >> > On Friday 18 March 2016

Re: [PATCH v3] dell-rbtn: Ignore ACPI notifications if device is suspended

On Thu, Mar 24, 2016 at 12:24:56PM +0100, Gabriele Mazzotta wrote: > 2016-03-24 10:39 GMT+01:00 Pali Rohár : > > On Monday 21 March 2016 16:13:34 Gabriele Mazzotta wrote: > >> 2016-03-21 13:17 GMT+01:00 Pali Rohár : > >> > On Friday 18 March 2016 23:44:23 Gabriele Mazzotta wrote: > >> >> +#ifdef

Re: [PATCH 07/31] Add mips-specific parity functions

On 03/26/2016 11:06 PM, zhaoxiu.zeng wrote: From: Zeng Zhaoxiu There is nothing MIPS specific here. Why not put it in asm-generic or some similar place where it can be shared by all architectures? Also, are you sure __builtin_popcount() is available on all GCC

Re: [PATCH 07/31] Add mips-specific parity functions

On 03/26/2016 11:06 PM, zhaoxiu.zeng wrote: From: Zeng Zhaoxiu There is nothing MIPS specific here. Why not put it in asm-generic or some similar place where it can be shared by all architectures? Also, are you sure __builtin_popcount() is available on all GCC versions that are

Re: [PATCH] net: macb: Only call GPIO functions if there is a valid GPIO

Hello. On 03/28/2016 03:47 PM, Charles Keepax wrote: GPIOlib will print warning messages if we call GPIO functions without a valid GPIO. Change the code to avoid doing so. Signed-off-by: Charles Keepax --- drivers/net/ethernet/cadence/macb.c | 8

Re: [PATCH] net: macb: Only call GPIO functions if there is a valid GPIO

Hello. On 03/28/2016 03:47 PM, Charles Keepax wrote: GPIOlib will print warning messages if we call GPIO functions without a valid GPIO. Change the code to avoid doing so. Signed-off-by: Charles Keepax --- drivers/net/ethernet/cadence/macb.c | 8 +--- 1 file changed, 5 insertions(+),

Re: [PATCH 09/17] watchdog: qcom: add kpss-standalone to device tree binding

On Mon, Mar 28, 2016 at 12:02 PM, Matthew McClintock wrote: > On Mar 25, 2016, at 9:15 AM, Rob Herring wrote: >> >> On Wed, Mar 23, 2016 at 05:05:04PM -0500, Matthew McClintock wrote: >>> Update the compatible string to add new device tree binding >>>

Re: [PATCH 09/17] watchdog: qcom: add kpss-standalone to device tree binding

On Mon, Mar 28, 2016 at 12:02 PM, Matthew McClintock wrote: > On Mar 25, 2016, at 9:15 AM, Rob Herring wrote: >> >> On Wed, Mar 23, 2016 at 05:05:04PM -0500, Matthew McClintock wrote: >>> Update the compatible string to add new device tree binding >>> >>> CC: linux-watch...@vger.kernel.org >>>

[PATCH v2 1/1] iio: accel: bmc150: use common definition for regmap conf

bmc150_i2c_regmap_conf is defined three times (in bmc150-accel-core.c, bmc150-accel-i2c.c and and bmc150-accel-spi.c), although the definition is the same. Use one common definition for bmc150_i2c_regmap_conf in all included files. Signed-off-by: Irina Tirdea ---

[PATCH v2 1/1] iio: accel: bmc150: use common definition for regmap conf

bmc150_i2c_regmap_conf is defined three times (in bmc150-accel-core.c, bmc150-accel-i2c.c and and bmc150-accel-spi.c), although the definition is the same. Use one common definition for bmc150_i2c_regmap_conf in all included files. Signed-off-by: Irina Tirdea --- Changes from v1: - instead

4.5 shmem lockdep/out-of-bound/list corruption disaster

I hit this a few days ago. I'm not 100% what kernel it was running, but I'm pretty sure it was a post 4.5 kernel from this merge window. WARNING: CPU: 2 PID: 28919 at kernel/locking/lockdep.c:3198 __lock_acquire+0x74d/0x1c60 DEBUG_LOCKS_WARN_ON(class_idx > MAX_LOCKDEP_KEYS) CPU: 2 PID: 28919

4.5 shmem lockdep/out-of-bound/list corruption disaster

I hit this a few days ago. I'm not 100% what kernel it was running, but I'm pretty sure it was a post 4.5 kernel from this merge window. WARNING: CPU: 2 PID: 28919 at kernel/locking/lockdep.c:3198 __lock_acquire+0x74d/0x1c60 DEBUG_LOCKS_WARN_ON(class_idx > MAX_LOCKDEP_KEYS) CPU: 2 PID: 28919

Re: [LKP] [lkp] [futex] 65d8fc777f: +25.6% will-it-scale.per_process_ops

On Mon, Mar 21, 2016 at 04:42:47PM +0800, Huang, Ying wrote: > Thomas Gleixner writes: > > > On Mon, 21 Mar 2016, Huang, Ying wrote: > >> > FYI, we noticed 25.6% performance improvement due to commit > >> > > >> >65d8fc777f6d "futex: Remove requirement for lock_page() in

Re: [LKP] [lkp] [futex] 65d8fc777f: +25.6% will-it-scale.per_process_ops

On Mon, Mar 21, 2016 at 04:42:47PM +0800, Huang, Ying wrote: > Thomas Gleixner writes: > > > On Mon, 21 Mar 2016, Huang, Ying wrote: > >> > FYI, we noticed 25.6% performance improvement due to commit > >> > > >> >65d8fc777f6d "futex: Remove requirement for lock_page() in > >> >

Re: [PATCH v14 3/4] ARM64: add SBSA Generic Watchdog device node in amd-seattle-soc.dtsi

Hi Pratyush, Guenter, On 28 March 2016 at 22:11, Pratyush Anand wrote: > On 28/03/2016:06:46:20 AM, Guenter Roeck wrote: >> On 03/28/2016 06:12 AM, Fu Wei wrote: >> >Hi Wim, Guenter: >> > >> >Great thanks for reviewing and applying this patchset :-) >> >Now I can see almost

Re: [PATCH v14 3/4] ARM64: add SBSA Generic Watchdog device node in amd-seattle-soc.dtsi

Hi Pratyush, Guenter, On 28 March 2016 at 22:11, Pratyush Anand wrote: > On 28/03/2016:06:46:20 AM, Guenter Roeck wrote: >> On 03/28/2016 06:12 AM, Fu Wei wrote: >> >Hi Wim, Guenter: >> > >> >Great thanks for reviewing and applying this patchset :-) >> >Now I can see almost all the patches of

[PATCH 1/1] iio: gyro: bmg160: fix buffer read values

When reading gyroscope axes using iio buffers, the values returned are always 0. In the interrupt handler, the return value of the read operation is returned to the user instead of the value read. Return the value read to the user. This is also fixed in commit 82d8e5da1a33 ("iio: accel: bmg160:

[PATCH 1/1] iio: gyro: bmg160: fix buffer read values

When reading gyroscope axes using iio buffers, the values returned are always 0. In the interrupt handler, the return value of the read operation is returned to the user instead of the value read. Return the value read to the user. This is also fixed in commit 82d8e5da1a33 ("iio: accel: bmg160:

[PATCH 1/1] iio: gyro: bmg160: fix endianness when reading axes

For big endian platforms, reading the axes will return invalid values. The device stores each axis value in a 16 bit little endian register. The driver uses regmap_read_bulk to get the axis value, resulting in a 16 bit little endian value. This needs to be converted to cpu endianness to work on

[PATCH 1/1] iio: gyro: bmg160: fix endianness when reading axes

For big endian platforms, reading the axes will return invalid values. The device stores each axis value in a 16 bit little endian register. The driver uses regmap_read_bulk to get the axis value, resulting in a 16 bit little endian value. This needs to be converted to cpu endianness to work on

fs/ocfs2/aops.c:1881:2-7: WARNING: NULL check before freeing functions like kfree, debugfs_remove, debugfs_remove_recursive or usb_free_urb is not needed. Maybe consider reorganizing relevant code to

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: f55532a0c0b8bb6148f4e07853b876ef73bc69ca commit: 4506cfb6f8cad594ac73e0df2b2961ca10dbd25e ocfs2: record UNWRITTEN extents when populate write desc date: 3 days ago coccinelle warnings: (new ones

fs/ocfs2/aops.c:1881:2-7: WARNING: NULL check before freeing functions like kfree, debugfs_remove, debugfs_remove_recursive or usb_free_urb is not needed. Maybe consider reorganizing relevant code to

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: f55532a0c0b8bb6148f4e07853b876ef73bc69ca commit: 4506cfb6f8cad594ac73e0df2b2961ca10dbd25e ocfs2: record UNWRITTEN extents when populate write desc date: 3 days ago coccinelle warnings: (new ones

[PATCH 1/1] iio: accel: bmc150: fix endianness when reading axes

For big endian platforms, reading the axes will return invalid values. The device stores each axis value in a 16 bit little endian register. The driver uses regmap_read_bulk to get the axis value, resulting in a 16 bit little endian value. This needs to be converted to cpu endianness to work on

[PATCH 1/1] iio: accel: bmc150: fix endianness when reading axes

For big endian platforms, reading the axes will return invalid values. The device stores each axis value in a 16 bit little endian register. The driver uses regmap_read_bulk to get the axis value, resulting in a 16 bit little endian value. This needs to be converted to cpu endianness to work on

Re: [PATCH 09/17] watchdog: qcom: add kpss-standalone to device tree binding

On Mar 25, 2016, at 9:15 AM, Rob Herring wrote: > > On Wed, Mar 23, 2016 at 05:05:04PM -0500, Matthew McClintock wrote: >> Update the compatible string to add new device tree binding >> >> CC: linux-watch...@vger.kernel.org >> Signed-off-by: Matthew McClintock

Re: [PATCH 09/17] watchdog: qcom: add kpss-standalone to device tree binding

On Mar 25, 2016, at 9:15 AM, Rob Herring wrote: > > On Wed, Mar 23, 2016 at 05:05:04PM -0500, Matthew McClintock wrote: >> Update the compatible string to add new device tree binding >> >> CC: linux-watch...@vger.kernel.org >> Signed-off-by: Matthew McClintock >> --- >>

Re: [PATCH RESEND v2 11/18] fs: Ensure the mounter of a filesystem is privileged towards its inodes

On Fri, Mar 04, 2016 at 04:43:06PM -0600, Eric W. Biederman wrote: > In general this is only an issue if uids and gids on the filesystem > do not map into the user namespace. > > Therefore the general fix is to limit the logic of checking for > capabilities in s_user_ns if we are dealing with

Re: [PATCH RESEND v2 11/18] fs: Ensure the mounter of a filesystem is privileged towards its inodes

On Fri, Mar 04, 2016 at 04:43:06PM -0600, Eric W. Biederman wrote: > In general this is only an issue if uids and gids on the filesystem > do not map into the user namespace. > > Therefore the general fix is to limit the logic of checking for > capabilities in s_user_ns if we are dealing with

Re: [PATCH] HID: wacom: fix Bamboo ONE oops

On Fri, Mar 25, 2016 at 7:26 AM, Benjamin Tissoires wrote: > > Looks like recent changes in the Wacom driver made the Bamboo ONE crashes. > The tablet behaves as if it was a regular Bamboo device with pen, touch > and pad, but there is no physical pad connected to

Re: [PATCH] HID: wacom: fix Bamboo ONE oops

On Fri, Mar 25, 2016 at 7:26 AM, Benjamin Tissoires wrote: > > Looks like recent changes in the Wacom driver made the Bamboo ONE crashes. > The tablet behaves as if it was a regular Bamboo device with pen, touch > and pad, but there is no physical pad connected to it. > The weird part is that the

Re: [PATCH 07/17] watchdog: qcom: add option for standalone watchdog not in timer block

> On Mar 25, 2016, at 11:23 AM, Guenter Roeck wrote: > >> -#define WDT_RST 0x38 >> -#define WDT_EN 0x40 >> -#define WDT_BITE_TIME 0x5C >> +enum wdt_reg { >> +WDT_RST, >> +WDT_EN, >> +WDT_BITE_TIME, >> +}; >> + >> +static const u32

Re: [PATCH 07/17] watchdog: qcom: add option for standalone watchdog not in timer block

> On Mar 25, 2016, at 11:23 AM, Guenter Roeck wrote: > >> -#define WDT_RST 0x38 >> -#define WDT_EN 0x40 >> -#define WDT_BITE_TIME 0x5C >> +enum wdt_reg { >> +WDT_RST, >> +WDT_EN, >> +WDT_BITE_TIME, >> +}; >> + >> +static const u32

[PATCH V2 0/3] Tracepoints for deadline scheduler

Deadline tasks behave differently of other tasks because deadline task's also depend on their period, deadline and runtime. Hence, the well known sched:sched_wakeup and sched:sched_switch tracepoints are not always enough to precisely explain the behavior of a deadline task with respect to the

[PATCH V2 0/3] Tracepoints for deadline scheduler

Deadline tasks behave differently of other tasks because deadline task's also depend on their period, deadline and runtime. Hence, the well known sched:sched_wakeup and sched:sched_switch tracepoints are not always enough to precisely explain the behavior of a deadline task with respect to the

[PATCH V2 3/3] sched/deadline: Tracepoints for deadline scheduler

Deadline tasks behave differently of other tasks because deadline task's also depend on their period, deadline and runtime. Hence, the well known sched:sched_wakeup and sched:sched_switch tracepoints are not always enough to precisely explain the behavior of a deadline task with respect to the

[PATCH V2 2/3] sched: Move deadline container_of() helper functions into sched.h

Move dl_task_of(), dl_rq_of_se() and rq_of_dl_rq() helper functions from kernel/sched/deadline.c to kernel/sched/sched.h, so they can be used on other scheduler files. Signed-off-by: Daniel Bristot de Oliveira diff --git a/kernel/sched/deadline.c b/kernel/sched/deadline.c

[PATCH V2 1/3] tracing: Add __print_ns_to_secs() and __print_ns_without_secs() helpers

From: "Steven Rostedt (Red Hat)" To have nanosecond output displayed in a more human readable format, its nicer to convert it to a seconds format (XXX.Y). The problem is that to do so, the numbers must be divided by NSEC_PER_SEC, and moded too. But as these numbers

[PATCH V2 3/3] sched/deadline: Tracepoints for deadline scheduler

Deadline tasks behave differently of other tasks because deadline task's also depend on their period, deadline and runtime. Hence, the well known sched:sched_wakeup and sched:sched_switch tracepoints are not always enough to precisely explain the behavior of a deadline task with respect to the

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