On Tue 10 Apr 15:25 PDT 2018, Alex Elder wrote:
> If there is at least one entry in the partition table, but no global
> entry, the qcom_smem_set_global_partition() should return an error
> just like it does if there are no partition table entries.
>
> It turns out the function still returns an
On Tue 10 Apr 15:25 PDT 2018, Alex Elder wrote:
> If there is at least one entry in the partition table, but no global
> entry, the qcom_smem_set_global_partition() should return an error
> just like it does if there are no partition table entries.
>
> It turns out the function still returns an
Use new return type vm_fault_t for fault handler. For
now, this is just documenting that the function returns
a VM_FAULT value rather than an errno. Once all instances
are converted, vm_fault_t will become a distinct type.
Commit 1c8f422059ae ("mm: change return type to vm_fault_t")
Use new return type vm_fault_t for fault handler. For
now, this is just documenting that the function returns
a VM_FAULT value rather than an errno. Once all instances
are converted, vm_fault_t will become a distinct type.
Commit 1c8f422059ae ("mm: change return type to vm_fault_t")
On Tue 10 Apr 15:25 PDT 2018, Alex Elder wrote:
> It's OK if the space for a newly-allocated uncached entry actually
> touches the free cached space boundary. It's only a problem if it
> would cross it.
>
> Signed-off-by: Alex Elder
Reviewed-by: Bjorn Andersson
On Tue 10 Apr 15:25 PDT 2018, Alex Elder wrote:
> It's OK if the space for a newly-allocated uncached entry actually
> touches the free cached space boundary. It's only a problem if it
> would cross it.
>
> Signed-off-by: Alex Elder
Reviewed-by: Bjorn Andersson
Regards,
Bjorn
> ---
>
On Tue 10 Apr 15:25 PDT 2018, Alex Elder wrote:
> Two places report an error when a partition header is found to
> not contain the right canary value. The error messages do not
> properly byte swap the host ids. Fix this, and adjust the format
> specificier to match the 16-bit unsigned data
On Tue 10 Apr 15:25 PDT 2018, Alex Elder wrote:
> Two places report an error when a partition header is found to
> not contain the right canary value. The error messages do not
> properly byte swap the host ids. Fix this, and adjust the format
> specificier to match the 16-bit unsigned data
Use new return type vm_fault_t for fault handler. For
now, this is just documenting that the function returns
a VM_FAULT value rather than an errno. Once all instances
are converted, vm_fault_t will become a distinct type.
Commit 1c8f422059ae ("mm: change return type to vm_fault_t")
Use new return type vm_fault_t for fault handler. For
now, this is just documenting that the function returns
a VM_FAULT value rather than an errno. Once all instances
are converted, vm_fault_t will become a distinct type.
Commit 1c8f422059ae ("mm: change return type to vm_fault_t")
On Tue 10 Apr 15:25 PDT 2018, Alex Elder wrote:
> What phdr_to_last_uncached_entry() returns is the address of the
> start of the free space following all allocated uncached entries.
> It really doesn't refer to an actual (initialized) private entry
> structure. Similarly
On Tue 10 Apr 15:25 PDT 2018, Alex Elder wrote:
> What phdr_to_last_uncached_entry() returns is the address of the
> start of the free space following all allocated uncached entries.
> It really doesn't refer to an actual (initialized) private entry
> structure. Similarly
On Tue 10 Apr 15:25 PDT 2018, Alex Elder wrote:
> Cached items are found at the high end of an smem partition. A
> cached item's shared memory precedes the private entry structure
> that describes it.
>
> The address of the structure describing the first cached item should
> be returned by
On Tue 10 Apr 15:25 PDT 2018, Alex Elder wrote:
> Cached items are found at the high end of an smem partition. A
> cached item's shared memory precedes the private entry structure
> that describes it.
>
> The address of the structure describing the first cached item should
> be returned by
From: Evan Wang
There are some special operations needed when stop engine
for Marvell AHCI IP, and it maybe needed by other vendors,
so it is necessary to allow to override ahci_stop_engine()
when stop the engine like overriding start_engine.
Evan Wang (2):
libahci: Allow
From: Evan Wang
Marvell armada37xx, armada7k and armada8k share the same
AHCI sata controller IP, and currently there is an issue
(Errata Ref#226)that the SATA can not be detected via SATA
Port-MultiPlayer(PMP). After debugging, the reason is
found that the value of Port-x
Use new return type vm_fault_t for fault handler. For
now, this is just documenting that the function returns
a VM_FAULT value rather than an errno. Once all instances
are converted, vm_fault_t will become a distinct type.
Commit 1c8f422059ae ("mm: change return type to vm_fault_t")
From: Evan Wang
There is an issue(Errata Ref#226) that the SATA can not be
detected via SATA Port-MultiPlayer(PMP) with following
error log:
ata1.15: PMP product ID mismatch
ata1.15: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
ata1.15: Port Multiplier vendor
From: Evan Wang
There are some special operations needed when stop engine
for Marvell AHCI IP, and it maybe needed by other vendors,
so it is necessary to allow to override ahci_stop_engine()
when stop the engine like overriding start_engine.
Evan Wang (2):
libahci: Allow drivers to override
From: Evan Wang
Marvell armada37xx, armada7k and armada8k share the same
AHCI sata controller IP, and currently there is an issue
(Errata Ref#226)that the SATA can not be detected via SATA
Port-MultiPlayer(PMP). After debugging, the reason is
found that the value of Port-x FIS-based Switching
Use new return type vm_fault_t for fault handler. For
now, this is just documenting that the function returns
a VM_FAULT value rather than an errno. Once all instances
are converted, vm_fault_t will become a distinct type.
Commit 1c8f422059ae ("mm: change return type to vm_fault_t")
From: Evan Wang
There is an issue(Errata Ref#226) that the SATA can not be
detected via SATA Port-MultiPlayer(PMP) with following
error log:
ata1.15: PMP product ID mismatch
ata1.15: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
ata1.15: Port Multiplier vendor mismatch '0x1b4b'!='0x0'
Add support for MT7622 AFE which shares the same binding with MT2701.
Cc: devicet...@vger.kernel.org
Signed-off-by: Ryder Lee
---
Documentation/devicetree/bindings/sound/mt2701-afe-pcm.txt | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git
dear Bjorn,
I understand the confusion. I quite messed up the bug report. Sorry.
The problem is that lspci with kernel 4.17-rc1 shows exactly the same behaviour when no
workaround is applied.
the lspci is from 4.17-rc1 with the workaround applied, but by default, it shows the same output
as
Add support for MT7622 AFE which shares the same binding with MT2701.
Cc: devicet...@vger.kernel.org
Signed-off-by: Ryder Lee
---
Documentation/devicetree/bindings/sound/mt2701-afe-pcm.txt | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git
dear Bjorn,
I understand the confusion. I quite messed up the bug report. Sorry.
The problem is that lspci with kernel 4.17-rc1 shows exactly the same behaviour when no
workaround is applied.
the lspci is from 4.17-rc1 with the workaround applied, but by default, it shows the same output
as
This patch adds support for the MT7622 AFE which reuses MT2701 driver.
We also introduce the 'struct mt2701_soc_variants' to differentiate
between the SoC generations as there might be other (existing or future)
chips that use the same binding and driver, then being a little more
abstract could
This patch adds support for the MT7622 AFE which reuses MT2701 driver.
We also introduce the 'struct mt2701_soc_variants' to differentiate
between the SoC generations as there might be other (existing or future)
chips that use the same binding and driver, then being a little more
abstract could
Add SPDX identifiers to all remaining files in sound/soc/mediatek/
Signed-off-by: Ryder Lee
---
sound/soc/mediatek/Makefile | 1 +
sound/soc/mediatek/common/Makefile | 14 +-
sound/soc/mediatek/common/mtk-afe-fe-dai.c
Add SPDX identifiers to all remaining files in sound/soc/mediatek/
Signed-off-by: Ryder Lee
---
sound/soc/mediatek/Makefile | 1 +
sound/soc/mediatek/common/Makefile | 14 +-
sound/soc/mediatek/common/mtk-afe-fe-dai.c | 10
On Tue, Apr 24, 2018 at 05:10:49PM -0700, Paul E. McKenney wrote:
> On Tue, Apr 24, 2018 at 04:46:54PM -0700, Joel Fernandes wrote:
> >
> >
> > On 04/24/2018 04:21 PM, Mathieu Desnoyers wrote:
> > >- On Apr 24, 2018, at 2:59 PM, Joel Fernandes joe...@google.com wrote:
> > >>On Tue, Apr 24,
On Tue, Apr 24, 2018 at 05:10:49PM -0700, Paul E. McKenney wrote:
> On Tue, Apr 24, 2018 at 04:46:54PM -0700, Joel Fernandes wrote:
> >
> >
> > On 04/24/2018 04:21 PM, Mathieu Desnoyers wrote:
> > >- On Apr 24, 2018, at 2:59 PM, Joel Fernandes joe...@google.com wrote:
> > >>On Tue, Apr 24,
Add MTK_STREAM_NUM to common header and modify related stuff so that
the other SoCs can reuse it.
Signed-off-by: Ryder Lee
Reviewed-by: Garlic Tseng
---
sound/soc/mediatek/common/mtk-base-afe.h | 2 +
Reduce the boilerplate code to retrieve the private data.
No functional change intended.
Signed-off-by: Ryder Lee
Reviewed-by: Garlic Tseng
---
sound/soc/mediatek/common/mtk-afe-fe-dai.c | 20 +++
sound/soc/mediatek/mt2701/mt2701-afe-pcm.c
This patch adjusts the mt2701_afe_i2s_ops to simplify the control
logic of the I2S path.
Signed-off-by: Ryder Lee
Reviewed-by: Garlic Tseng
---
sound/soc/mediatek/mt2701/mt2701-afe-clock-ctrl.c | 39
Add MTK_STREAM_NUM to common header and modify related stuff so that
the other SoCs can reuse it.
Signed-off-by: Ryder Lee
Reviewed-by: Garlic Tseng
---
sound/soc/mediatek/common/mtk-base-afe.h | 2 +
sound/soc/mediatek/mt2701/mt2701-afe-clock-ctrl.c | 15 +++--
Reduce the boilerplate code to retrieve the private data.
No functional change intended.
Signed-off-by: Ryder Lee
Reviewed-by: Garlic Tseng
---
sound/soc/mediatek/common/mtk-afe-fe-dai.c | 20 +++
sound/soc/mediatek/mt2701/mt2701-afe-pcm.c | 86 +++---
This patch adjusts the mt2701_afe_i2s_ops to simplify the control
logic of the I2S path.
Signed-off-by: Ryder Lee
Reviewed-by: Garlic Tseng
---
sound/soc/mediatek/mt2701/mt2701-afe-clock-ctrl.c | 39
sound/soc/mediatek/mt2701/mt2701-afe-clock-ctrl.h | 13 ++-
Use new return type vm_fault_t for fault handler. For
now, this is just documenting that the function returns
a VM_FAULT value rather than an errno. Once all instances
are converted, vm_fault_t will become a distinct type.
Commit 1c8f422059ae ("mm: change return type to vm_fault_t")
Use new return type vm_fault_t for fault handler. For
now, this is just documenting that the function returns
a VM_FAULT value rather than an errno. Once all instances
are converted, vm_fault_t will become a distinct type.
Commit 1c8f422059ae ("mm: change return type to vm_fault_t")
Use new return type vm_fault_t for fault handler. For
now, this is just documenting that the function returns
a VM_FAULT value rather than an errno. Once all instances
are converted, vm_fault_t will become a distinct type.
Commit 1c8f422059ae ("mm: change return type to vm_fault_t")
Use new return type vm_fault_t for fault handler. For
now, this is just documenting that the function returns
a VM_FAULT value rather than an errno. Once all instances
are converted, vm_fault_t will become a distinct type.
Commit 1c8f422059ae ("mm: change return type to vm_fault_t")
When DMA is to be performed to a MIPS32 1004K CPS, the
L1-cache for the range needs to be flushed and invalidated
first.
The code currently takes one of two approaches.
1/ If the range is less than the size of the dcache, then
HIT type requests flush/invalidate cache lines for the
When DMA is to be performed to a MIPS32 1004K CPS, the
L1-cache for the range needs to be flushed and invalidated
first.
The code currently takes one of two approaches.
1/ If the range is less than the size of the dcache, then
HIT type requests flush/invalidate cache lines for the
On Fri, Apr 20, 2018 at 07:11:41AM -0500, Alex Elder wrote:
> On 04/10/2018 05:25 PM, Alex Elder wrote:
> > This series contains mostly bug fixes to the Qualcomm shared memory
> > ("smem") code. Although the bugs are real, they have most likely
> > never been observed.
> >
> >
On Fri, Apr 20, 2018 at 07:11:41AM -0500, Alex Elder wrote:
> On 04/10/2018 05:25 PM, Alex Elder wrote:
> > This series contains mostly bug fixes to the Qualcomm shared memory
> > ("smem") code. Although the bugs are real, they have most likely
> > never been observed.
> >
> >
Hello,
syzbot hit the following crash on upstream commit
24cac7009cb1b211f1c793ecb6a462c03dc35818 (Tue Apr 24 21:16:40 2018 +)
Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net
syzbot dashboard link:
https://syzkaller.appspot.com/bug?extid=4529a1346c0a67500ab9
So far this
Hello,
syzbot hit the following crash on upstream commit
24cac7009cb1b211f1c793ecb6a462c03dc35818 (Tue Apr 24 21:16:40 2018 +)
Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net
syzbot dashboard link:
https://syzkaller.appspot.com/bug?extid=4529a1346c0a67500ab9
So far this
On 4/13/2018 5:43 PM, vinayak menon wrote:
> On Thu, Apr 12, 2018 at 8:27 PM, Roman Gushchin wrote:
>> On Thu, Apr 12, 2018 at 08:52:52AM +0200, Vlastimil Babka wrote:
>>> On 04/11/2018 03:56 PM, Roman Gushchin wrote:
On Wed, Apr 11, 2018 at 03:16:08PM +0200, Vlastimil Babka
On 4/13/2018 5:43 PM, vinayak menon wrote:
> On Thu, Apr 12, 2018 at 8:27 PM, Roman Gushchin wrote:
>> On Thu, Apr 12, 2018 at 08:52:52AM +0200, Vlastimil Babka wrote:
>>> On 04/11/2018 03:56 PM, Roman Gushchin wrote:
On Wed, Apr 11, 2018 at 03:16:08PM +0200, Vlastimil Babka wrote:
>
From: Vijayanand Jitta
An issue is observed where mallocs are failing due to overcommit failure.
The failure happens when there is high ION page pool since ION page
pool is not considered reclaimable by the overcommit calculation code.
This change considers ion pool pages
From: Vijayanand Jitta
An issue is observed where mallocs are failing due to overcommit failure.
The failure happens when there is high ION page pool since ION page
pool is not considered reclaimable by the overcommit calculation code.
This change considers ion pool pages as indirectly
On 4/24/2018 10:06 PM, Daniel Kurtz wrote:
On Mon, Apr 23, 2018 at 9:03 PM Vijendar Mukunda
wrote:
From: Akshu Agrawal
hw_param can be called multiple times and thus we can have
more clk enable. The clk may not get diabled due to
On 4/24/2018 10:06 PM, Daniel Kurtz wrote:
On Mon, Apr 23, 2018 at 9:03 PM Vijendar Mukunda
wrote:
From: Akshu Agrawal
hw_param can be called multiple times and thus we can have
more clk enable. The clk may not get diabled due to refcounting.
startup/shutdown ensures single clk
i.MX6SX Sabre Auto board has GPIO1_IO13 pin can be
MUXed as WDOG output to reset PMIC, add this function
support.
Signed-off-by: Anson Huang
---
no changes since V2.
arch/arm/boot/dts/imx6sx-sabreauto.dts | 12
1 file changed, 12 insertions(+)
diff --git
i.MX6SX Sabre Auto board has GPIO1_IO13 pin can be
MUXed as WDOG output to reset PMIC, add this function
support.
Signed-off-by: Anson Huang
---
no changes since V2.
arch/arm/boot/dts/imx6sx-sabreauto.dts | 12
1 file changed, 12 insertions(+)
diff --git
i.MX6SX Sabre Auto board has two max7310 IO expander
on I2C3 bus, add support for them.
Signed-off-by: Anson Huang
---
no changes since V2.
arch/arm/boot/dts/imx6sx-sabreauto.dts | 28
1 file changed, 28 insertions(+)
diff --git
i.MX6SX Sabre Auto board has two max7310 IO expander
on I2C3 bus, add support for them.
Signed-off-by: Anson Huang
---
no changes since V2.
arch/arm/boot/dts/imx6sx-sabreauto.dts | 28
1 file changed, 28 insertions(+)
diff --git
Add pfuze100 support on i.MX6SX Sabre Auto board.
Signed-off-by: Anson Huang
---
no changes since V2.
arch/arm/boot/dts/imx6sx-sabreauto.dts | 117 +
1 file changed, 117 insertions(+)
diff --git a/arch/arm/boot/dts/imx6sx-sabreauto.dts
Add MAX7322 IO expander support.
Signed-off-by: Anson Huang
---
no changes since V2.
arch/arm/boot/dts/imx6sx-sabreauto.dts | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/boot/dts/imx6sx-sabreauto.dts
b/arch/arm/boot/dts/imx6sx-sabreauto.dts
index
Add pfuze100 support on i.MX6SX Sabre Auto board.
Signed-off-by: Anson Huang
---
no changes since V2.
arch/arm/boot/dts/imx6sx-sabreauto.dts | 117 +
1 file changed, 117 insertions(+)
diff --git a/arch/arm/boot/dts/imx6sx-sabreauto.dts
Add MAX7322 IO expander support.
Signed-off-by: Anson Huang
---
no changes since V2.
arch/arm/boot/dts/imx6sx-sabreauto.dts | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/boot/dts/imx6sx-sabreauto.dts
b/arch/arm/boot/dts/imx6sx-sabreauto.dts
index 2caca934..d59084f 100644
On Tue, Apr 24, 2018 at 11:09:02AM -0700, Alexander Duyck wrote:
> On Tue, Apr 24, 2018 at 8:14 AM, Holger Schurig
> wrote:
> > Sometimes, plugging the cable back in is detected ...
> >
> > [ 43.736922] igb :02:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps
> >
On Tue, Apr 24, 2018 at 11:09:02AM -0700, Alexander Duyck wrote:
> On Tue, Apr 24, 2018 at 8:14 AM, Holger Schurig
> wrote:
> > Sometimes, plugging the cable back in is detected ...
> >
> > [ 43.736922] igb :02:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps
> > Full Duplex, Flow Control:
Hi, Fabio
Anson Huang
Best Regards!
> -Original Message-
> From: Fabio Estevam [mailto:feste...@gmail.com]
> Sent: Tuesday, April 24, 2018 8:23 PM
> To: Anson Huang
> Cc: Shawn Guo ; Sascha Hauer
> ; Fabio Estevam
Hi, Fabio
Anson Huang
Best Regards!
> -Original Message-
> From: Fabio Estevam [mailto:feste...@gmail.com]
> Sent: Tuesday, April 24, 2018 8:23 PM
> To: Anson Huang
> Cc: Shawn Guo ; Sascha Hauer
> ; Fabio Estevam ; Rob
> Herring ; Mark Rutland ;
> dl-linux-imx ; moderated
Hi all,
When an IRQ line is set affinity using irq_set_affinity, which calls
irq_do_set_affinity, this API copies affinity mask to affinity variable
in irq_common_data of this irq descriptor.
But as per ARM GICv2 document in order to drive a interrupt to a
specific CPU we need to program
Hi all,
When an IRQ line is set affinity using irq_set_affinity, which calls
irq_do_set_affinity, this API copies affinity mask to affinity variable
in irq_common_data of this irq descriptor.
But as per ARM GICv2 document in order to drive a interrupt to a
specific CPU we need to program
Hi Atish, Palmer,
On Tue, Apr 24, 2018 at 06:15:49PM -0700, Atish Patra wrote:
> On 4/24/18 5:29 PM, Palmer Dabbelt wrote:
> >On Tue, 24 Apr 2018 15:16:16 PDT (-0700), atish.pa...@wdc.com wrote:
> >>On 4/24/18 12:44 PM, Palmer Dabbelt wrote:
> >>>On Tue, 24 Apr 2018 12:27:26 PDT (-0700),
Hi Atish, Palmer,
On Tue, Apr 24, 2018 at 06:15:49PM -0700, Atish Patra wrote:
> On 4/24/18 5:29 PM, Palmer Dabbelt wrote:
> >On Tue, 24 Apr 2018 15:16:16 PDT (-0700), atish.pa...@wdc.com wrote:
> >>On 4/24/18 12:44 PM, Palmer Dabbelt wrote:
> >>>On Tue, 24 Apr 2018 12:27:26 PDT (-0700),
On Wed, Apr 25, 2018 at 3:37 AM, Maxime Ripard
wrote:
> On Tue, Apr 24, 2018 at 08:17:11PM +0800, Chen-Yu Tsai wrote:
>> On Tue, Apr 24, 2018 at 8:13 PM, Maxime Ripard
>> wrote:
>> > On Tue, Apr 24, 2018 at 07:34:19PM +0800, Chen-Yu Tsai
On Wed, Apr 25, 2018 at 3:37 AM, Maxime Ripard
wrote:
> On Tue, Apr 24, 2018 at 08:17:11PM +0800, Chen-Yu Tsai wrote:
>> On Tue, Apr 24, 2018 at 8:13 PM, Maxime Ripard
>> wrote:
>> > On Tue, Apr 24, 2018 at 07:34:19PM +0800, Chen-Yu Tsai wrote:
>> >> The Libre Computer Project ALL-H3-CC has
It means firmware attempts to immediately process or launch the capsule
when flags in capsule header is not set. Moreover, reset is not needed
in this case. Current code will output log to indicate reset.
This patch adds a branch to avoid reset log output when the flags is not
set.
Cc: Joey
It means firmware attempts to immediately process or launch the capsule
when flags in capsule header is not set. Moreover, reset is not needed
in this case. Current code will output log to indicate reset.
This patch adds a branch to avoid reset log output when the flags is not
set.
Cc: Joey
On 24-04-18, 15:34, Rohit Jain wrote:
> Including the "unlikely" suggestion and the original patch, as expected
> with a quick hackbench test on a 44 core 2 socket x86 machine causes no
> change in performance.
Want me to include your Tested-by in next version ?
--
viresh
On 24-04-18, 15:34, Rohit Jain wrote:
> Including the "unlikely" suggestion and the original patch, as expected
> with a quick hackbench test on a 44 core 2 socket x86 machine causes no
> change in performance.
Want me to include your Tested-by in next version ?
--
viresh
On 24-04-18, 22:32, Krzysztof Kozlowski wrote:
> The Exynos5440 is not actively developed, there are no development
> boards available and probably there are no real products with it.
> Remove wide-tree support for Exynos5440.
>
> Signed-off-by: Krzysztof Kozlowski
> ---
>
On 24-04-18, 22:32, Krzysztof Kozlowski wrote:
> The Exynos5440 is not actively developed, there are no development
> boards available and probably there are no real products with it.
> Remove wide-tree support for Exynos5440.
>
> Signed-off-by: Krzysztof Kozlowski
> ---
>
On Tue, Apr 24, 2018 at 03:11:11PM -0600, Simon Glass wrote:
> This is used in some systems from user space for determining the identity
> of the device.
>
> Expose this as a file so that that user-space tools don't need to read
> from /sys/firmware/dmi/tables/DMI
sysfs is an ABI and needs to be
On 24-04-18, 15:14, Luc Van Oostenryck wrote:
> speedstep_detect_processor() is declared as returing an
> 'enum speedstep_processor' but use an 'int' in its definition.
>
> Fix this by using 'enum speedstep_processor' in its definition too.
>
> Signed-off-by: Luc Van Oostenryck
On Tue, Apr 24, 2018 at 03:11:11PM -0600, Simon Glass wrote:
> This is used in some systems from user space for determining the identity
> of the device.
>
> Expose this as a file so that that user-space tools don't need to read
> from /sys/firmware/dmi/tables/DMI
sysfs is an ABI and needs to be
On 24-04-18, 15:14, Luc Van Oostenryck wrote:
> speedstep_detect_processor() is declared as returing an
> 'enum speedstep_processor' but use an 'int' in its definition.
>
> Fix this by using 'enum speedstep_processor' in its definition too.
>
> Signed-off-by: Luc Van Oostenryck
> ---
>
On Tue, Apr 24, 2018 at 6:16 PM, Stephen Rothwell wrote:
> Hi Thomas,
>
> On Sun, 22 Apr 2018 18:23:46 +0200 Thomas Gleixner wrote:
>>
>> The rslib usage in dm/verity_fec is broken because init_rs() can nest in
>> GFP_NOIO mempool allocations as
On Tue, Apr 24, 2018 at 6:16 PM, Stephen Rothwell wrote:
> Hi Thomas,
>
> On Sun, 22 Apr 2018 18:23:46 +0200 Thomas Gleixner wrote:
>>
>> The rslib usage in dm/verity_fec is broken because init_rs() can nest in
>> GFP_NOIO mempool allocations as init_rs() is invoked from the mempool alloc
>>
Hi,
On Tue, 24 Apr 2018 15:17:25 +0200
Luc Van Oostenryck wrote:
> The method ndo_start_xmit() is defined as returning an 'netdev_tx_t',
> which is a typedef for an enum type, but the implementation in this
> driver returns an 'int'.
>
> Fix this by returning
Hi,
On Tue, 24 Apr 2018 15:17:25 +0200
Luc Van Oostenryck wrote:
> The method ndo_start_xmit() is defined as returning an 'netdev_tx_t',
> which is a typedef for an enum type, but the implementation in this
> driver returns an 'int'.
>
> Fix this by returning 'netdev_tx_t' in this driver too.
Now, Linux uses matrix allocator for vector assignment, the original
assignment code which used VECTOR_OFFSET_START has been removed.
So remove the stale macro as well
Signed-off-by: Dou Liyang
---
arch/x86/include/asm/irq_vectors.h | 5 -
1 file changed, 5
Now, Linux uses matrix allocator for vector assignment, the original
assignment code which used VECTOR_OFFSET_START has been removed.
So remove the stale macro as well
Signed-off-by: Dou Liyang
---
arch/x86/include/asm/irq_vectors.h | 5 -
1 file changed, 5 deletions(-)
diff --git
On 4/24/18 12:16 PM, Christoph Hellwig wrote:
> ide_toggle_bounce did select various strange block bounce limits, including
> not bouncing at all as soon as an iommu is present in the system. Given
> that the dma_map routines now handle any required bounce buffering except
> for ISA DMA, and the
On 4/24/18 12:16 PM, Christoph Hellwig wrote:
> ide_toggle_bounce did select various strange block bounce limits, including
> not bouncing at all as soon as an iommu is present in the system. Given
> that the dma_map routines now handle any required bounce buffering except
> for ISA DMA, and the
On (04/24/18 10:51), Steven Rostedt wrote:
[..]
> > console_lock_spinning_enable();
> >
> > + __printk_safe_exit();
> > stop_critical_timings();/* don't trace print latency */
> > call_console_drivers(ext_text, ext_len, text, len);
> >
On (04/24/18 10:51), Steven Rostedt wrote:
[..]
> > console_lock_spinning_enable();
> >
> > + __printk_safe_exit();
> > stop_critical_timings();/* don't trace print latency */
> > call_console_drivers(ext_text, ext_len, text, len);
> >
> > >
> > > The patch doesn't remove extcon support from chipidea driver.
> > > I just want to not select EXTCON unconditionally, but let the users
> > > choose. If the users need extcon, they could enable EXTCON
> > > themselves
> > >
> > > I just searched all the dts in arch/arm/boot/dts and
>
> > >
> > > The patch doesn't remove extcon support from chipidea driver.
> > > I just want to not select EXTCON unconditionally, but let the users
> > > choose. If the users need extcon, they could enable EXTCON
> > > themselves
> > >
> > > I just searched all the dts in arch/arm/boot/dts and
>
2018-04-25 3:16 GMT+08:00 Christoph Hellwig :
> Hi Greentime,
>
> thanks for testing the patch!
>
> It looks like nds32 doesn't have a buildbot yet, so this code didn't
> even get syntax checkin, sorry.
>
> Below is the incremental fixes based on this thread.
>
> Can you check if my
2018-04-25 3:16 GMT+08:00 Christoph Hellwig :
> Hi Greentime,
>
> thanks for testing the patch!
>
> It looks like nds32 doesn't have a buildbot yet, so this code didn't
> even get syntax checkin, sorry.
>
> Below is the incremental fixes based on this thread.
>
> Can you check if my tree works if
Hello,
syzbot hit the following crash on net-next commit
9c20b9372fbaf6f7d4c05f5f925806a7928f0c73 (Tue Apr 24 03:08:41 2018 +)
net: fib_rules: fix l3mdev netlink attr processing
syzbot dashboard link:
https://syzkaller.appspot.com/bug?extid=cf9012c597c8379d535c
So far this crash happened
Hello,
syzbot hit the following crash on net-next commit
9c20b9372fbaf6f7d4c05f5f925806a7928f0c73 (Tue Apr 24 03:08:41 2018 +)
net: fib_rules: fix l3mdev netlink attr processing
syzbot dashboard link:
https://syzkaller.appspot.com/bug?extid=cf9012c597c8379d535c
So far this crash happened
Hi Thomas,
On Sun, 22 Apr 2018 18:23:46 +0200 Thomas Gleixner wrote:
>
> The rslib usage in dm/verity_fec is broken because init_rs() can nest in
> GFP_NOIO mempool allocations as init_rs() is invoked from the mempool alloc
> callback.
>
> Provide a variant which takes gfp_t
Hi Thomas,
On Sun, 22 Apr 2018 18:23:46 +0200 Thomas Gleixner wrote:
>
> The rslib usage in dm/verity_fec is broken because init_rs() can nest in
> GFP_NOIO mempool allocations as init_rs() is invoked from the mempool alloc
> callback.
>
> Provide a variant which takes gfp_t flags as argument.
101 - 200 of 2614 matches
Mail list logo