All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Burton <paul.burton@mips.com>
To: Fancer's opinion <fancer.lancer@gmail.com>,
	Mike Rapoport <rppt@linux.vnet.ibm.com>
Cc: Linux-MIPS <linux-mips@linux-mips.org>,
	Ralf Baechle <ralf@linux-mips.org>,
	James Hogan <jhogan@kernel.org>, Huacai Chen <chenhc@lemote.com>,
	Michal Hocko <mhocko@kernel.org>,
	linux-mm@kvack.org, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mips: switch to NO_BOOTMEM
Date: Wed, 8 Aug 2018 14:42:15 -0700	[thread overview]
Message-ID: <20180808214215.bf6hyurv3nunfynd@pburton-laptop> (raw)
In-Reply-To: <CAMPMW8qq-aEm-0dQrWh08SBBSRp3xAqR1PL5Oe-RvkJgUk6LjA@mail.gmail.com>

Hi Sergey & Mike,

On Thu, Aug 09, 2018 at 12:30:03AM +0300, Fancer's opinion wrote:
> Hello Mike,
> I haven't read your patch text yet. I am waiting for the subsystem
> maintainers response at least
> about the necessity to have this type of changes being merged into the
> sources (I mean
> memblock/no-bootmem alteration). If they find it pointless (although I
> would strongly disagree), then
> nothing to discuss. Otherwise we can come up with a solution.
> 
> -Sergey

I'm all for dropping bootmem.

It's too late for something this invasive in 4.19, but I'd love to get
it into 4.20.

Thanks,
    Paul

  reply	other threads:[~2018-08-08 21:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-16  7:47 [PATCH] mips: switch to NO_BOOTMEM Mike Rapoport
2018-07-26  7:03 ` Mike Rapoport
2018-07-26 17:20   ` Paul Burton
2018-07-26 19:55     ` Fancer's opinion
2018-08-02 11:55       ` Mike Rapoport
2018-08-02 11:55         ` Mike Rapoport
2018-08-08 21:30         ` Fancer's opinion
2018-08-08 21:42           ` Paul Burton [this message]
2018-08-09 12:34             ` Mike Rapoport
2018-07-27 21:23     ` 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=20180808214215.bf6hyurv3nunfynd@pburton-laptop \
    --to=paul.burton@mips.com \
    --cc=chenhc@lemote.com \
    --cc=fancer.lancer@gmail.com \
    --cc=jhogan@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@kernel.org \
    --cc=ralf@linux-mips.org \
    --cc=rppt@linux.vnet.ibm.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.