On 11/15/18 at 08:30am, Michal Hocko wrote:
> On Thu 15-11-18 13:10:34, Baoquan He wrote:
> > On 11/14/18 at 04:00pm, Michal Hocko wrote:
> > > On Wed 14-11-18 22:52:50, Baoquan He wrote:
> > > > On 11/14/18 at 10:01am, Michal Hocko wrote:
> > > > > I have seen an issue when the migration cannot
On 11/15/18 at 08:30am, Michal Hocko wrote:
> On Thu 15-11-18 13:10:34, Baoquan He wrote:
> > On 11/14/18 at 04:00pm, Michal Hocko wrote:
> > > On Wed 14-11-18 22:52:50, Baoquan He wrote:
> > > > On 11/14/18 at 10:01am, Michal Hocko wrote:
> > > > > I have seen an issue when the migration cannot
On Thu, Nov 15, 2018 at 01:12:53AM -0600, Bjorn Helgaas wrote:
> > and I kinda see the point of maybe not having your ssh username in the
> > URL. Not that it is a big deal for us, k.org users though.
>
> Sorry, I don't understand the problem. I have this in my .gitconfig:
>
> [url
On Thu, Nov 15, 2018 at 01:12:53AM -0600, Bjorn Helgaas wrote:
> > and I kinda see the point of maybe not having your ssh username in the
> > URL. Not that it is a big deal for us, k.org users though.
>
> Sorry, I don't understand the problem. I have this in my .gitconfig:
>
> [url
On Wed, 14 Nov 2018 22:10:52 +0100
Patrick Staehlin wrote:
> On 14.11.18 16:49, Masami Hiramatsu wrote:
> > On Wed, 14 Nov 2018 00:37:30 -0800
> > Masami Hiramatsu wrote:
> >
> >>> +
> >>> +static int __kprobes patch_text(kprobe_opcode_t *addr, u32 opcode)
> >>> +{
> >>> + if
On Wed, 14 Nov 2018 22:10:52 +0100
Patrick Staehlin wrote:
> On 14.11.18 16:49, Masami Hiramatsu wrote:
> > On Wed, 14 Nov 2018 00:37:30 -0800
> > Masami Hiramatsu wrote:
> >
> >>> +
> >>> +static int __kprobes patch_text(kprobe_opcode_t *addr, u32 opcode)
> >>> +{
> >>> + if
On Wed 14-11-18 15:18:09, Andrew Morton wrote:
> On Wed, 14 Nov 2018 08:14:42 +0100 Michal Hocko wrote:
>
> > It seems there were no objections here. So can we have it in linux-next
> > for a wider testing a possibly target the next merge window?
> >
>
> top-posting sucks!
I thought it would
This bitmap parameter allows the user to add/remove modes for
DFR_CHANGE_ROW to cycle through.
Users who wish to cycle through WEB_BROWSER_MODE and/or
WEB_CONFERENCE_MODE may now do so by enabling corresponding bits.
While some appreciate more modes, I made this feature because I
wanted to lock
On Wed 14-11-18 15:18:09, Andrew Morton wrote:
> On Wed, 14 Nov 2018 08:14:42 +0100 Michal Hocko wrote:
>
> > It seems there were no objections here. So can we have it in linux-next
> > for a wider testing a possibly target the next merge window?
> >
>
> top-posting sucks!
I thought it would
This bitmap parameter allows the user to add/remove modes for
DFR_CHANGE_ROW to cycle through.
Users who wish to cycle through WEB_BROWSER_MODE and/or
WEB_CONFERENCE_MODE may now do so by enabling corresponding bits.
While some appreciate more modes, I made this feature because I
wanted to lock
On Thu 15-11-18 13:10:34, Baoquan He wrote:
> On 11/14/18 at 04:00pm, Michal Hocko wrote:
> > On Wed 14-11-18 22:52:50, Baoquan He wrote:
> > > On 11/14/18 at 10:01am, Michal Hocko wrote:
> > > > I have seen an issue when the migration cannot make a forward progress
> > > > because of a glibc page
On Thu 15-11-18 13:10:34, Baoquan He wrote:
> On 11/14/18 at 04:00pm, Michal Hocko wrote:
> > On Wed 14-11-18 22:52:50, Baoquan He wrote:
> > > On 11/14/18 at 10:01am, Michal Hocko wrote:
> > > > I have seen an issue when the migration cannot make a forward progress
> > > > because of a glibc page
Hi,
> On Nov 9, 2018, at 08:21, Bjorn Helgaas wrote:
>
> On Tue, Nov 06, 2018 at 03:12:13PM +0800, AceLan Kao wrote:
>> It leads to the power consumption raises to 2.2W during s2idle, while
>> it consumes less than 1W during long idle if put SK hynix nvme to D3
>> and then enter s2idle.
>> From
Hi,
> On Nov 9, 2018, at 08:21, Bjorn Helgaas wrote:
>
> On Tue, Nov 06, 2018 at 03:12:13PM +0800, AceLan Kao wrote:
>> It leads to the power consumption raises to 2.2W during s2idle, while
>> it consumes less than 1W during long idle if put SK hynix nvme to D3
>> and then enter s2idle.
>> From
On Wed, Nov 14, 2018 at 11:48:39PM +0100, Borislav Petkov wrote:
> On Wed, Nov 14, 2018 at 05:21:54PM -0500, Konstantin Ryabitsev wrote:
> > For the record, there's nothing wrong with that, it's just a condition
> > that I didn't expect. I have a fix in place that should avoid this in
> > the
On Wed, Nov 14, 2018 at 11:48:39PM +0100, Borislav Petkov wrote:
> On Wed, Nov 14, 2018 at 05:21:54PM -0500, Konstantin Ryabitsev wrote:
> > For the record, there's nothing wrong with that, it's just a condition
> > that I didn't expect. I have a fix in place that should avoid this in
> > the
Output of pcm3060 codec may be configured as single-ended or differential
Signed-off-by: Kirill Marinushkin
Cc: devicet...@vger.kernel.org
---
Hello Mark,
yesterday there was a misunderstanding: when I wrote you
> I think you forgot one patch in the series
you accidently applied the
Output of pcm3060 codec may be configured as single-ended or differential
Signed-off-by: Kirill Marinushkin
Cc: devicet...@vger.kernel.org
---
Hello Mark,
yesterday there was a misunderstanding: when I wrote you
> I think you forgot one patch in the series
you accidently applied the
From: kbuild test robot
drivers/spi/spi-npcm-pspi.c:470:3-8: No need to set .owner here. The core will
do it.
Remove .owner field if calls are used which set it automatically
Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci
Fixes: 2a22f1b30cee ("spi: npcm: add NPCM PSPI
From: kbuild test robot
drivers/spi/spi-npcm-pspi.c:470:3-8: No need to set .owner here. The core will
do it.
Remove .owner field if calls are used which set it automatically
Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci
Fixes: 2a22f1b30cee ("spi: npcm: add NPCM PSPI
Hi Finn
Am 15.11.2018 um 12:54 schrieb Michael Schmitz:
That one does appear to work - different versions of ARAnyM, and
different userland versions though. I'll test that again with the setup
that saw c606b5cf902 fail.
Still fails on that emulator / userland.
Must be a quirk of ARAnyM
On Thu, 2018-11-15 at 14:26 +0800, Ryder Lee wrote:
> This updates bindings for MT7629 pwm controller.
>
> Signed-off-by: Ryder Lee
> ---
> Documentation/devicetree/bindings/pwm/pwm-mediatek.txt | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git
Hi Finn
Am 15.11.2018 um 12:54 schrieb Michael Schmitz:
That one does appear to work - different versions of ARAnyM, and
different userland versions though. I'll test that again with the setup
that saw c606b5cf902 fail.
Still fails on that emulator / userland.
Must be a quirk of ARAnyM
On Thu, 2018-11-15 at 14:26 +0800, Ryder Lee wrote:
> This updates bindings for MT7629 pwm controller.
>
> Signed-off-by: Ryder Lee
> ---
> Documentation/devicetree/bindings/pwm/pwm-mediatek.txt | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git
This updates bindings for the MT7629 SPI-NOR controller.
Signed-off-by: Ryder Lee
---
Documentation/devicetree/bindings/mtd/mtk-quadspi.txt | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/mtd/mtk-quadspi.txt
This updates bindings for the MT7629 SPI-NOR controller.
Signed-off-by: Ryder Lee
---
Documentation/devicetree/bindings/mtd/mtk-quadspi.txt | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/mtd/mtk-quadspi.txt
The quadspi is a generic communication interface which could be shared
with other MediaTek SoCs. Hence rename it to a common one.
Signed-off-by: Ryder Lee
---
drivers/mtd/spi-nor/Kconfig | 16
drivers/mtd/spi-nor/Makefile | 2 +-
2 files changed, 9 insertions(+), 9
The quadspi is a generic communication interface which could be shared
with other MediaTek SoCs. Hence rename it to a common one.
Signed-off-by: Ryder Lee
---
drivers/mtd/spi-nor/Kconfig | 16
drivers/mtd/spi-nor/Makefile | 2 +-
2 files changed, 9 insertions(+), 9
This updates bindings for MT7629 pwm controller.
Signed-off-by: Ryder Lee
---
Documentation/devicetree/bindings/pwm/pwm-mediatek.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/pwm/pwm-mediatek.txt
From: Guochun Mao
SNOR_HWCAPS_READ is a basic read mode for both flash and controller,
it should be supported, so add the capcity for mtk-quadspi.
Signed-off-by: Guochun Mao
Tested-by: Ryder Lee
---
drivers/mtd/spi-nor/mtk-quadspi.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
This updates bindings for MT7629 pwm controller.
Signed-off-by: Ryder Lee
---
Documentation/devicetree/bindings/pwm/pwm-mediatek.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/pwm/pwm-mediatek.txt
From: Guochun Mao
SNOR_HWCAPS_READ is a basic read mode for both flash and controller,
it should be supported, so add the capcity for mtk-quadspi.
Signed-off-by: Guochun Mao
Tested-by: Ryder Lee
---
drivers/mtd/spi-nor/mtk-quadspi.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
From: Guochun Mao
Replace mtd_device_register with mtd_device_parse_register for
parsing partitions.
Add ofpart support.
Signed-off-by: Guochun Mao
Tested-by: Ryder Lee
---
drivers/mtd/spi-nor/mtk-quadspi.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git
From: Guochun Mao
Replace mtd_device_register with mtd_device_parse_register for
parsing partitions.
Add ofpart support.
Signed-off-by: Guochun Mao
Tested-by: Ryder Lee
---
drivers/mtd/spi-nor/mtk-quadspi.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git
Hi Daniel,
thanks for your feedback!
On Thu, Nov 15, 2018 at 2:35 AM Daniel Lezcano
wrote:
>
> On 28/10/2018 13:55, Martin Blumenstingl wrote:
> > This makes the driver use the names from S805 datasheet for the
> > preprocessor #defines. This makes it easier to spot that the driver
> >
Hi Frieder,
With below patch on top of your v5, Read/Write/Erase on CS1 is working fine for
me.
I have tested with JFFS2 mounting and booting also for both CS0 and CS1.
diff --git a/drivers/spi/spi-fsl-qspi.c b/drivers/spi/spi-fsl-qspi.c
index ce45e8e..4467983 100644
---
Hi Daniel,
thanks for your feedback!
On Thu, Nov 15, 2018 at 2:35 AM Daniel Lezcano
wrote:
>
> On 28/10/2018 13:55, Martin Blumenstingl wrote:
> > This makes the driver use the names from S805 datasheet for the
> > preprocessor #defines. This makes it easier to spot that the driver
> >
Hi Frieder,
With below patch on top of your v5, Read/Write/Erase on CS1 is working fine for
me.
I have tested with JFFS2 mounting and booting also for both CS0 and CS1.
diff --git a/drivers/spi/spi-fsl-qspi.c b/drivers/spi/spi-fsl-qspi.c
index ce45e8e..4467983 100644
---
Add a /proc//arch_state interface to expose per-task cpu specific
state values.
Exposing AVX-512 Hi16_ZMM registers usage is for the user space job
scheduler to cluster AVX-512 using tasks together, because these tasks
could cause core turbo frequency drop.
Signed-off-by: Aubrey Li
Cc: Peter
User space tools which do automated task placement need information
about AVX-512 usage of tasks, because AVX-512 usage could cause core
turbo frequency drop and impact the running task on the sibling CPU.
XSAVE header contains a state-component bitmap, which allows software
to discover the state
User space tools which do automated task placement need information
about AVX-512 usage of tasks, because AVX-512 usage could cause core
turbo frequency drop and impact the running task on the sibling CPU.
XSAVE header contains a state-component bitmap, which allows software
to discover the state
Add a /proc//arch_state interface to expose per-task cpu specific
state values.
Exposing AVX-512 Hi16_ZMM registers usage is for the user space job
scheduler to cluster AVX-512 using tasks together, because these tasks
could cause core turbo frequency drop.
Signed-off-by: Aubrey Li
Cc: Peter
On 15/11/18 02:43 AM, Wesley Sheng wrote:
> Hi, Everyone,
>
> This patch series adds support for the Switchtec MRPC DMA mode.
I've reviewed this series from it's conception on github[1] and would
like to see it land in the upstream driver, so for the entire series:
Reviewed-by: Logan
On 15/11/18 02:43 AM, Wesley Sheng wrote:
> Hi, Everyone,
>
> This patch series adds support for the Switchtec MRPC DMA mode.
I've reviewed this series from it's conception on github[1] and would
like to see it land in the upstream driver, so for the entire series:
Reviewed-by: Logan
On Wed, Nov 7, 2018 at 11:30 PM Chen-Yu Tsai wrote:
> > +
> > + speaker_amp: speaker_amp {
> > + compatible = "simple-audio-amplifier";
> > + enable-gpios = < 7 7 GPIO_ACTIVE_HIGH>; /* PH7 */
>
> You might want to add a sound-name-prefix property. See
>
>
On Wed, Nov 7, 2018 at 11:30 PM Chen-Yu Tsai wrote:
> > +
> > + speaker_amp: speaker_amp {
> > + compatible = "simple-audio-amplifier";
> > + enable-gpios = < 7 7 GPIO_ACTIVE_HIGH>; /* PH7 */
>
> You might want to add a sound-name-prefix property. See
>
>
On Wed, Nov 14, 2018 at 07:56:47PM -0800, Florian Fainelli wrote:
>
>
> On November 14, 2018 5:11:25 PM PST, Guenter Roeck wrote:
> >On Thu, Nov 01, 2018 at 11:26:06AM -0700, Florian Fainelli wrote:
> >> It is way too easy to miss enabling SERIAL_OF_PLATFORM which would
> >> result in the
On Wed, Nov 14, 2018 at 07:56:47PM -0800, Florian Fainelli wrote:
>
>
> On November 14, 2018 5:11:25 PM PST, Guenter Roeck wrote:
> >On Thu, Nov 01, 2018 at 11:26:06AM -0700, Florian Fainelli wrote:
> >> It is way too easy to miss enabling SERIAL_OF_PLATFORM which would
> >> result in the
On Wed, Nov 14, 2018 at 07:56:47PM -0800, Florian Fainelli wrote:
>
>
> On November 14, 2018 5:11:25 PM PST, Guenter Roeck wrote:
> >On Thu, Nov 01, 2018 at 11:26:06AM -0700, Florian Fainelli wrote:
> >> It is way too easy to miss enabling SERIAL_OF_PLATFORM which would
> >> result in the
On Wed, Nov 14, 2018 at 07:56:47PM -0800, Florian Fainelli wrote:
>
>
> On November 14, 2018 5:11:25 PM PST, Guenter Roeck wrote:
> >On Thu, Nov 01, 2018 at 11:26:06AM -0700, Florian Fainelli wrote:
> >> It is way too easy to miss enabling SERIAL_OF_PLATFORM which would
> >> result in the
On Wed, Nov 14, 2018 at 06:47:57PM +, Joseph Myers wrote:
> On Wed, 14 Nov 2018, Daniel Colascione wrote:
>
> > A good demonstration of a new commitment to pragmatism would be
> > merging the trivial wrappers for gettid(2).
>
> I support the addition of gettid (for use with those syscalls
On Wed, Nov 14, 2018 at 06:47:57PM +, Joseph Myers wrote:
> On Wed, 14 Nov 2018, Daniel Colascione wrote:
>
> > A good demonstration of a new commitment to pragmatism would be
> > merging the trivial wrappers for gettid(2).
>
> I support the addition of gettid (for use with those syscalls
On 11/14/18 at 04:00pm, Michal Hocko wrote:
> On Wed 14-11-18 22:52:50, Baoquan He wrote:
> > On 11/14/18 at 10:01am, Michal Hocko wrote:
> > > I have seen an issue when the migration cannot make a forward progress
> > > because of a glibc page with a reference count bumping up and down. Most
> >
On 11/14/18 at 04:00pm, Michal Hocko wrote:
> On Wed 14-11-18 22:52:50, Baoquan He wrote:
> > On 11/14/18 at 10:01am, Michal Hocko wrote:
> > > I have seen an issue when the migration cannot make a forward progress
> > > because of a glibc page with a reference count bumping up and down. Most
> >
From: "huijin.park"
This patch casts the "len" parameter to an unsigned int.
The callers of erase_write() pass the "len" parameter as unsigned int.
Signed-off-by: huijin.park
---
drivers/mtd/mtdblock.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
From: "huijin.park"
This patch casts the "len" parameter to an unsigned int.
The callers of erase_write() pass the "len" parameter as unsigned int.
Signed-off-by: huijin.park
---
drivers/mtd/mtdblock.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
From: "huijin.park"
The "params->size" is defined as "u64".
And "info->sector_size" and "info->n_sectors" are defined as
unsigned int and u16.
Thus, u64 data might have strange data(loss data) if the result
overflows an unsigned int.
This patch casts "info->sector_size" and "info->n_sectors" to
From: "huijin.park"
The "params->size" is defined as "u64".
And "info->sector_size" and "info->n_sectors" are defined as
unsigned int and u16.
Thus, u64 data might have strange data(loss data) if the result
overflows an unsigned int.
This patch casts "info->sector_size" and "info->n_sectors" to
Hi all,
Changes since 20181114:
New trees: gnss-fixes, gnss
The tip tree still had its build failure for which I applied a fix patch.
Non-merge commits (relative to Linus' tree): 2799
2907 files changed, 117529 insertions(+), 99581 deletions
Hi all,
Changes since 20181114:
New trees: gnss-fixes, gnss
The tip tree still had its build failure for which I applied a fix patch.
Non-merge commits (relative to Linus' tree): 2799
2907 files changed, 117529 insertions(+), 99581 deletions
On Thu, 15 Nov 2018, Michael Schmitz wrote:
> Hi Finn,
>
> On 14/11/18 3:58 PM, Michael Schmitz wrote:
> > Hi Finn,
> >
> > Am 14.11.2018 um 14:08 schrieb Michael Schmitz:
> > > > Can you also test tree fbf8405cd982 please?
> > > >
> > > My tests were on c606b5cf902 in case it wasn't clear.
On Thu, 15 Nov 2018, Michael Schmitz wrote:
> Hi Finn,
>
> On 14/11/18 3:58 PM, Michael Schmitz wrote:
> > Hi Finn,
> >
> > Am 14.11.2018 um 14:08 schrieb Michael Schmitz:
> > > > Can you also test tree fbf8405cd982 please?
> > > >
> > > My tests were on c606b5cf902 in case it wasn't clear.
Geert Uytterhoeven writes:
> Below is the list of build error/warning regressions/improvements in
> v4.20-rc2[1] compared to v4.19[2].
>
> Summarized:
> - build errors: +3/-0
> - build warnings: +123/-12803
>
> JFYI, when comparing v4.20-rc2[1] to v4.20-rc1[3], the summaries are:
> - build
Geert Uytterhoeven writes:
> Below is the list of build error/warning regressions/improvements in
> v4.20-rc2[1] compared to v4.19[2].
>
> Summarized:
> - build errors: +3/-0
> - build warnings: +123/-12803
>
> JFYI, when comparing v4.20-rc2[1] to v4.20-rc1[3], the summaries are:
> - build
Hi,
On 15/11/18 3:53 AM, Sasha Levin wrote:
> From: Vignesh R
>
> [ Upstream commit 5b277402deac0691226a947df71c581686bd4020 ]
This patch depends on c77245722fb4 ("arm64: Add support for TI's K3
Multicore SoC architecture") which adds ARCH_K3 Kconfig symbol and
merged to mainline in v4.19.
Hi,
On 15/11/18 3:53 AM, Sasha Levin wrote:
> From: Vignesh R
>
> [ Upstream commit 5b277402deac0691226a947df71c581686bd4020 ]
This patch depends on c77245722fb4 ("arm64: Add support for TI's K3
Multicore SoC architecture") which adds ARCH_K3 Kconfig symbol and
merged to mainline in v4.19.
USLUGI REPETITORA 1-7 klass.
Nizkie ceni
7:27:08 AM
USLUGI REPETITORA 1-7 klass.
Nizkie ceni
7:27:08 AM
Add regulator support to turn on cpvdd and avdd in probe.
If a regulator is not given from device tree, a dummy regulator will be
used.
Signed-off-by: Cheng-Yi Chiang
---
sound/soc/codecs/rt5663.c | 68 +++
1 file changed, 61 insertions(+), 7 deletions(-)
Add regulator support to turn on cpvdd and avdd in probe.
If a regulator is not given from device tree, a dummy regulator will be
used.
Signed-off-by: Cheng-Yi Chiang
---
sound/soc/codecs/rt5663.c | 68 +++
1 file changed, 61 insertions(+), 7 deletions(-)
rt5663 codec driver will support setting CPVDD and AVDD power supply
from device tree.
Signed-off-by: Cheng-Yi Chiang
---
Fixed the commit title of v1.
Documentation/devicetree/bindings/sound/rt5663.txt | 5 +
1 file changed, 5 insertions(+)
diff --git
rt5663 codec driver will support setting CPVDD and AVDD power supply
from device tree.
Signed-off-by: Cheng-Yi Chiang
---
Fixed the commit title of v1.
Documentation/devicetree/bindings/sound/rt5663.txt | 5 +
1 file changed, 5 insertions(+)
diff --git
On Wed, 14 Nov 2018, Russell King - ARM Linux wrote:
> However, I now see (having searched mailing lists) what you are trying
> to do - you have _not_ copied me or the mailing lists I'm on with your
> cover message, so I'm *totally* lacking in the context of your patch
> series, particularly
On Wed, 14 Nov 2018, Russell King - ARM Linux wrote:
> However, I now see (having searched mailing lists) what you are trying
> to do - you have _not_ copied me or the mailing lists I'm on with your
> cover message, so I'm *totally* lacking in the context of your patch
> series, particularly
Hi Oleg,
On 11/14/18 9:36 PM, Oleg Nesterov wrote:
> On 11/14, Ravi Bangoria wrote:
>>
>> syzbot reported a kernel crash with delayed_uprobe_remove():
>> https://lkml.org/lkml/2018/11/1/1244
>>
>> Backtrace mentioned in the link points to a race between process
>> exit and uprobe_unregister().
Thank you for all your comments.
Thanks,
Kyungtae Kim
On Wed, Nov 14, 2018 at 11:05 AM Paul E. McKenney wrote:
>
> On Wed, Nov 14, 2018 at 04:31:11PM +0100, Alexander Potapenko wrote:
> > On Wed, Nov 14, 2018 at 4:09 PM Paul E. McKenney
> > wrote:
> > >
> > > On Wed, Nov 14, 2018 at 04:03:33AM
Hi Oleg,
On 11/14/18 9:36 PM, Oleg Nesterov wrote:
> On 11/14, Ravi Bangoria wrote:
>>
>> syzbot reported a kernel crash with delayed_uprobe_remove():
>> https://lkml.org/lkml/2018/11/1/1244
>>
>> Backtrace mentioned in the link points to a race between process
>> exit and uprobe_unregister().
Thank you for all your comments.
Thanks,
Kyungtae Kim
On Wed, Nov 14, 2018 at 11:05 AM Paul E. McKenney wrote:
>
> On Wed, Nov 14, 2018 at 04:31:11PM +0100, Alexander Potapenko wrote:
> > On Wed, Nov 14, 2018 at 4:09 PM Paul E. McKenney
> > wrote:
> > >
> > > On Wed, Nov 14, 2018 at 04:03:33AM
Introducing the use of asm macros in c-code broke distcc, since it only
sends the preprocessed source file. The solution is to break the
compilation into two separate phases of compilation and assembly, and
between the two concatenate the assembly macros and the compiled (yet
not assembled) source
Changes in macros.S should trigger the recompilation of all C files, as
the macros might need to affect their compilation.
Acked-by: Ingo Molnar
Signed-off-by: Nadav Amit
---
scripts/Makefile.build | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/scripts/Makefile.build
There has been a complaint that the recent use of assembly macros in C
files broke distcc. The first patch fixes this issue.
The second patch adds a dependency for all C files on macros.S, to
trigger their recompilation when the relevant macros change.
I think it will be better to get the
Introducing the use of asm macros in c-code broke distcc, since it only
sends the preprocessed source file. The solution is to break the
compilation into two separate phases of compilation and assembly, and
between the two concatenate the assembly macros and the compiled (yet
not assembled) source
Changes in macros.S should trigger the recompilation of all C files, as
the macros might need to affect their compilation.
Acked-by: Ingo Molnar
Signed-off-by: Nadav Amit
---
scripts/Makefile.build | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/scripts/Makefile.build
There has been a complaint that the recent use of assembly macros in C
files broke distcc. The first patch fixes this issue.
The second patch adds a dependency for all C files on macros.S, to
trigger their recompilation when the relevant macros change.
I think it will be better to get the
On November 14, 2018 5:11:25 PM PST, Guenter Roeck wrote:
>On Thu, Nov 01, 2018 at 11:26:06AM -0700, Florian Fainelli wrote:
>> It is way too easy to miss enabling SERIAL_OF_PLATFORM which would
>> result in the inability for the kernel to have a valid console
>device,
>> which can be seen
On November 14, 2018 5:11:25 PM PST, Guenter Roeck wrote:
>On Thu, Nov 01, 2018 at 11:26:06AM -0700, Florian Fainelli wrote:
>> It is way too easy to miss enabling SERIAL_OF_PLATFORM which would
>> result in the inability for the kernel to have a valid console
>device,
>> which can be seen
On 01-10-18, 11:51, Vinod Koul wrote:
> This adds prng-ee nodes for msm8996 and sdm845
Ping Andy, would appreciate if you can pick these up.
Thanks
>
> changes in v6:
> - Fix comments given by Stan
>
> changes in v5:
> - Add more description in patch logs
>
> changes in v4:
> - Fix node
On 01-10-18, 11:51, Vinod Koul wrote:
> This adds prng-ee nodes for msm8996 and sdm845
Ping Andy, would appreciate if you can pick these up.
Thanks
>
> changes in v6:
> - Fix comments given by Stan
>
> changes in v5:
> - Add more description in patch logs
>
> changes in v4:
> - Fix node
From: Xavier Deguillard
Julien will be replacing me as the vmw_balloon maintainer.
Cc: Julien Freche
Signed-off-by: Xavier Deguillard
Signed-off-by: Nadav Amit
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index
From: Xavier Deguillard
Julien will be replacing me as the vmw_balloon maintainer.
Cc: Julien Freche
Signed-off-by: Xavier Deguillard
Signed-off-by: Nadav Amit
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index
On 11/15/18 at 11:13am, Baoquan He wrote:
> On 11/06/18 at 10:55am, Michal Hocko wrote:
> > From: Michal Hocko
> >
> > Page state checks are racy. Under a heavy memory workload (e.g. stress
> > -m 200 -t 2h) it is quite easy to hit a race window when the page is
> > allocated but its state is
On 11/15/18 at 11:13am, Baoquan He wrote:
> On 11/06/18 at 10:55am, Michal Hocko wrote:
> > From: Michal Hocko
> >
> > Page state checks are racy. Under a heavy memory workload (e.g. stress
> > -m 200 -t 2h) it is quite easy to hit a race window when the page is
> > allocated but its state is
From: Kelvin Cao
MRPC Input buffer is mostly memory without any side effects, thus we can
improve the access time by enabling write combining on only this region of
the BAR.
In a few places, we still need to flush the WC buffer. To do this, we
simply read from the Outbound Doorbell register
MRPC normal mode requires the host to read the MRPC command status and
output data from BAR. This results in high latency responses from the
Memory Read TLP and potential Completion Timeout (CTO).
MRPC DMA mode implementation includes:
Macro definitions for registers and data structures
From: Joey Zhang
For nr_idxs is larger than 1 switchtec_ioctl_event_ctl event flags will be
used by each event indexes. In current implementation the event flags are
overwritten by first call of the function event_ctl().
Preserve the event flag value with a temporary variable.
Fixes:
MRPC normal mode requires the host to read the MRPC command status and
output data from BAR. This results in high latency responses from the
Memory Read TLP and potential Completion Timeout (CTO).
MRPC DMA mode implementation includes:
Macro definitions for registers and data structures
From: Joey Zhang
For nr_idxs is larger than 1 switchtec_ioctl_event_ctl event flags will be
used by each event indexes. In current implementation the event flags are
overwritten by first call of the function event_ctl().
Preserve the event flag value with a temporary variable.
Fixes:
From: Kelvin Cao
MRPC Input buffer is mostly memory without any side effects, thus we can
improve the access time by enabling write combining on only this region of
the BAR.
In a few places, we still need to flush the WC buffer. To do this, we
simply read from the Outbound Doorbell register
Hi, Everyone,
This patch series adds support for the Switchtec MRPC DMA mode.
Switchtec switches supports 2 MRPC interaction modes: MRPC normal mode and
MRPC DMA mode, a new feature in the latest firmware versions. MRPC normal
mode requires the host to read the MRPC command status and output
From: Boris Glimcher
Switchtec hardware supports 64-bit DMA, set the correct DMA mask.
This allows the CMA to allocate larger buffers for memory windows.
Signed-off-by: Boris Glimcher
Signed-off-by: Wesley Sheng
---
drivers/pci/switch/switchtec.c | 4
1 file changed, 4 insertions(+)
1 - 100 of 1344 matches
Mail list logo
