On 04.05.20 23:08, Stephen Rothwell wrote:
> Hi Mike,
>
> On Mon, 4 May 2020 18:44:10 +0300 Mike Rapoport wrote:
>>
>> Ho Christian,
>>
>> On Mon, May 04, 2020 at 04:50:06PM +0200, Christian Borntraeger wrote:
>>> Mike,
>>> commit 51a2f644fd020d5f090044825c388444d11029d ("mm: free_area_init:
Hi Mike,
On Mon, 4 May 2020 18:44:10 +0300 Mike Rapoport wrote:
>
> Ho Christian,
>
> On Mon, May 04, 2020 at 04:50:06PM +0200, Christian Borntraeger wrote:
> > Mike,
> > commit 51a2f644fd020d5f090044825c388444d11029d ("mm: free_area_init: allow
> > defining max_zone_pfn in descending order")
Ho Christian,
On Mon, May 04, 2020 at 04:50:06PM +0200, Christian Borntraeger wrote:
> Mike,
> commit 51a2f644fd020d5f090044825c388444d11029d ("mm: free_area_init: allow
> defining max_zone_pfn in descending order")
> does increase the memory use on s390 (e.g. 700 MB vs.1.8 GB).
>
> Something
Mike,
commit 51a2f644fd020d5f090044825c388444d11029d ("mm: free_area_init: allow
defining max_zone_pfn in descending order")
does increase the memory use on s390 (e.g. 700 MB vs.1.8 GB).
Something is odd in this patch. Any idea?
Hi all,
Changes since 20200501:
My fixes tree contains:
bbefc924d0ff ("ubsan: disable UBSAN_ALIGNMENT under COMPILE_TEST")
7cb1d38f52b1 ("drm/msm: Fix undefined "rd_full" link error")
The qcom tree still had its build failure for which I reverted a commit.
The keys tree gained a conflict
Hi all,
Changes since 20180503:
Non-merge commits (relative to Linus' tree): 3965
3776 files changed, 154371 insertions(+), 67944 deletions(-)
I have created today's linux-next tree at
Hi all,
Changes since 20180503:
Non-merge commits (relative to Linus' tree): 3965
3776 files changed, 154371 insertions(+), 67944 deletions(-)
I have created today's linux-next tree at
Hi all,
Please do not add any v4.13 destined material in your linux-next
included branches until after v4.12-rc1 has been released.
Changes since 20170503:
The f2fs tree gained a conflict against the fscrypt tree.
The spi-nor tree gained a build failure so I used the version from
Hi all,
Please do not add any v4.13 destined material in your linux-next
included branches until after v4.12-rc1 has been released.
Changes since 20170503:
The f2fs tree gained a conflict against the fscrypt tree.
The spi-nor tree gained a build failure so I used the version from
Hi all,
Changes since 20160503:
Dropped tree: hsi (at the maintainer's request)
The tip tree gained a conflict against the arc tree.
The kvm-arm tree gained a conflict against the tip tree.
Non-merge commits (relative to Linus' tree): 7982
6997 files changed, 298694 insertions(+), 148713
Hi all,
Changes since 20160503:
Dropped tree: hsi (at the maintainer's request)
The tip tree gained a conflict against the arc tree.
The kvm-arm tree gained a conflict against the tip tree.
Non-merge commits (relative to Linus' tree): 7982
6997 files changed, 298694 insertions(+), 148713
Hi all,
Changes since 20150501:
Removed tree: virtio (maintainer moved on)
The akpm-current tree lost its build failure.
Non-merge commits (relative to Linus' tree): 1436
1426 files changed, 81272 insertions(+), 32795 deletions(-)
Hi all,
Changes since 20150501:
Removed tree: virtio (maintainer moved on)
The akpm-current tree lost its build failure.
Non-merge commits (relative to Linus' tree): 1436
1426 files changed, 81272 insertions(+), 32795 deletions(-)
13 matches
Mail list logo