Hi,
On 09/08/17 at 12:16pm, AKASHI Takahiro wrote:
[snip]
> --- a/include/linux/kexec.h
> +++ b/include/linux/kexec.h
> @@ -162,6 +162,25 @@ int __weak arch_kexec_walk_mem(struct kexec_buf *kbuf,
> int (*func)(u64, u64, void *));
> extern int kexec_add_buffer(struct
Hi,
On 09/08/17 at 12:16pm, AKASHI Takahiro wrote:
[snip]
> --- a/include/linux/kexec.h
> +++ b/include/linux/kexec.h
> @@ -162,6 +162,25 @@ int __weak arch_kexec_walk_mem(struct kexec_buf *kbuf,
> int (*func)(u64, u64, void *));
> extern int kexec_add_buffer(struct
If 'dmam_alloc_attrs()' fails, we must go through the error handling code,
as done elsewhere in this function. Otherwise, there is a resource leak.
Signed-off-by: Christophe JAILLET
---
I'm also puzzled by the 'framebuffer_alloc()' call a few lines above.
'ret' is
If 'dmam_alloc_attrs()' fails, we must go through the error handling code,
as done elsewhere in this function. Otherwise, there is a resource leak.
Signed-off-by: Christophe JAILLET
---
I'm also puzzled by the 'framebuffer_alloc()' call a few lines above.
'ret' is known to be 0 at this point. I
On Tue, Sep 12, 2017 at 10:10:51AM +0900, Masami Hiramatsu wrote:
> To enable jump optimized probe with CONFIG_PREEMPT, use
> synchronize_rcu_tasks() to wait for all tasks preempted
> on trampoline code back on track.
>
> Since the jump optimized kprobes can replace multiple
> instructions, there
On Tue, Sep 12, 2017 at 10:10:51AM +0900, Masami Hiramatsu wrote:
> To enable jump optimized probe with CONFIG_PREEMPT, use
> synchronize_rcu_tasks() to wait for all tasks preempted
> on trampoline code back on track.
>
> Since the jump optimized kprobes can replace multiple
> instructions, there
On Tue, Sep 12, 2017 at 5:42 AM, Cameron Gutman wrote:
> On 09/11/2017 05:26 AM, Andrey Konovalov wrote:
>> Hi!
>>
>> I've got the following crashes while fuzzing the kernel with syzkaller.
>>
>> On commit 81a84ad3cb5711cec79f4dd53a4ce026b092c432 (Sep 3).
>>
>> usb 1-1:
On Tue, Sep 12, 2017 at 5:42 AM, Cameron Gutman wrote:
> On 09/11/2017 05:26 AM, Andrey Konovalov wrote:
>> Hi!
>>
>> I've got the following crashes while fuzzing the kernel with syzkaller.
>>
>> On commit 81a84ad3cb5711cec79f4dd53a4ce026b092c432 (Sep 3).
>>
>> usb 1-1: BOGUS urb xfer, pipe 1 !=
Minchan Kim writes:
> page_cluster 0 means "we don't want readahead" so in the case,
> let's skip the readahead detection logic.
>
> Cc: "Huang, Ying"
> Signed-off-by: Minchan Kim
> ---
> include/linux/swap.h | 3 ++-
> 1 file
Minchan Kim writes:
> page_cluster 0 means "we don't want readahead" so in the case,
> let's skip the readahead detection logic.
>
> Cc: "Huang, Ying"
> Signed-off-by: Minchan Kim
> ---
> include/linux/swap.h | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git
Hi Luis,
To confirm, reverting this fixes the problem I was seeing in 4.13. I've
queued it up for the next 4.13-stable release as well.
>>>
>>> Commit 81f95076281f ("firmware: add sanity check on shutdown/suspend") may
>>> seem kludgy but the reason for it was to cleanup the horrible
Hi Luis,
To confirm, reverting this fixes the problem I was seeing in 4.13. I've
queued it up for the next 4.13-stable release as well.
>>>
>>> Commit 81f95076281f ("firmware: add sanity check on shutdown/suspend") may
>>> seem kludgy but the reason for it was to cleanup the horrible
This helper, in the spirit of ext4_should_dioread_nolock() et al., replaces
the complex conditional in ext4_set_inode_flags().
Signed-off-by: Ross Zwisler
---
fs/ext4/inode.c | 19 ---
1 file changed, 16 insertions(+), 3 deletions(-)
diff --git
This helper, in the spirit of ext4_should_dioread_nolock() et al., replaces
the complex conditional in ext4_set_inode_flags().
Signed-off-by: Ross Zwisler
---
fs/ext4/inode.c | 19 ---
1 file changed, 16 insertions(+), 3 deletions(-)
diff --git a/fs/ext4/inode.c
The following commit:
commit 9b7365fc1c82 ("ext4: add FS_IOC_FSSETXATTR/FS_IOC_FSGETXATTR
interface support")
added several defines related to extended attributes to ext4.h. They were
added within an #ifndef FS_IOC_FSGETXATTR block with the comment:
/* Until the uapi changes get merged for
If an inode has inline data it is currently prevented from using DAX by a
check in ext4_set_inode_flags(). When the inode grows inline data via
ext4_create_inline_data() or removes its inline data via
ext4_destroy_inline_data_nolock(), the value of S_DAX can change.
Currently these changes are
The following commit:
commit 9b7365fc1c82 ("ext4: add FS_IOC_FSSETXATTR/FS_IOC_FSGETXATTR
interface support")
added several defines related to extended attributes to ext4.h. They were
added within an #ifndef FS_IOC_FSGETXATTR block with the comment:
/* Until the uapi changes get merged for
If an inode has inline data it is currently prevented from using DAX by a
check in ext4_set_inode_flags(). When the inode grows inline data via
ext4_create_inline_data() or removes its inline data via
ext4_destroy_inline_data_nolock(), the value of S_DAX can change.
Currently these changes are
This series prevents a pair of data corruptions with ext4 + DAX. The first
such corruption happens when combining the inline data feature with DAX,
and the second happens when combining data journaling with DAX.
Both can be reliably reproduced with the fstests that I have posted here:
This series prevents a pair of data corruptions with ext4 + DAX. The first
such corruption happens when combining the inline data feature with DAX,
and the second happens when combining data journaling with DAX.
Both can be reliably reproduced with the fstests that I have posted here:
We prevent DAX from being used on inodes which are using ext4's built in
encryption via a check in ext4_set_inode_flags(). We do have what appears
to be an unsafe transition of S_DAX in ext4_set_context(), though, where
S_DAX can get disabled without us doing a proper writeback + invalidate.
We prevent DAX from being used on inodes which are using ext4's built in
encryption via a check in ext4_set_inode_flags(). We do have what appears
to be an unsafe transition of S_DAX in ext4_set_context(), though, where
S_DAX can get disabled without us doing a proper writeback + invalidate.
The current code has the potential for data corruption when changing an
inode's journaling mode, as that can result in a subsequent unsafe change
in S_DAX.
I've captured an instance of this data corruption in the following fstest:
https://patchwork.kernel.org/patch/9948377/
Prevent this data
The current code has the potential for data corruption when changing an
inode's journaling mode, as that can result in a subsequent unsafe change
in S_DAX.
I've captured an instance of this data corruption in the following fstest:
https://patchwork.kernel.org/patch/9948377/
Prevent this data
ZSTD tends to outperform deflate/inflate, thus we remove
zlib from the list of recommended algorithms and recommend
zstd instead.
Signed-off-by: Sergey Senozhatsky
Suggested-by: Minchan Kim
---
drivers/block/zram/zcomp.c | 3 ---
1 file
ZSTD tends to outperform deflate/inflate, thus we remove
zlib from the list of recommended algorithms and recommend
zstd instead.
Signed-off-by: Sergey Senozhatsky
Suggested-by: Minchan Kim
---
drivers/block/zram/zcomp.c | 3 ---
1 file changed, 3 deletions(-)
diff --git
Add ZSTD to the list of supported compression algorithms.
ZRAM fio perf test:
LZO DEFLATE ZSTD
#jobs1
WRITE: (2180MB/s) (77.2MB/s) (1429MB/s)
WRITE: (1617MB/s) (77.7MB/s) (1202MB/s)
READ:(426MB/s)
Add ZSTD to the list of supported compression algorithms.
ZRAM fio perf test:
LZO DEFLATE ZSTD
#jobs1
WRITE: (2180MB/s) (77.2MB/s) (1429MB/s)
WRITE: (1617MB/s) (77.7MB/s) (1202MB/s)
READ:(426MB/s)
On Mon, Sep 11, 2017 at 12:56 PM, Christophe JAILLET
wrote:
> All other error handling paths in this function go through the 'error'
> label. This one should do the same.
>
> Fixes: 9cc9a5cb176c ("datapath: Avoid using stack larger than 1024.")
> Signed-off-by:
On Mon, Sep 11, 2017 at 12:56 PM, Christophe JAILLET
wrote:
> All other error handling paths in this function go through the 'error'
> label. This one should do the same.
>
> Fixes: 9cc9a5cb176c ("datapath: Avoid using stack larger than 1024.")
> Signed-off-by: Christophe JAILLET
> ---
> I think
On (09/12/17 11:37), Minchan Kim wrote:
[..]
> If rw-page based fast storage is used for swap devices, we need to
> detect it to enhance swap IO operations.
> This patch is preparation for optimizing of swap-in operation with
> next patch.
>
> Signed-off-by: Minchan Kim
> ---
On (09/12/17 11:37), Minchan Kim wrote:
[..]
> If rw-page based fast storage is used for swap devices, we need to
> detect it to enhance swap IO operations.
> This patch is preparation for optimizing of swap-in operation with
> next patch.
>
> Signed-off-by: Minchan Kim
> ---
>
Add a regression test for the following kernel commit:
ext4: prevent data corruption with journaling + DAX
The test passes if either we successfully compare the data between the mmap
with journaling turned on and the one with journaling turned off, or if we
fail the chattr command to turn on
Add a regression test for the following kernel commit:
ext4: prevent data corruption with journaling + DAX
The test passes if either we successfully compare the data between the mmap
with journaling turned on and the one with journaling turned off, or if we
fail the chattr command to turn on
Signed-off-by: Ross Zwisler
---
.gitignore | 4
1 file changed, 4 insertions(+)
diff --git a/.gitignore b/.gitignore
index 28fe84d..2accc37 100644
--- a/.gitignore
+++ b/.gitignore
@@ -238,3 +238,7 @@
/tests/xfs/033.out
/tests/xfs/071.out
/tests/xfs/096.out
Signed-off-by: Ross Zwisler
---
.gitignore | 4
1 file changed, 4 insertions(+)
diff --git a/.gitignore b/.gitignore
index 28fe84d..2accc37 100644
--- a/.gitignore
+++ b/.gitignore
@@ -238,3 +238,7 @@
/tests/xfs/033.out
/tests/xfs/071.out
/tests/xfs/096.out
+
+# cscope files
+cscope.*
Add a regression test for the following kernel commit:
ext4: prevent data corruption with inline data + DAX
The test passes either if we don't encounter corruption, or if mounting
with DAX + inline data fails. The latter is the way that we prevent this
issue in the kernel.
Signed-off-by:
Add a regression test for the following kernel commit:
ext4: prevent data corruption with inline data + DAX
The test passes either if we don't encounter corruption, or if mounting
with DAX + inline data fails. The latter is the way that we prevent this
issue in the kernel.
Signed-off-by:
On Mon, Sep 11, 2017 at 02:47:54PM +0800, Dave Young wrote:
> Hi,
>
> On 09/08/17 at 12:16pm, AKASHI Takahiro wrote:
> > load_other_segments() sets up and adds all the memory segments necessary
> > other than kernel, including initrd, device-tree blob and purgatory.
> > Most of the code was
On Mon, Sep 11, 2017 at 02:47:54PM +0800, Dave Young wrote:
> Hi,
>
> On 09/08/17 at 12:16pm, AKASHI Takahiro wrote:
> > load_other_segments() sets up and adds all the memory segments necessary
> > other than kernel, including initrd, device-tree blob and purgatory.
> > Most of the code was
On Sun, Sep 10, 2017 at 11:41:47PM +0800, kbuild test robot wrote:
> Hi AKASHI,
>
> [auto build test ERROR on arm64/for-next/core]
> [also build test ERROR on v4.13 next-20170908]
> [if your patch is applied to the wrong git tree, please drop us a note to
> help improve the system]
>
> url:
On Sun, Sep 10, 2017 at 11:41:47PM +0800, kbuild test robot wrote:
> Hi AKASHI,
>
> [auto build test ERROR on arm64/for-next/core]
> [also build test ERROR on v4.13 next-20170908]
> [if your patch is applied to the wrong git tree, please drop us a note to
> help improve the system]
>
> url:
Hi Mathieu,
On Tue, Aug 29, 2017 at 11:55 AM, Mathieu Desnoyers
wrote:
> - On Aug 28, 2017, at 1:12 PM, Max Filippov jcmvb...@gmail.com wrote:
>> On Mon, Aug 28, 2017 at 12:36 AM, Mathieu Desnoyers
>> wrote:
>>> The membarrier
Hi Mathieu,
On Tue, Aug 29, 2017 at 11:55 AM, Mathieu Desnoyers
wrote:
> - On Aug 28, 2017, at 1:12 PM, Max Filippov jcmvb...@gmail.com wrote:
>> On Mon, Aug 28, 2017 at 12:36 AM, Mathieu Desnoyers
>> wrote:
>>> The membarrier system call now requires all architectures to implement
>>>
> Yeah, that's exactly like what I made a mistake before.
> I should have mentioned that earlier. :)
Or I think the previous code which used "iter++" might be right.
You might just want to check the fixed number of small discards,
DISCARD_ISSUE_RATE,
when issue_cond is "true".
Anyways, I have
> Yeah, that's exactly like what I made a mistake before.
> I should have mentioned that earlier. :)
Or I think the previous code which used "iter++" might be right.
You might just want to check the fixed number of small discards,
DISCARD_ISSUE_RATE,
when issue_cond is "true".
Anyways, I have
On 09/12, Chao Yu wrote:
> On 2017/9/12 9:53, Chao Yu wrote:
> > On 2017/9/11 11:38, Jaegeuk Kim wrote:
> >> If issue_cond is true, it does double count for # of issued commands.
> >>
> >> Signed-off-by: Jaegeuk Kim
> >
> > Reviewed-by: Chao Yu
>
> As
On 09/12, Chao Yu wrote:
> On 2017/9/12 9:53, Chao Yu wrote:
> > On 2017/9/11 11:38, Jaegeuk Kim wrote:
> >> If issue_cond is true, it does double count for # of issued commands.
> >>
> >> Signed-off-by: Jaegeuk Kim
> >
> > Reviewed-by: Chao Yu
>
> As Daeho Jeong mentioned, the change makes
Hi all,
Please do not add any v4.15 related material to your linux-next
included branches until after v4.14-rc1 has been released.
Changes since 20170911:
Non-merge commits (relative to Linus' tree): 1124
1423 files changed, 55946 insertions(+), 14234 deletions
Hi all,
Please do not add any v4.15 related material to your linux-next
included branches until after v4.14-rc1 has been released.
Changes since 20170911:
Non-merge commits (relative to Linus' tree): 1124
1423 files changed, 55946 insertions(+), 14234 deletions
On 2017/9/12 9:53, Chao Yu wrote:
> On 2017/9/11 11:38, Jaegeuk Kim wrote:
>> If issue_cond is true, it does double count for # of issued commands.
>>
>> Signed-off-by: Jaegeuk Kim
>
> Reviewed-by: Chao Yu
As Daeho Jeong mentioned, the change makes 'iter
On 2017/9/12 9:53, Chao Yu wrote:
> On 2017/9/11 11:38, Jaegeuk Kim wrote:
>> If issue_cond is true, it does double count for # of issued commands.
>>
>> Signed-off-by: Jaegeuk Kim
>
> Reviewed-by: Chao Yu
As Daeho Jeong mentioned, the change makes 'iter > DISCARD_ISSUE_RATE' dead
code, I just
This commit allows OMAP3530 variants to use common data that is
available in 'omap3-evm-processor-common.dtsi'. It adds proper pinmux
macros for 'omap3_pmx_core2' on OMAP3430. The Micron NAND chip is also
added for the TMDSEVM3530 processor module.
Signed-off-by: Derald D. Woods
This commit allows OMAP3530 variants to use common data that is
available in 'omap3-evm-processor-common.dtsi'. It adds proper pinmux
macros for 'omap3_pmx_core2' on OMAP3430. The Micron NAND chip is also
added for the TMDSEVM3530 processor module.
Signed-off-by: Derald D. Woods
---
This commit moves common OMAP3-EVM processor module device tree data
to a separate include file. This will allow for 'omap3-evm.dts' to use
device tree data that is unique to the OMAP3530 version of the
processor module, while making use of the work already done for the
'omap3-evm-37xx.dts'.
The Sharp panel driver and regulator are now selected properly. This
commit eliminates a dummy regulator assignment.
Signed-off-by: Derald D. Woods
---
arch/arm/boot/dts/omap3-panel-sharp-ls037v7dw01.dtsi | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff
This commit moves common OMAP3-EVM processor module device tree data
to a separate include file. This will allow for 'omap3-evm.dts' to use
device tree data that is unique to the OMAP3530 version of the
processor module, while making use of the work already done for the
'omap3-evm-37xx.dts'.
The Sharp panel driver and regulator are now selected properly. This
commit eliminates a dummy regulator assignment.
Signed-off-by: Derald D. Woods
---
arch/arm/boot/dts/omap3-panel-sharp-ls037v7dw01.dtsi | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
This patch set allows TMDSEVM3530(omap3-evm.dts) to boot using common
processor module data that is shared with 'omap3-evm-37xx.dts'. A new
common file for processor module data is introduced to help facilitate
the updated OMAP3530 support.
Changes in v2
-
- Pull in change from
This commit eliminates two dummy regulator assignments.
Signed-off-by: Derald D. Woods
---
arch/arm/boot/dts/omap3-evm-processor-common.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/omap3-evm-processor-common.dtsi
This patch set allows TMDSEVM3530(omap3-evm.dts) to boot using common
processor module data that is shared with 'omap3-evm-37xx.dts'. A new
common file for processor module data is introduced to help facilitate
the updated OMAP3530 support.
Changes in v2
-
- Pull in change from
This commit eliminates two dummy regulator assignments.
Signed-off-by: Derald D. Woods
---
arch/arm/boot/dts/omap3-evm-processor-common.dtsi | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/omap3-evm-processor-common.dtsi
On 09/11/2017 09:53 AM, Petr Mladek wrote:
> On Wed 2017-08-30 17:38:44, Jason Baron wrote:
>> When doing cumulative patches, if patch A introduces a change to function 1,
>> and patch B reverts the change to function 1 and introduces changes to say
>> function 2 and 3 as well, the change that
On 09/11/2017 09:53 AM, Petr Mladek wrote:
> On Wed 2017-08-30 17:38:44, Jason Baron wrote:
>> When doing cumulative patches, if patch A introduces a change to function 1,
>> and patch B reverts the change to function 1 and introduces changes to say
>> function 2 and 3 as well, the change that
Mainline crashes as follows when running nios2 images.
On node 0 totalpages: 65536
free_area_init_node: node 0, pgdat c8408fa0, node_mem_map c8726000
Normal zone: 512 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 65536 pages, LIFO batch:15
Unable to handle kernel NULL
Mainline crashes as follows when running nios2 images.
On node 0 totalpages: 65536
free_area_init_node: node 0, pgdat c8408fa0, node_mem_map c8726000
Normal zone: 512 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 65536 pages, LIFO batch:15
Unable to handle kernel NULL
On 09/11/2017 05:26 AM, Andrey Konovalov wrote:
> Hi!
>
> I've got the following crashes while fuzzing the kernel with syzkaller.
>
> On commit 81a84ad3cb5711cec79f4dd53a4ce026b092c432 (Sep 3).
>
> usb 1-1: BOGUS urb xfer, pipe 1 != type 3
> WARNING: CPU: 1 PID: 2574 at
On 09/11/2017 05:26 AM, Andrey Konovalov wrote:
> Hi!
>
> I've got the following crashes while fuzzing the kernel with syzkaller.
>
> On commit 81a84ad3cb5711cec79f4dd53a4ce026b092c432 (Sep 3).
>
> usb 1-1: BOGUS urb xfer, pipe 1 != type 3
> WARNING: CPU: 1 PID: 2574 at
Document struct tcpc_config and struct tcpc_dev.
Drop unused TCPC_USB_SWITCH_RESTORE.
Signed-off-by: Guenter Roeck
---
v2, v3: No change
drivers/staging/typec/tcpm.h | 57 ++--
1 file changed, 50 insertions(+), 7 deletions(-)
diff
Document struct tcpc_config and struct tcpc_dev.
Drop unused TCPC_USB_SWITCH_RESTORE.
Signed-off-by: Guenter Roeck
---
v2, v3: No change
drivers/staging/typec/tcpm.h | 57 ++--
1 file changed, 50 insertions(+), 7 deletions(-)
diff --git
The driver is in good enough shape to be moved out of staging.
Do it.
Signed-off-by: Guenter Roeck
---
v2: Use format-patch -M
v3: No change
drivers/staging/typec/Kconfig| 2 --
drivers/staging/typec/Makefile | 1 -
The driver is in good enough shape to be moved out of staging.
Do it.
Signed-off-by: Guenter Roeck
---
v2: Use format-patch -M
v3: No change
drivers/staging/typec/Kconfig| 2 --
drivers/staging/typec/Makefile | 1 -
Move tcpm (USB Type-C Port Manager) out of staging.
Signed-off-by: Guenter Roeck
---
v2: Use format-patch -M
v3: No change
drivers/staging/typec/Kconfig | 8
drivers/staging/typec/Makefile| 1 -
Move tcpm (USB Type-C Port Manager) out of staging.
Signed-off-by: Guenter Roeck
---
v2: Use format-patch -M
v3: No change
drivers/staging/typec/Kconfig | 8
drivers/staging/typec/Makefile| 1 -
drivers/staging/typec/TODO
Commented out code can be added as needed. Drop it.
Also drop TODO and an obsolete XXX comment.
Signed-off-by: Guenter Roeck
---
v2, v3: No change
drivers/staging/typec/tcpm.c | 37 +
1 file changed, 1 insertion(+), 36 deletions(-)
diff
Commented out code can be added as needed. Drop it.
Also drop TODO and an obsolete XXX comment.
Signed-off-by: Guenter Roeck
---
v2, v3: No change
drivers/staging/typec/tcpm.c | 37 +
1 file changed, 1 insertion(+), 36 deletions(-)
diff --git
struct pd_message is the format of a PD message as seen on the wire.
Signed-off-by: Guenter Roeck
---
v2: No change
v3: Fix document tag
drivers/staging/typec/pd.h | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/staging/typec/pd.h
struct pd_message is the format of a PD message as seen on the wire.
Signed-off-by: Guenter Roeck
---
v2: No change
v3: Fix document tag
drivers/staging/typec/pd.h | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/staging/typec/pd.h b/drivers/staging/typec/pd.h
index
On Sun, Sep 10, 2017 at 6:58 PM, Max Filippov wrote:
> On Sun, Sep 10, 2017 at 11:31 AM, Guenter Roeck wrote:
>> xtensa:allmodconfig fails to build in mainline with compiler errors
>> as follows.
>>
>> drivers/staging/rtl8723bs/core/rtw_ap.c: In function
On Sun, Sep 10, 2017 at 6:58 PM, Max Filippov wrote:
> On Sun, Sep 10, 2017 at 11:31 AM, Guenter Roeck wrote:
>> xtensa:allmodconfig fails to build in mainline with compiler errors
>> as follows.
>>
>> drivers/staging/rtl8723bs/core/rtw_ap.c: In function ‘expire_timeout_chk’:
>>
From: Masaki Ota
-To support Alps T4 device, separate U1 device code
Signed-off-by: Masaki Ota
---
drivers/hid/hid-alps.c | 120 +++--
1 file changed, 67 insertions(+), 53 deletions(-)
diff --git
From: Masaki Ota
-To support Alps T4 device, separate U1 device code
Signed-off-by: Masaki Ota
---
drivers/hid/hid-alps.c | 120 +++--
1 file changed, 67 insertions(+), 53 deletions(-)
diff --git a/drivers/hid/hid-alps.c b/drivers/hid/hid-alps.c
From: Masaki Ota
-To support Alps T4 device, clean up the source code
-Delete unnecessary structure
Signed-off-by: Masaki Ota
---
drivers/hid/hid-alps.c | 69 +-
1 file changed, 34 insertions(+), 35
From: Masaki Ota
-To support Alps T4 device, clean up the source code
-Delete unnecessary structure
Signed-off-by: Masaki Ota
---
drivers/hid/hid-alps.c | 69 +-
1 file changed, 34 insertions(+), 35 deletions(-)
diff --git
From: Masaki Ota
-Add T4 USB device code and Product ID
-This device is used on HP Elite x2 series
Signed-off-by: Masaki Ota
---
drivers/hid/hid-alps.c | 35 +--
drivers/hid/hid-core.c | 1 +
drivers/hid/hid-ids.h
From: Masaki Ota
-Add T4 USB device code and Product ID
-This device is used on HP Elite x2 series
Signed-off-by: Masaki Ota
---
drivers/hid/hid-alps.c | 35 +--
drivers/hid/hid-core.c | 1 +
drivers/hid/hid-ids.h | 1 +
3 files changed, 27 insertions(+), 10
From: Masaki Ota
-To support Alps T4 device, replace some variables
Signed-off-by: Masaki Ota
---
drivers/hid/hid-alps.c | 67 --
1 file changed, 27 insertions(+), 40 deletions(-)
diff --git
From: Masaki Ota
-To support Alps T4 device, replace some variables
Signed-off-by: Masaki Ota
---
drivers/hid/hid-alps.c | 67 --
1 file changed, 27 insertions(+), 40 deletions(-)
diff --git a/drivers/hid/hid-alps.c b/drivers/hid/hid-alps.c
From: Masaki Ota
-To support Alps T4 device, add x_min, y_min, max_fingers variables
Signed-off-by: Masaki Ota
---
drivers/hid/hid-alps.c | 38 --
1 file changed, 24 insertions(+), 14 deletions(-)
diff --git
From: Masaki Ota
-To support Alps T4 device, add x_min, y_min, max_fingers variables
Signed-off-by: Masaki Ota
---
drivers/hid/hid-alps.c | 38 --
1 file changed, 24 insertions(+), 14 deletions(-)
diff --git a/drivers/hid/hid-alps.c b/drivers/hid/hid-alps.c
From: Masaki Ota
-Add new U1 device Product ID
-This device is used on HP Elite book x360 series
Signed-off-by: Masaki Ota
---
drivers/hid/hid-alps.c | 3 +++
drivers/hid/hid-core.c | 1 +
drivers/hid/hid-ids.h | 1 +
3 files changed, 5
From: Masaki Ota
-Add new U1 device Product ID
-This device is used on HP Elite book x360 series
Signed-off-by: Masaki Ota
---
drivers/hid/hid-alps.c | 3 +++
drivers/hid/hid-core.c | 1 +
drivers/hid/hid-ids.h | 1 +
3 files changed, 5 insertions(+)
diff --git a/drivers/hid/hid-alps.c
From: Masaki Ota
-Add T4 device code and Product ID
-This device is used on HP EliteBook 1000 series and Zbook Stduio
Signed-off-by: Masaki Ota
---
drivers/hid/hid-alps.c | 343 ++---
From: Masaki Ota
-Add T4 device code and Product ID
-This device is used on HP EliteBook 1000 series and Zbook Stduio
Signed-off-by: Masaki Ota
---
drivers/hid/hid-alps.c | 343 ++---
drivers/hid/hid-core.c | 3 +-
drivers/hid/hid-ids.h | 1 +
3
Hi, Linus,
Please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/rzhang/linux.git next
to receive the latest Thermal Management updates for v4.14-rc1 with
top-most commit b32b5e14b4e0d40e06f094d2593b447e00acdf37:
Merge branches 'thermal-core', 'thermal-soc', 'thermal-intel' and
Hi, Linus,
Please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/rzhang/linux.git next
to receive the latest Thermal Management updates for v4.14-rc1 with
top-most commit b32b5e14b4e0d40e06f094d2593b447e00acdf37:
Merge branches 'thermal-core', 'thermal-soc', 'thermal-intel' and
Hi, Jiri, Benjamin,
This is the patch for support new Alps HID Touchpad device.
I submitted these patch before, but it was not completed.
So I separate the patch to some parts and release it again.
Best Regards,
Masaki Ota
Hi, Jiri, Benjamin,
This is the patch for support new Alps HID Touchpad device.
I submitted these patch before, but it was not completed.
So I separate the patch to some parts and release it again.
Best Regards,
Masaki Ota
Currently, Denali NAND driver always expects 3 row address cycle
devices because the driver init code hard-code the register setting.
I will fix it in 2/2.
Many drivers check chip->chipsize if the third row address cycle
is needed or not. This is not nice because 32MB, 128MB are
magic numbers.
Currently, Denali NAND driver always expects 3 row address cycle
devices because the driver init code hard-code the register setting.
I will fix it in 2/2.
Many drivers check chip->chipsize if the third row address cycle
is needed or not. This is not nice because 32MB, 128MB are
magic numbers.
1 - 100 of 1082 matches
Mail list logo