We get 1 warning when biuld kernel with W=1:
drivers/net/wireless/broadcom/brcm80211/brcmfmac/tracepoint.c:23:6: warning: no
previous prototype for '__brcmf_err' [-Wmissing-
prototypes]
In fact, this function is declared in brcmfmac/debuge.h, so this patch
add missing header dependencies
We get 1 warning when biuld kernel with W=1:
drivers/net/wireless/broadcom/brcm80211/brcmfmac/tracepoint.c:23:6: warning: no
previous prototype for '__brcmf_err' [-Wmissing-
prototypes]
In fact, this function is declared in brcmfmac/debuge.h, so this patch
add missing header dependencies
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 28687b935e93a9041a485b9ecdcab0e335f8eda5
commit: ed58c0e9eefef517aa5a547b78658e2ab4422232 gcc-plugins: abort builds
cleanly when not supported
date: 3 weeks ago
config: x86_64-randconfig-s1-08271305
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 28687b935e93a9041a485b9ecdcab0e335f8eda5
commit: ed58c0e9eefef517aa5a547b78658e2ab4422232 gcc-plugins: abort builds
cleanly when not supported
date: 3 weeks ago
config: x86_64-randconfig-s1-08271305
On Fri, Aug 26, 2016 at 10:26 PM, Borislav Petkov wrote:
>
> Shouldn't all that stuff below be in arch/x86/?
>
> arch/x86/pci/fixup.c maybe, for example?
Good catch.
As it's under a CONFIG_X86_64 test anyway, it looks to make a ton more
sense in the x86 pci fixup code.
On Fri, Aug 26, 2016 at 10:26 PM, Borislav Petkov wrote:
>
> Shouldn't all that stuff below be in arch/x86/?
>
> arch/x86/pci/fixup.c maybe, for example?
Good catch.
As it's under a CONFIG_X86_64 test anyway, it looks to make a ton more
sense in the x86 pci fixup code.
Linus
On Fri, Aug 26, 2016 at 02:08:03PM -0700, Tony Luck wrote:
> Each Xeon includes a number of capability registers in PCI space
> that describe some features not enumerated by CPUID.
>
> Use these to determine that we are running on a model that can recover
> from machine checks. Hooks for
On Fri, Aug 26, 2016 at 02:08:03PM -0700, Tony Luck wrote:
> Each Xeon includes a number of capability registers in PCI space
> that describe some features not enumerated by CPUID.
>
> Use these to determine that we are running on a model that can recover
> from machine checks. Hooks for
Le 26/08/2016 à 15:35, Doug Ledford a écrit :
On 8/26/2016 12:49 AM, Christophe JAILLET wrote:
The 2nd parameter of 'find_first_bit' is the number of bits to search.
In this case, we are passing 'sizeof(unsigned long)' which is likely to
be 4 or 8.
If the size can be 4 or 8, then using 64
Le 26/08/2016 à 15:35, Doug Ledford a écrit :
On 8/26/2016 12:49 AM, Christophe JAILLET wrote:
The 2nd parameter of 'find_first_bit' is the number of bits to search.
In this case, we are passing 'sizeof(unsigned long)' which is likely to
be 4 or 8.
If the size can be 4 or 8, then using 64
On Fri, Aug 26, 2016 at 02:08:03PM -0700, Tony Luck wrote:
> The original version of this used a check of the x86_model_id string
> for the magic "Intel(R) Xeon(R) CPU E7-" to determine whether we are
> running on a cpu that supports machine check recovery.
>
> Boris tried to talk me out of that,
On Fri, Aug 26, 2016 at 02:08:03PM -0700, Tony Luck wrote:
> The original version of this used a check of the x86_model_id string
> for the magic "Intel(R) Xeon(R) CPU E7-" to determine whether we are
> running on a cpu that supports machine check recovery.
>
> Boris tried to talk me out of that,
From: Colin King
Date: Fri, 26 Aug 2016 19:35:25 +0100
> From: Colin Ian King
>
> Trivial fix to spelling mistake in dev_warn message.
>
> Signed-off-by: Colin Ian King
Applied.
From: Colin King
Date: Fri, 26 Aug 2016 19:35:25 +0100
> From: Colin Ian King
>
> Trivial fix to spelling mistake in dev_warn message.
>
> Signed-off-by: Colin Ian King
Applied.
Add API to change vdso blob type with arch_prctl.
As this is usefull only by needs of CRIU, expose
this interface under CONFIG_CHECKPOINT_RESTORE.
Cc: Andy Lutomirski
Cc: Oleg Nesterov
Cc: Thomas Gleixner
Cc: "H. Peter Anvin"
Add API to change vdso blob type with arch_prctl.
As this is usefull only by needs of CRIU, expose
this interface under CONFIG_CHECKPOINT_RESTORE.
Cc: Andy Lutomirski
Cc: Oleg Nesterov
Cc: Thomas Gleixner
Cc: "H. Peter Anvin"
Cc: Ingo Molnar
Cc: linux...@kvack.org
Cc: x...@kernel.org
Cc:
On 08/26/2016 07:55 PM, Linus Torvalds wrote:
On Fri, Aug 26, 2016 at 8:16 AM, Jens Axboe wrote:
Hi Linus,
- Revert two previous floppy changes, since they caused a user visibile
regression. A better fix is in the works.
Those reverts have no sign-off, and no explanation for
On 08/26/2016 07:55 PM, Linus Torvalds wrote:
On Fri, Aug 26, 2016 at 8:16 AM, Jens Axboe wrote:
Hi Linus,
- Revert two previous floppy changes, since they caused a user visibile
regression. A better fix is in the works.
Those reverts have no sign-off, and no explanation for them.
No, a
This patch fix a minor checkpath warming:
"WARNING: line over 80 characters"
Signed-off-by: Sean
---
drivers/staging/dgnc/dgnc_neo.c | 116
1 file changed, 82 insertions(+), 34 deletions(-)
diff --git a/drivers/staging/dgnc/dgnc_neo.c
On Thu, Aug 25, 2016 at 05:56:25PM +, Ben Maurer wrote:
> rseq opens up a whole world of algorithms to userspace – algorithms
> that are O(num CPUs) and where one can have an extremely fast fastpath
> at the cost of a slower slow path. Many of these algorithms are in use
> in the kernel today
This patch fix a minor checkpath warming:
"WARNING: line over 80 characters"
Signed-off-by: Sean
---
drivers/staging/dgnc/dgnc_neo.c | 116
1 file changed, 82 insertions(+), 34 deletions(-)
diff --git a/drivers/staging/dgnc/dgnc_neo.c
On Thu, Aug 25, 2016 at 05:56:25PM +, Ben Maurer wrote:
> rseq opens up a whole world of algorithms to userspace – algorithms
> that are O(num CPUs) and where one can have an extremely fast fastpath
> at the cost of a slower slow path. Many of these algorithms are in use
> in the kernel today
On Wed, 2016-08-24 at 10:50 -0700, Stephen Boyd wrote:
> On 08/22, Erin Lo wrote:
> > diff --git a/drivers/clk/mediatek/clk-mt2701-hif.c
> > b/drivers/clk/mediatek/clk-mt2701-hif.c
> > index 18b4ab5..702fd74 100644
> > --- a/drivers/clk/mediatek/clk-mt2701-hif.c
> > +++
On Wed, 2016-08-24 at 10:50 -0700, Stephen Boyd wrote:
> On 08/22, Erin Lo wrote:
> > diff --git a/drivers/clk/mediatek/clk-mt2701-hif.c
> > b/drivers/clk/mediatek/clk-mt2701-hif.c
> > index 18b4ab5..702fd74 100644
> > --- a/drivers/clk/mediatek/clk-mt2701-hif.c
> > +++
Networking patch series need to be submitted to net...@vger.kernel.org
Thank you.
Networking patch series need to be submitted to net...@vger.kernel.org
Thank you.
Hi Stephen,
On Wed, 2016-08-24 at 10:49 -0700, Stephen Boyd wrote:
> On 08/22, Erin Lo wrote:
> > +
> > +static void __init mtk_infrasys_init_early(struct device_node *node)
> > +{
> > + int r, i;
> > +
> > + if (!infra_clk_data) {
> > + infra_clk_data =
Hi Stephen,
On Wed, 2016-08-24 at 10:49 -0700, Stephen Boyd wrote:
> On 08/22, Erin Lo wrote:
> > +
> > +static void __init mtk_infrasys_init_early(struct device_node *node)
> > +{
> > + int r, i;
> > +
> > + if (!infra_clk_data) {
> > + infra_clk_data =
On Aug 26, 2016, at 11:18 PM, Joe Perches wrote:
> On Fri, 2016-08-26 at 23:05 -0400, Oleg Drokin wrote:
>> %ul was probably meant as %lu since the former would print
>> an unsigned value and a letter l.
>>
>> But in fact the whole value we are printing in u32 anyway, so
>> we don't need the
On Aug 26, 2016, at 11:18 PM, Joe Perches wrote:
> On Fri, 2016-08-26 at 23:05 -0400, Oleg Drokin wrote:
>> %ul was probably meant as %lu since the former would print
>> an unsigned value and a letter l.
>>
>> But in fact the whole value we are printing in u32 anyway, so
>> we don't need the
The setting of vop registers need a reg_done writing to take effect.
In vop_enable the vop return to work by by restoring registers, but the
registers do not take effect immediately, it should a vop_cfg_done
after it. The same thing is needed by windows_disabled in
vop_crtc_disable.
The setting of vop registers need a reg_done writing to take effect.
In vop_enable the vop return to work by by restoring registers, but the
registers do not take effect immediately, it should a vop_cfg_done
after it. The same thing is needed by windows_disabled in
vop_crtc_disable.
Fix checkpath.pl warning:
trailing statements should be on next line
open brace '{' following function declarations go on the next line
Signed-off-by: Anson Jacob
---
drivers/staging/i4l/act2000/capi.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff
Fix checkpath.pl warning:
trailing statements should be on next line
open brace '{' following function declarations go on the next line
Signed-off-by: Anson Jacob
---
drivers/staging/i4l/act2000/capi.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git
(added Chunyan Zhang to cc)
On Fri, 2016-08-26 at 23:14 -0400, Oleg Drokin wrote:
> %ul would print an unsigned with a letter l at the end which does
> not seem to be desired here, on the other hand the value being printed
> is u32 so just drop the l instead of converting to %lu
Fixes:
(added Chunyan Zhang to cc)
On Fri, 2016-08-26 at 23:14 -0400, Oleg Drokin wrote:
> %ul would print an unsigned with a letter l at the end which does
> not seem to be desired here, on the other hand the value being printed
> is u32 so just drop the l instead of converting to %lu
Fixes:
On Fri, 2016-08-26 at 23:05 -0400, Oleg Drokin wrote:
> %ul was probably meant as %lu since the former would print
> an unsigned value and a letter l.
>
> But in fact the whole value we are printing in u32 anyway, so
> we don't need the format to be long. Therefore just drop the l
> altogether.
On Fri, 2016-08-26 at 23:05 -0400, Oleg Drokin wrote:
> %ul was probably meant as %lu since the former would print
> an unsigned value and a letter l.
>
> But in fact the whole value we are printing in u32 anyway, so
> we don't need the format to be long. Therefore just drop the l
> altogether.
%ul would print an unsigned with a letter l at the end which does
not seem to be desired here, on the other hand the value being printed
is u32 so just drop the l instead of converting to %lu
Signed-off-by: Oleg Drokin
---
drivers/net/irda/vlsi_ir.c | 2 +-
1 file changed,
%ul would print an unsigned with a letter l at the end which does
not seem to be desired here, on the other hand the value being printed
is u32 so just drop the l instead of converting to %lu
Signed-off-by: Oleg Drokin
---
drivers/net/irda/vlsi_ir.c | 2 +-
1 file changed, 1 insertion(+), 1
%ul was likely meant as %lu to print an unsigned long,
not an unsigned with a letter l at the end.
But in fact the value printed is u32 anyway, so just drop
the l completely.
Signed-off-by: Oleg Drokin
---
drivers/net/wireless/realtek/rtlwifi/rtl8192de/phy.c | 6 +++---
1
%ul was likely meant as %lu to print an unsigned long,
not an unsigned with a letter l at the end.
But in fact the value printed is u32 anyway, so just drop
the l completely.
Signed-off-by: Oleg Drokin
---
drivers/net/wireless/realtek/rtlwifi/rtl8192de/phy.c | 6 +++---
1 file changed, 3
%ul would print an unsigned value and a letter l,
likely it was %lu that was meant to print the long int,
but in reality the values printed there are just regular signed
ints, so just dropping the l altogether.
Signed-off-by: Oleg Drokin
---
net/bridge/br_stp_bpdu.c | 2 +-
%ul would print an unsigned value and a letter l,
likely it was %lu that was meant to print the long int,
but in reality the values printed there are just regular signed
ints, so just dropping the l altogether.
Signed-off-by: Oleg Drokin
---
net/bridge/br_stp_bpdu.c | 2 +-
1 file changed, 1
%ul was probably meant as %lu since the former would print
an unsigned value and a letter l.
But in fact the whole value we are printing in u32 anyway, so
we don't need the format to be long. Therefore just drop the l
altogether.
Signed-off-by: Oleg Drokin
---
Also do we
%ul was probably meant as %lu since the former would print
an unsigned value and a letter l.
But in fact the whole value we are printing in u32 anyway, so
we don't need the format to be long. Therefore just drop the l
altogether.
Signed-off-by: Oleg Drokin
---
Also do we really need 1000UL
Fix checkpatch.pl warning:
Block comments use * on subsequent lines
Fix Commenting Style
Anson Jacob (2):
staging: fsl-mc: dpmng-cmd: Fix checkpatch warning
staging: fsl-mc: dprc-cmd: Fix checkpatch warning
drivers/staging/fsl-mc/bus/dpmng-cmd.h | 15 ---
Fix checkpatch.pl warning:
Block comments use * on subsequent lines
Fix Commenting Style
Anson Jacob (2):
staging: fsl-mc: dpmng-cmd: Fix checkpatch warning
staging: fsl-mc: dprc-cmd: Fix checkpatch warning
drivers/staging/fsl-mc/bus/dpmng-cmd.h | 15 ---
Fix checkpatch.pl warning:
Block comments use * on subsequent lines
Fix Commenting Style
Signed-off-by: Anson Jacob
---
drivers/staging/fsl-mc/bus/dprc-cmd.h | 15 ---
1 file changed, 8 insertions(+), 7 deletions(-)
diff --git
Fix checkpatch.pl warning:
Block comments use * on subsequent lines
Fix Commenting Style
Signed-off-by: Anson Jacob
---
drivers/staging/fsl-mc/bus/dpmng-cmd.h | 15 ---
1 file changed, 8 insertions(+), 7 deletions(-)
diff --git
Fix checkpatch.pl warning:
Block comments use * on subsequent lines
Fix Commenting Style
Signed-off-by: Anson Jacob
---
drivers/staging/fsl-mc/bus/dprc-cmd.h | 15 ---
1 file changed, 8 insertions(+), 7 deletions(-)
diff --git a/drivers/staging/fsl-mc/bus/dprc-cmd.h
Fix checkpatch.pl warning:
Block comments use * on subsequent lines
Fix Commenting Style
Signed-off-by: Anson Jacob
---
drivers/staging/fsl-mc/bus/dpmng-cmd.h | 15 ---
1 file changed, 8 insertions(+), 7 deletions(-)
diff --git a/drivers/staging/fsl-mc/bus/dpmng-cmd.h
Large PIO transfers are broken up into chunks to try to avoid disabling
local IRQs for long periods. But IRQs are still disabled for too long
and this causes SCC FIFO overruns during serial port transfers. This
patch fixes the problem by halving the PIO chunk size.
Testing with mac_scsi shows
Large PIO transfers are broken up into chunks to try to avoid disabling
local IRQs for long periods. But IRQs are still disabled for too long
and this causes SCC FIFO overruns during serial port transfers. This
patch fixes the problem by halving the PIO chunk size.
Testing with mac_scsi shows
Miscellaneous small patches for an interrupt latency issue,
a compiler warning and a documentation cleanup.
---
Documentation/kernel-parameters.txt|2 --
Documentation/scsi/scsi-parameters.txt |2 --
drivers/scsi/NCR5380.c | 13 +++--
drivers/scsi/NCR5380.h
With commit 3a0f64bfa907 ("mac_scsi: Fix pseudo DMA implementation")
some versions of gcc now warn:
In file included from drivers/scsi/mac_scsi.c:335:
drivers/scsi/NCR5380.h:295: warning: `NCR5380_poll_politely' declared inline
after being called
drivers/scsi/NCR5380.h:295: warning: previous
Miscellaneous small patches for an interrupt latency issue,
a compiler warning and a documentation cleanup.
---
Documentation/kernel-parameters.txt|2 --
Documentation/scsi/scsi-parameters.txt |2 --
drivers/scsi/NCR5380.c | 13 +++--
drivers/scsi/NCR5380.h
With commit 3a0f64bfa907 ("mac_scsi: Fix pseudo DMA implementation")
some versions of gcc now warn:
In file included from drivers/scsi/mac_scsi.c:335:
drivers/scsi/NCR5380.h:295: warning: `NCR5380_poll_politely' declared inline
after being called
drivers/scsi/NCR5380.h:295: warning: previous
The driver that used the 'nodisconnect' parameter was removed in
commit 565bae6a4a8f ("[SCSI] 53c7xx: kill driver"). Related documentation
was cleaned up in commit f37a7238d379 ("[SCSI] 53c7xx: fix removal
fallout"), except for the remaining two mentions that are removed here.
Signed-off-by: Finn
The driver that used the 'nodisconnect' parameter was removed in
commit 565bae6a4a8f ("[SCSI] 53c7xx: kill driver"). Related documentation
was cleaned up in commit f37a7238d379 ("[SCSI] 53c7xx: fix removal
fallout"), except for the remaining two mentions that are removed here.
Signed-off-by: Finn
Introduce BPF_PROG_TYPE_PERF_EVENT programs that can be attached to
HW and SW perf events (PERF_TYPE_HARDWARE and PERF_TYPE_SOFTWARE
correspondingly in uapi/linux/perf_event.h)
The program visible context meta structure is
struct bpf_perf_event_data {
struct pt_regs regs;
__u64
Introduce BPF_PROG_TYPE_PERF_EVENT programs that can be attached to
HW and SW perf events (PERF_TYPE_HARDWARE and PERF_TYPE_SOFTWARE
correspondingly in uapi/linux/perf_event.h)
The program visible context meta structure is
struct bpf_perf_event_data {
struct pt_regs regs;
__u64
Make sure that BPF_PROG_TYPE_PERF_EVENT programs only use
preallocated hash maps, since doing memory allocation
in overflow_handler can crash depending on where nmi got triggered.
Signed-off-by: Alexei Starovoitov
---
kernel/bpf/verifier.c | 22 +-
1 file
Make sure that BPF_PROG_TYPE_PERF_EVENT programs only use
preallocated hash maps, since doing memory allocation
in overflow_handler can crash depending on where nmi got triggered.
Signed-off-by: Alexei Starovoitov
---
kernel/bpf/verifier.c | 22 +-
1 file changed, 21
The verifier supported only 4-byte metafields in
struct __sk_buff and struct xdp_md. The metafields in upcoming
struct bpf_perf_event are 8-byte to match register width in struct pt_regs.
Teach verifier to recognize 8-byte metafield access.
The patch doesn't affect safety of sockets and xdp
From: Brendan Gregg
sample instruction pointer and frequency count in a BPF map
Signed-off-by: Brendan Gregg
Signed-off-by: Alexei Starovoitov
---
samples/bpf/Makefile| 4 +
samples/bpf/sampleip_kern.c | 38 +
The bpf program is called 50 times a second and does
hashmap[kern_stackid]++
It's primary purpose to check that key bpf helpers like map lookup, update,
get_stackid, trace_printk and ctx access are all working.
It checks:
- PERF_COUNT_HW_CPU_CYCLES on all cpus
- PERF_COUNT_HW_CPU_CYCLES for
The verifier supported only 4-byte metafields in
struct __sk_buff and struct xdp_md. The metafields in upcoming
struct bpf_perf_event are 8-byte to match register width in struct pt_regs.
Teach verifier to recognize 8-byte metafield access.
The patch doesn't affect safety of sockets and xdp
From: Brendan Gregg
sample instruction pointer and frequency count in a BPF map
Signed-off-by: Brendan Gregg
Signed-off-by: Alexei Starovoitov
---
samples/bpf/Makefile| 4 +
samples/bpf/sampleip_kern.c | 38 +
samples/bpf/sampleip_user.c | 196
The bpf program is called 50 times a second and does
hashmap[kern_stackid]++
It's primary purpose to check that key bpf helpers like map lookup, update,
get_stackid, trace_printk and ctx access are all working.
It checks:
- PERF_COUNT_HW_CPU_CYCLES on all cpus
- PERF_COUNT_HW_CPU_CYCLES for
Hi Peter, Dave,
this patch set is a follow up to the discussion:
https://lkml.org/lkml/2016/8/4/304
It turned out to be simpler than what we discussed.
Patches 1-3 is a bpf-side prep for the main patch 4
that adds bpf program as an overflow_handler to sw and hw perf_events.
Peter, please review.
Allow attaching BPF_PROG_TYPE_PERF_EVENT programs to sw and hw perf events
via overflow_handler mechanism.
When program is attached the overflow_handlers become stacked.
The program acts as a filter.
Returning zero from the program means that the normal perf_event_output handler
will not be called
Hi Peter, Dave,
this patch set is a follow up to the discussion:
https://lkml.org/lkml/2016/8/4/304
It turned out to be simpler than what we discussed.
Patches 1-3 is a bpf-side prep for the main patch 4
that adds bpf program as an overflow_handler to sw and hw perf_events.
Peter, please review.
Allow attaching BPF_PROG_TYPE_PERF_EVENT programs to sw and hw perf events
via overflow_handler mechanism.
When program is attached the overflow_handlers become stacked.
The program acts as a filter.
Returning zero from the program means that the normal perf_event_output handler
will not be called
Hi Jaegeuk,
>> > - [lkp] [f2fs] b93f771286: aim7.jobs-per-min -81.2% regression
>> >
>> > The disk is 4 12G ram disk, and setup RAID0 on them via mdadm. The
>> > steps for aim7 is,
>> >
>> > cat > workfile <> > FILESIZE: 1M
>> > POOLSIZE: 10M
>> > 10 sync_disk_rw
>> > EOF
>> >
>> > (
>> >
Hi Jaegeuk,
>> > - [lkp] [f2fs] b93f771286: aim7.jobs-per-min -81.2% regression
>> >
>> > The disk is 4 12G ram disk, and setup RAID0 on them via mdadm. The
>> > steps for aim7 is,
>> >
>> > cat > workfile <> > FILESIZE: 1M
>> > POOLSIZE: 10M
>> > 10 sync_disk_rw
>> > EOF
>> >
>> > (
>> >
Hi all,
On 2016/8/27 9:01, Jaegeuk Kim wrote:
On Fri, Aug 26, 2016 at 10:20:18PM +0800, Chao Yu wrote:
From: Chao Yu
tests/generic/251 of fstest suit complains us with below message:
[ cut here ]
invalid opcode: [#1] PREEMPT SMP
CPU: 2 PID:
Hi all,
On 2016/8/27 9:01, Jaegeuk Kim wrote:
On Fri, Aug 26, 2016 at 10:20:18PM +0800, Chao Yu wrote:
From: Chao Yu
tests/generic/251 of fstest suit complains us with below message:
[ cut here ]
invalid opcode: [#1] PREEMPT SMP
CPU: 2 PID: 7698 Comm: fstrim
On Fri, Aug 26, 2016 at 8:16 AM, Jens Axboe wrote:
> Hi Linus,
>
> - Revert two previous floppy changes, since they caused a user visibile
> regression. A better fix is in the works.
Those reverts have no sign-off, and no explanation for them.
No, a revert may not have any
On Fri, Aug 26, 2016 at 8:16 AM, Jens Axboe wrote:
> Hi Linus,
>
> - Revert two previous floppy changes, since they caused a user visibile
> regression. A better fix is in the works.
Those reverts have no sign-off, and no explanation for them.
No, a revert may not have any copyright value,
Resending as plain text
On 08/18/2016 02:24 AM, Benjamin Tissoires wrote:
From: Lyude Paul
This adds basic functionality for PS/2 passthrough on Synaptics
Touchpads using RMI4 through smbus.
Signed-off-by: Lyude Paul
Signed-off-by: Benjamin
Resending as plain text
On 08/18/2016 02:24 AM, Benjamin Tissoires wrote:
From: Lyude Paul
This adds basic functionality for PS/2 passthrough on Synaptics
Touchpads using RMI4 through smbus.
Signed-off-by: Lyude Paul
Signed-off-by: Benjamin Tissoires
Reviewed-by: Andrew Duggan
---
Resending as plain text
On 08/18/2016 02:24 AM, Benjamin Tissoires wrote:
If struct rmi_device_platform_data contains pointers to other struct,
it gets difficult to allocate a fixed size struct and copy it over between
drivers.
Change the pointers into a struct and change the code in rmi4
Resending as plain text
On 08/18/2016 02:24 AM, Benjamin Tissoires wrote:
If struct rmi_device_platform_data contains pointers to other struct,
it gets difficult to allocate a fixed size struct and copy it over between
drivers.
Change the pointers into a struct and change the code in rmi4
Resending as plain text
On 08/18/2016 02:24 AM, Benjamin Tissoires wrote:
From: Dennis Wassenberg
First check if there are data available passed by the transport device.
If data available use these data. If there are no data available
try to read the rmi block
Resending as plain text
On 08/18/2016 02:24 AM, Benjamin Tissoires wrote:
From: Dennis Wassenberg
First check if there are data available passed by the transport device.
If data available use these data. If there are no data available
try to read the rmi block if dsata are passed this way.
This reverts commit 6f8245b4e37c ("usb: dwc3: gadget: always decrement
by 1").
We can't always decrement this value.
We should decrement only if the calculation of free slots results in a
LINK TRB being among one of the free slots (dequeue < enqueue).
Otherwise, if the LINK TRB is not among the
This reverts commit 6f8245b4e37c ("usb: dwc3: gadget: always decrement
by 1").
We can't always decrement this value.
We should decrement only if the calculation of free slots results in a
LINK TRB being among one of the free slots (dequeue < enqueue).
Otherwise, if the LINK TRB is not among the
Resending as plain text
On 08/18/2016 02:24 AM, Benjamin Tissoires wrote:
With RMI4 over SMBus, the pass-through device can be instantiated
in a SMBus driver. However, compared to the psmouse-synaptics driver,
this pass-through PS/2 driver has no clue whether the current
serio_interrupt() is
Resending as plain text
On 08/18/2016 02:24 AM, Benjamin Tissoires wrote:
With RMI4 over SMBus, the pass-through device can be instantiated
in a SMBus driver. However, compared to the psmouse-synaptics driver,
this pass-through PS/2 driver has no clue whether the current
serio_interrupt() is
Resending as plain text
On 08/18/2016 02:24 AM, Benjamin Tissoires wrote:
If a function needs to communicate with an other, it's better to have
a way to retrieve this other.
Signed-off-by: Benjamin Tissoires
Reviewed-by: Andrew Duggan
Resending as plain text
Hi Benjamin,
This patch causes standard clickpads without extended buttons to not
work. I'll explain some more below.
On 08/18/2016 02:24 AM, Benjamin Tissoires wrote:
From: Lyude Paul
On the latest series of ThinkPads, the button events for
Resending as plain text
On 08/18/2016 02:24 AM, Benjamin Tissoires wrote:
If a function needs to communicate with an other, it's better to have
a way to retrieve this other.
Signed-off-by: Benjamin Tissoires
Reviewed-by: Andrew Duggan
---
drivers/input/rmi4/rmi_driver.c | 13
Resending as plain text
Hi Benjamin,
This patch causes standard clickpads without extended buttons to not
work. I'll explain some more below.
On 08/18/2016 02:24 AM, Benjamin Tissoires wrote:
From: Lyude Paul
On the latest series of ThinkPads, the button events for the TrackPoint
are
Warn when block comments are not aligned on the *
/*
* block comment, no warning
*/
/*
* block comment, emit warning
*/
Reported-by: Sudip Mukherjee
Signed-off-by: Joe Perches
---
scripts/checkpatch.pl | 19 +++
1 file
Warn when block comments are not aligned on the *
/*
* block comment, no warning
*/
/*
* block comment, emit warning
*/
Reported-by: Sudip Mukherjee
Signed-off-by: Joe Perches
---
scripts/checkpatch.pl | 19 +++
1 file changed, 19 insertions(+)
diff --git
On Fri, Aug 26, 2016 at 10:20:18PM +0800, Chao Yu wrote:
> From: Chao Yu
>
> tests/generic/251 of fstest suit complains us with below message:
>
> [ cut here ]
> invalid opcode: [#1] PREEMPT SMP
> CPU: 2 PID: 7698 Comm: fstrim Tainted: G
On Fri, Aug 26, 2016 at 10:20:18PM +0800, Chao Yu wrote:
> From: Chao Yu
>
> tests/generic/251 of fstest suit complains us with below message:
>
> [ cut here ]
> invalid opcode: [#1] PREEMPT SMP
> CPU: 2 PID: 7698 Comm: fstrim Tainted: G O4.7.0+ #21
>
This can avoid bio splits due to different op_flags.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/data.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
index 7c8e219..c7c2022 100644
--- a/fs/f2fs/data.c
+++ b/fs/f2fs/data.c
@@ -267,6
This can avoid bio splits due to different op_flags.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/data.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c
index 7c8e219..c7c2022 100644
--- a/fs/f2fs/data.c
+++ b/fs/f2fs/data.c
@@ -267,6 +267,11 @@ void
1 - 100 of 1160 matches
Mail list logo