From: Mike Rapoport <rppt@linux.vnet.ibm.com>
To: Jeff Dike <jdike@addtoit.com>, Richard Weinberger <richard@nod.at>
Cc: linux-mm@kvack.org, linux-um@lists.infradead.org,
linux-kernel@vger.kernel.org, Michal Hocko <mhocko@kernel.org>
Subject: Re: [PATCH 0/2] um: switch to NO_BOOTMEM
Date: Tue, 31 Jul 2018 16:38:27 +0300 [thread overview]
Message-ID: <20180731133827.GC23494@rapoport-lnx> (raw)
In-Reply-To: <1532438594-4530-1-git-send-email-rppt@linux.vnet.ibm.com>
Any comments on this?
On Tue, Jul 24, 2018 at 04:23:12PM +0300, Mike Rapoport wrote:
> Hi,
>
> These patches convert UML to use NO_BOOTMEM.
> Tested on x86-64.
>
> Mike Rapoport (2):
> um: setup_physmem: stop using global variables
> um: switch to NO_BOOTMEM
>
> arch/um/Kconfig.common | 2 ++
> arch/um/kernel/physmem.c | 22 ++++++++++------------
> 2 files changed, 12 insertions(+), 12 deletions(-)
>
> --
> 2.7.4
>
--
Sincerely yours,
Mike.
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
WARNING: multiple messages have this Message-ID (diff)
From: Mike Rapoport <rppt@linux.vnet.ibm.com>
To: Jeff Dike <jdike@addtoit.com>, Richard Weinberger <richard@nod.at>
Cc: Michal Hocko <mhocko@kernel.org>,
linux-um@lists.infradead.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] um: switch to NO_BOOTMEM
Date: Tue, 31 Jul 2018 16:38:27 +0300 [thread overview]
Message-ID: <20180731133827.GC23494@rapoport-lnx> (raw)
In-Reply-To: <1532438594-4530-1-git-send-email-rppt@linux.vnet.ibm.com>
Any comments on this?
On Tue, Jul 24, 2018 at 04:23:12PM +0300, Mike Rapoport wrote:
> Hi,
>
> These patches convert UML to use NO_BOOTMEM.
> Tested on x86-64.
>
> Mike Rapoport (2):
> um: setup_physmem: stop using global variables
> um: switch to NO_BOOTMEM
>
> arch/um/Kconfig.common | 2 ++
> arch/um/kernel/physmem.c | 22 ++++++++++------------
> 2 files changed, 12 insertions(+), 12 deletions(-)
>
> --
> 2.7.4
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2018-07-31 13:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-24 13:23 [PATCH 0/2] um: switch to NO_BOOTMEM Mike Rapoport
2018-07-24 13:23 ` Mike Rapoport
2018-07-24 13:23 ` [PATCH 1/2] um: setup_physmem: stop using global variables Mike Rapoport
2018-07-24 13:23 ` Mike Rapoport
2018-07-24 13:23 ` [PATCH 2/2] um: switch to NO_BOOTMEM Mike Rapoport
2018-07-24 13:23 ` Mike Rapoport
2018-07-31 13:38 ` Mike Rapoport [this message]
2018-07-31 13:38 ` [PATCH 0/2] " Mike Rapoport
2018-07-31 19:03 ` Richard Weinberger
2018-07-31 19:03 ` Richard Weinberger
2018-08-01 12:41 ` Mike Rapoport
2018-08-01 12:41 ` 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=20180731133827.GC23494@rapoport-lnx \
--to=rppt@linux.vnet.ibm.com \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-um@lists.infradead.org \
--cc=mhocko@kernel.org \
--cc=richard@nod.at \
/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.