On 8/15/18 10:45 PM, Anup Patel wrote:
On Thu, Aug 16, 2018 at 10:53 AM, Atish Patra wrote:
On 8/15/18 9:24 PM, Anup Patel wrote:
On Thu, Aug 16, 2018 at 5:26 AM, Atish Patra wrote:
Setup the cpu_logical_map during boot. Moreover, every SBI call
and PLIC context are based on the physical
On 8/15/18 10:45 PM, Anup Patel wrote:
On Thu, Aug 16, 2018 at 10:53 AM, Atish Patra wrote:
On 8/15/18 9:24 PM, Anup Patel wrote:
On Thu, Aug 16, 2018 at 5:26 AM, Atish Patra wrote:
Setup the cpu_logical_map during boot. Moreover, every SBI call
and PLIC context are based on the physical
On Thu, Aug 16, 2018 at 10:53 AM, Atish Patra wrote:
> On 8/15/18 9:24 PM, Anup Patel wrote:
>>
>> On Thu, Aug 16, 2018 at 5:26 AM, Atish Patra wrote:
>>>
>>> Setup the cpu_logical_map during boot. Moreover, every SBI call
>>> and PLIC context are based on the physical hartid. Use the logical
On Thu, Aug 16, 2018 at 10:53 AM, Atish Patra wrote:
> On 8/15/18 9:24 PM, Anup Patel wrote:
>>
>> On Thu, Aug 16, 2018 at 5:26 AM, Atish Patra wrote:
>>>
>>> Setup the cpu_logical_map during boot. Moreover, every SBI call
>>> and PLIC context are based on the physical hartid. Use the logical
Hi all,
Please do not add any v4.20 material to your linux-next included
branches until after v4.19-rc1 has been released.
Changes since 20180815:
Non-merge commits (relative to Linus' tree): 9298
8206 files changed, 426675 insertions(+), 158863 deletions
Hi all,
Please do not add any v4.20 material to your linux-next included
branches until after v4.19-rc1 has been released.
Changes since 20180815:
Non-merge commits (relative to Linus' tree): 9298
8206 files changed, 426675 insertions(+), 158863 deletions
Substitute spaces with tab. No functional changes.
Signed-off-by: Yi Wang
Reviewed-by: Jiang Biao
---
arch/x86/kvm/vmx.c | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
index 46b428c0..ef712b2 100644
---
Substitute spaces with tab. No functional changes.
Signed-off-by: Yi Wang
Reviewed-by: Jiang Biao
---
arch/x86/kvm/vmx.c | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
index 46b428c0..ef712b2 100644
---
On 8/15/18 10:02 PM, Anup Patel wrote:
On Thu, Aug 16, 2018 at 5:26 AM, Atish Patra wrote:
Defining cpu_operations now helps adding cpu hotplug
support in proper manner. Moreover, it provides flexibility
in supporting other cpu enable/boot methods can be
supported in future. This patch has
On 8/15/18 10:02 PM, Anup Patel wrote:
On Thu, Aug 16, 2018 at 5:26 AM, Atish Patra wrote:
Defining cpu_operations now helps adding cpu hotplug
support in proper manner. Moreover, it provides flexibility
in supporting other cpu enable/boot methods can be
supported in future. This patch has
On Thu, Aug 16, 2018 at 10:47 AM, Atish Patra wrote:
> On 8/15/18 9:06 PM, Anup Patel wrote:
>>
>> On Thu, Aug 16, 2018 at 5:26 AM, Atish Patra wrote:
>>>
>>> Currently, both linux cpu id and hardware cpu id are same.
>>> This is not recommended as it will lead to discontinuous cpu
>>> indexing
On Thu, Aug 16, 2018 at 10:47 AM, Atish Patra wrote:
> On 8/15/18 9:06 PM, Anup Patel wrote:
>>
>> On Thu, Aug 16, 2018 at 5:26 AM, Atish Patra wrote:
>>>
>>> Currently, both linux cpu id and hardware cpu id are same.
>>> This is not recommended as it will lead to discontinuous cpu
>>> indexing
On Wed, 2018-08-15 at 18:54 -0700, Andy Lutomirski wrote:
> On Mon, Jul 16, 2018 at 12:03 PM, Rik van Riel
> wrote:
> Hi Rik-
>
> I was looking through this, and I see:
>
> > -static void tlb_remove_table_one(void *table)
> > +static void tlb_remove_table_one(void *table, struct mmu_gather
> >
On Wed, 2018-08-15 at 18:54 -0700, Andy Lutomirski wrote:
> On Mon, Jul 16, 2018 at 12:03 PM, Rik van Riel
> wrote:
> Hi Rik-
>
> I was looking through this, and I see:
>
> > -static void tlb_remove_table_one(void *table)
> > +static void tlb_remove_table_one(void *table, struct mmu_gather
> >
On Thu, 16 Aug 2018 04:08:04 +0200,
Linus Torvalds wrote:
>
> On Wed, Aug 15, 2018 at 7:05 PM Joe Perches wrote:
> >
> > Why does the commit change snd_hda_gen_add_micmute_led
> > to return 0; instead of return 1;
> >
> > That bit looks wrong.
>
> Well, it changes the comment too, and is
On Thu, 16 Aug 2018 04:08:04 +0200,
Linus Torvalds wrote:
>
> On Wed, Aug 15, 2018 at 7:05 PM Joe Perches wrote:
> >
> > Why does the commit change snd_hda_gen_add_micmute_led
> > to return 0; instead of return 1;
> >
> > That bit looks wrong.
>
> Well, it changes the comment too, and is
On 8/15/18 9:24 PM, Anup Patel wrote:
On Thu, Aug 16, 2018 at 5:26 AM, Atish Patra wrote:
Setup the cpu_logical_map during boot. Moreover, every SBI call
and PLIC context are based on the physical hartid. Use the logical
cpu to hartid mapping to pass correct hartid to respective functions.
On 8/15/18 9:24 PM, Anup Patel wrote:
On Thu, Aug 16, 2018 at 5:26 AM, Atish Patra wrote:
Setup the cpu_logical_map during boot. Moreover, every SBI call
and PLIC context are based on the physical hartid. Use the logical
cpu to hartid mapping to pass correct hartid to respective functions.
On Wed, Aug 15 2018, Jeff Layton wrote:
> On Wed, 2018-08-15 at 14:28 +0200, Krzysztof Kozlowski wrote:
>> Hi,
>>
>> Bisect pointed commit ce3147990450a68b3f549088b30f087742a08b5d
>> ("fs/locks: allow a lock request to block other requests.") to failure
>> boot of NFSv4 with root on several
On Wed, Aug 15 2018, Jeff Layton wrote:
> On Wed, 2018-08-15 at 14:28 +0200, Krzysztof Kozlowski wrote:
>> Hi,
>>
>> Bisect pointed commit ce3147990450a68b3f549088b30f087742a08b5d
>> ("fs/locks: allow a lock request to block other requests.") to failure
>> boot of NFSv4 with root on several
On 8/15/18 9:06 PM, Anup Patel wrote:
On Thu, Aug 16, 2018 at 5:26 AM, Atish Patra wrote:
Currently, both linux cpu id and hardware cpu id are same.
This is not recommended as it will lead to discontinuous cpu
indexing in Linux. Moreover, kdump kernel will run from CPU0
which would be absent
On 8/15/18 9:06 PM, Anup Patel wrote:
On Thu, Aug 16, 2018 at 5:26 AM, Atish Patra wrote:
Currently, both linux cpu id and hardware cpu id are same.
This is not recommended as it will lead to discontinuous cpu
indexing in Linux. Moreover, kdump kernel will run from CPU0
which would be absent
Use of_device_is_system_power_controller instead of manually reading
the system-power-controller property from the device tree node.
Reviewed-by: Johan Hovold
Signed-off-by: Keerthy
---
drivers/rtc/rtc-omap.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git
Use of_device_is_system_power_controller instead of manually reading
the system-power-controller property from the device tree node.
Reviewed-by: Johan Hovold
Signed-off-by: Keerthy
---
drivers/rtc/rtc-omap.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git
Cut down the shutdown time from 2 seconds to 1 sec. In case of roll
over try again.
Signed-off-by: Keerthy
---
drivers/rtc/rtc-omap.c | 25 +++--
1 file changed, 15 insertions(+), 10 deletions(-)
diff --git a/drivers/rtc/rtc-omap.c b/drivers/rtc/rtc-omap.c
index
Cut down the shutdown time from 2 seconds to 1 sec. In case of roll
over try again.
Signed-off-by: Keerthy
---
drivers/rtc/rtc-omap.c | 25 +++--
1 file changed, 15 insertions(+), 10 deletions(-)
diff --git a/drivers/rtc/rtc-omap.c b/drivers/rtc/rtc-omap.c
index
David Howells writes:
> Having just re-ported NFS on top of the new mount API stuff, I find that I
> don't really like the idea of superblocks being separated by communication
> parameters - especially when it might seem reasonable to be able to adjust
> those parameters.
>
> Does it make sense
David Howells writes:
> Having just re-ported NFS on top of the new mount API stuff, I find that I
> don't really like the idea of superblocks being separated by communication
> parameters - especially when it might seem reasonable to be able to adjust
> those parameters.
>
> Does it make sense
Hi Rick,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.18 next-20180815]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
Hi Rick,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.18 next-20180815]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
On Thu, Aug 16, 2018 at 5:26 AM, Atish Patra wrote:
> Defining cpu_operations now helps adding cpu hotplug
> support in proper manner. Moreover, it provides flexibility
> in supporting other cpu enable/boot methods can be
> supported in future. This patch has been largely inspired from
> ARM64.
On Thu, Aug 16, 2018 at 5:26 AM, Atish Patra wrote:
> Defining cpu_operations now helps adding cpu hotplug
> support in proper manner. Moreover, it provides flexibility
> in supporting other cpu enable/boot methods can be
> supported in future. This patch has been largely inspired from
> ARM64.
On Wed, 15 Aug 2018, Greg Kroah-Hartman wrote:
On Wed, Aug 15, 2018 at 01:24:25PM -0400, Byron Stanoszek wrote:
Hi Greg & Thomas,
I'd like to report a regression in Linux 4.18.1 regarding the L1TF patches.
The kernel no longer thinks I have SMT enabled in the BIOS. This works fine in
4.18.0.
Hi Borislav,
2018-06-16 20:10 GMT+09:00 Borislav Petkov :
> Hi,
>
> I'm seeing this when I do
>
> # make menuconfig
>
> after a fresh repo clean: git clean -dqfx
>
> Might wanna silence it...
>
> /bin/sh: 1: .: Can't open scripts/kconfig/.mconf-cfg
> /bin/sh: 1: .: Can't open
On Wed, 15 Aug 2018, Greg Kroah-Hartman wrote:
On Wed, Aug 15, 2018 at 01:24:25PM -0400, Byron Stanoszek wrote:
Hi Greg & Thomas,
I'd like to report a regression in Linux 4.18.1 regarding the L1TF patches.
The kernel no longer thinks I have SMT enabled in the BIOS. This works fine in
4.18.0.
Hi Borislav,
2018-06-16 20:10 GMT+09:00 Borislav Petkov :
> Hi,
>
> I'm seeing this when I do
>
> # make menuconfig
>
> after a fresh repo clean: git clean -dqfx
>
> Might wanna silence it...
>
> /bin/sh: 1: .: Can't open scripts/kconfig/.mconf-cfg
> /bin/sh: 1: .: Can't open
On Thu, Aug 16, 2018 at 5:26 AM, Atish Patra wrote:
> Setup the cpu_logical_map during boot. Moreover, every SBI call
> and PLIC context are based on the physical hartid. Use the logical
> cpu to hartid mapping to pass correct hartid to respective functions.
>
> Signed-off-by: Atish Patra
> ---
Eric Biggers writes:
> You'd probably attract more contributors if you followed established
> open source conventions.
SUPERCOP already has thousands of implementations from hundreds of
contributors. New speed records are more likely to appear in SUPERCOP
than in any other cryptographic software
On Thu, Aug 16, 2018 at 5:26 AM, Atish Patra wrote:
> Setup the cpu_logical_map during boot. Moreover, every SBI call
> and PLIC context are based on the physical hartid. Use the logical
> cpu to hartid mapping to pass correct hartid to respective functions.
>
> Signed-off-by: Atish Patra
> ---
Eric Biggers writes:
> You'd probably attract more contributors if you followed established
> open source conventions.
SUPERCOP already has thousands of implementations from hundreds of
contributors. New speed records are more likely to appear in SUPERCOP
than in any other cryptographic software
I have important transaction for you as next of kin to claim $16m Dolles email
me at ( dray...@gmail.com )
Regards
Mr.Fung
I have important transaction for you as next of kin to claim $16m Dolles email
me at ( dray...@gmail.com )
Regards
Mr.Fung
On Thu, Aug 16, 2018 at 5:26 AM, Atish Patra wrote:
> Currently, both linux cpu id and hardware cpu id are same.
> This is not recommended as it will lead to discontinuous cpu
> indexing in Linux. Moreover, kdump kernel will run from CPU0
> which would be absent if we follow existing scheme.
>
>
On Thu, Aug 16, 2018 at 5:26 AM, Atish Patra wrote:
> Currently, both linux cpu id and hardware cpu id are same.
> This is not recommended as it will lead to discontinuous cpu
> indexing in Linux. Moreover, kdump kernel will run from CPU0
> which would be absent if we follow existing scheme.
>
>
Recently syzbot reported crashes in send_sigio_to_task and
send_sigurg_to_task in linux-next. Despite finding a reproducer
syzbot apparently did not bisected this or otherwise track down the
offending commit in linux-next.
I happened to see this report and examined the code because I had
Recently syzbot reported crashes in send_sigio_to_task and
send_sigurg_to_task in linux-next. Despite finding a reproducer
syzbot apparently did not bisected this or otherwise track down the
offending commit in linux-next.
I happened to see this report and examined the code because I had
Dmitry Vyukov writes:
> On Tue, Aug 14, 2018 at 12:11 PM, J. Bruce Fields
> wrote:
>> On Mon, Aug 13, 2018 at 06:33:02AM -0700, syzbot wrote:
>>> syzbot has found a reproducer for the following crash on:
>>>
>>> HEAD commit:5ed5da74de9e Add linux-next specific files for 20180813
>>> git
Dmitry Vyukov writes:
> On Tue, Aug 14, 2018 at 12:11 PM, J. Bruce Fields
> wrote:
>> On Mon, Aug 13, 2018 at 06:33:02AM -0700, syzbot wrote:
>>> syzbot has found a reproducer for the following crash on:
>>>
>>> HEAD commit:5ed5da74de9e Add linux-next specific files for 20180813
>>> git
This is worth further detailed discussion re:SMB3 as there are some fascinating
protocol features that might help here, but my first thought is just the obvious
one - this could help 'DFS' (the global name space feature almost all modern
CIFS/SMB3 implement) work a little better in the client. A
This is worth further detailed discussion re:SMB3 as there are some fascinating
protocol features that might help here, but my first thought is just the obvious
one - this could help 'DFS' (the global name space feature almost all modern
CIFS/SMB3 implement) work a little better in the client. A
Hi zhouxianrong,
Please could you be more sepcific what case can we encounter below BUG?
(Please use plain text)
What zs_class size did you this this problem?
Could you say how that can happen?
As I wrote in other reply, zsmalloc should never allocate last parital
object when I look at source
Hi zhouxianrong,
Please could you be more sepcific what case can we encounter below BUG?
(Please use plain text)
What zs_class size did you this this problem?
Could you say how that can happen?
As I wrote in other reply, zsmalloc should never allocate last parital
object when I look at source
On Thu, 16 Aug 2018 10:48:35 +0900 Sergey Senozhatsky
wrote:
> > The implementation might be able to use strim() somehow.
>
> strim() trims white-spaces.
Which includes \n.
> What we have here is a trailing new line symbol,
> which echo appends to the string it writes to the kernel [echo -n
On Thu, 16 Aug 2018 10:48:35 +0900 Sergey Senozhatsky
wrote:
> > The implementation might be able to use strim() somehow.
>
> strim() trims white-spaces.
Which includes \n.
> What we have here is a trailing new line symbol,
> which echo appends to the string it writes to the kernel [echo -n
2018-08-15 9:36 GMT+09:00 Randy Dunlap :
> From: Randy Dunlap
>
> Add build-only targets for build_menuconfig, build_nconfig,
> build_xconfig, and build_gconfig.
> (targets must end in "config" to qualify in top-level Makefile)
>
> This allows these target to be built without execution (e.g., to
2018-08-15 9:36 GMT+09:00 Randy Dunlap :
> From: Randy Dunlap
>
> Add build-only targets for build_menuconfig, build_nconfig,
> build_xconfig, and build_gconfig.
> (targets must end in "config" to qualify in top-level Makefile)
>
> This allows these target to be built without execution (e.g., to
On 2018/8/14 18:41, Jerome Brunet wrote:
> On Tue, 2018-08-14 at 02:18 -0400, Hanjie Lin wrote:
>> From: Yue Wang
>>
>> The Amlogic Meson PCIe host controller is based on the Synopsys DesignWare
>> PCI core. This patch adds the driver support for Meson PCIe controller.
>>
>> Signed-off-by: Yue
On 2018/8/14 18:41, Jerome Brunet wrote:
> On Tue, 2018-08-14 at 02:18 -0400, Hanjie Lin wrote:
>> From: Yue Wang
>>
>> The Amlogic Meson PCIe host controller is based on the Synopsys DesignWare
>> PCI core. This patch adds the driver support for Meson PCIe controller.
>>
>> Signed-off-by: Yue
On 2018/8/15 6:53, Rob Herring wrote:
> On Tue, Aug 14, 2018 at 02:18:41AM -0400, Hanjie Lin wrote:
>> From: Yue Wang
>>
>> The Amlogic Meson PCIe host controller is based on the Synopsys DesignWare
>> PCI core. This patch adds documentation for the DT bindings in Meson PCIe
>> controller.
>>
On 2018/8/15 6:53, Rob Herring wrote:
> On Tue, Aug 14, 2018 at 02:18:41AM -0400, Hanjie Lin wrote:
>> From: Yue Wang
>>
>> The Amlogic Meson PCIe host controller is based on the Synopsys DesignWare
>> PCI core. This patch adds documentation for the DT bindings in Meson PCIe
>> controller.
>>
On 2018/8/14 18:41, Jerome Brunet wrote:
> On Tue, 2018-08-14 at 02:18 -0400, Hanjie Lin wrote:
>> From: Yue Wang
>>
>> The Amlogic Meson PCIe host controller is based on the Synopsys DesignWare
>> PCI core. This patch adds documentation for the DT bindings in Meson PCIe
>> controller.
>>
>>
On 2018/8/14 18:41, Jerome Brunet wrote:
> On Tue, 2018-08-14 at 02:18 -0400, Hanjie Lin wrote:
>> From: Yue Wang
>>
>> The Amlogic Meson PCIe host controller is based on the Synopsys DesignWare
>> PCI core. This patch adds documentation for the DT bindings in Meson PCIe
>> controller.
>>
>>
On 08/10/2018 04:35 PM, Joerg Roedel wrote:
On Fri, Aug 10, 2018 at 06:33:42AM +0800, kernel test robot wrote:
commit a13c600e15de44ccf03df28d3311ef3cb754ed9b
Author: Joerg Roedel
AuthorDate: Wed Aug 8 13:16:40 2018 +0200
Commit: Thomas Gleixner
CommitDate: Thu Aug 9 20:42:07 2018
On 08/10/2018 04:35 PM, Joerg Roedel wrote:
On Fri, Aug 10, 2018 at 06:33:42AM +0800, kernel test robot wrote:
commit a13c600e15de44ccf03df28d3311ef3cb754ed9b
Author: Joerg Roedel
AuthorDate: Wed Aug 8 13:16:40 2018 +0200
Commit: Thomas Gleixner
CommitDate: Thu Aug 9 20:42:07 2018
On 2018/8/14 18:41, Jerome Brunet wrote:
> On Tue, 2018-08-14 at 02:12 -0400, Hanjie Lin wrote:
>> From: Yue Wang
>>
>> The Meson-PCIE-PHY controller supports the 5-Gbps data rate
>> of the PCI Express Gen 2 specification and is backwardcompatible
>> with the 2.5-Gbps Gen 1.1 specification
On 2018/8/14 18:41, Jerome Brunet wrote:
> On Tue, 2018-08-14 at 02:12 -0400, Hanjie Lin wrote:
>> From: Yue Wang
>>
>> The Meson-PCIE-PHY controller supports the 5-Gbps data rate
>> of the PCI Express Gen 2 specification and is backwardcompatible
>> with the 2.5-Gbps Gen 1.1 specification
On 2018/8/15 6:50, Rob Herring wrote:
> On Tue, Aug 14, 2018 at 02:12:13AM -0400, Hanjie Lin wrote:
>> From: Yue Wang
>
> Subject should be "dt-bindings: phy: ..."
>
>> The Meson-PCIE-PHY controller supports the 5-Gbps data rate
>> of the PCI Express Gen 2 specification and is
On 2018/8/15 6:50, Rob Herring wrote:
> On Tue, Aug 14, 2018 at 02:12:13AM -0400, Hanjie Lin wrote:
>> From: Yue Wang
>
> Subject should be "dt-bindings: phy: ..."
>
>> The Meson-PCIE-PHY controller supports the 5-Gbps data rate
>> of the PCI Express Gen 2 specification and is
Sorry for the late reply, I actually wrote this email over a week ago,
but never hit send. And the email was pushed back behind other
windows. :-/
On Fri, 3 Aug 2018 19:58:42 +0530
Sai Prakash Ranjan wrote:
> diff --git a/kernel/trace/trace_rtb.c b/kernel/trace/trace_rtb.c
> new file mode
Sorry for the late reply, I actually wrote this email over a week ago,
but never hit send. And the email was pushed back behind other
windows. :-/
On Fri, 3 Aug 2018 19:58:42 +0530
Sai Prakash Ranjan wrote:
> diff --git a/kernel/trace/trace_rtb.c b/kernel/trace/trace_rtb.c
> new file mode
From: Roy Im
This patch adds support for the Dialog DA7280 Haptic driver IC.
In this patch set the following is provided:
[PATCH V1 1/3] MAINTAINERS file update for DA7280
[PATCH V1 2/3] DA7280 DT Binding
[PATCH V1 3/3] DA7280 Driver
This patch applies against linux-next and v4.18
Thank you,
From: Roy Im
This patch adds support for the Dialog DA7280 Haptic driver IC.
In this patch set the following is provided:
[PATCH V1 1/3] MAINTAINERS file update for DA7280
[PATCH V1 2/3] DA7280 DT Binding
[PATCH V1 3/3] DA7280 Driver
This patch applies against linux-next and v4.18
Thank you,
from: Roy Im
Add device tree binding information for DA7280 haptic driver.
Example bindings for DA7280 are added.
Signed-off-by: Roy Im
---
.../devicetree/bindings/input/dlg,da7280.txt | 91
1 file changed, 91 insertions(+)
create mode 100644
from: Roy Im
Adds support for the Dialog DA7280 LRA/ERM Haptic Driver with
multiple mode and integrated waveform memory and wideband support.
It communicates via an I2C bus to the device.
Signed-off-by: Roy Im
---
drivers/input/misc/Kconfig | 12 +
drivers/input/misc/Makefile |1 +
From: Roy Im
This patch adds the da7280 bindings doc and driver to the Dialog
Semiconductor support list.
Signed-off-by: Roy Im
---
MAINTAINERS |2 ++
1 file changed, 2 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 544cac8..720f9fe 100644
--- a/MAINTAINERS
+++
from: Roy Im
Add device tree binding information for DA7280 haptic driver.
Example bindings for DA7280 are added.
Signed-off-by: Roy Im
---
.../devicetree/bindings/input/dlg,da7280.txt | 91
1 file changed, 91 insertions(+)
create mode 100644
from: Roy Im
Adds support for the Dialog DA7280 LRA/ERM Haptic Driver with
multiple mode and integrated waveform memory and wideband support.
It communicates via an I2C bus to the device.
Signed-off-by: Roy Im
---
drivers/input/misc/Kconfig | 12 +
drivers/input/misc/Makefile |1 +
From: Roy Im
This patch adds the da7280 bindings doc and driver to the Dialog
Semiconductor support list.
Signed-off-by: Roy Im
---
MAINTAINERS |2 ++
1 file changed, 2 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 544cac8..720f9fe 100644
--- a/MAINTAINERS
+++
On Wed, Aug 15, 2018 at 02:54:13PM -0700, Yang Shi wrote:
>
>
> On 8/15/18 2:09 PM, Matthew Wilcox wrote:
> > On Wed, Aug 15, 2018 at 12:16:06PM -0700, Matthew Wilcox wrote:
> > > (not even compiled, and I can see a good opportunity for combining the
> > > VM_LOCKED loop with the has_uprobes
On Wed, Aug 15, 2018 at 02:54:13PM -0700, Yang Shi wrote:
>
>
> On 8/15/18 2:09 PM, Matthew Wilcox wrote:
> > On Wed, Aug 15, 2018 at 12:16:06PM -0700, Matthew Wilcox wrote:
> > > (not even compiled, and I can see a good opportunity for combining the
> > > VM_LOCKED loop with the has_uprobes
In order to be able to have more than just an unsigned long worth of
private data, convert the code to allocate and use a dedicated struct.
Cc: Dmitry Torokhov
Cc: Jiri Kosina
Cc: Benjamin Tissoires
Cc: linux-in...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Cc: Pierre-Loup A. Griffais
In order to be able to have more than just an unsigned long worth of
private data, convert the code to allocate and use a dedicated struct.
Cc: Dmitry Torokhov
Cc: Jiri Kosina
Cc: Benjamin Tissoires
Cc: linux-in...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Cc: Pierre-Loup A. Griffais
Add HID quirk driver for Xbox One S controller over bluetooth.
This driver only adds support for rumble. Standard controller
functionality is exposed by default HID driver.
Cc: Dmitry Torokhov
Cc: Jiri Kosina
Cc: Benjamin Tissoires
Cc: linux-in...@vger.kernel.org
Cc:
Add HID quirk driver for Xbox One S controller over bluetooth.
This driver only adds support for rumble. Standard controller
functionality is exposed by default HID driver.
Cc: Dmitry Torokhov
Cc: Jiri Kosina
Cc: Benjamin Tissoires
Cc: linux-in...@vger.kernel.org
Cc:
Everyone:
This is v2 of the patches adding support for rumble for Xbox One S
controller connected over Bluetooth. Hopefully all of the changes are
pretty straightforward and self-explanatory.
Feedback is wellcome!
Changes since [v1]:
- code converting the driver to use struct ms_data is
Hi,
We recently hit a weird problem on the ASUS laptop UX433FN with
latest Intel Core i7-8565U CPU on kernel 4.18. The keyboard stops
functioning after exit s2idle. It stops firing interrupts after resume
on any keypress. We thought it should be something wrong with i8042
driver or even atkbd
Everyone:
This is v2 of the patches adding support for rumble for Xbox One S
controller connected over Bluetooth. Hopefully all of the changes are
pretty straightforward and self-explanatory.
Feedback is wellcome!
Changes since [v1]:
- code converting the driver to use struct ms_data is
Hi,
We recently hit a weird problem on the ASUS laptop UX433FN with
latest Intel Core i7-8565U CPU on kernel 4.18. The keyboard stops
functioning after exit s2idle. It stops firing interrupts after resume
on any keypress. We thought it should be something wrong with i8042
driver or even atkbd
2018-08-16 4:30 GMT+09:00 Randy Dunlap :
> From: Randy Dunlap
>
> Fix missing error check for memory allocation functions in
> scripts/mod/modpost.c.
>
> Fixes kernel bugzilla #200319:
> https://bugzilla.kernel.org/show_bug.cgi?id=200319
>
> Signed-off-by: Randy Dunlap
> Cc: Yuexing Wang
> Cc:
2018-08-16 4:30 GMT+09:00 Randy Dunlap :
> From: Randy Dunlap
>
> Fix missing error check for memory allocation functions in
> scripts/mod/modpost.c.
>
> Fixes kernel bugzilla #200319:
> https://bugzilla.kernel.org/show_bug.cgi?id=200319
>
> Signed-off-by: Randy Dunlap
> Cc: Yuexing Wang
> Cc:
On Thu, Aug 16, 2018 at 02:38:51AM +0300, Tuomas Tynkkynen wrote:
> Hello,
>
> Booting Linus's master of today with the usual arm64 defconfig fails for
> me on the Hikey960 board. I've bisected it down to:
>
> commit 693350a7998018391852c48f68956cf0f855b2b9 (HEAD, refs/bisect/bad)
> Author: Will
On Thu, Aug 16, 2018 at 02:38:51AM +0300, Tuomas Tynkkynen wrote:
> Hello,
>
> Booting Linus's master of today with the usual arm64 defconfig fails for
> me on the Hikey960 board. I've bisected it down to:
>
> commit 693350a7998018391852c48f68956cf0f855b2b9 (HEAD, refs/bisect/bad)
> Author: Will
On Wed, Aug 15, 2018 at 7:05 PM Joe Perches wrote:
>
> Why does the commit change snd_hda_gen_add_micmute_led
> to return 0; instead of return 1;
>
> That bit looks wrong.
Well, it changes the comment too, and is clearly intentional.
I guess the logic was to have the usual "0 for success,
On Wed, Aug 15, 2018 at 7:05 PM Joe Perches wrote:
>
> Why does the commit change snd_hda_gen_add_micmute_led
> to return 0; instead of return 1;
>
> That bit looks wrong.
Well, it changes the comment too, and is clearly intentional.
I guess the logic was to have the usual "0 for success,
On Wed, 2018-08-15 at 19:00 -0700, Linus Torvalds wrote:
> On Wed, Aug 15, 2018 at 6:27 PM Linus Torvalds
> wrote:
> >
> > I have no idea _why_, but it's consistent, and it bisects down to
> >
> > c647f806b8c2 "ALSA: hda - Allow multiple ADCs for mic mute LED controls"
> >
> > where the
On Wed, 2018-08-15 at 19:00 -0700, Linus Torvalds wrote:
> On Wed, Aug 15, 2018 at 6:27 PM Linus Torvalds
> wrote:
> >
> > I have no idea _why_, but it's consistent, and it bisects down to
> >
> > c647f806b8c2 "ALSA: hda - Allow multiple ADCs for mic mute LED controls"
> >
> > where the
On Wed, Aug 15, 2018 at 6:27 PM Linus Torvalds
wrote:
>
> I have no idea _why_, but it's consistent, and it bisects down to
>
> c647f806b8c2 "ALSA: hda - Allow multiple ADCs for mic mute LED controls"
>
> where the previous commit works fine, but that commit definitely
> causes the problem.
On Wed, Aug 15, 2018 at 6:27 PM Linus Torvalds
wrote:
>
> I have no idea _why_, but it's consistent, and it bisects down to
>
> c647f806b8c2 "ALSA: hda - Allow multiple ADCs for mic mute LED controls"
>
> where the previous commit works fine, but that commit definitely
> causes the problem.
A bunch of corrections
On (08/16/18 10:48), Sergey Senozhatsky wrote:
> The problem is that strlcpy() copies as many bytes as the source string
> has, not as many bytes as destination string can fit.
I mean - strlcpy() expects that the 3rd argument will be sizeof(dst), but
we passed the wrong
A bunch of corrections
On (08/16/18 10:48), Sergey Senozhatsky wrote:
> The problem is that strlcpy() copies as many bytes as the source string
> has, not as many bytes as destination string can fit.
I mean - strlcpy() expects that the 3rd argument will be sizeof(dst), but
we passed the wrong
1 - 100 of 890 matches
Mail list logo
