All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Mike Rapoport <rppt@linux.ibm.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	Marc Gonzalez <marc.w.gonzalez@free.fr>,
	Frank Rowand <frowand.list@gmail.com>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Prateek Patel <prpatel@nvidia.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] of: fix kmemleak crash caused by imbalance in early memory reservation
Date: Wed, 13 Feb 2019 13:47:24 -0800	[thread overview]
Message-ID: <20190213134724.f134e3388b591016e96cbf56@linux-foundation.org> (raw)
In-Reply-To: <20190213211329.GD15270@rapoport-lnx>

On Wed, 13 Feb 2019 23:13:29 +0200 Mike Rapoport <rppt@linux.ibm.com> wrote:

> > > As a bonus, since memblock_find_in_range() ensures the allocation in the
> > > specified range, the bounds check can be removed.
> > 
> > hm, why is this against -mm rather than against mainline?
> > 
> > Do the OF maintainers intend to merge the fix?
> 
> There's a conflict this fix and resent memblock related changes in -mm.
> Rob said he anyway wasn't planning to to send this for 5.0 [1] and
> suggested to merge it via your tree.
> 
> [1] https://lore.kernel.org/lkml/CAL_JsqK-cC6oVZ9MkP+ExOGjCRhA0XxGSgqGKL3W9bFF3rKAgA@mail.gmail.com/

OK, thanks, no probs.

      reply	other threads:[~2019-02-13 21:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-13 18:19 Mike Rapoport
2019-02-13 18:19 ` Mike Rapoport
2019-02-13 20:12 ` Andrew Morton
2019-02-13 21:13   ` Mike Rapoport
2019-02-13 21:47     ` Andrew Morton [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=20190213134724.f134e3388b591016e96cbf56@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=catalin.marinas@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=frowand.list@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=marc.w.gonzalez@free.fr \
    --cc=prpatel@nvidia.com \
    --cc=robh+dt@kernel.org \
    --cc=rppt@linux.ibm.com \
    --subject='Re: [PATCH v3] of: fix kmemleak crash caused by imbalance in early memory reservation' \
    /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

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.