On Mon 03 Sep 04:52 PDT 2018, Rohit kumar wrote:
> Add devicetree bindings documentation file for Qualcomm
> Technolgies Inc ADSP Peripheral Image Loader.
>
> Signed-off-by: Rohit kumar
Rob, this revision looks good to me and I would like to move ahead and
merge it.
Regards,
Bjorn
> ---
>
On Mon 03 Sep 04:52 PDT 2018, Rohit kumar wrote:
> Add devicetree bindings documentation file for Qualcomm
> Technolgies Inc ADSP Peripheral Image Loader.
>
> Signed-off-by: Rohit kumar
Rob, this revision looks good to me and I would like to move ahead and
merge it.
Regards,
Bjorn
> ---
>
On Mon, 10 Sep 2018 19:33:56 +0200,
Rohit kumar wrote:
>
> In functions snd_soc_get_volsw_sx() or snd_soc_put_volsw_sx(),
> if the result of (min + max) is negative, then fls() returns
> signed integer with value as 32. This leads to signed integer
> overflow as complete operation is considered
> -Original Message-
> From: Jiri Kosina [mailto:ji...@kernel.org]
> Sent: Monday, September 10, 2018 2:24 AM
> To: Thomas Gleixner ; Ingo Molnar ;
> Peter Zijlstra ; Josh Poimboeuf
> ; Andrea Arcangeli ;
> Woodhouse, David ; Andi Kleen ;
> Tim Chen ; Schaufler, Casey
>
> Cc:
On Mon, 10 Sep 2018 19:33:56 +0200,
Rohit kumar wrote:
>
> In functions snd_soc_get_volsw_sx() or snd_soc_put_volsw_sx(),
> if the result of (min + max) is negative, then fls() returns
> signed integer with value as 32. This leads to signed integer
> overflow as complete operation is considered
> -Original Message-
> From: Jiri Kosina [mailto:ji...@kernel.org]
> Sent: Monday, September 10, 2018 2:24 AM
> To: Thomas Gleixner ; Ingo Molnar ;
> Peter Zijlstra ; Josh Poimboeuf
> ; Andrea Arcangeli ;
> Woodhouse, David ; Andi Kleen ;
> Tim Chen ; Schaufler, Casey
>
> Cc:
Hi,
I'm seeing a regression with Linux next with commit 7b6ec2ae877a
("fs: convert return type int to vm_fault_t") where apps can just
hang.
The reproducable test case I have is to remove a distro package
and then add it back where adding the package back just hangs and
the package file seems
Hi,
I'm seeing a regression with Linux next with commit 7b6ec2ae877a
("fs: convert return type int to vm_fault_t") where apps can just
hang.
The reproducable test case I have is to remove a distro package
and then add it back where adding the package back just hangs and
the package file seems
On Fri, 7 Sep 2018 08:24:58 +0200, Andrea Merello wrote:
> The width of the "length register" cannot be autodetected, and it is now
> specified with a DT property. Add documentation for it.
>
> Cc: Rob Herring
> Cc: Mark Rutland
> Cc: devicet...@vger.kernel.org
> Cc: Radhey Shyam Pandey
>
On Fri, 7 Sep 2018 08:24:58 +0200, Andrea Merello wrote:
> The width of the "length register" cannot be autodetected, and it is now
> specified with a DT property. Add documentation for it.
>
> Cc: Rob Herring
> Cc: Mark Rutland
> Cc: devicet...@vger.kernel.org
> Cc: Radhey Shyam Pandey
>
On Mon, Sep 10, 2018 at 09:16:43PM +0800, Pu Wen wrote:
> The PMU architecture for Hygon Dhyana CPU is similar to the AMD Family
> 17h one. To support Hygon Dhyana PMU, call amd_pmu_init() to share
> AMD PMU initialization flow, and change the PMU name to "HYGON".
>
> The Hygon Dhyana CPU support
On Mon, Sep 10, 2018 at 09:16:43PM +0800, Pu Wen wrote:
> The PMU architecture for Hygon Dhyana CPU is similar to the AMD Family
> 17h one. To support Hygon Dhyana PMU, call amd_pmu_init() to share
> AMD PMU initialization flow, and change the PMU name to "HYGON".
>
> The Hygon Dhyana CPU support
On Mon, Sep 10, 2018 at 6:53 PM, Christoph Hellwig wrote:
> On Mon, Sep 10, 2018 at 12:41:05AM -0700, syzbot wrote:
>> =
>> WARNING: SOFTIRQ-safe -> SOFTIRQ-unsafe lock order detected
>> 4.19.0-rc2+ #229 Not tainted
>>
On Mon, Sep 10, 2018 at 6:53 PM, Christoph Hellwig wrote:
> On Mon, Sep 10, 2018 at 12:41:05AM -0700, syzbot wrote:
>> =
>> WARNING: SOFTIRQ-safe -> SOFTIRQ-unsafe lock order detected
>> 4.19.0-rc2+ #229 Not tainted
>>
On 10 September 2018 at 20:01, Olof Johansson wrote:
> On Mon, Sep 10, 2018 at 10:53 AM, Scott Branden
> wrote:
>> Olof/All,
>>
>>
>> On 18-09-04 03:13 AM, Grant Likely wrote:
>>>
>>> Hey folks. More comments below, but the short answer is I really don't
>>> see what the problem is. Distros
On 10 September 2018 at 20:01, Olof Johansson wrote:
> On Mon, Sep 10, 2018 at 10:53 AM, Scott Branden
> wrote:
>> Olof/All,
>>
>>
>> On 18-09-04 03:13 AM, Grant Likely wrote:
>>>
>>> Hey folks. More comments below, but the short answer is I really don't
>>> see what the problem is. Distros
On Mon, Sep 10, 2018 at 09:16:03PM +0800, Pu Wen wrote:
> The Hygon Dhyana CPU have a special magic MSR way to force WB for
>From the last review round:
Also, it is "The ... CPU has a special..."
Please take your time and incorporate *all* review feedback - no need to
*rush* a new revision out
On Mon, Sep 10, 2018 at 09:16:03PM +0800, Pu Wen wrote:
> The Hygon Dhyana CPU have a special magic MSR way to force WB for
>From the last review round:
Also, it is "The ... CPU has a special..."
Please take your time and incorporate *all* review feedback - no need to
*rush* a new revision out
An ACPI buffer that was allocated was not being freed after use.
Signed-off-by: Mario Limonciello
Cc: sta...@vger.kernel.org
---
drivers/platform/x86/alienware-wmi.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/platform/x86/alienware-wmi.c
b/drivers/platform/x86/alienware-wmi.c
ACPI buffers were being allocated but never freed.
Reported-by: Pinzhen Xu
Signed-off-by: Mario Limonciello
Cc: sta...@vger.kernel.org
---
drivers/platform/x86/dell-smbios-wmi.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/platform/x86/dell-smbios-wmi.c
ACPI buffers were being allocated but never freed.
Reported-by: Pinzhen Xu
Signed-off-by: Mario Limonciello
Cc: sta...@vger.kernel.org
---
drivers/platform/x86/dell-smbios-wmi.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/platform/x86/dell-smbios-wmi.c
An ACPI buffer that was allocated was not being freed after use.
Signed-off-by: Mario Limonciello
Cc: sta...@vger.kernel.org
---
drivers/platform/x86/alienware-wmi.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/platform/x86/alienware-wmi.c
b/drivers/platform/x86/alienware-wmi.c
On Mon, Sep 10, 2018 at 10:53 AM, Scott Branden
wrote:
> Olof/All,
>
>
> On 18-09-04 03:13 AM, Grant Likely wrote:
>>
>> Hey folks. More comments below, but the short answer is I really don't
>> see what the problem is. Distros cannot easily support platforms that
>> require a dtb= parameter, and
On Mon, Sep 10, 2018 at 10:53 AM, Scott Branden
wrote:
> Olof/All,
>
>
> On 18-09-04 03:13 AM, Grant Likely wrote:
>>
>> Hey folks. More comments below, but the short answer is I really don't
>> see what the problem is. Distros cannot easily support platforms that
>> require a dtb= parameter, and
On Mon, Sep 10, 2018 at 10:42:59PM +0800, Song Qiang wrote:
> This driver was originally written by ST in 2016 as a misc input device,
> and hasn't been maintained for a long time. I grabbed some code from
> it's API and reformed it to a iio proximity device driver.
> This version of driver uses
On Mon, Sep 10, 2018 at 10:42:59PM +0800, Song Qiang wrote:
> This driver was originally written by ST in 2016 as a misc input device,
> and hasn't been maintained for a long time. I grabbed some code from
> it's API and reformed it to a iio proximity device driver.
> This version of driver uses
On Mon, Sep 10, 2018 at 07:36:51PM +0200, Julien Folly wrote:
>
> Signed-off-by: Julien Folly
> Acked-by: Evgeniy Polyakov
> ---
> drivers/w1/slaves/w1_ds2438.c | 66
> ++-
> 1 file changed, 52 insertions(+), 14 deletions(-)
Hi,
This is the friendly
On Mon, Sep 10, 2018 at 07:36:51PM +0200, Julien Folly wrote:
>
> Signed-off-by: Julien Folly
> Acked-by: Evgeniy Polyakov
> ---
> drivers/w1/slaves/w1_ds2438.c | 66
> ++-
> 1 file changed, 52 insertions(+), 14 deletions(-)
Hi,
This is the friendly
Olof/All,
On 18-09-04 03:13 AM, Grant Likely wrote:
Hey folks. More comments below, but the short answer is I really don't
see what the problem is. Distros cannot easily support platforms that
require a dtb= parameter, and so they probably won't. They may or may
not disable 'dtb=', depending
Olof/All,
On 18-09-04 03:13 AM, Grant Likely wrote:
Hey folks. More comments below, but the short answer is I really don't
see what the problem is. Distros cannot easily support platforms that
require a dtb= parameter, and so they probably won't. They may or may
not disable 'dtb=', depending
The patch
spi: spi-mem: Adjust op len based on message/transfer size limitations
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the
The patch
spi: spi-mem: Adjust op len based on message/transfer size limitations
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the
Am Montag, 10. September 2018, 19:26:55 CEST schrieb Manivannan Sadhasivam:
> Hi Heiko,
>
> On Mon, Sep 10, 2018 at 07:22:26PM +0200, Heiko Stuebner wrote:
> > Am Montag, 10. September 2018, 17:13:54 CEST schrieb Manivannan Sadhasivam:
> > > Add devicetree binding for Rock960 board from Vamrs
The patch
ASoC: pxa: switch to new ac97 bus support
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to
Am Montag, 10. September 2018, 19:26:55 CEST schrieb Manivannan Sadhasivam:
> Hi Heiko,
>
> On Mon, Sep 10, 2018 at 07:22:26PM +0200, Heiko Stuebner wrote:
> > Am Montag, 10. September 2018, 17:13:54 CEST schrieb Manivannan Sadhasivam:
> > > Add devicetree binding for Rock960 board from Vamrs
The patch
ASoC: pxa: switch to new ac97 bus support
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to
On 08.09.2018 14:24, Miguel Ojeda wrote:
> The naked attribute is supported by at least gcc >= 4.6 (for ARM,
> which is the only current user), gcc >= 8 (for x86), clang >= 3.1
> and icc >= 13. See https://godbolt.org/z/350Dyc
>
> Therefore, move it out of compiler-gcc.h so that the definition
>
On 08.09.2018 14:24, Miguel Ojeda wrote:
> The naked attribute is supported by at least gcc >= 4.6 (for ARM,
> which is the only current user), gcc >= 8 (for x86), clang >= 3.1
> and icc >= 13. See https://godbolt.org/z/350Dyc
>
> Therefore, move it out of compiler-gcc.h so that the definition
>
On Wed 22 Aug 10:36 PDT 2018, Douglas Anderson wrote:
> Set the various nodes to "okay" and hook up the regulators.
>
> NOTE: For now the main USB port (the one that goes out the Type C
> connector) is forced to host. Eventually someone will need to get the
> Type C detection hooked up and get
On Wed 22 Aug 10:36 PDT 2018, Douglas Anderson wrote:
> Set the various nodes to "okay" and hook up the regulators.
>
> NOTE: For now the main USB port (the one that goes out the Type C
> connector) is forced to host. Eventually someone will need to get the
> Type C detection hooked up and get
On Wed 22 Aug 10:36 PDT 2018, Douglas Anderson wrote:
> diff --git a/arch/arm64/boot/dts/qcom/sdm845-mtp.dts
> b/arch/arm64/boot/dts/qcom/sdm845-mtp.dts
[..]
> +
> + vdd_qusb_hs0:
> + vdda_hp_pcie_core:
> + vdda_mipi_csi0_0p9:
> +
On Wed 22 Aug 10:36 PDT 2018, Douglas Anderson wrote:
> diff --git a/arch/arm64/boot/dts/qcom/sdm845-mtp.dts
> b/arch/arm64/boot/dts/qcom/sdm845-mtp.dts
[..]
> +
> + vdd_qusb_hs0:
> + vdda_hp_pcie_core:
> + vdda_mipi_csi0_0p9:
> +
Instead of defining symbols already defined in
linux/platform_data/gpio-omap.h, use that header file.
Since we include the header into an assembler code, prevent C only bits
from being read in.
Signed-off-by: Janusz Krzysztofik
---
arch/arm/mach-omap1/ams-delta-fiq-handler.S | 12 +++-
Instead of defining symbols already defined in
linux/platform_data/gpio-omap.h, use that header file.
Since we include the header into an assembler code, prevent C only bits
from being read in.
Signed-off-by: Janusz Krzysztofik
---
arch/arm/mach-omap1/ams-delta-fiq-handler.S | 12 +++-
Hi Linus,
On Fri, Sep 07, 2018 at 10:51:19AM -0700, Linus Torvalds wrote:
> On Fri, Sep 7, 2018 at 8:45 AM Will Deacon wrote:
> >
> > Just one small fix here, preventing a VM_WARN_ON when a !present PMD/PUD
> > is "freed" as part of a huge ioremap() operation. The correct behaviour
> > is to
Hi Linus,
On Fri, Sep 07, 2018 at 10:51:19AM -0700, Linus Torvalds wrote:
> On Fri, Sep 7, 2018 at 8:45 AM Will Deacon wrote:
> >
> > Just one small fix here, preventing a VM_WARN_ON when a !present PMD/PUD
> > is "freed" as part of a huge ioremap() operation. The correct behaviour
> > is to
Hi,
On 08.09.2018 14:24, Miguel Ojeda wrote:
> Commit 9c695203a7dd ("compiler-gcc.h: gcc-4.5 needs noclone
> and noinline on __naked functions") added noinline and noclone
> as a workaround for a gcc 4.5 bug, which was resolved in 4.6.0.
>
> Since now the minimum gcc supported version is 4.6,
>
Hi,
On 08.09.2018 14:24, Miguel Ojeda wrote:
> Commit 9c695203a7dd ("compiler-gcc.h: gcc-4.5 needs noclone
> and noinline on __naked functions") added noinline and noclone
> as a workaround for a gcc 4.5 bug, which was resolved in 4.6.0.
>
> Since now the minimum gcc supported version is 4.6,
>
On Wed 22 Aug 10:36 PDT 2018, Douglas Anderson wrote:
> From: Manu Gautam
>
> This adds nodes for USB and related PHYs.
>
> Signed-off-by: Manu Gautam
> [dianders: reworked quite a bit]
> Signed-off-by: Douglas Anderson
Reviewed-by: Bjorn Andersson
> ---
>
> Changes in v3:
> - Don't just
On Wed 22 Aug 10:36 PDT 2018, Douglas Anderson wrote:
> From: Manu Gautam
>
> This adds nodes for USB and related PHYs.
>
> Signed-off-by: Manu Gautam
> [dianders: reworked quite a bit]
> Signed-off-by: Douglas Anderson
Reviewed-by: Bjorn Andersson
> ---
>
> Changes in v3:
> - Don't just
Hi Sahitya,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on f2fs/dev-test]
[also build test ERROR on next-20180910]
[cannot apply to v4.19-rc3]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https
Hi Sahitya,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on f2fs/dev-test]
[also build test ERROR on next-20180910]
[cannot apply to v4.19-rc3]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https
On 9/10/18 10:20 AM, Davidlohr Bueso wrote:
> On Mon, 10 Sep 2018, Waiman Long wrote:
>> On 09/08/2018 12:13 AM, John Hubbard wrote:
[...]
>>> It's also interesting that there are two main huge page systems (THP and
>>> Hugetlbfs), and I sometimes
>>> wonder the obvious thing to wonder: are these
On 9/10/18 10:20 AM, Davidlohr Bueso wrote:
> On Mon, 10 Sep 2018, Waiman Long wrote:
>> On 09/08/2018 12:13 AM, John Hubbard wrote:
[...]
>>> It's also interesting that there are two main huge page systems (THP and
>>> Hugetlbfs), and I sometimes
>>> wonder the obvious thing to wonder: are these
In functions snd_soc_get_volsw_sx() or snd_soc_put_volsw_sx(),
if the result of (min + max) is negative, then fls() returns
signed integer with value as 32. This leads to signed integer
overflow as complete operation is considered as signed integer.
UBSAN: Undefined behaviour in
In functions snd_soc_get_volsw_sx() or snd_soc_put_volsw_sx(),
if the result of (min + max) is negative, then fls() returns
signed integer with value as 32. This leads to signed integer
overflow as complete operation is considered as signed integer.
UBSAN: Undefined behaviour in
On Thu, Aug 30, 2018 at 10:34:20AM +0800, Jia-Ju Bai wrote:
> My static tool DSAC reports many sleep-in-atomic-context bugs involving
> regmap_lock_mutex(), so I wonder whether this function is possible to be
> executed in atomic context.
Have you actually analyzed the code paths that are really
On Thu, Aug 30, 2018 at 10:34:20AM +0800, Jia-Ju Bai wrote:
> My static tool DSAC reports many sleep-in-atomic-context bugs involving
> regmap_lock_mutex(), so I wonder whether this function is possible to be
> executed in atomic context.
Have you actually analyzed the code paths that are really
Em Mon, Sep 10, 2018 at 11:18:30AM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Mon, Sep 10, 2018 at 10:47:54AM -0300, Arnaldo Carvalho de Melo escreveu:
> > Em Mon, Sep 10, 2018 at 12:31:54PM +0200, Jiri Olsa escreveu:
> > > On Mon, Sep 10, 2018 at 03:28:11PM +0530, Ravi Bangoria wrote:
> > > >
Em Mon, Sep 10, 2018 at 11:18:30AM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Mon, Sep 10, 2018 at 10:47:54AM -0300, Arnaldo Carvalho de Melo escreveu:
> > Em Mon, Sep 10, 2018 at 12:31:54PM +0200, Jiri Olsa escreveu:
> > > On Mon, Sep 10, 2018 at 03:28:11PM +0530, Ravi Bangoria wrote:
> > > >
Hi all,
Just to say that I've pushed the base tlb.h changes to a stable branch
here:
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git tlb/asm-generic
and this is already in -next via the arm64 tree. Feel free to pull this
into your own trees if you need it too.
Cheers,
Will
Hi all,
Just to say that I've pushed the base tlb.h changes to a stable branch
here:
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git tlb/asm-generic
and this is already in -next via the arm64 tree. Feel free to pull this
into your own trees if you need it too.
Cheers,
Will
On 09/10, Oleg Nesterov wrote:
>
> On 09/10, Kees Cook wrote:
> >
> > On Mon, Sep 10, 2018 at 9:41 AM, Kees Cook wrote:
> > > On Mon, Sep 10, 2018 at 5:29 AM, Oleg Nesterov wrote:
> > >> Hi Kees,
> > >>
> > >> I was thinking about backporting the commit 98da7d08850fb8bde
> > >> ("fs/exec.c:
On 09/10, Oleg Nesterov wrote:
>
> On 09/10, Kees Cook wrote:
> >
> > On Mon, Sep 10, 2018 at 9:41 AM, Kees Cook wrote:
> > > On Mon, Sep 10, 2018 at 5:29 AM, Oleg Nesterov wrote:
> > >> Hi Kees,
> > >>
> > >> I was thinking about backporting the commit 98da7d08850fb8bde
> > >> ("fs/exec.c:
Currently we use ktime_us_delta() to calculate last residency and
state usage unconditionally, it makes no sense to do this calculation
when we fails to enter any idle state.
It can be optimize by moving the calculation after entered_state >= 0
While at it, merge those comment blocks into one
Currently we use ktime_us_delta() to calculate last residency and
state usage unconditionally, it makes no sense to do this calculation
when we fails to enter any idle state.
It can be optimize by moving the calculation after entered_state >= 0
While at it, merge those comment blocks into one
Using the kernel 4.19.0-rc2 it works now, so With the fix for not
calling fput when memfd == NULL the patch is
Reviewed-By: Gert Wollny
best,
Gert
Am Montag, den 10.09.2018, 15:30 +0200 schrieb Gerd Hoffmann:
> On Mon, Sep 10, 2018 at 01:31:08PM +0200, Gert Wollny wrote:
> > Am Montag, den
Using the kernel 4.19.0-rc2 it works now, so With the fix for not
calling fput when memfd == NULL the patch is
Reviewed-By: Gert Wollny
best,
Gert
Am Montag, den 10.09.2018, 15:30 +0200 schrieb Gerd Hoffmann:
> On Mon, Sep 10, 2018 at 01:31:08PM +0200, Gert Wollny wrote:
> > Am Montag, den
On Tue, Apr 10, 2018 at 02:41:54PM +0200, Bartlomiej Zolnierkiewicz wrote:
> Hi,
>
> [devm]_thermal_zone_of_sensor_register() is used to register
> thermal sensor by thermal drivers using DeviceTree. Besides
> registering sensor this function also immediately enables it
> (using ->set_mode
On Tue, Apr 10, 2018 at 02:41:54PM +0200, Bartlomiej Zolnierkiewicz wrote:
> Hi,
>
> [devm]_thermal_zone_of_sensor_register() is used to register
> thermal sensor by thermal drivers using DeviceTree. Besides
> registering sensor this function also immediately enables it
> (using ->set_mode
Signed-off-by: Julien Folly
Acked-by: Evgeniy Polyakov
---
drivers/w1/slaves/w1_ds2438.c | 66 ++-
1 file changed, 52 insertions(+), 14 deletions(-)
diff --git a/drivers/w1/slaves/w1_ds2438.c b/drivers/w1/slaves/w1_ds2438.c
index bf641a1..7c4e33d
Signed-off-by: Julien Folly
Acked-by: Evgeniy Polyakov
---
drivers/w1/slaves/w1_ds2438.c | 66 ++-
1 file changed, 52 insertions(+), 14 deletions(-)
diff --git a/drivers/w1/slaves/w1_ds2438.c b/drivers/w1/slaves/w1_ds2438.c
index bf641a1..7c4e33d
On 09/10/2018 01:15 PM, Davidlohr Bueso wrote:
> On Mon, 10 Sep 2018, Waiman Long wrote:
>
>> One major issue with a combined count/owner is that we may have to use
>> cmpxchg for reader lock which will certainly impact reader-heavy
>> workloads. I have also thought about ways to compress the task
On 09/10/2018 01:15 PM, Davidlohr Bueso wrote:
> On Mon, 10 Sep 2018, Waiman Long wrote:
>
>> One major issue with a combined count/owner is that we may have to use
>> cmpxchg for reader lock which will certainly impact reader-heavy
>> workloads. I have also thought about ways to compress the task
Hi Heiko,
On Mon, Sep 10, 2018 at 07:22:26PM +0200, Heiko Stuebner wrote:
> Am Montag, 10. September 2018, 17:13:54 CEST schrieb Manivannan Sadhasivam:
> > Add devicetree binding for Rock960 board from Vamrs Limited.
> >
> > Signed-off-by: Manivannan Sadhasivam
> > ---
> >
Hi Heiko,
On Mon, Sep 10, 2018 at 07:22:26PM +0200, Heiko Stuebner wrote:
> Am Montag, 10. September 2018, 17:13:54 CEST schrieb Manivannan Sadhasivam:
> > Add devicetree binding for Rock960 board from Vamrs Limited.
> >
> > Signed-off-by: Manivannan Sadhasivam
> > ---
> >
If capture and playback are started on different channel (I2S/BT)
there is a possibilty that channel information passed from machine driver
is overwritten before the configuration is done in dma driver.
Example:
113.597588: cz_max_startup: ---playback sets BT channel
113.597694: cz_dmic1_startup:
If capture and playback are started on different channel (I2S/BT)
there is a possibilty that channel information passed from machine driver
is overwritten before the configuration is done in dma driver.
Example:
113.597588: cz_max_startup: ---playback sets BT channel
113.597694: cz_dmic1_startup:
On 08/31/2018 01:58 AM, Jarkko Sakkinen wrote:
> Just the change to the commit message. Mislooked patchwork, the typo was
> in my response :-) I'll do recheck for 2/2. Check those comments before
> v6 if there is anything else.
Hi,
I have done the changes you requested and ran the "checkpatch.pl
On 08/31/2018 01:58 AM, Jarkko Sakkinen wrote:
> Just the change to the commit message. Mislooked patchwork, the typo was
> in my response :-) I'll do recheck for 2/2. Check those comments before
> v6 if there is anything else.
Hi,
I have done the changes you requested and ran the "checkpatch.pl
On 9/10/2018 5:08 PM, Mark Brown wrote:
> On Mon, Sep 10, 2018 at 01:36:29PM +0530, Akshu Agrawal wrote:
>> If capture and playback are started on different channel (I2S/BT)
>> there is a possibilty that channel information passed from machine driver
>> is overwritten before the configuration
Am Montag, 10. September 2018, 17:13:54 CEST schrieb Manivannan Sadhasivam:
> Add devicetree binding for Rock960 board from Vamrs Limited.
>
> Signed-off-by: Manivannan Sadhasivam
> ---
> Documentation/devicetree/bindings/arm/rockchip.txt | 4
> 1 file changed, 4 insertions(+)
>
> diff
On 9/10/2018 5:08 PM, Mark Brown wrote:
> On Mon, Sep 10, 2018 at 01:36:29PM +0530, Akshu Agrawal wrote:
>> If capture and playback are started on different channel (I2S/BT)
>> there is a possibilty that channel information passed from machine driver
>> is overwritten before the configuration
Am Montag, 10. September 2018, 17:13:54 CEST schrieb Manivannan Sadhasivam:
> Add devicetree binding for Rock960 board from Vamrs Limited.
>
> Signed-off-by: Manivannan Sadhasivam
> ---
> Documentation/devicetree/bindings/arm/rockchip.txt | 4
> 1 file changed, 4 insertions(+)
>
> diff
On Fri, Sep 07, 2018 at 11:54:46PM +0200, Cedric Roux wrote:
> The mini2440 computer uses "active high" to signal that the "write protect"
> of the inserted MMC is set. The current code uses the opposite, leading to
> a wrong detection of write protection. The solution is simply to use
>
On Fri, Sep 07, 2018 at 11:54:46PM +0200, Cedric Roux wrote:
> The mini2440 computer uses "active high" to signal that the "write protect"
> of the inserted MMC is set. The current code uses the opposite, leading to
> a wrong detection of write protection. The solution is simply to use
>
On 09/10, Kees Cook wrote:
>
> On Mon, Sep 10, 2018 at 9:41 AM, Kees Cook wrote:
> > On Mon, Sep 10, 2018 at 5:29 AM, Oleg Nesterov wrote:
> >> Hi Kees,
> >>
> >> I was thinking about backporting the commit 98da7d08850fb8bde
> >> ("fs/exec.c: account for argv/envp pointers"), but I am not sure
>
On 09/10, Kees Cook wrote:
>
> On Mon, Sep 10, 2018 at 9:41 AM, Kees Cook wrote:
> > On Mon, Sep 10, 2018 at 5:29 AM, Oleg Nesterov wrote:
> >> Hi Kees,
> >>
> >> I was thinking about backporting the commit 98da7d08850fb8bde
> >> ("fs/exec.c: account for argv/envp pointers"), but I am not sure
>
On Mon, 10 Sep 2018, Waiman Long wrote:
On 09/08/2018 12:13 AM, John Hubbard wrote:
Hi Daniel and all,
I'm interested in the first 3 of those 4 topics, so if it doesn't conflict with
HMM topics or
fix-gup-with-dma topics, I'd like to attend. GPUs generally need to access
large chunks of
On Mon, 10 Sep 2018, Waiman Long wrote:
On 09/08/2018 12:13 AM, John Hubbard wrote:
Hi Daniel and all,
I'm interested in the first 3 of those 4 topics, so if it doesn't conflict with
HMM topics or
fix-gup-with-dma topics, I'd like to attend. GPUs generally need to access
large chunks of
Add a ptr to struct tpm_space to the file_priv and consolidate
of the write operations for the two interfaces.
Tested-by: Philip Tricca
Signed-off-by: Tadeusz Struk
---
drivers/char/tpm/tpm-dev-common.c |8 +---
drivers/char/tpm/tpm-dev.c| 10 ++
The TCG SAPI specification [1] defines a set of functions, which allow
applications to use the TPM device in either blocking or non-blocking fashion.
Each command defined by the specification has a corresponding
Tss2_Sys__Prepare() and Tss2_Sys__Complete() call, which
together with
Add a ptr to struct tpm_space to the file_priv and consolidate
of the write operations for the two interfaces.
Tested-by: Philip Tricca
Signed-off-by: Tadeusz Struk
---
drivers/char/tpm/tpm-dev-common.c |8 +---
drivers/char/tpm/tpm-dev.c| 10 ++
The TCG SAPI specification [1] defines a set of functions, which allow
applications to use the TPM device in either blocking or non-blocking fashion.
Each command defined by the specification has a corresponding
Tss2_Sys__Prepare() and Tss2_Sys__Complete() call, which
together with
On 09/10, Kees Cook wrote:
>
> > So get_arg_page() does
> >
> > /*
> > * Since the stack will hold pointers to the strings, we
> > * must account for them as well.
> > *
> > * The size calculation is the entire vma
Currently the TPM driver only supports blocking calls, which doesn't allow
asynchronous IO operations to the TPM hardware.
This patch changes it and adds support for nonblocking write and a new poll
function to enable applications, which want to take advantage of this.
Tested-by: Philip Tricca
On 09/10, Kees Cook wrote:
>
> > So get_arg_page() does
> >
> > /*
> > * Since the stack will hold pointers to the strings, we
> > * must account for them as well.
> > *
> > * The size calculation is the entire vma
Currently the TPM driver only supports blocking calls, which doesn't allow
asynchronous IO operations to the TPM hardware.
This patch changes it and adds support for nonblocking write and a new poll
function to enable applications, which want to take advantage of this.
Tested-by: Philip Tricca
Signed-off-by: Horia Geantă
---
drivers/bus/fsl-mc/fsl-mc-bus.c | 5 +
include/linux/fsl/mc.h | 6 ++
2 files changed, 11 insertions(+)
diff --git a/drivers/bus/fsl-mc/fsl-mc-bus.c b/drivers/bus/fsl-mc/fsl-mc-bus.c
index 5d8266c6571f..4552b06fe601 100644
---
Signed-off-by: Horia Geantă
---
drivers/bus/fsl-mc/fsl-mc-bus.c | 5 +
include/linux/fsl/mc.h | 6 ++
2 files changed, 11 insertions(+)
diff --git a/drivers/bus/fsl-mc/fsl-mc-bus.c b/drivers/bus/fsl-mc/fsl-mc-bus.c
index 5d8266c6571f..4552b06fe601 100644
---
401 - 500 of 1628 matches
Mail list logo
