From: Tony Lindgren <tony@atomide.com>
To: Mike Rapoport <rppt@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
Andrew Morton <akpm@linux-foundation.org>,
Kefeng Wang <wangkefeng.wang@huawei.com>,
Mike Rapoport <rppt@linux.ibm.com>,
Russell King <linux@armlinux.org.uk>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v3 0/4] memblock, arm: fixes for freeing of the memory map
Date: Wed, 30 Jun 2021 11:26:33 +0300 [thread overview]
Message-ID: <YNwquYgqR4PZtE+/@atomide.com> (raw)
In-Reply-To: <20210630071211.21011-1-rppt@kernel.org>
Hi,
* Mike Rapoport <rppt@kernel.org> [210630 07:12]:
> From: Mike Rapoport <rppt@linux.ibm.com>
> v3:
> * Add patch 3/4 to ensure there is no overflow in memblock_overlaps_region()
This series boots for me, so:
Tested-by: Tony Lindgren <tony@atomide.com>
WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Mike Rapoport <rppt@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
Andrew Morton <akpm@linux-foundation.org>,
Kefeng Wang <wangkefeng.wang@huawei.com>,
Mike Rapoport <rppt@linux.ibm.com>,
Russell King <linux@armlinux.org.uk>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v3 0/4] memblock, arm: fixes for freeing of the memory map
Date: Wed, 30 Jun 2021 11:26:33 +0300 [thread overview]
Message-ID: <YNwquYgqR4PZtE+/@atomide.com> (raw)
In-Reply-To: <20210630071211.21011-1-rppt@kernel.org>
Hi,
* Mike Rapoport <rppt@kernel.org> [210630 07:12]:
> From: Mike Rapoport <rppt@linux.ibm.com>
> v3:
> * Add patch 3/4 to ensure there is no overflow in memblock_overlaps_region()
This series boots for me, so:
Tested-by: Tony Lindgren <tony@atomide.com>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-06-30 8:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-30 7:12 [PATCH v3 0/4] memblock, arm: fixes for freeing of the memory map Mike Rapoport
2021-06-30 7:12 ` Mike Rapoport
2021-06-30 7:12 ` [PATCH v3 1/4] memblock: free_unused_memmap: use pageblock units instead of MAX_ORDER Mike Rapoport
2021-06-30 7:12 ` Mike Rapoport
2021-06-30 7:12 ` [PATCH v3 2/4] memblock: align freed memory map on pageblock boundaries with SPARSEMEM Mike Rapoport
2021-06-30 7:12 ` Mike Rapoport
2021-06-30 7:12 ` [PATCH v3 3/4] memblock: ensure there is no overflow in memblock_overlaps_region() Mike Rapoport
2021-06-30 7:12 ` Mike Rapoport
2021-06-30 7:12 ` [PATCH v3 4/4] arm: extend pfn_valid to take into account freed memory map alignment Mike Rapoport
2021-06-30 7:12 ` Mike Rapoport
2021-07-05 4:22 ` Guenter Roeck
2021-07-05 4:22 ` Guenter Roeck
2021-07-05 7:23 ` Mike Rapoport
2021-07-05 7:23 ` Mike Rapoport
2021-07-05 14:55 ` Guenter Roeck
2021-07-05 14:55 ` Guenter Roeck
2021-07-09 4:56 ` Alexey Minnekhanov
2021-07-09 4:56 ` Alexey Minnekhanov
2021-06-30 8:26 ` Tony Lindgren [this message]
2021-06-30 8:26 ` [PATCH v3 0/4] memblock, arm: fixes for freeing of the memory map Tony Lindgren
2021-11-11 7:33 ` Mark-PK Tsai
2021-11-11 7:33 ` Mark-PK Tsai
2021-11-11 9:45 ` Mike Rapoport
2021-11-11 9:45 ` Mike Rapoport
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YNwquYgqR4PZtE+/@atomide.com \
--to=tony@atomide.com \
--cc=akpm@linux-foundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@armlinux.org.uk \
--cc=rppt@kernel.org \
--cc=rppt@linux.ibm.com \
--cc=wangkefeng.wang@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.