Re: [folded-merged] mm-memblock-hardcode-the-end_pfn-being-1-fix.patch removed from -mm tree

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Andrew,

On Sat, Mar 10, 2018 at 12:45 AM,  <akpm@xxxxxxxxxxxxxxxxxxxx> wrote:
>
> The patch titled
>      Subject: mm-memblock-hardcode-the-end_pfn-being-1-fix
> has been removed from the -mm tree.  Its filename was
>      mm-memblock-hardcode-the-end_pfn-being-1-fix.patch
>
> This patch was dropped because it was folded into mm-memblock-hardcode-the-end_pfn-being-1.patch
>
> ------------------------------------------------------
> From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
> Subject: mm-memblock-hardcode-the-end_pfn-being-1-fix
>
> make it work against current -linus, not against -mm

What I've originally sent was already diff against -linus. There
should be no need for any fix.

> -                       pfn = memblock_next_valid_pfn(pfn) - 1;
> +                       pfn = memblock_next_valid_pfn(pfn, end_pfn) - 1;

The end_pfn should be gone. That's actually the reason for this patch.

--nX



[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]