All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: David Woodhouse <dwmw2@infradead.org>,
	Brian Norris <computersforpeace@gmail.com>,
	Boris BREZILLON <boris.brezillon@free-electrons.com>,
	Mark Vasut <marek.vasut@gmail.com>,
	Richard Weinberger <richard@nod.at>,
	linux-mtd@lists.infradead.org
Subject: Re: [PATCH 1/2] mtd: physmap_of: Move custom initialization
Date: Sun, 14 Oct 2018 08:34:44 +0200	[thread overview]
Message-ID: <20181014083444.6e8f5b59@bbrezillon> (raw)
In-Reply-To: <CACRpkdYin5kj1p3Z2h2ugwMSSHeLMCabb5gdLMSNhmX+_EZADA@mail.gmail.com>

On Sat, 13 Oct 2018 18:26:00 +0200
Linus Walleij <linus.walleij@linaro.org> wrote:

> On Fri, Oct 12, 2018 at 11:21 AM Boris Brezillon
> <boris.brezillon@bootlin.com> wrote:
> > Linus Walleij <linus.walleij@linaro.org> wrote:  
> 
> > > In order to be able to assign custom complex mappings
> > > to the physmap_of plugin for Gemini, move the initialization
> > > so that the simple map is initialized before we enter the
> > > platform-specific functions so the latter can override
> > > them.  
> >
> > I forgot to Cc you but I'm currently reworking the physmap driver to
> > merge the physmap_of logic in it [1]. I'll probably ask you to rebase
> > this patchset on top of mtd/next once [1] is applied.  
> 
> No problem. Will you apply it after v4.20-rc1?

Yep, that's the plan.

      reply	other threads:[~2018-10-14  6:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-11 18:53 [PATCH 1/2] mtd: physmap_of: Move custom initialization Linus Walleij
2018-10-11 18:53 ` [PATCH 2/2] mtd: physmap_of_gemini: Handle pin control Linus Walleij
2018-10-12  9:20 ` [PATCH 1/2] mtd: physmap_of: Move custom initialization Boris Brezillon
2018-10-13 16:26   ` Linus Walleij
2018-10-14  6:34     ` Boris Brezillon [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=20181014083444.6e8f5b59@bbrezillon \
    --to=boris.brezillon@bootlin.com \
    --cc=boris.brezillon@free-electrons.com \
    --cc=computersforpeace@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=marek.vasut@gmail.com \
    --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.