From: msalter@redhat.com (Mark Salter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/5] mm: create generic early_ioremap() support
Date: Wed, 08 Jan 2014 11:09:48 -0500 [thread overview]
Message-ID: <1389197388.29144.37.camel@deneb.redhat.com> (raw)
In-Reply-To: <52CC89B4.4060300@zytor.com>
On Tue, 2014-01-07 at 15:11 -0800, H. Peter Anvin wrote:
> On 01/06/2014 06:35 PM, Mark Salter wrote:
> >
> > There is one difference from the existing x86 implementation which
> > should be noted. The generic early_memremap() function does not return
> > an __iomem pointer and a new early_memunmap() function has been added
> > to act as a wrapper for early_iounmap() but with a non __iomem pointer
> > passed in. This is in line with the first patch of this series:
> >
>
> This makes a lot of sense. However, I would suggest that we preface the
> patch series with a single patch changing the signature for the existing
> x86 function, that way this change becomes bisectable.
Ok, that sounds like a good idea. I'm uncertain how best to coordinate
with Dave Young's patch series to avoid conflicts. His first patch does
the signature change (and adds the early_memunmap function but that
isn't used anywhere):
https://lkml.org/lkml/2013/12/20/143
Any thoughts on how best to avoid potential merge conflicts here?
next prev parent reply other threads:[~2014-01-08 16:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 2:35 [PATCH v2 0/5] generic early_ioremap support Mark Salter
2014-01-07 2:35 ` [PATCH v2 1/5] mm: create generic early_ioremap() support Mark Salter
2014-01-07 15:25 ` Catalin Marinas
2014-01-07 23:11 ` H. Peter Anvin
2014-01-08 16:09 ` Mark Salter [this message]
2014-01-09 10:15 ` Matt Fleming
2014-01-07 2:35 ` [PATCH v2 3/5] arm: add early_ioremap support Mark Salter
2014-01-07 17:23 ` Catalin Marinas
2014-01-07 2:35 ` [PATCH v2 4/5] arm64: initialize pgprot info earlier in boot Mark Salter
2014-01-07 2:35 ` [PATCH v2 5/5] arm64: add early_ioremap support Mark Salter
2014-01-07 17:26 ` [PATCH v2 0/5] generic " Catalin Marinas
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=1389197388.29144.37.camel@deneb.redhat.com \
--to=msalter@redhat.com \
--cc=linux-arm-kernel@lists.infradead.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).