linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Mike Rapoport <rppt@linux.vnet.ibm.com>
Cc: "David S. Miller" <davem@davemloft.net>,
	Michal Hocko <mhocko@kernel.org>,
	sparclinux@vger.kernel.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] sparc32: split ramdisk detection and reservation to a helper function
Date: Mon, 6 Aug 2018 15:09:02 +0200	[thread overview]
Message-ID: <20180806130902.GB23652@ravnborg.org> (raw)
In-Reply-To: <1533552755-16679-4-git-send-email-rppt@linux.vnet.ibm.com>

On Mon, Aug 06, 2018 at 01:52:35PM +0300, Mike Rapoport wrote:
> The detection and reservation of ramdisk memory were separated to allow
> bootmem bitmap initialization after the ramdisk boundaries are detected.
> Since the bootmem initialization is removed, the reservation of ramdisk
> memory is done immediately after its boundaries are found.
> 
> Split the entire block into a separate helper function.
> 
> Signed-off-by: Mike Rapoport <rppt@linux.vnet.ibm.com>
> Suggested-by: Sam Ravnborg <sam@ravnborg.org>
Reviewed-by: Sam Ravnborg <sam@ravnborg.org>


  reply	other threads:[~2018-08-06 13:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-06 10:52 [PATCH v2 0/3] sparc32: switch to NO_BOOTMEM Mike Rapoport
2018-08-06 10:52 ` [PATCH v2 1/3] sparc: mm/init_32: kill trailing whitespace Mike Rapoport
2018-08-06 10:52 ` [PATCH v2 2/3] sparc32: switch to NO_BOOTMEM Mike Rapoport
2018-08-06 13:08   ` Sam Ravnborg
2018-08-06 10:52 ` [PATCH v2 3/3] sparc32: split ramdisk detection and reservation to a helper function Mike Rapoport
2018-08-06 13:09   ` Sam Ravnborg [this message]
2018-08-21 19:40 ` [PATCH v2 0/3] sparc32: switch to NO_BOOTMEM David Miller

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=20180806130902.GB23652@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@kernel.org \
    --cc=rppt@linux.vnet.ibm.com \
    --cc=sparclinux@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).