[PATCH v2] dell-rbtn: constify rfkill_ops structures

Add const to rfkill_ops structures that are only passed as an argument to the functions rfkill_alloc or samsung_new_rfkill. These arguments are of type const, so such structures can be annotated with const. Signed-off-by: Bhumika Goyal --- Changes since v1: * Split the

[PATCH v2] dell-rbtn: constify rfkill_ops structures

Add const to rfkill_ops structures that are only passed as an argument to the functions rfkill_alloc or samsung_new_rfkill. These arguments are of type const, so such structures can be annotated with const. Signed-off-by: Bhumika Goyal --- Changes since v1: * Split the changes to one patch per

Re: [PATCH 2/3] target: Add TARGET_SCF_LOOKUP_LUN_FROM_TAG support for ABORT_TASK

On Mon, 2017-06-05 at 15:57 +, Bart Van Assche wrote: > On Sat, 2017-06-03 at 22:10 +, Nicholas A. Bellinger wrote: > > +static bool target_lookup_lun_from_tag(struct se_session *se_sess, u64 tag, > > + u64 *unpacked_lun) > > +{ > > + struct se_cmd

Re: [PATCH 2/3] target: Add TARGET_SCF_LOOKUP_LUN_FROM_TAG support for ABORT_TASK

On Mon, 2017-06-05 at 15:57 +, Bart Van Assche wrote: > On Sat, 2017-06-03 at 22:10 +, Nicholas A. Bellinger wrote: > > +static bool target_lookup_lun_from_tag(struct se_session *se_sess, u64 tag, > > + u64 *unpacked_lun) > > +{ > > + struct se_cmd

[git pull] drm fixes for 4.12-rc5

Hi Linus, Bit more spread out fixes this time, fixes for 7 drivers + a couple of core fixes. i915 and vmwgfx are the main ones. The vmwgfx ones fix a bunch of regressions in their atomic rework, and a few fixes destined for stable. i915 has some 4.12 regressions and older things that need to be

[git pull] drm fixes for 4.12-rc5

Hi Linus, Bit more spread out fixes this time, fixes for 7 drivers + a couple of core fixes. i915 and vmwgfx are the main ones. The vmwgfx ones fix a bunch of regressions in their atomic rework, and a few fixes destined for stable. i915 has some 4.12 regressions and older things that need to be

Re: [PATCHv3] Bluetooth: hci_ll: Add compatible values for more WL chips

Hi Sebastian, > Add compatible values for WiLink chips from 128x and 180x series. > Also the DT binding already contained compatible values for the 127x > series, but the driver did not. This brings the list on par with > the list from wlcore (the wifi driver). > > Signed-off-by: Sebastian

Re: [PATCHv3] Bluetooth: hci_ll: Add compatible values for more WL chips

Hi Sebastian, > Add compatible values for WiLink chips from 128x and 180x series. > Also the DT binding already contained compatible values for the 127x > series, but the driver did not. This brings the list on par with > the list from wlcore (the wifi driver). > > Signed-off-by: Sebastian

Re: [PATCH linux-next v3 1/1] spi: imx: dynamic burst length adjust for PIO mode

On Thu, Jun 08, 2017 at 10:09:07PM -0700, Jiada Wang wrote: > On 06/01/2017 10:38 PM, Sascha Hauer wrote: > > On Thu, Jun 01, 2017 at 04:58:47AM -0700, Jiada Wang wrote: > > > Hi Sascha > > > > > > On 05/29/2017 02:50 AM, Sascha Hauer wrote: > > > > Hi, > > > > > > > > On Thu, May 25, 2017 at

Re: [PATCH linux-next v3 1/1] spi: imx: dynamic burst length adjust for PIO mode

On Thu, Jun 08, 2017 at 10:09:07PM -0700, Jiada Wang wrote: > On 06/01/2017 10:38 PM, Sascha Hauer wrote: > > On Thu, Jun 01, 2017 at 04:58:47AM -0700, Jiada Wang wrote: > > > Hi Sascha > > > > > > On 05/29/2017 02:50 AM, Sascha Hauer wrote: > > > > Hi, > > > > > > > > On Thu, May 25, 2017 at

Re: [PATCH 11/16] powerpc: vio_cmo: use dev_groups and not dev_attrs for bus_type

On Fri, Jun 09, 2017 at 08:53:22AM +1000, Michael Ellerman wrote: > Greg Kroah-Hartman writes: > > > On Thu, Jun 08, 2017 at 11:12:10PM +1000, Michael Ellerman wrote: > >> Greg Kroah-Hartman writes: > >> > >> > The dev_attrs field has

Re: [PATCH 11/16] powerpc: vio_cmo: use dev_groups and not dev_attrs for bus_type

On Fri, Jun 09, 2017 at 08:53:22AM +1000, Michael Ellerman wrote: > Greg Kroah-Hartman writes: > > > On Thu, Jun 08, 2017 at 11:12:10PM +1000, Michael Ellerman wrote: > >> Greg Kroah-Hartman writes: > >> > >> > The dev_attrs field has long been "depreciated" and is finally being > >> >

linux-next: build failure after merge of the uuid tree

Hi Christoph, After merging the uuid tree, today's linux-next build (x86_64 allmodconfig) failed like this: /home/sfr/next/next/drivers/thermal/int340x_thermal/int3400_thermal.c: In function 'int3400_thermal_get_uuids':

linux-next: build failure after merge of the uuid tree

Hi Christoph, After merging the uuid tree, today's linux-next build (x86_64 allmodconfig) failed like this: /home/sfr/next/next/drivers/thermal/int340x_thermal/int3400_thermal.c: In function 'int3400_thermal_get_uuids':

Re: [PATCH] staging: wlan-ng: cfg80211.c: fixed a line over 80 characters long

On Thu, Jun 08, 2017 at 06:38:30PM -0700, Elias Carter wrote: > From: edcarter > > Fixed a coding style issue where a line was longer than 80 characters. > > Signed-off-by: Elias Carter Your from and signed-off-by names have to match :(

Re: [PATCH] staging: wlan-ng: cfg80211.c: fixed a line over 80 characters long

On Thu, Jun 08, 2017 at 06:38:30PM -0700, Elias Carter wrote: > From: edcarter > > Fixed a coding style issue where a line was longer than 80 characters. > > Signed-off-by: Elias Carter Your from and signed-off-by names have to match :(

Re: [PATCH 0/3] target: Add TARGET_SCF_LOOKUP_LUN_FROM_TAG support

Hi Himanshu & Quinn, On Wed, 2017-06-07 at 05:02 +, Madhani, Himanshu wrote: > > On Jun 3, 2017, at 3:10 PM, Nicholas A. Bellinger > > wrote: > > > > From: Nicholas Bellinger > > > > Hi Himanshu + Quinn, > > > > Here is a small series to

Re: [PATCH 0/3] target: Add TARGET_SCF_LOOKUP_LUN_FROM_TAG support

Hi Himanshu & Quinn, On Wed, 2017-06-07 at 05:02 +, Madhani, Himanshu wrote: > > On Jun 3, 2017, at 3:10 PM, Nicholas A. Bellinger > > wrote: > > > > From: Nicholas Bellinger > > > > Hi Himanshu + Quinn, > > > > Here is a small series to introduce proper percpu se_lun->lun_ref > >

Re: [PATCH 4/7] zram: use class_groups instead of class_attrs

On (06/08/17 10:12), Greg Kroah-Hartman wrote: > The class_attrs pointer is long depreciated, and is about to be finally > removed, so move to use the class_groups pointer instead. > > Cc: Minchan Kim > Cc: Nitin Gupta > Cc: Sergey Senozhatsky

Re: [PATCH 4/7] zram: use class_groups instead of class_attrs

On (06/08/17 10:12), Greg Kroah-Hartman wrote: > The class_attrs pointer is long depreciated, and is about to be finally > removed, so move to use the class_groups pointer instead. > > Cc: Minchan Kim > Cc: Nitin Gupta > Cc: Sergey Senozhatsky > Signed-off-by: Greg Kroah-Hartman FWIW, looks

[lkp-robot] [x86/mm] d52d163f42: WARNING:at_arch/x86/mm/tlb.c:#switch_mm_irqs_off

FYI, we noticed the following commit: commit: d52d163f428136feb592f7546cb2333cfad775bf ("x86/mm: Rework lazy TLB mode and TLB freshness tracking") https://git.kernel.org/cgit/linux/kernel/git/luto/linux.git x86/pcid in testcase: trinity with following parameters: runtime: 300s

[lkp-robot] [x86/mm] d52d163f42: WARNING:at_arch/x86/mm/tlb.c:#switch_mm_irqs_off

FYI, we noticed the following commit: commit: d52d163f428136feb592f7546cb2333cfad775bf ("x86/mm: Rework lazy TLB mode and TLB freshness tracking") https://git.kernel.org/cgit/linux/kernel/git/luto/linux.git x86/pcid in testcase: trinity with following parameters: runtime: 300s

[lkp-robot] [drm] e1f8a89c4f: pft.faults_per_sec_per_cpu -77.9% regression

Greeting, FYI, we noticed a -77.9% regression of pft.faults_per_sec_per_cpu due to commit: commit: e1f8a89c4f33f5b32cfb047f07fdf6d38cda854a ("drm: introduce sync objects (v4)") git://people.freedesktop.org/~airlied/linux.git drm-syncobj-sem in testcase: pft on test machine:

[lkp-robot] [drm] e1f8a89c4f: pft.faults_per_sec_per_cpu -77.9% regression

Greeting, FYI, we noticed a -77.9% regression of pft.faults_per_sec_per_cpu due to commit: commit: e1f8a89c4f33f5b32cfb047f07fdf6d38cda854a ("drm: introduce sync objects (v4)") git://people.freedesktop.org/~airlied/linux.git drm-syncobj-sem in testcase: pft on test machine:

Re: [PATCH RFC] KVM: async_pf: fix async_pf exception injection

2017-06-08 19:52 GMT+08:00 Paolo Bonzini : > > 3) add an async_page_fault member to vcpu->arch.exception Do you think we should also add an async_page_fault field to x86_exception, then pass down to kvm_inject_page_fault() through x86_exception? Maybe we should modify

Re: [PATCH RFC] KVM: async_pf: fix async_pf exception injection

2017-06-08 19:52 GMT+08:00 Paolo Bonzini : > > 3) add an async_page_fault member to vcpu->arch.exception Do you think we should also add an async_page_fault field to x86_exception, then pass down to kvm_inject_page_fault() through x86_exception? Maybe we should modify

Re: [PATCH] iscsi-target: Fix delayed logout processing greater than SECONDS_FOR_LOGOUT_COMP

Reviews pretty please..? On Sat, 2017-06-03 at 21:32 +, Nicholas A. Bellinger wrote: > From: Nicholas Bellinger > > This patch fixes a BUG() in iscsit_close_session() that could be > triggered when iscsit_logout_post_handler() execution from within > tx thread context

Re: [PATCH] iscsi-target: Fix delayed logout processing greater than SECONDS_FOR_LOGOUT_COMP

Reviews pretty please..? On Sat, 2017-06-03 at 21:32 +, Nicholas A. Bellinger wrote: > From: Nicholas Bellinger > > This patch fixes a BUG() in iscsit_close_session() that could be > triggered when iscsit_logout_post_handler() execution from within > tx thread context was not run for more

Re: [PATCH] target: Fix kref->refcount underflow in transport_cmd_finish_abort

(Adding Quinn CC') Reviews please..? On Sat, 2017-06-03 at 21:09 +, Nicholas A. Bellinger wrote: > From: Nicholas Bellinger > > This patch fixes a se_cmd->cmd_kref underflow during CMD_T_ABORTED > when a fabric driver drops it's second reference from below the >

Re: [PATCH] target: Fix kref->refcount underflow in transport_cmd_finish_abort

(Adding Quinn CC') Reviews please..? On Sat, 2017-06-03 at 21:09 +, Nicholas A. Bellinger wrote: > From: Nicholas Bellinger > > This patch fixes a se_cmd->cmd_kref underflow during CMD_T_ABORTED > when a fabric driver drops it's second reference from below the > target_core_tmr.c based

Re: [PATCH 3/3] libnvdimm: New ACPI 6.2 DSM functions

On Thu, Jun 8, 2017 at 1:02 AM, Johannes Thumshirn wrote: > On 06/07/2017 07:04 PM, Jerry Hoemann wrote: >> @@ -179,6 +217,10 @@ static inline const char *nvdimm_bus_cmd_name(unsigned >> cmd) >> [ND_CMD_ARS_START] = "ars_start", >>

Re: [PATCH 3/3] libnvdimm: New ACPI 6.2 DSM functions

On Thu, Jun 8, 2017 at 1:02 AM, Johannes Thumshirn wrote: > On 06/07/2017 07:04 PM, Jerry Hoemann wrote: >> @@ -179,6 +217,10 @@ static inline const char *nvdimm_bus_cmd_name(unsigned >> cmd) >> [ND_CMD_ARS_START] = "ars_start", >> [ND_CMD_ARS_STATUS] = "ars_status",

[PATCH] Drivers: unisys: visorhba - style fix

Fixed style of permissions to octal. Found using checkpatch Signed-off-by: Derek Robson --- drivers/staging/unisys/visorhba/visorhba_main.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/unisys/visorhba/visorhba_main.c

[PATCH] Drivers: unisys: visorhba - style fix

Fixed style of permissions to octal. Found using checkpatch Signed-off-by: Derek Robson --- drivers/staging/unisys/visorhba/visorhba_main.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/unisys/visorhba/visorhba_main.c

[PATCH 2/9] libnvdimm, label: add v1.2 interleave-set-cookie algorithm

The interleave-set-cookie algorithm is extended to incorporate all the same components that are used to generate an nvdimm unique-id. For backwards compatibility we still maintain the old v1.1 definition. Signed-off-by: Dan Williams --- drivers/acpi/nfit/core.c

[PATCH 2/9] libnvdimm, label: add v1.2 interleave-set-cookie algorithm

The interleave-set-cookie algorithm is extended to incorporate all the same components that are used to generate an nvdimm unique-id. For backwards compatibility we still maintain the old v1.1 definition. Signed-off-by: Dan Williams --- drivers/acpi/nfit/core.c| 53

[PATCH 4/9] libnvdimm, label: populate the type_guid property for v1.2 namespaces

The type_guid refers to the "Address Range Type GUID" for the region backing a namespace as defined the ACPI NFIT (NVDIMM Firmware Interface Table). This 'type' identifier specifies an access mechanism for the given namespace. This capability replaces the confusing usage of the

[PATCH 4/9] libnvdimm, label: populate the type_guid property for v1.2 namespaces

The type_guid refers to the "Address Range Type GUID" for the region backing a namespace as defined the ACPI NFIT (NVDIMM Firmware Interface Table). This 'type' identifier specifies an access mechanism for the given namespace. This capability replaces the confusing usage of the

[PATCH 7/9] libnvdimm, label: add v1.2 label checksum support

The v1.2 namespace label specification adds a fletcher checksum to each label instance. Add generation and validation support for the new field. Signed-off-by: Dan Williams --- drivers/nvdimm/label.c | 39 +++ 1 file changed, 35

[PATCH 7/9] libnvdimm, label: add v1.2 label checksum support

The v1.2 namespace label specification adds a fletcher checksum to each label instance. Add generation and validation support for the new field. Signed-off-by: Dan Williams --- drivers/nvdimm/label.c | 39 +++ 1 file changed, 35 insertions(+), 4

[PATCH 9/9] libnvdimm, label: switch to using v1.2 labels by default

The rules for which version of the label specification are in effect at any given point in time are as follows: 1/ If a DIMM has an existing / valid index block then the version specified is used regardless if it is a previous version. 2/ By default when the kernel is initializing new index

[PATCH 8/9] libnvdimm, label: add address abstraction identifiers

Starting with v1.2 labels, 'address abstractions' can be hinted via an address abstraction id that implies an info-block format. The standard address abstraction in the specification is the v2 format of the Block-Translation-Table (BTT). Support for that is saved for a later patch, for now we add

[PATCH 9/9] libnvdimm, label: switch to using v1.2 labels by default

The rules for which version of the label specification are in effect at any given point in time are as follows: 1/ If a DIMM has an existing / valid index block then the version specified is used regardless if it is a previous version. 2/ By default when the kernel is initializing new index

[PATCH 8/9] libnvdimm, label: add address abstraction identifiers

Starting with v1.2 labels, 'address abstractions' can be hinted via an address abstraction id that implies an info-block format. The standard address abstraction in the specification is the v2 format of the Block-Translation-Table (BTT). Support for that is saved for a later patch, for now we add

[PATCH 0/9] libnvdimm, label: namespace specification v1.2 support

The recently released UEFI 2.7 Specification [1], includes an updated version (v1.2) of the NVDIMM Namespace Label Specification that was previously published on pmem.io [2] (v1.1). In the process of moving to a UEFI standard definition the v1.2 updates adds several features for improved cross-OS

[PATCH 1/9] libnvdimm, label: add v1.2 nvdimm label definitions

In support of improved interoperability between operating systems and pre-boot environments the Intel proposed NVDIMM Namespace Specification [1], has been adopted and modified to the the UEFI 2.7 NVDIMM Label Protocol [2]. Update the definitions of the namespace label data structures so that the

[PATCH 6/9] libnvdimm, label: update 'nlabel' and 'position' handling for local namespaces

The v1.2 namespace label specification requires 'nlabel' and 'position' to be valid for the first ("lowest dpa") label in the set. It also requires all non-first labels to set those fields to 0xff. Linux does not much care if these values are correct, because we can just trust the count of labels

[PATCH 0/9] libnvdimm, label: namespace specification v1.2 support

The recently released UEFI 2.7 Specification [1], includes an updated version (v1.2) of the NVDIMM Namespace Label Specification that was previously published on pmem.io [2] (v1.1). In the process of moving to a UEFI standard definition the v1.2 updates adds several features for improved cross-OS

[PATCH 1/9] libnvdimm, label: add v1.2 nvdimm label definitions

In support of improved interoperability between operating systems and pre-boot environments the Intel proposed NVDIMM Namespace Specification [1], has been adopted and modified to the the UEFI 2.7 NVDIMM Label Protocol [2]. Update the definitions of the namespace label data structures so that the

[PATCH 6/9] libnvdimm, label: update 'nlabel' and 'position' handling for local namespaces

The v1.2 namespace label specification requires 'nlabel' and 'position' to be valid for the first ("lowest dpa") label in the set. It also requires all non-first labels to set those fields to 0xff. Linux does not much care if these values are correct, because we can just trust the count of labels

[PATCH 3/9] libnvdimm, label: honor the lba size specified in v1.2 labels

Previously we only honored the lba size for blk-aperture mode namespaces. For pmem namespaces the lba size was just assumed to be 512. With the new v1.2 label definition and compatibility with other operating environments, the ->lbasize property is now respected for pmem namespaces. Cc: Ross

[PATCH 5/9] libnvdimm, label: populate 'isetcookie' for blk-aperture namespaces

Starting with the v1.2 definition of namespace labels, the isetcookie field is populated and validated for blk-aperture namespaces. This adds some safety against inadvertent copying of namespace labels from one DIMM-device to another. Signed-off-by: Dan Williams ---

[PATCH 3/9] libnvdimm, label: honor the lba size specified in v1.2 labels

Previously we only honored the lba size for blk-aperture mode namespaces. For pmem namespaces the lba size was just assumed to be 512. With the new v1.2 label definition and compatibility with other operating environments, the ->lbasize property is now respected for pmem namespaces. Cc: Ross

[PATCH 5/9] libnvdimm, label: populate 'isetcookie' for blk-aperture namespaces

Starting with the v1.2 definition of namespace labels, the isetcookie field is populated and validated for blk-aperture namespaces. This adds some safety against inadvertent copying of namespace labels from one DIMM-device to another. Signed-off-by: Dan Williams --- drivers/acpi/nfit/core.c

Re: [PATCH v10 1/6] i2c: designware: Cleaning and comment style fixes.

On 2017-06-08 19:36, Luis Oliveira wrote: > complicated to review. The work here won't bring any additional work to > backported fixes because is just style and reordering. I challenge that. If there is an old bug that existed before this patch that is fixed in the future after this patch has

Re: [PATCH v10 1/6] i2c: designware: Cleaning and comment style fixes.

On 2017-06-08 19:36, Luis Oliveira wrote: > complicated to review. The work here won't bring any additional work to > backported fixes because is just style and reordering. I challenge that. If there is an old bug that existed before this patch that is fixed in the future after this patch has

Re: [PATCH linux-next v3 1/1] spi: imx: dynamic burst length adjust for PIO mode

On 06/01/2017 10:38 PM, Sascha Hauer wrote: On Thu, Jun 01, 2017 at 04:58:47AM -0700, Jiada Wang wrote: Hi Sascha On 05/29/2017 02:50 AM, Sascha Hauer wrote: Hi, On Thu, May 25, 2017 at 10:02:42PM -0700, jiada_w...@mentor.com wrote: From: Jiada Wang previously burst

Re: [PATCH linux-next v3 1/1] spi: imx: dynamic burst length adjust for PIO mode

On 06/01/2017 10:38 PM, Sascha Hauer wrote: On Thu, Jun 01, 2017 at 04:58:47AM -0700, Jiada Wang wrote: Hi Sascha On 05/29/2017 02:50 AM, Sascha Hauer wrote: Hi, On Thu, May 25, 2017 at 10:02:42PM -0700, jiada_w...@mentor.com wrote: From: Jiada Wang previously burst length (BURST_LENGTH)

Re: [PATCH v1 00/25] lib, rtc: Print rtc_time via %pt[dt][rv]

On Thu, 2017-06-08 at 18:02 +0300, Andy Shevchenko wrote: > On Thu, Jun 8, 2017 at 5:52 PM, Joe Perches wrote: > > On Thu, 2017-06-08 at 16:47 +0300, Andy Shevchenko wrote: > > > Recently I have noticed too many users of struct rtc_time that printing > > > its content field by

Re: [PATCH v1 00/25] lib, rtc: Print rtc_time via %pt[dt][rv]

On Thu, 2017-06-08 at 18:02 +0300, Andy Shevchenko wrote: > On Thu, Jun 8, 2017 at 5:52 PM, Joe Perches wrote: > > On Thu, 2017-06-08 at 16:47 +0300, Andy Shevchenko wrote: > > > Recently I have noticed too many users of struct rtc_time that printing > > > its content field by field. > > > > > >

[PATCH] staging: ks7010: use little-endian types

This patch fixes a number of sparse warnings of the form: drivers/staging/ks7010/ks_hostif.c:2187:29: warning: incorrect type in assignment (different base types) generated when storing little-endian data in variables that do not have a specified endianness. Signed-off-by: Perry Hooker

[PATCH] staging: ks7010: use little-endian types

This patch fixes a number of sparse warnings of the form: drivers/staging/ks7010/ks_hostif.c:2187:29: warning: incorrect type in assignment (different base types) generated when storing little-endian data in variables that do not have a specified endianness. Signed-off-by: Perry Hooker

[PATCH 0/3] Add support for the s6e63j0x03 panel on Rinato board

Hi all, The purpose of this patch is add support for s6e63j0x03 AMOLED panel on the rinato board(Samsung Galaxy Gear 2). The first and second patches are Add the binding document and panel driver. The third patch is remove the unnecessary properties in the rinato dts. Best regards, Hoegeun

[PATCH 0/3] Add support for the s6e63j0x03 panel on Rinato board

Hi all, The purpose of this patch is add support for s6e63j0x03 AMOLED panel on the rinato board(Samsung Galaxy Gear 2). The first and second patches are Add the binding document and panel driver. The third patch is remove the unnecessary properties in the rinato dts. Best regards, Hoegeun

[PATCH 3/3] ARM: dts: exynos: Remove the display-timing and delay from rinato dts

The display-timing and delay are included in the panel driver. So it should be removed in dts. Signed-off-by: Hoegeun Kwon --- arch/arm/boot/dts/exynos3250-rinato.dts | 22 -- 1 file changed, 22 deletions(-) diff --git

[PATCH 3/3] ARM: dts: exynos: Remove the display-timing and delay from rinato dts

The display-timing and delay are included in the panel driver. So it should be removed in dts. Signed-off-by: Hoegeun Kwon --- arch/arm/boot/dts/exynos3250-rinato.dts | 22 -- 1 file changed, 22 deletions(-) diff --git a/arch/arm/boot/dts/exynos3250-rinato.dts

[PATCH 1/3] dt-bindings: Add support for samsung s6e63j0x03 panel binding

The Samsung s6e63j0x03 is a 1.63" 320x320 AMOLED panel connected using MIPI-DSI interfaces. Signed-off-by: Hoegeun Kwon --- .../bindings/display/panel/samsung,s6e63j0x03.txt | 24 ++ 1 file changed, 24 insertions(+) create mode 100644

[PATCH 2/3] drm/panel: Add support for s6e63j0x03 panel driver

This patch adds MIPI-DSI based S6E63J0X03 AMOLED LCD panel driver which uses mipi_dsi bus to communicate with panel. The panel has 320×320 resolution in 1.63" physical panel. This panel is used in Samsung Galaxy Gear 2. Signed-off-by: Inki Dae Signed-off-by: Hyungwon Hwang

[PATCH 1/3] dt-bindings: Add support for samsung s6e63j0x03 panel binding

The Samsung s6e63j0x03 is a 1.63" 320x320 AMOLED panel connected using MIPI-DSI interfaces. Signed-off-by: Hoegeun Kwon --- .../bindings/display/panel/samsung,s6e63j0x03.txt | 24 ++ 1 file changed, 24 insertions(+) create mode 100644

[PATCH 2/3] drm/panel: Add support for s6e63j0x03 panel driver

This patch adds MIPI-DSI based S6E63J0X03 AMOLED LCD panel driver which uses mipi_dsi bus to communicate with panel. The panel has 320×320 resolution in 1.63" physical panel. This panel is used in Samsung Galaxy Gear 2. Signed-off-by: Inki Dae Signed-off-by: Hyungwon Hwang Signed-off-by:

[PATCH] netfilter: ctnetlink: move CTA_TIMEOUT case to outside

When cda[CTA_TIMEOUT] is zero, ctnetlink_new_conntrack will free allocated ct and return, so move it to outside to optimize this situation. Signed-off-by: Haishuang Yan --- net/netfilter/nf_conntrack_netlink.c | 5 + 1 file changed, 1 insertion(+), 4

[PATCH] netfilter: ctnetlink: move CTA_TIMEOUT case to outside

When cda[CTA_TIMEOUT] is zero, ctnetlink_new_conntrack will free allocated ct and return, so move it to outside to optimize this situation. Signed-off-by: Haishuang Yan --- net/netfilter/nf_conntrack_netlink.c | 5 + 1 file changed, 1 insertion(+), 4 deletions(-) diff --git

Re: [PATCH 1/3] media: ngene: Replace semaphore cmd_mutex with mutex

On 8 June 2017 at 20:40, Arnd Bergmann wrote: > On Thu, Jun 8, 2017 at 12:04 PM, Binoy Jayan wrote: >> The semaphore 'cmd_mutex' is used as a simple mutex, so >> it should be written as one. Semaphores are going away in the future. >> >> Signed-off-by:

Re: [PATCH 1/3] media: ngene: Replace semaphore cmd_mutex with mutex

On 8 June 2017 at 20:40, Arnd Bergmann wrote: > On Thu, Jun 8, 2017 at 12:04 PM, Binoy Jayan wrote: >> The semaphore 'cmd_mutex' is used as a simple mutex, so >> it should be written as one. Semaphores are going away in the future. >> >> Signed-off-by: Binoy Jayan >> --- > >> @@ -1283,7 +1283,7

Re: [PATCH v2 2/2] ARM: sun8i: a83t: add dwmac-sun8i ethernet driver

On Thu, Jun 8, 2017 at 8:48 PM, Maxime Ripard wrote: > On Thu, Jun 08, 2017 at 10:42:22AM +0200, Corentin Labbe wrote: >> On Thu, Jun 08, 2017 at 10:34:28AM +0200, Maxime Ripard wrote: >> > On Wed, Jun 07, 2017 at 07:33:45PM +0200, Corentin Labbe wrote: >> > >

Re: [PATCH v2 2/2] ARM: sun8i: a83t: add dwmac-sun8i ethernet driver

On Thu, Jun 8, 2017 at 8:48 PM, Maxime Ripard wrote: > On Thu, Jun 08, 2017 at 10:42:22AM +0200, Corentin Labbe wrote: >> On Thu, Jun 08, 2017 at 10:34:28AM +0200, Maxime Ripard wrote: >> > On Wed, Jun 07, 2017 at 07:33:45PM +0200, Corentin Labbe wrote: >> > > The dwmac-sun8i is an ethernet MAC

[PATCH v2] acpi: handle the acpi hotplug schedule error

Kernel should decrements the reference count of acpi device when the scheduling of acpi hotplug work is failed, and evaluates _OST to notify BIOS the failure. v2: To simplify the code. (Andy Shevchenko) Cc: "Rafael J. Wysocki" Cc: Len Brown Cc: Andy

[PATCH v2] acpi: handle the acpi hotplug schedule error

Kernel should decrements the reference count of acpi device when the scheduling of acpi hotplug work is failed, and evaluates _OST to notify BIOS the failure. v2: To simplify the code. (Andy Shevchenko) Cc: "Rafael J. Wysocki" Cc: Len Brown Cc: Andy Shevchenko Signed-off-by: "Lee, Chun-Yi"

Re: [PATCH 0/2] perf stat: fix segfault when closing events

ping? On Tue, May 23, 2017 at 8:44 PM, Ganapatrao Kulkarni wrote: > On Tue, May 23, 2017 at 3:34 PM, Mark Rutland wrote: >> Hi, >> >> Does anyone have any comments on these? >> >> I'm happy to rebase/resend if necessary. >> >> I'd very much like to

Re: [PATCH 0/2] perf stat: fix segfault when closing events

ping? On Tue, May 23, 2017 at 8:44 PM, Ganapatrao Kulkarni wrote: > On Tue, May 23, 2017 at 3:34 PM, Mark Rutland wrote: >> Hi, >> >> Does anyone have any comments on these? >> >> I'm happy to rebase/resend if necessary. >> >> I'd very much like to see this fixed. > > arm64 platforms have

linux-next: manual merge of the kvms390 tree with the kvm-arm tree

Hi all, Today's linux-next merge of the kvms390 tree got a conflict in: arch/s390/include/asm/kvm_host.h between commit: 2387149eade2 ("KVM: improve arch vcpu request defining") from the kvm-arm tree and commit: 8611a6a64661 ("KVM: s390: CMMA tracking, ESSA emulation, migration mode")

linux-next: manual merge of the kvms390 tree with the kvm-arm tree

Hi all, Today's linux-next merge of the kvms390 tree got a conflict in: arch/s390/include/asm/kvm_host.h between commit: 2387149eade2 ("KVM: improve arch vcpu request defining") from the kvm-arm tree and commit: 8611a6a64661 ("KVM: s390: CMMA tracking, ESSA emulation, migration mode")

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

ive-managed zoned block device target") > > I have used the device-mapper tree from next-20170608 for today. My apologies for that. My mistake. I just posted a patch to dm-devel to fix this. Everything should come in order after Mike's review. Best regards. -- Damien Le Moal

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

ive-managed zoned block device target") > > I have used the device-mapper tree from next-20170608 for today. My apologies for that. My mistake. I just posted a patch to dm-devel to fix this. Everything should come in order after Mike's review. Best regards. -- Damien Le Moal

Re: [PATCH v2] refcount: Create unchecked atomic_t implementation

Hi Davidlohr, On 06/08/2017 10:09 PM, Davidlohr Bueso wrote: Yes, this would be a prerequisite for ipc; which I initially thought didn't take a performance hit. Did you see a regression for ipc? The fast paths don't use the refcount, it is only used for rare situations: - GETALL, SETALL

Re: [PATCH v2] refcount: Create unchecked atomic_t implementation

Hi Davidlohr, On 06/08/2017 10:09 PM, Davidlohr Bueso wrote: Yes, this would be a prerequisite for ipc; which I initially thought didn't take a performance hit. Did you see a regression for ipc? The fast paths don't use the refcount, it is only used for rare situations: - GETALL, SETALL

Re: [PATCH] s390/crash: Fix KEXEC_NOTE_BYTES definition

On Friday 09 June 2017 07:47 AM, Xunlei Pang wrote: S390 KEXEC_NOTE_BYTES is not used by note_buf_t as before, which is now defined as follows: typedef u32 note_buf_t[CRASH_CORE_NOTE_BYTES/4]; It was changed by the CONFIG_CRASH_CORE feature. This patch gets rid of all the old

Re: [PATCH] s390/crash: Fix KEXEC_NOTE_BYTES definition

On Friday 09 June 2017 07:47 AM, Xunlei Pang wrote: S390 KEXEC_NOTE_BYTES is not used by note_buf_t as before, which is now defined as follows: typedef u32 note_buf_t[CRASH_CORE_NOTE_BYTES/4]; It was changed by the CONFIG_CRASH_CORE feature. This patch gets rid of all the old

Re: [PATCH 1/4] drm: bridge: dw-hdmi: Export hdmi_phy_configure_dwc_hdmi_3d_tx

Ignore this patch, Jose has a better patch to solve rk3399 hdmi phy configure. Hi Jose Sorry for missing your patch about hdmi 2.0 vendor phy fixup: https://patchwork.kernel.org/patch/9702229 It works fine on rk3399/rk3288, can you resend a standard patch to upstream? Thanks On 2017年06月09日

Re: [PATCH 1/4] drm: bridge: dw-hdmi: Export hdmi_phy_configure_dwc_hdmi_3d_tx

Ignore this patch, Jose has a better patch to solve rk3399 hdmi phy configure. Hi Jose Sorry for missing your patch about hdmi 2.0 vendor phy fixup: https://patchwork.kernel.org/patch/9702229 It works fine on rk3399/rk3288, can you resend a standard patch to upstream? Thanks On 2017年06月09日

[PATCH v6] mtd: handle partitioning on devices with 0 erasesize

erasesize is meaningful for flash devices but for SRAM there is no concept of an erase block so erasesize is set to 0. When partitioning these devices instead of ensuring partitions fall on erasesize boundaries we ensure they fall on writesize boundaries. Helped-by: Boris Brezillon

[PATCH v6] mtd: handle partitioning on devices with 0 erasesize

erasesize is meaningful for flash devices but for SRAM there is no concept of an erase block so erasesize is set to 0. When partitioning these devices instead of ensuring partitions fall on erasesize boundaries we ensure they fall on writesize boundaries. Helped-by: Boris Brezillon

Re: [kernel-hardening] [PATCH 0/6] LSM: Security module blob management

On Thu, 8 Jun 2017, Matt Brown wrote: > On 6/8/17 4:43 PM, Casey Schaufler wrote: > > Subject: [PATCH 0/6] LSM: Security module blob management > > > > This patch set moves management of security blobs out of > > the Linux security modules and into the security module > > infrastructure. This

Re: [kernel-hardening] [PATCH 0/6] LSM: Security module blob management

On Thu, 8 Jun 2017, Matt Brown wrote: > On 6/8/17 4:43 PM, Casey Schaufler wrote: > > Subject: [PATCH 0/6] LSM: Security module blob management > > > > This patch set moves management of security blobs out of > > the Linux security modules and into the security module > > infrastructure. This

Re: [HMM 07/15] mm/ZONE_DEVICE: new type of ZONE_DEVICE for unaddressable memory v3

On 05/24/2017 10:20 AM, Jérôme Glisse wrote: [...8<...] +#if IS_ENABLED(CONFIG_DEVICE_PRIVATE) +int device_private_entry_fault(struct vm_area_struct *vma, + unsigned long addr, + swp_entry_t entry, + unsigned int flags, +

Re: [HMM 07/15] mm/ZONE_DEVICE: new type of ZONE_DEVICE for unaddressable memory v3

On 05/24/2017 10:20 AM, Jérôme Glisse wrote: [...8<...] +#if IS_ENABLED(CONFIG_DEVICE_PRIVATE) +int device_private_entry_fault(struct vm_area_struct *vma, + unsigned long addr, + swp_entry_t entry, + unsigned int flags, +

linux-next: manual merge of the devicetree tree with the renesas tree

Hi Rob, Today's linux-next merge of the devicetree tree got a conflict in: Documentation/devicetree/bindings/vendor-prefixes.txt between commit: d795f15618b8 ("of: Add vendor prefix for iWave Systems Technologies Pvt. Ltd") from the renesas tree and commit: 97a0268e764c ("devicetree:

linux-next: manual merge of the devicetree tree with the renesas tree

Hi Rob, Today's linux-next merge of the devicetree tree got a conflict in: Documentation/devicetree/bindings/vendor-prefixes.txt between commit: d795f15618b8 ("of: Add vendor prefix for iWave Systems Technologies Pvt. Ltd") from the renesas tree and commit: 97a0268e764c ("devicetree:

Re: [PATCH v3 0/3] Add support for the S6E3HF2 panel on TM2e board

Dear Thierry, Could you check these patches. Regards, Hoegeun On 05/19/2017 03:56 PM, Hoegeun Kwon wrote: Dear Thierry, Could you check these patches? I think this patches have accumulated enough dust. If you have a another opinion, please tell me. Best regards, Hoegeun On 04/18/2017 05:40

Re: [PATCH v3 0/3] Add support for the S6E3HF2 panel on TM2e board

Dear Thierry, Could you check these patches. Regards, Hoegeun On 05/19/2017 03:56 PM, Hoegeun Kwon wrote: Dear Thierry, Could you check these patches? I think this patches have accumulated enough dust. If you have a another opinion, please tell me. Best regards, Hoegeun On 04/18/2017 05:40

  1   2   3   4   5   6   7   8   9   10   >