linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mark Salter <msalter@redhat.com>
To: Mike Rapoport <rppt@linux.ibm.com>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-c6x-dev@linux-c6x.org
Subject: Re: [Linux-c6x-dev] [PATCH RESEND] c6x: switch to NO_BOOTMEM
Date: Sun, 28 Oct 2018 12:30:38 -0400	[thread overview]
Message-ID: <14e021f1976700540d05287ca70f5a0834760f4e.camel@redhat.com> (raw)
In-Reply-To: <6ff7ce1b549ad4a17ebb5d8221edaac57518fca4.camel@redhat.com>

On Sat, 2018-10-27 at 13:20 -0400, Mark Salter wrote:
> On Sat, 2018-10-27 at 10:20 +0100, Mike Rapoport wrote:
> > Hi,
> > 
> > The patch below that switches c6x to NO_BOOTMEM is already merged into c6x
> > tree, but as there were no pull request from c6x during v4.19 merge window
> > it is still not present in Linus' tree.
> > 
> > Probably it would be better to direct it via mm tree to avoid possible
> > conflicts and breakage because of bootmem removal.
> > 
> 
> I had to refresh the patch due to conflict with
> 
> commit be7cd2df1d22d29e5f23ce8744fc465cc07cc2bc
> Author: Rob Herring <robh@kernel.org>
> Date:   Wed Aug 1 15:00:12 2018 -0600
> 
>     c6x: use common built-in dtb support
> 
> The updated patch is in the c6x tree:
> 
> git://linux-c6x.org/git/projects/linux-c6x-upstreaming.git
> commit fe381767b94fc53d3db700ba1d55928a4b5bc6c8

Oops, forgot to add my s-o-b. It's now:

commit 4d8106f0299c7942c5f13a22da6d553d28127ef5
Author: Mike Rapoport <rppt@linux.vnet.ibm.com>
Date:   Mon Jun 25 12:02:34 2018 +0300

    c6x: switch to NO_BOOTMEM

      reply	other threads:[~2018-10-28 16:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-27  9:20 [PATCH RESEND] c6x: switch to NO_BOOTMEM Mike Rapoport
2018-10-27 17:20 ` Mark Salter
2018-10-28 16:30   ` Mark Salter [this message]

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=14e021f1976700540d05287ca70f5a0834760f4e.camel@redhat.com \
    --to=msalter@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-c6x-dev@linux-c6x.org \
    --cc=linux-mm@kvack.org \
    --cc=rppt@linux.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 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).