From: Christoph Hellwig <hch@infradead.org>
To: Christophe Leroy <christophe.leroy@c-s.fr>
Cc: linux-kernel@vger.kernel.org, npiggin@gmail.com,
hch@infradead.org, Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v1 0/4] powerpc: Add support for GENERIC_EARLY_IOREMAP
Date: Wed, 18 Sep 2019 06:40:17 -0700 [thread overview]
Message-ID: <20190918134017.GA22027@infradead.org> (raw)
In-Reply-To: <cover.1568295907.git.christophe.leroy@c-s.fr>
On Thu, Sep 12, 2019 at 01:49:40PM +0000, Christophe Leroy wrote:
> This series adds support for GENERIC_EARLY_IOREMAP on powerpc.
>
> It also adds a warning in the standard ioremap() when it's called
> before vmalloc is available in order to help locate those users.
>
> Next step will be to incrementaly migrate all early users of
> ioremap() to using early_ioremap() or other method.
>
> Once they are all converted we can drop all the logic
> behind ioremap_bot.
Thanks, this looks pretty nice!
prev parent reply other threads:[~2019-09-18 13:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-12 13:49 [PATCH v1 0/4] powerpc: Add support for GENERIC_EARLY_IOREMAP Christophe Leroy
2019-09-12 13:49 ` [PATCH v1 1/4] powerpc/fixmap: don't clear fixmap area in paging_init() Christophe Leroy
2019-11-26 1:13 ` Michael Ellerman
2019-11-27 14:43 ` Christophe Leroy
2019-11-28 8:06 ` Christophe Leroy
2019-09-12 13:49 ` [PATCH v1 2/4] powerpc/fixmap: Use __fix_to_virt() instead of fix_to_virt() Christophe Leroy
2019-11-25 10:47 ` Michael Ellerman
2019-09-12 13:49 ` [PATCH v1 3/4] powerpc: Add support for GENERIC_EARLY_IOREMAP Christophe Leroy
2019-09-12 15:37 ` Aneesh Kumar K.V
2019-09-12 15:43 ` Christophe Leroy
[not found] ` <874l1hsed6.fsf@linux.ibm.com>
2019-09-12 16:01 ` Christophe Leroy
2019-11-25 10:47 ` Michael Ellerman
2019-09-12 13:49 ` [PATCH v1 4/4] powerpc/ioremap: warn on early use of ioremap() Christophe Leroy
2019-11-25 10:47 ` Michael Ellerman
2019-09-18 13:40 ` Christoph Hellwig [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=20190918134017.GA22027@infradead.org \
--to=hch@infradead.org \
--cc=christophe.leroy@c-s.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
--cc=paulus@samba.org \
/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).