On Thursday 10 August 2017 05:30 AM, Rob Herring wrote:
> On Tue, Aug 01, 2017 at 10:11:14AM +0530, Lokesh Vutla wrote:
>> Update ti,edma binding documentation to reflect 66AK2G specific
>> properties.
>>
>> Signed-off-by: Lokesh Vutla
>> ---
>>
On Thursday 10 August 2017 05:30 AM, Rob Herring wrote:
> On Tue, Aug 01, 2017 at 10:11:14AM +0530, Lokesh Vutla wrote:
>> Update ti,edma binding documentation to reflect 66AK2G specific
>> properties.
>>
>> Signed-off-by: Lokesh Vutla
>> ---
>>
From: Jagan Teki
Sunxi arm64 doesn't have separate configs for
h5 and a64 so enable SUNXI_RSB bus for ARM64.
Signed-off-by: Jagan Teki
---
drivers/bus/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
From: Jagan Teki
Sunxi arm64 doesn't have separate configs for
h5 and a64 so enable SUNXI_RSB bus for ARM64.
Signed-off-by: Jagan Teki
---
drivers/bus/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/bus/Kconfig b/drivers/bus/Kconfig
index 2408ea3..ae3d8f3
From: Jagan Teki
X-POWERS AXP20X PMIC Regulators is need for sunxi a64
so make it default in defconfig.
Signed-off-by: Jagan Teki
---
arch/arm64/configs/defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git
From: Jagan Teki
X-Powers AXP series PMICs with RSB is need for sunxi a64
so make it default in defconfig.
Signed-off-by: Jagan Teki
---
arch/arm64/configs/defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git
From: Jagan Teki
X-POWERS AXP20X PMIC Regulators is need for sunxi a64
so make it default in defconfig.
Signed-off-by: Jagan Teki
---
arch/arm64/configs/defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index
From: Jagan Teki
X-Powers AXP series PMICs with RSB is need for sunxi a64
so make it default in defconfig.
Signed-off-by: Jagan Teki
---
arch/arm64/configs/defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index
From: Jagan Teki
Since current tree support AXP803 regulators, replace
fixed regulator with AXP803 dcdc1 regulator.
Tested on pine64.
Signed-off-by: Jagan Teki
---
arch/arm64/boot/dts/allwinner/sun50i-a64-pine64.dts | 9 +
1
From: Jagan Teki
Since current tree support AXP803 regulators, replace
fixed regulator with AXP803 dcdc1 regulator.
Tested on pine64.
Signed-off-by: Jagan Teki
---
arch/arm64/boot/dts/allwinner/sun50i-a64-pine64.dts | 9 +
1 file changed, 1 insertion(+), 8 deletions(-)
diff --git
From: Jagan Teki
NanoPi A64 is a new board of high performance with low cost
designed by FriendlyElec., using the Allwinner A64 SOC.
Nanopi A64 features
- Allwinner A64, 64-bit Quad-core Cortex-A53@648MHz to 1.152GHz, DVFS
- 1GB DDR3 RAM
- MicroSD
- Gigabit Ethernet
From: Jagan Teki
NanoPi A64 is a new board of high performance with low cost
designed by FriendlyElec., using the Allwinner A64 SOC.
Nanopi A64 features
- Allwinner A64, 64-bit Quad-core Cortex-A53@648MHz to 1.152GHz, DVFS
- 1GB DDR3 RAM
- MicroSD
- Gigabit Ethernet (RTL8211E)
- Wi-Fi
From: Oliver O'Halloran
The alignment of a DAX and PFN regions dictates the page sizes that can
be used to map the region. Even if the hardware page sizes are known the
actual range of supported page sizes that can be used with DAX depends
on the kernel configuration. As a
From: Oliver O'Halloran
The alignment of a DAX and PFN regions dictates the page sizes that can
be used to map the region. Even if the hardware page sizes are known the
actual range of supported page sizes that can be used with DAX depends
on the kernel configuration. As a result it's best that
Now that we properly advertise the supported pte, pmd, and pud sizes,
restrict the supported alignments that can be set on a namespace. This
assumes that userspace was not previously relying on the ability to set
odd alignments. At least ndctl only ever supported setting the namespace
alignment to
Now that we properly advertise the supported pte, pmd, and pud sizes,
restrict the supported alignments that can be set on a namespace. This
assumes that userspace was not previously relying on the ability to set
odd alignments. At least ndctl only ever supported setting the namespace
alignment to
Prepare for other another consumer of this size selection scheme that is
not a 'sector size'.
Cc: Oliver O'Halloran
Signed-off-by: Dan Williams
---
drivers/nvdimm/btt_devs.c |4 ++--
drivers/nvdimm/core.c | 10 +-
Prepare for other another consumer of this size selection scheme that is
not a 'sector size'.
Cc: Oliver O'Halloran
Signed-off-by: Dan Williams
---
drivers/nvdimm/btt_devs.c |4 ++--
drivers/nvdimm/core.c | 10 +-
drivers/nvdimm/namespace_devs.c |6 +++---
This series is a minor rework of Oliver's original patch:
https://patchwork.kernel.org/patch/9811257/
It allows userspace to discover the system huge and gigantic page sizes
for aligning devices to support larger than PAGE_SIZE mappings for dax.
---
Dan Williams (2):
libnvdimm: rename
This series is a minor rework of Oliver's original patch:
https://patchwork.kernel.org/patch/9811257/
It allows userspace to discover the system huge and gigantic page sizes
for aligning devices to support larger than PAGE_SIZE mappings for dax.
---
Dan Williams (2):
libnvdimm: rename
On Sat, Aug 12, 2017 at 12:51 PM, wrote:
> 在 2017-08-12 12:04,Chen-Yu Tsai 写道:
>>
>> On Sat, Jul 22, 2017 at 11:00 AM, wrote:
>>>
>>> 在 2017-05-29 15:34,Chen-Yu Tsai 写道:
Hi,
On Sat, May 27, 2017 at 06:23:06PM +0800, Icenowy Zheng
On Sat, Aug 12, 2017 at 12:51 PM, wrote:
> 在 2017-08-12 12:04,Chen-Yu Tsai 写道:
>>
>> On Sat, Jul 22, 2017 at 11:00 AM, wrote:
>>>
>>> 在 2017-05-29 15:34,Chen-Yu Tsai 写道:
Hi,
On Sat, May 27, 2017 at 06:23:06PM +0800, Icenowy Zheng wrote:
>>
>>
>> [...]
>>
> +
>
在 2017-08-12 12:04,Chen-Yu Tsai 写道:
On Sat, Jul 22, 2017 at 11:00 AM, wrote:
在 2017-05-29 15:34,Chen-Yu Tsai 写道:
Hi,
On Sat, May 27, 2017 at 06:23:06PM +0800, Icenowy Zheng wrote:
[...]
+
+/*
+ * For the special bit in gate part, please see the BSP source code
at
+ *
在 2017-08-12 12:04,Chen-Yu Tsai 写道:
On Sat, Jul 22, 2017 at 11:00 AM, wrote:
在 2017-05-29 15:34,Chen-Yu Tsai 写道:
Hi,
On Sat, May 27, 2017 at 06:23:06PM +0800, Icenowy Zheng wrote:
[...]
+
+/*
+ * For the special bit in gate part, please see the BSP source code
at
+ *
在 2017-08-12 12:13,Chen-Yu Tsai 写道:
On Sat, Aug 12, 2017 at 11:07 AM, wrote:
在 2017-07-17 16:52,Maxime Ripard 写道:
On Fri, Jul 14, 2017 at 05:49:23PM +0300, Priit Laes wrote:
SATA clock on sun4i/sun7i is of type (parent) / M / 6 where
6 is fixed post-divider.
在 2017-08-12 12:13,Chen-Yu Tsai 写道:
On Sat, Aug 12, 2017 at 11:07 AM, wrote:
在 2017-07-17 16:52,Maxime Ripard 写道:
On Fri, Jul 14, 2017 at 05:49:23PM +0300, Priit Laes wrote:
SATA clock on sun4i/sun7i is of type (parent) / M / 6 where
6 is fixed post-divider.
Signed-off-by: Priit Laes
On Fri, Aug 11, 2017 at 8:57 PM, Andy Lutomirski wrote:
> On Fri, Aug 11, 2017 at 3:26 PM, Dan Williams
> wrote:
>> On Fri, Aug 11, 2017 at 3:44 AM, Christoph Hellwig wrote:
>>> Please explain how this interface allows for any sort of
On Fri, Aug 11, 2017 at 8:57 PM, Andy Lutomirski wrote:
> On Fri, Aug 11, 2017 at 3:26 PM, Dan Williams
> wrote:
>> On Fri, Aug 11, 2017 at 3:44 AM, Christoph Hellwig wrote:
>>> Please explain how this interface allows for any sort of safe userspace
>>> DMA.
>>
>> So this is where I continue
On Sat, Aug 12, 2017 at 11:07 AM, wrote:
> 在 2017-07-17 16:52,Maxime Ripard 写道:
>>
>> On Fri, Jul 14, 2017 at 05:49:23PM +0300, Priit Laes wrote:
>>>
>>> SATA clock on sun4i/sun7i is of type (parent) / M / 6 where
>>> 6 is fixed post-divider.
>>>
>>> Signed-off-by: Priit Laes
On Sat, Aug 12, 2017 at 11:07 AM, wrote:
> 在 2017-07-17 16:52,Maxime Ripard 写道:
>>
>> On Fri, Jul 14, 2017 at 05:49:23PM +0300, Priit Laes wrote:
>>>
>>> SATA clock on sun4i/sun7i is of type (parent) / M / 6 where
>>> 6 is fixed post-divider.
>>>
>>> Signed-off-by: Priit Laes
>>> ---
>>>
On Fri, Aug 11, 2017 at 07:31:54PM -0700, Darrick J. Wong wrote:
> On Sat, Aug 12, 2017 at 10:30:34AM +1000, Dave Chinner wrote:
> > On Fri, Aug 11, 2017 at 04:42:18PM -0700, Dan Williams wrote:
> > > On Fri, Aug 11, 2017 at 4:27 PM, Dave Chinner wrote:
> > > > On Thu, Aug
On Fri, Aug 11, 2017 at 07:31:54PM -0700, Darrick J. Wong wrote:
> On Sat, Aug 12, 2017 at 10:30:34AM +1000, Dave Chinner wrote:
> > On Fri, Aug 11, 2017 at 04:42:18PM -0700, Dan Williams wrote:
> > > On Fri, Aug 11, 2017 at 4:27 PM, Dave Chinner wrote:
> > > > On Thu, Aug 10, 2017 at 11:39:28PM
On Sat, Aug 12, 2017 at 12:04 PM, wrote:
> 在 2017-05-29 15:34,Chen-Yu Tsai 写道:
>>
>> Hi,
>>
>> On Sat, May 27, 2017 at 06:23:06PM +0800, Icenowy Zheng wrote:
>>>
>>> Allwinner R40 SoC have a clock controller module in the style of the
>>> SoCs beyond sun6i, however, it's more
On Sat, Aug 12, 2017 at 12:04 PM, wrote:
> 在 2017-05-29 15:34,Chen-Yu Tsai 写道:
>>
>> Hi,
>>
>> On Sat, May 27, 2017 at 06:23:06PM +0800, Icenowy Zheng wrote:
>>>
>>> Allwinner R40 SoC have a clock controller module in the style of the
>>> SoCs beyond sun6i, however, it's more rich and complex.
On Sat, Jul 22, 2017 at 11:00 AM, wrote:
> 在 2017-05-29 15:34,Chen-Yu Tsai 写道:
>>
>> Hi,
>>
>> On Sat, May 27, 2017 at 06:23:06PM +0800, Icenowy Zheng wrote:
[...]
>>> +
>>> +/*
>>> + * For the special bit in gate part, please see the BSP source code at
>>> + *
>>>
On Sat, Jul 22, 2017 at 11:00 AM, wrote:
> 在 2017-05-29 15:34,Chen-Yu Tsai 写道:
>>
>> Hi,
>>
>> On Sat, May 27, 2017 at 06:23:06PM +0800, Icenowy Zheng wrote:
[...]
>>> +
>>> +/*
>>> + * For the special bit in gate part, please see the BSP source code at
>>> + *
>>>
在 2017-05-29 15:34,Chen-Yu Tsai 写道:
Hi,
On Sat, May 27, 2017 at 06:23:06PM +0800, Icenowy Zheng wrote:
Allwinner R40 SoC have a clock controller module in the style of the
SoCs beyond sun6i, however, it's more rich and complex.
Add support for it.
Signed-off-by: Icenowy Zheng
在 2017-05-29 15:34,Chen-Yu Tsai 写道:
Hi,
On Sat, May 27, 2017 at 06:23:06PM +0800, Icenowy Zheng wrote:
Allwinner R40 SoC have a clock controller module in the style of the
SoCs beyond sun6i, however, it's more rich and complex.
Add support for it.
Signed-off-by: Icenowy Zheng
---
Changes in
On Fri, Aug 11, 2017 at 3:26 PM, Dan Williams wrote:
> On Fri, Aug 11, 2017 at 3:44 AM, Christoph Hellwig wrote:
>> Please explain how this interface allows for any sort of safe userspace
>> DMA.
>
> So this is where I continue to see S_IOMAP_IMMUTABLE
On Fri, Aug 11, 2017 at 3:26 PM, Dan Williams wrote:
> On Fri, Aug 11, 2017 at 3:44 AM, Christoph Hellwig wrote:
>> Please explain how this interface allows for any sort of safe userspace
>> DMA.
>
> So this is where I continue to see S_IOMAP_IMMUTABLE being able to
> support applications that
some versions of windows guest access rtc frequently because of
rtc as system tick.guest access rtc like this: write register index
to 0x70, then write or read data from 0x71. writing 0x70 port is
just as index and do nothing else. So we can use coalesced mmio to
handle this scene to reduce
some versions of windows guest access rtc frequently because of
rtc as system tick.guest access rtc like this: write register index
to 0x70, then write or read data from 0x71. writing 0x70 port is
just as index and do nothing else. So we can use coalesced mmio to
handle this scene to reduce
On 8/11/17 6:25 PM, Wei Wang wrote:
> By "a patch to fix that" do you mean after your patch, for every rt6,
> rt6->rt6i_idev will be the same as rt6->dst.dev?
FIB entries should have them the same device with my patch.
The copies done (ip6_rt_cache_alloc and ip6_rt_pcpu_alloc) will have to
set
On 8/11/17 6:25 PM, Wei Wang wrote:
> By "a patch to fix that" do you mean after your patch, for every rt6,
> rt6->rt6i_idev will be the same as rt6->dst.dev?
FIB entries should have them the same device with my patch.
The copies done (ip6_rt_cache_alloc and ip6_rt_pcpu_alloc) will have to
set
Hi.
2017-08-11 3:28 GMT+09:00 Randy Dunlap :
>> 2.) compile modpost with debug symbols, -g
>> how do I compile the modpost helper program with debug symbols? In what
>> makefile, kbuild file do I need to add the compiler flag?
>> Any help would be appreciated!
If you
Hi.
2017-08-11 3:28 GMT+09:00 Randy Dunlap :
>> 2.) compile modpost with debug symbols, -g
>> how do I compile the modpost helper program with debug symbols? In what
>> makefile, kbuild file do I need to add the compiler flag?
>> Any help would be appreciated!
If you want to pass extra options
Hi.
2017-08-11 7:11 GMT+09:00 Jim Davis :
> On Thu, Aug 10, 2017 at 11:28 AM, Randy Dunlap wrote:
>> [adding linux-kbuild]
>>
>> On 08/10/2017 08:42 AM, Thomas Meyer wrote:
>>> Hi,
>>>
>>> 1.) make with multiple targets
>>>
>>> When running
>>> $ make
Hi.
2017-08-11 7:11 GMT+09:00 Jim Davis :
> On Thu, Aug 10, 2017 at 11:28 AM, Randy Dunlap wrote:
>> [adding linux-kbuild]
>>
>> On 08/10/2017 08:42 AM, Thomas Meyer wrote:
>>> Hi,
>>>
>>> 1.) make with multiple targets
>>>
>>> When running
>>> $ make -j4 clean all
>>> I get error from make
On Fri, Aug 11, 2017 at 5:31 PM, John Stultz wrote:
> On Fri, Aug 11, 2017 at 5:10 PM, Wei Wang wrote:
>>> If after Cong's fix, the issue still happens, could you help try the
>>> patch attached and collect all logs when you try the reproduce the
>>>
On Fri, Aug 11, 2017 at 5:31 PM, John Stultz wrote:
> On Fri, Aug 11, 2017 at 5:10 PM, Wei Wang wrote:
>>> If after Cong's fix, the issue still happens, could you help try the
>>> patch attached and collect all logs when you try the reproduce the
>>> issue? It would be great to have logs for
在 2017-07-17 16:52,Maxime Ripard 写道:
On Fri, Jul 14, 2017 at 05:49:23PM +0300, Priit Laes wrote:
SATA clock on sun4i/sun7i is of type (parent) / M / 6 where
6 is fixed post-divider.
Signed-off-by: Priit Laes
---
drivers/clk/sunxi-ng/ccu_div.c | 15 +--
在 2017-07-17 16:52,Maxime Ripard 写道:
On Fri, Jul 14, 2017 at 05:49:23PM +0300, Priit Laes wrote:
SATA clock on sun4i/sun7i is of type (parent) / M / 6 where
6 is fixed post-divider.
Signed-off-by: Priit Laes
---
drivers/clk/sunxi-ng/ccu_div.c | 15 +--
This patch series based on v4.13-rc1, include MT7622 i2c dt-binding
and compatible.
changes since v1:
- Modify commit message
- Revise dt-binding documentation
Jun Gao (2):
dt-bindings: i2c: Add MediaTek MT7622 i2c binding
i2c: mediatek: Add i2c compatible for MediaTek MT7622
From: Jun Gao
Add MT7622 i2c binding to binding file and change the compatible
information formats of all SoCs to the same.
Signed-off-by: Jun Gao
---
Documentation/devicetree/bindings/i2c/i2c-mtk.txt | 11 ++-
1 file changed, 6
This patch series based on v4.13-rc1, include MT7622 i2c dt-binding
and compatible.
changes since v1:
- Modify commit message
- Revise dt-binding documentation
Jun Gao (2):
dt-bindings: i2c: Add MediaTek MT7622 i2c binding
i2c: mediatek: Add i2c compatible for MediaTek MT7622
From: Jun Gao
Add MT7622 i2c binding to binding file and change the compatible
information formats of all SoCs to the same.
Signed-off-by: Jun Gao
---
Documentation/devicetree/bindings/i2c/i2c-mtk.txt | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git
From: Jun Gao
Add i2c compatible for MT7622. Compare to MT8173 i2c controller,
MT7622 limits message numbers to 255, and does not support 4GB
DMA mode.
Signed-off-by: Jun Gao
---
drivers/i2c/busses/i2c-mt65xx.c | 18 ++
1 file
From: Jun Gao
Add i2c compatible for MT7622. Compare to MT8173 i2c controller,
MT7622 limits message numbers to 255, and does not support 4GB
DMA mode.
Signed-off-by: Jun Gao
---
drivers/i2c/busses/i2c-mt65xx.c | 18 ++
1 file changed, 18 insertions(+)
diff --git
On 2017年08月12日 07:12, Jakub Kicinski wrote:
On Fri, 11 Aug 2017 19:41:18 +0800, Jason Wang wrote:
This patch tries to implement XDP for tun. The implementation was
split into two parts:
- fast path: small and no gso packet. We try to do XDP at page level
before build_skb(). For XDP_TX,
On 2017年08月12日 07:12, Jakub Kicinski wrote:
On Fri, 11 Aug 2017 19:41:18 +0800, Jason Wang wrote:
This patch tries to implement XDP for tun. The implementation was
split into two parts:
- fast path: small and no gso packet. We try to do XDP at page level
before build_skb(). For XDP_TX,
> On Aug 11, 2017, at 8:13 PM, Philip Prindeville
> wrote:
>
>>
>> On Jul 21, 2017, at 12:48 PM, Lennart Sorensen
>> wrote:
>>
>> On Fri, Jul 21, 2017 at 11:36:27AM -0700, Benjamin Poirier wrote:
>>> When e1000e_poll() is
> On Aug 11, 2017, at 8:13 PM, Philip Prindeville
> wrote:
>
>>
>> On Jul 21, 2017, at 12:48 PM, Lennart Sorensen
>> wrote:
>>
>> On Fri, Jul 21, 2017 at 11:36:27AM -0700, Benjamin Poirier wrote:
>>> When e1000e_poll() is not fast enough to keep up with incoming traffic, the
>>> adapter
On Sat, Aug 12, 2017 at 10:30:34AM +1000, Dave Chinner wrote:
> On Fri, Aug 11, 2017 at 04:42:18PM -0700, Dan Williams wrote:
> > On Fri, Aug 11, 2017 at 4:27 PM, Dave Chinner wrote:
> > > On Thu, Aug 10, 2017 at 11:39:28PM -0700, Dan Williams wrote:
> > >> >From falloc.h:
>
On Sat, Aug 12, 2017 at 10:30:34AM +1000, Dave Chinner wrote:
> On Fri, Aug 11, 2017 at 04:42:18PM -0700, Dan Williams wrote:
> > On Fri, Aug 11, 2017 at 4:27 PM, Dave Chinner wrote:
> > > On Thu, Aug 10, 2017 at 11:39:28PM -0700, Dan Williams wrote:
> > >> >From falloc.h:
> > >>
> > >>
/proc/pid/smaps_rollup is a new proc file that improves the
performance of user programs that determine aggregate memory
statistics (e.g., total PSS) of a process.
Android regularly "samples" the memory usage of various processes in
order to balance its memory pool sizes. This sampling process
/proc/pid/smaps_rollup is a new proc file that improves the
performance of user programs that determine aggregate memory
statistics (e.g., total PSS) of a process.
Android regularly "samples" the memory usage of various processes in
order to balance its memory pool sizes. This sampling process
> On Jul 21, 2017, at 12:48 PM, Lennart Sorensen
> wrote:
>
> On Fri, Jul 21, 2017 at 11:36:27AM -0700, Benjamin Poirier wrote:
>> When e1000e_poll() is not fast enough to keep up with incoming traffic, the
>> adapter (when operating in msix mode) raises the Other
> On Jul 21, 2017, at 12:48 PM, Lennart Sorensen
> wrote:
>
> On Fri, Jul 21, 2017 at 11:36:27AM -0700, Benjamin Poirier wrote:
>> When e1000e_poll() is not fast enough to keep up with incoming traffic, the
>> adapter (when operating in msix mode) raises the Other interrupt to signal
>>
On 08/11/2017 04:02 PM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.82 release.
> There are 15 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On 08/11/2017 04:02 PM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.82 release.
> There are 15 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On 08/11/2017 04:01 PM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.43 release.
> There are 16 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On 08/11/2017 04:01 PM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.43 release.
> There are 16 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On 08/11/2017 04:01 PM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.12.7 release.
> There are 17 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On 08/11/2017 04:01 PM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.12.7 release.
> There are 17 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On 08/11/2017 04:02 PM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.18.65 release.
> There are 9 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On 08/11/2017 04:02 PM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.18.65 release.
> There are 9 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
NULL check at line 528: if (!sender || !data_out || !len_out) {, implies
that pointer _sender_ might be NULL.
Move pointer _sender_ dereference after NULL check in order to avoid a
potential NULL pointer dereference.
This issue was detected with the help of Coccinelle.
Signed-off-by: Gustavo A.
NULL check at line 528: if (!sender || !data_out || !len_out) {, implies
that pointer _sender_ might be NULL.
Move pointer _sender_ dereference after NULL check in order to avoid a
potential NULL pointer dereference.
This issue was detected with the help of Coccinelle.
Signed-off-by: Gustavo A.
This adds support the AHCI-compliant Serial ATA controller present
on MediaTek SoCs.
Signed-off-by: Ryder Lee
---
drivers/ata/Kconfig| 10 +++
drivers/ata/Makefile | 1 +
drivers/ata/ahci_mtk.c | 196 +
3 files
This adds support the AHCI-compliant Serial ATA controller present
on MediaTek SoCs.
Signed-off-by: Ryder Lee
---
drivers/ata/Kconfig| 10 +++
drivers/ata/Makefile | 1 +
drivers/ata/ahci_mtk.c | 196 +
3 files changed, 207 insertions(+)
Add DT bindings for the onboard SATA controller present on the MediaTek
SoCs.
Signed-off-by: Ryder Lee
---
Documentation/devicetree/bindings/ata/ahci-mtk.txt | 51 ++
1 file changed, 51 insertions(+)
create mode 100644
Add DT bindings for the onboard SATA controller present on the MediaTek
SoCs.
Signed-off-by: Ryder Lee
---
Documentation/devicetree/bindings/ata/ahci-mtk.txt | 51 ++
1 file changed, 51 insertions(+)
create mode 100644 Documentation/devicetree/bindings/ata/ahci-mtk.txt
Hi,
This patch series add support for AHCI compatible SATA controller, and it is
compliant with the ahci 1.3 and sata 3.0 specification. This driver is slightly
different than ahci_platform.c (e.g., reset control, subsystem setting).
changes since v3:
- update binding text: fix a typo and modify
Hi,
This patch series add support for AHCI compatible SATA controller, and it is
compliant with the ahci 1.3 and sata 3.0 specification. This driver is slightly
different than ahci_platform.c (e.g., reset control, subsystem setting).
changes since v3:
- update binding text: fix a typo and modify
Hi Honghui,
On Fri, 2017-08-11 at 20:27 +0800, honghui.zh...@mediatek.com wrote:
...
> +static void mtk_pcie_enable_msi(struct mtk_pcie_port *port)
> +{
> + u32 val;
> +
> + val = lower_32_bits((u64)(port->base + PCIE_MSI_VECTOR));
> + writel(val, port->base + PCIE_IMSI_ADDR);
> +
> +
Hi Honghui,
On Fri, 2017-08-11 at 20:27 +0800, honghui.zh...@mediatek.com wrote:
...
> +static void mtk_pcie_enable_msi(struct mtk_pcie_port *port)
> +{
> + u32 val;
> +
> + val = lower_32_bits((u64)(port->base + PCIE_MSI_VECTOR));
> + writel(val, port->base + PCIE_IMSI_ADDR);
> +
> +
Hi Brian,
Thanks for noting.
On 08/12/2017 12:59 AM, Brian Norris wrote:
Hi Jeffy,
You need to be more careful about the addressee's of your patches. No
one on To/CC is a maintainer or a sufficiently-targeted mailing list. I
doubt any of the maintainers will read your patch. (I've added
Hi Brian,
Thanks for noting.
On 08/12/2017 12:59 AM, Brian Norris wrote:
Hi Jeffy,
You need to be more careful about the addressee's of your patches. No
one on To/CC is a maintainer or a sufficiently-targeted mailing list. I
doubt any of the maintainers will read your patch. (I've added
Since commit 54a7d50b9205 ("x86: mark kprobe templates as
character arrays, not single characters") changes
optprobe_template_* to arrays, we can remove addressof
operators from those symbols.
Signed-off-by: Masami Hiramatsu
---
arch/x86/include/asm/kprobes.h |4 ++--
Since commit 54a7d50b9205 ("x86: mark kprobe templates as
character arrays, not single characters") changes
optprobe_template_* to arrays, we can remove addressof
operators from those symbols.
Signed-off-by: Masami Hiramatsu
---
arch/x86/include/asm/kprobes.h |4 ++--
> So yes, sorry I haven't been able to get back quicker on the other
> patches sent, was mucking about in other work.
>
> So yea, this patch (potential fix for unregister_netdevice()) seems
> to avoid the issue.
>
> I'm going to do some further testing, but its looking good so far.
>
Great.
> So yes, sorry I haven't been able to get back quicker on the other
> patches sent, was mucking about in other work.
>
> So yea, this patch (potential fix for unregister_netdevice()) seems
> to avoid the issue.
>
> I'm going to do some further testing, but its looking good so far.
>
Great.
Do not forget to set kprobes insn buffer memory back
to RO on failure path. Without this fix, if there is
an unexpected error on copying instructions, kprobes
insn buffer kept RW, which can allow unexpected modifying
instruction buffer.
Fixes: d0381c81c2f7 ("kprobes/x86: Set kprobes pages
Do not forget to set kprobes insn buffer memory back
to RO on failure path. Without this fix, if there is
an unexpected error on copying instructions, kprobes
insn buffer kept RW, which can allow unexpected modifying
instruction buffer.
Fixes: d0381c81c2f7 ("kprobes/x86: Set kprobes pages
Hi,
This series fixes a kprobe-x86 bug related to RO text and
cleans up addressof operators.
The first one is an obvious bug that misses to set memory
RO when the function fails. And the second one is just a
cleanup patch to remove addressof operators ("&") since
it is meaningless anymore.
V2
Hi,
This series fixes a kprobe-x86 bug related to RO text and
cleans up addressof operators.
The first one is an obvious bug that misses to set memory
RO when the function fails. And the second one is just a
cleanup patch to remove addressof operators ("&") since
it is meaningless anymore.
V2
Currently the hdmi i2s playback stream and hdmi spdif playback stream
are using the same name. So when they are enabled at the same time,
kernel will print this warning:
[2.201835] hdmi-audio-codec hdmi-audio-codec.1.auto: ASoC: Failed to
create Playback debugfs file
Assign different names
Currently the hdmi i2s playback stream and hdmi spdif playback stream
are using the same name. So when they are enabled at the same time,
kernel will print this warning:
[2.201835] hdmi-audio-codec hdmi-audio-codec.1.auto: ASoC: Failed to
create Playback debugfs file
Assign different names
On Fri, Aug 11, 2017 at 5:10 PM, Wei Wang wrote:
>> If after Cong's fix, the issue still happens, could you help try the
>> patch attached and collect all logs when you try the reproduce the
>> issue? It would be great to have logs for both success case and the
>> failure case.
On Fri, Aug 11, 2017 at 5:10 PM, Wei Wang wrote:
>> If after Cong's fix, the issue still happens, could you help try the
>> patch attached and collect all logs when you try the reproduce the
>> issue? It would be great to have logs for both success case and the
>> failure case.
>>
>> Thanks so
1 - 100 of 1846 matches
Mail list logo