On Wed, Aug 15, 2018 at 02:36:00AM +0200, Sebastian Gottschall wrote:
> if SWAP is disabled in kernel config, the following compile error will raise
> up with this release
>
> arch/x86/built-in.o: in function `max_swapfile_size': (.text+0x3bba1):
> undefined reference to
On Wed, Aug 15, 2018 at 02:36:00AM +0200, Sebastian Gottschall wrote:
> if SWAP is disabled in kernel config, the following compile error will raise
> up with this release
>
> arch/x86/built-in.o: in function `max_swapfile_size': (.text+0x3bba1):
> undefined reference to
On Tue, Aug 14, 2018 at 08:14:47PM -0400, Michael Jin wrote:
> Therefore, I would like you to confirm that model 10h uses 0x15e8 (device
> F0) and 0x15ee (device F6) as I can not find any documentation or test
> whether ECC works.
He just asked you to make the change for models 0x10-0x2f. How
On Tue, Aug 14, 2018 at 08:14:47PM -0400, Michael Jin wrote:
> Therefore, I would like you to confirm that model 10h uses 0x15e8 (device
> F0) and 0x15ee (device F6) as I can not find any documentation or test
> whether ECC works.
He just asked you to make the change for models 0x10-0x2f. How
On Tue, Aug 14, 2018 at 11:58:18AM -0700, Nathan Chancellor wrote:
> On Tue, Aug 14, 2018 at 07:16:23PM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.9.120 release.
> > There are 107 patches in this series, all will be posted as a response
> > to this
On Tue, Aug 14, 2018 at 11:58:18AM -0700, Nathan Chancellor wrote:
> On Tue, Aug 14, 2018 at 07:16:23PM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.9.120 release.
> > There are 107 patches in this series, all will be posted as a response
> > to this
On 2018/8/15 4:48, Rob Herring wrote:
On Fri, Aug 10, 2018 at 05:54:27PM +0800, Jian Hu wrote:
Add new clock controller compatible and dt-bingdings headers
for the Always-On domain of the g12a SoC
Signed-off-by: Jian Hu
---
.../bindings/clock/amlogic,gxbb-aoclkc.txt | 1 +
On 2018/8/15 4:48, Rob Herring wrote:
On Fri, Aug 10, 2018 at 05:54:27PM +0800, Jian Hu wrote:
Add new clock controller compatible and dt-bingdings headers
for the Always-On domain of the g12a SoC
Signed-off-by: Jian Hu
---
.../bindings/clock/amlogic,gxbb-aoclkc.txt | 1 +
Fix ram size and sort nodes in alphabetical order.
Signed-off-by: Ryder Lee
---
arch/arm64/boot/dts/mediatek/mt7622-rfb1.dts | 196 +--
1 file changed, 98 insertions(+), 98 deletions(-)
diff --git a/arch/arm64/boot/dts/mediatek/mt7622-rfb1.dts
Fix ram size and sort nodes in alphabetical order.
Signed-off-by: Ryder Lee
---
arch/arm64/boot/dts/mediatek/mt7622-rfb1.dts | 196 +--
1 file changed, 98 insertions(+), 98 deletions(-)
diff --git a/arch/arm64/boot/dts/mediatek/mt7622-rfb1.dts
Add timer and CCI-400 device nodes for MT7622.
Signed-off-by: Ryder Lee
---
arch/arm64/boot/dts/mediatek/mt7622.dtsi | 48
1 file changed, 48 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt7622.dtsi
b/arch/arm64/boot/dts/mediatek/mt7622.dtsi
index
Add timer and CCI-400 device nodes for MT7622.
Signed-off-by: Ryder Lee
---
arch/arm64/boot/dts/mediatek/mt7622.dtsi | 48
1 file changed, 48 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt7622.dtsi
b/arch/arm64/boot/dts/mediatek/mt7622.dtsi
index
Add support for the bananapi R64 (BPI-R64) development board from
BIPAI KEJI. Detailed hardware information for BPI-R64 which could be
found on http://wiki.banana-pi.org/Banana_Pi_BPI-R64
Signed-off-by: Ryder Lee
---
arch/arm64/boot/dts/mediatek/Makefile | 1 +
Add a built-in bluetooth 5 support for MT7622.
Signed-off-by: Ryder Lee
---
arch/arm64/boot/dts/mediatek/mt7622.dtsi | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt7622.dtsi
b/arch/arm64/boot/dts/mediatek/mt7622.dtsi
index b235df7..f8c3495 100644
---
Update binding document for bananapi BPI-R64 board being supported.
Signed-off-by: Ryder Lee
---
Documentation/devicetree/bindings/arm/mediatek.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/mediatek.txt
Update binding document for bananapi BPI-R64 board being supported.
Signed-off-by: Ryder Lee
---
Documentation/devicetree/bindings/arm/mediatek.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/mediatek.txt
Add support for the bananapi R64 (BPI-R64) development board from
BIPAI KEJI. Detailed hardware information for BPI-R64 which could be
found on http://wiki.banana-pi.org/Banana_Pi_BPI-R64
Signed-off-by: Ryder Lee
---
arch/arm64/boot/dts/mediatek/Makefile | 1 +
Add a built-in bluetooth 5 support for MT7622.
Signed-off-by: Ryder Lee
---
arch/arm64/boot/dts/mediatek/mt7622.dtsi | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt7622.dtsi
b/arch/arm64/boot/dts/mediatek/mt7622.dtsi
index b235df7..f8c3495 100644
---
On Wed, 2018-08-15 at 11:59 +0800, Dave Young wrote:
> > Does this improve things, and plug the no boot hole?
>
> Would you mind to tune my patch with some acpi_rsdp checking and add
> some error message in case kexec load failure? Eg. suggest people to use
> append acpi_rsdp for noefi booting
On Wed, 2018-08-15 at 11:59 +0800, Dave Young wrote:
> > Does this improve things, and plug the no boot hole?
>
> Would you mind to tune my patch with some acpi_rsdp checking and add
> some error message in case kexec load failure? Eg. suggest people to use
> append acpi_rsdp for noefi booting
Hi all,
On Wed, 8 Aug 2018 13:54:45 +1000 Stephen Rothwell
wrote:
>
> Paolo pointed out a semantic conflict between the kvm tree and the tip
> tree in
>
> arch/x86/kernel/kvm.c
>
> between commit:
>
> 368a540e0232 ("x86/kvmclock: Remove memblock dependency")
>
> from the tip tree and
Hi all,
On Wed, 8 Aug 2018 13:54:45 +1000 Stephen Rothwell
wrote:
>
> Paolo pointed out a semantic conflict between the kvm tree and the tip
> tree in
>
> arch/x86/kernel/kvm.c
>
> between commit:
>
> 368a540e0232 ("x86/kvmclock: Remove memblock dependency")
>
> from the tip tree and
Hi all,
Today's linux-next merge of the kvm tree got a conflict in:
arch/x86/include/asm/kvm_host.h
between commit:
5b76a3cff011 ("KVM: VMX: Tell the nested hypervisor to skip L1D flush on
vmentry")
from Linus' tree and commit:
4180bf1b655a ("KVM: X86: Implement "send IPI" hypercall")
Hi all,
Today's linux-next merge of the kvm tree got a conflict in:
arch/x86/include/asm/kvm_host.h
between commit:
5b76a3cff011 ("KVM: VMX: Tell the nested hypervisor to skip L1D flush on
vmentry")
from Linus' tree and commit:
4180bf1b655a ("KVM: X86: Implement "send IPI" hypercall")
Hi all,
Today's linux-next merge of the kvm tree got a conflict in:
arch/x86/kvm/vmx.c
between commit:
a399477e52c1 ("x86/KVM/VMX: Add module argument for L1TF mitigation")
from Linus' tree and commit:
877ad952be3d ("KVM: vmx: Add tlb_remote_flush callback support")
from the kvm tree.
Hi all,
Today's linux-next merge of the kvm tree got a conflict in:
arch/x86/kvm/vmx.c
between commit:
a399477e52c1 ("x86/KVM/VMX: Add module argument for L1TF mitigation")
from Linus' tree and commit:
877ad952be3d ("KVM: vmx: Add tlb_remote_flush callback support")
from the kvm tree.
Hi Steven,
Today's linux-next merge of the ftrace tree got a conflict in:
kernel/events/uprobes.c
between commit:
788faab70d5a ("perf, tools: Use correct articles in comments")
from Linus' tree and commit:
38e967ae1e60 ("Uprobes: Simplify uprobe_register() body")
from the ftrace tree.
Hi Steven,
Today's linux-next merge of the ftrace tree got a conflict in:
kernel/events/uprobes.c
between commit:
788faab70d5a ("perf, tools: Use correct articles in comments")
from Linus' tree and commit:
38e967ae1e60 ("Uprobes: Simplify uprobe_register() body")
from the ftrace tree.
Apologize for late reply, I'm occupied with something else.
On 08/10/18 at 07:39pm, Mike Galbraith wrote:
> On Fri, 2018-08-10 at 18:28 +0800, Dave Young wrote:
> >
> > > @@ -250,8 +253,10 @@ setup_boot_parameters(struct kimage *image, struct
> > > boot_params *params,
> > >
> > > #ifdef
Apologize for late reply, I'm occupied with something else.
On 08/10/18 at 07:39pm, Mike Galbraith wrote:
> On Fri, 2018-08-10 at 18:28 +0800, Dave Young wrote:
> >
> > > @@ -250,8 +253,10 @@ setup_boot_parameters(struct kimage *image, struct
> > > boot_params *params,
> > >
> > > #ifdef
uexing Wang
> Cc: Masahiro Yamada
> ---
> scripts/mod/modpost.c |2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- linux-next-20180814.orig/scripts/mod/modpost.c
> +++ linux-next-20180814/scripts/mod/modpost.c
> @@ -672,7
uexing Wang
> Cc: Masahiro Yamada
> ---
> scripts/mod/modpost.c |2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- linux-next-20180814.orig/scripts/mod/modpost.c
> +++ linux-next-20180814/scripts/mod/modpost.c
> @@ -672,7
Greetings in the name of God
Dear Friend
Greetings in the name of God,please let this not sound strange to you
for my only surviving lawyer who would have done this died early this
year.I prayed and got your email id from your country guestbook. I am
Mrs Suran Yoda from London,I am 72 years
Greetings in the name of God
Dear Friend
Greetings in the name of God,please let this not sound strange to you
for my only surviving lawyer who would have done this died early this
year.I prayed and got your email id from your country guestbook. I am
Mrs Suran Yoda from London,I am 72 years
On Fri, 10 Aug 2018 13:57:06 -0300
Arnaldo Carvalho de Melo wrote:
> > Arnaldo takes care of that, but I guess pulling from branch is the prefered
> > way
>
> I'll try pulling and building it automatically patch by patch,
Hi Arnaldo,
Were you able to take this? We have another patch series
On Fri, 10 Aug 2018 13:57:06 -0300
Arnaldo Carvalho de Melo wrote:
> > Arnaldo takes care of that, but I guess pulling from branch is the prefered
> > way
>
> I'll try pulling and building it automatically patch by patch,
Hi Arnaldo,
Were you able to take this? We have another patch series
+Cc: stable
Hi Greg, JFI:
This one has hit a couple of times on autotests on v4.9 stable.
The fix for BUG() is trivial, so probably worth to ship it to v4.9/v4.4/v3.18.
2017-06-13 5:59 GMT+01:00 Song liwei :
> From: Liwei Song
>
> Fix the following kernel bug:
>
> kernel BUG at
+Cc: stable
Hi Greg, JFI:
This one has hit a couple of times on autotests on v4.9 stable.
The fix for BUG() is trivial, so probably worth to ship it to v4.9/v4.4/v3.18.
2017-06-13 5:59 GMT+01:00 Song liwei :
> From: Liwei Song
>
> Fix the following kernel bug:
>
> kernel BUG at
Hi Rob,
On 15 August 2018 at 04:27, Rob Herring wrote:
> On Thu, Aug 09, 2018 at 11:03:11AM +0800, Baolin Wang wrote:
>> Hi Trent,
>>
>> On 9 August 2018 at 02:57, Trent Piepho wrote:
>> > On Wed, 2018-08-08 at 11:54 +0100, Mark Brown wrote:
>> >> On Wed, Aug 08, 2018 at 06:35:28PM +0800,
Hi Rob,
On 15 August 2018 at 04:27, Rob Herring wrote:
> On Thu, Aug 09, 2018 at 11:03:11AM +0800, Baolin Wang wrote:
>> Hi Trent,
>>
>> On 9 August 2018 at 02:57, Trent Piepho wrote:
>> > On Wed, 2018-08-08 at 11:54 +0100, Mark Brown wrote:
>> >> On Wed, Aug 08, 2018 at 06:35:28PM +0800,
On Tue, Aug 14, 2018 at 6:35 PM Michal Wnukowski wrote:
>
> I got confused after comaring disassembly of this code with and
> without volatile keyword. Thanks for the correction.
Note that _usually_, the "volatile" has absolutely no impact. When
there is one read in the source code, it's almost
On Tue, Aug 14, 2018 at 6:35 PM Michal Wnukowski wrote:
>
> I got confused after comaring disassembly of this code with and
> without volatile keyword. Thanks for the correction.
Note that _usually_, the "volatile" has absolutely no impact. When
there is one read in the source code, it's almost
Hi all,
On Mon, 6 Aug 2018 14:53:31 +1000 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the tip tree got a conflict in:
>
> drivers/infiniband/core/rdma_core.c
>
> between commit:
>
> 9867f5c6695f ("IB/uverbs: Convert 'bool exclusive' into an enum")
>
> from the rdma tree and
Hi all,
On Mon, 6 Aug 2018 14:53:31 +1000 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the tip tree got a conflict in:
>
> drivers/infiniband/core/rdma_core.c
>
> between commit:
>
> 9867f5c6695f ("IB/uverbs: Convert 'bool exclusive' into an enum")
>
> from the rdma tree and
On Wed, 2018-07-25 at 09:26 +0800, Houlong Wei wrote:
> This patch adds the device node of the GCE hardware for CMDQ module.
>
> Signed-off-by: Houlong Wei
> Signed-off-by: HS Liao
> ---
> arch/arm64/boot/dts/mediatek/mt8173.dtsi | 10 ++
> 1 file changed, 10 insertions(+)
>
> diff
On Wed, 2018-07-25 at 09:26 +0800, Houlong Wei wrote:
> This patch adds the device node of the GCE hardware for CMDQ module.
>
> Signed-off-by: Houlong Wei
> Signed-off-by: HS Liao
> ---
> arch/arm64/boot/dts/mediatek/mt8173.dtsi | 10 ++
> 1 file changed, 10 insertions(+)
>
> diff
On Wed, 2018-07-25 at 09:26 +0800, Houlong Wei wrote:
> Add Mediatek CMDQ helper to create CMDQ packet and assemble GCE op code.
>
> Signed-off-by: Houlong Wei
> Signed-off-by: HS Liao
> ---
> drivers/soc/mediatek/Kconfig | 12 ++
> drivers/soc/mediatek/Makefile |1 +
>
On Wed, 2018-07-25 at 09:26 +0800, Houlong Wei wrote:
> Add Mediatek CMDQ helper to create CMDQ packet and assemble GCE op code.
>
> Signed-off-by: Houlong Wei
> Signed-off-by: HS Liao
> ---
> drivers/soc/mediatek/Kconfig | 12 ++
> drivers/soc/mediatek/Makefile |1 +
>
Hi all,
On Thu, 26 Jul 2018 13:58:04 +1000 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the block tree got a conflict in:
>
> drivers/nvme/target/rdma.c
>
> between commit:
>
> 23f96d1f15a7 ("nvmet-rdma: Simplify ib_post_(send|recv|srq_recv)() calls")
> 202093848cac
Hi all,
On Thu, 26 Jul 2018 13:58:04 +1000 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the block tree got a conflict in:
>
> drivers/nvme/target/rdma.c
>
> between commit:
>
> 23f96d1f15a7 ("nvmet-rdma: Simplify ib_post_(send|recv|srq_recv)() calls")
> 202093848cac
Hi Rob,
On 15 August 2018 at 04:21, Rob Herring wrote:
> On Tue, Aug 07, 2018 at 06:43:37PM +0800, Baolin Wang wrote:
>> From: Lanqing Liu
>>
>> This patch adds the binding documentation for Spreadtrum SPI
>> controller device.
>>
>> Signed-off-by: Lanqing Liu
>> Signed-off-by: Baolin Wang
>>
Hi Rob,
On 15 August 2018 at 04:21, Rob Herring wrote:
> On Tue, Aug 07, 2018 at 06:43:37PM +0800, Baolin Wang wrote:
>> From: Lanqing Liu
>>
>> This patch adds the binding documentation for Spreadtrum SPI
>> controller device.
>>
>> Signed-off-by: Lanqing Liu
>> Signed-off-by: Baolin Wang
>>
Hi all,
On Thu, 26 Jul 2018 14:56:24 +1000 Stephen Rothwell
wrote:
>
> After merging the block tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/nvme/target/rdma.c: In function 'nvmet_rdma_find_get_device':
> drivers/nvme/target/rdma.c:894:26: error: 'struct
Hi all,
On Thu, 26 Jul 2018 14:56:24 +1000 Stephen Rothwell
wrote:
>
> After merging the block tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/nvme/target/rdma.c: In function 'nvmet_rdma_find_get_device':
> drivers/nvme/target/rdma.c:894:26: error: 'struct
On 08/14/2018 04:16 PM, Linus Torvalds wrote:
> On Tue, Aug 14, 2018 at 03:17:35PM -0700, Michal Wnukowski wrote:
>>
>> With memory barrier in place, the volatile keyword around *dbbuf_ei is
>> redundant.
>
> No. The memory barrier enforces _ordering_, but it doesn't enforce
> that the
On 08/14/2018 04:16 PM, Linus Torvalds wrote:
> On Tue, Aug 14, 2018 at 03:17:35PM -0700, Michal Wnukowski wrote:
>>
>> With memory barrier in place, the volatile keyword around *dbbuf_ei is
>> redundant.
>
> No. The memory barrier enforces _ordering_, but it doesn't enforce
> that the
On 08/14/2018 04:56 PM, Doug Anderson wrote:
> On Tue, Aug 14, 2018 at 2:59 PM, David Collins
> wrote:
>> On 08/14/2018 01:03 PM, Doug Anderson wrote:
>>> On Tue, Aug 14, 2018 at 11:30 AM, David Collins
>>> wrote:>>> --- a/drivers/regulator/core.c
> +++ b/drivers/regulator/core.c
> @@
On 08/14/2018 04:56 PM, Doug Anderson wrote:
> On Tue, Aug 14, 2018 at 2:59 PM, David Collins
> wrote:
>> On 08/14/2018 01:03 PM, Doug Anderson wrote:
>>> On Tue, Aug 14, 2018 at 11:30 AM, David Collins
>>> wrote:>>> --- a/drivers/regulator/core.c
> +++ b/drivers/regulator/core.c
> @@
.flush_iotlb_all can not just wait for previous tlbi operations to be
completed, but should also invalid all TLBs of the related domain.
Signed-off-by: Zhen Lei
Reviewed-by: Robin Murphy
---
drivers/iommu/arm-smmu-v3.c | 10 +-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git
.flush_iotlb_all can not just wait for previous tlbi operations to be
completed, but should also invalid all TLBs of the related domain.
Signed-off-by: Zhen Lei
Reviewed-by: Robin Murphy
---
drivers/iommu/arm-smmu-v3.c | 10 +-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git
On 08/14/18 07:46, 张波 wrote:
> /delete-node/ /delete-prop/ could be used in dtsi files without device
> tree overlay.
>
> but with device tree overlay, /delete-node/ and /delete-prop/ are not work.
> How to delete property and node in overlay dts?
>
> for example,
> in basel.dts have following
On 08/14/18 07:46, 张波 wrote:
> /delete-node/ /delete-prop/ could be used in dtsi files without device
> tree overlay.
>
> but with device tree overlay, /delete-node/ and /delete-prop/ are not work.
> How to delete property and node in overlay dts?
>
> for example,
> in basel.dts have following
On Tue, Aug 14, 2018 at 5:37 PM Roman Gushchin wrote:
>
> If CONFIG_VMAP_STACK is set, kernel stacks are allocated
> using __vmalloc_node_range() with __GFP_ACCOUNT. So kernel
> stack pages are charged against corresponding memory cgroups
> on allocation and uncharged on releasing them.
>
> The
On Tue, Aug 14, 2018 at 5:37 PM Roman Gushchin wrote:
>
> If CONFIG_VMAP_STACK is set, kernel stacks are allocated
> using __vmalloc_node_range() with __GFP_ACCOUNT. So kernel
> stack pages are charged against corresponding memory cgroups
> on allocation and uncharged on releasing them.
>
> The
On 2018/8/13 20:42, Paul E. McKenney wrote:
On Mon, Aug 13, 2018 at 05:26:49PM +0800, Jia-Ju Bai wrote:
On 2018/8/13 12:18, Paul E. McKenney wrote:
On Mon, Aug 13, 2018 at 11:04:10AM +0800, Jia-Ju Bai wrote:
The kernel may sleep with holding a spinlock.
The function call paths (from
On 2018/8/13 20:42, Paul E. McKenney wrote:
On Mon, Aug 13, 2018 at 05:26:49PM +0800, Jia-Ju Bai wrote:
On 2018/8/13 12:18, Paul E. McKenney wrote:
On Mon, Aug 13, 2018 at 11:04:10AM +0800, Jia-Ju Bai wrote:
The kernel may sleep with holding a spinlock.
The function call paths (from
On 08/14/2018 04:20 PM, Linus Torvalds wrote:
On Tue, Aug 14, 2018 at 4:02 PM Andrew Morton wrote:
The m68k build still fails because 0cc3cd21657 ("cpu/hotplug: Boot HT
siblings at least once") was evidently never tested on CONFIG_SMP=n.
How could that come about - the patch is six weeks
On 08/14/2018 04:20 PM, Linus Torvalds wrote:
On Tue, Aug 14, 2018 at 4:02 PM Andrew Morton wrote:
The m68k build still fails because 0cc3cd21657 ("cpu/hotplug: Boot HT
siblings at least once") was evidently never tested on CONFIG_SMP=n.
How could that come about - the patch is six weeks
On 08/14/2018 05:36 PM, Sebastian Gottschall wrote:
if SWAP is disabled in kernel config, the following compile error will raise up
with this release
arch/x86/built-in.o: in function `max_swapfile_size': (.text+0x3bba1):
undefined reference to `generic_max_swapfile_size'
of course this is
On 08/14/2018 05:36 PM, Sebastian Gottschall wrote:
if SWAP is disabled in kernel config, the following compile error will raise up
with this release
arch/x86/built-in.o: in function `max_swapfile_size': (.text+0x3bba1):
undefined reference to `generic_max_swapfile_size'
of course this is
On Wed, Aug 15, 2018 at 02:36:00AM +0200, Sebastian Gottschall wrote:
> if SWAP is disabled in kernel config, the following compile error will raise
> up with this release
>
> arch/x86/built-in.o: in function `max_swapfile_size': (.text+0x3bba1):
> undefined reference to
On Wed, Aug 15, 2018 at 02:36:00AM +0200, Sebastian Gottschall wrote:
> if SWAP is disabled in kernel config, the following compile error will raise
> up with this release
>
> arch/x86/built-in.o: in function `max_swapfile_size': (.text+0x3bba1):
> undefined reference to
if SWAP is disabled in kernel config, the following compile error will
raise up with this release
arch/x86/built-in.o: in function `max_swapfile_size': (.text+0x3bba1):
undefined reference to `generic_max_swapfile_size'
of course this is simple to fix. the function max_swapfile_size must be
if SWAP is disabled in kernel config, the following compile error will
raise up with this release
arch/x86/built-in.o: in function `max_swapfile_size': (.text+0x3bba1):
undefined reference to `generic_max_swapfile_size'
of course this is simple to fix. the function max_swapfile_size must be
On Tue, Aug 14, 2018 at 5:36 PM Roman Gushchin wrote:
>
> Memcg charge is batched using per-cpu stocks, so an offline memcg
> can be pinned by a cached charge up to a moment, when a process
> belonging to some other cgroup will charge some memory on the same
> cpu. In other words, cached charges
On Tue, Aug 14, 2018 at 5:36 PM Roman Gushchin wrote:
>
> Memcg charge is batched using per-cpu stocks, so an offline memcg
> can be pinned by a cached charge up to a moment, when a process
> belonging to some other cgroup will charge some memory on the same
> cpu. In other words, cached charges
o be built and checked by sparse.
Signed-off-by: Randy Dunlap
---
scripts/kconfig/Makefile |8
1 file changed, 8 insertions(+)
--- linux-next-20180814.orig/scripts/kconfig/Makefile
+++ linux-next-20180814/scripts/kconfig/Makefile
@@ -33,6 +33,14 @@ config: $(obj)/conf
nconfig: $(
If CONFIG_VMAP_STACK is set, kernel stacks are allocated
using __vmalloc_node_range() with __GFP_ACCOUNT. So kernel
stack pages are charged against corresponding memory cgroups
on allocation and uncharged on releasing them.
The problem is that we do cache kernel stacks in small
per-cpu caches and
If CONFIG_VMAP_STACK is set, kernel stacks are allocated
using __vmalloc_node_range() with __GFP_ACCOUNT. So kernel
stack pages are charged against corresponding memory cgroups
on allocation and uncharged on releasing them.
The problem is that we do cache kernel stacks in small
per-cpu caches and
o be built and checked by sparse.
Signed-off-by: Randy Dunlap
---
scripts/kconfig/Makefile |8
1 file changed, 8 insertions(+)
--- linux-next-20180814.orig/scripts/kconfig/Makefile
+++ linux-next-20180814/scripts/kconfig/Makefile
@@ -33,6 +33,14 @@ config: $(obj)/conf
nconfig: $(
Memcg charge is batched using per-cpu stocks, so an offline memcg
can be pinned by a cached charge up to a moment, when a process
belonging to some other cgroup will charge some memory on the same
cpu. In other words, cached charges can prevent a memory cgroup
from being reclaimed for some time,
Memcg charge is batched using per-cpu stocks, so an offline memcg
can be pinned by a cached charge up to a moment, when a process
belonging to some other cgroup will charge some memory on the same
cpu. In other words, cached charges can prevent a memory cgroup
from being reclaimed for some time,
On Tue, Aug 14, 2018 at 4:26 PM, Ghannam, Yazen wrote:
>
> > -Original Message-
> > From: Michael Jin
> > Sent: Friday, August 10, 2018 2:36 PM
> > To: Borislav Petkov ; Ghannam, Yazen
> > ; Mauro Carvalho Chehab
> >
> > Cc: linux-e...@vger.kernel.org; linux-kernel@vger.kernel.org;
On Tue, Aug 14, 2018 at 4:26 PM, Ghannam, Yazen wrote:
>
> > -Original Message-
> > From: Michael Jin
> > Sent: Friday, August 10, 2018 2:36 PM
> > To: Borislav Petkov ; Ghannam, Yazen
> > ; Mauro Carvalho Chehab
> >
> > Cc: linux-e...@vger.kernel.org; linux-kernel@vger.kernel.org;
On 08/14/2018 01:48 AM, Kirill A. Shutemov wrote:
> On Mon, Aug 13, 2018 at 11:21:41PM +, Mike Kravetz wrote:
>> On 08/13/2018 03:58 AM, Kirill A. Shutemov wrote:
>>> On Sun, Aug 12, 2018 at 08:41:08PM -0700, Mike Kravetz wrote:
I am not %100 sure on the required flushing, so suggestions
On 08/14/2018 01:48 AM, Kirill A. Shutemov wrote:
> On Mon, Aug 13, 2018 at 11:21:41PM +, Mike Kravetz wrote:
>> On 08/13/2018 03:58 AM, Kirill A. Shutemov wrote:
>>> On Sun, Aug 12, 2018 at 08:41:08PM -0700, Mike Kravetz wrote:
I am not %100 sure on the required flushing, so suggestions
> >> HEAD commit:5ed5da74de9e Add linux-next specific files for 20180813
> >> git tree: linux-next
> >
> > I fetched linux-next but don't have 5ed5da74de9e.
>
> +Stephen for the disappeared linux-next commit.
That is just the HEAD commit on linux-nex
> >> HEAD commit:5ed5da74de9e Add linux-next specific files for 20180813
> >> git tree: linux-next
> >
> > I fetched linux-next but don't have 5ed5da74de9e.
>
> +Stephen for the disappeared linux-next commit.
That is just the HEAD commit on linux-nex
If cppc_cpufreq.ko is deleted at the same time that tuned-adm is
changing profiles, there is a small chance that a race can occur
between cpufreq_dbs_governor_exit() and cpufreq_dbs_governor_limits()
resulting in a system failure when the latter tries to use
policy->governor_data that has been
If cppc_cpufreq.ko is deleted at the same time that tuned-adm is
changing profiles, there is a small chance that a race can occur
between cpufreq_dbs_governor_exit() and cpufreq_dbs_governor_limits()
resulting in a system failure when the latter tries to use
policy->governor_data that has been
On Thu, Jul 26, 2018 at 2:26 AM, Federico Vaga wrote:
> Hi Alan,
>
> have you considered the possibility of having something like devm_fpga_[mgr|
> bridge|region]_[create|free]() ? Like this, it will be obvious that 'struct
> fpga_mgr' will be released automatically without reading any comment
On Thu, Jul 26, 2018 at 2:26 AM, Federico Vaga wrote:
> Hi Alan,
>
> have you considered the possibility of having something like devm_fpga_[mgr|
> bridge|region]_[create|free]() ? Like this, it will be obvious that 'struct
> fpga_mgr' will be released automatically without reading any comment
Hi,
On Tue, Aug 14, 2018 at 2:59 PM, David Collins wrote:
> Hi,
>
> On 08/14/2018 01:03 PM, Doug Anderson wrote:
>> On Tue, Aug 14, 2018 at 11:30 AM, David Collins
>> wrote:>>> --- a/drivers/regulator/core.c
+++ b/drivers/regulator/core.c
@@ -732,6 +732,7 @@ static int
Hi,
On Tue, Aug 14, 2018 at 2:59 PM, David Collins wrote:
> Hi,
>
> On 08/14/2018 01:03 PM, Doug Anderson wrote:
>> On Tue, Aug 14, 2018 at 11:30 AM, David Collins
>> wrote:>>> --- a/drivers/regulator/core.c
+++ b/drivers/regulator/core.c
@@ -732,6 +732,7 @@ static int
On Tue, Aug 14, 2018 at 04:16:41PM -0700, Linus Torvalds wrote:
> On Tue, Aug 14, 2018 at 3:56 PM Keith Busch
> wrote:
> >
> > You just want to ensure the '*dbbuf_db = value' isn't reordered, right?
> > The order dependency might be more obvious if done as:
> >
> > WRITE_ONCE(*dbbuf_db,
On Tue, Aug 14, 2018 at 04:16:41PM -0700, Linus Torvalds wrote:
> On Tue, Aug 14, 2018 at 3:56 PM Keith Busch
> wrote:
> >
> > You just want to ensure the '*dbbuf_db = value' isn't reordered, right?
> > The order dependency might be more obvious if done as:
> >
> > WRITE_ONCE(*dbbuf_db,
On Mon, 13 Aug 2018 16:38:25 +0900 Sergey Senozhatsky
wrote:
> On (08/13/18 15:16), Minchan Kim wrote:
> > > The call to strlcpy in backing_dev_store is incorrect. It should take
> > > the size of the destination buffer instead of the size of the source
> > > buffer. Additionally, ignore the
On Mon, 13 Aug 2018 16:38:25 +0900 Sergey Senozhatsky
wrote:
> On (08/13/18 15:16), Minchan Kim wrote:
> > > The call to strlcpy in backing_dev_store is incorrect. It should take
> > > the size of the destination buffer instead of the size of the source
> > > buffer. Additionally, ignore the
From: Justin Chen
Sometimes we have empty banks within the GPIO block. This commit allows
proper handling of 0 width GPIO banks. We handle 0 width GPIO banks by
incrementing the bank and number of GPIOs, but not initializing them.
This will mean a call into the non-existent GPIOs will return an
From: Justin Chen
Sometimes we have empty banks within the GPIO block. This commit allows
proper handling of 0 width GPIO banks. We handle 0 width GPIO banks by
incrementing the bank and number of GPIOs, but not initializing them.
This will mean a call into the non-existent GPIOs will return an
1 - 100 of 1640 matches
Mail list logo
