All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Salter <msalter@redhat.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Will Deacon <will.deacon@arm.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"x86@kernel.org" <x86@kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Arnd Bergmann <arnd@arndb.de>, Ingo Molnar <mingo@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Russell King <linux@arm.linux.org.uk>,
	Catalin Marinas <Catalin.Marinas@arm.com>,
	Dave Young <dyoung@redhat.com>,
	Rob Herring <robherring2@gmail.com>,
	Leif Lindholm <leif.lindholm@linaro.org>,
	"patches@linaro.org" <patches@linaro.org>
Subject: Re: [PATCH v4 0/6] generic early_ioremap support
Date: Mon, 03 Mar 2014 17:29:08 -0500	[thread overview]
Message-ID: <1393885748.5094.14.camel@deneb.redhat.com> (raw)
In-Reply-To: <530CF21E.1020603@zytor.com>

On Tue, 2014-02-25 at 11:42 -0800, H. Peter Anvin wrote:
> On 02/25/2014 10:45 AM, Mark Salter wrote:
> > On Tue, 2014-02-25 at 18:30 +0000, Will Deacon wrote:
> >> I'd suggest spitting the core part out from the arch-specific parts. That
> >> way, the core part can merged independently and architectures can move over
> >> as they see fit. It also signals (at least to me) that, "hey, I should
> >> probably review this" whilst my current stance is "there's a whole load of
> >> stuff under mm/ that needs to be acked first".
> >>
> >> If you put the whole thing into next, you just run the risk of conflicts
> >> with all the arch trees.
> > 
> > I've been thinking of breaking out the common bits and x86 bits and just
> > going with that for now. There's no point in just doing the common bits
> > because it won't get tested without at least one architecture using it.
> > 
> 
> If you think it makes sense we could take the common bits + x86 and put
> them through the -tip tree.  The other option would be to put the whole
> thread in linux-next with Acks.
> 
> As far as x86 is concerned it looks like it is mostly just code
> movement, so I'm happy giving my:
> 
> Acked-by: H. Peter Anvin <hpa@linux.intel.com>
> 

I going to send out a v5 with the arm bits dropped and Ack-bys added.
There is still some work left there, so I think I'll redo the arm bits
separately after once the common bits are in the kernel.

Peter, is your Acked-by only for "[3/6] x86: use generic early_ioremap"?
Or did you intend "[1/6] x86/mm: sparse warning fix for early_memremap"
and/or "[2/6] mm: create generic early_ioremap() support" also?



WARNING: multiple messages have this Message-ID (diff)
From: msalter@redhat.com (Mark Salter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/6] generic early_ioremap support
Date: Mon, 03 Mar 2014 17:29:08 -0500	[thread overview]
Message-ID: <1393885748.5094.14.camel@deneb.redhat.com> (raw)
In-Reply-To: <530CF21E.1020603@zytor.com>

On Tue, 2014-02-25 at 11:42 -0800, H. Peter Anvin wrote:
> On 02/25/2014 10:45 AM, Mark Salter wrote:
> > On Tue, 2014-02-25 at 18:30 +0000, Will Deacon wrote:
> >> I'd suggest spitting the core part out from the arch-specific parts. That
> >> way, the core part can merged independently and architectures can move over
> >> as they see fit. It also signals (at least to me) that, "hey, I should
> >> probably review this" whilst my current stance is "there's a whole load of
> >> stuff under mm/ that needs to be acked first".
> >>
> >> If you put the whole thing into next, you just run the risk of conflicts
> >> with all the arch trees.
> > 
> > I've been thinking of breaking out the common bits and x86 bits and just
> > going with that for now. There's no point in just doing the common bits
> > because it won't get tested without at least one architecture using it.
> > 
> 
> If you think it makes sense we could take the common bits + x86 and put
> them through the -tip tree.  The other option would be to put the whole
> thread in linux-next with Acks.
> 
> As far as x86 is concerned it looks like it is mostly just code
> movement, so I'm happy giving my:
> 
> Acked-by: H. Peter Anvin <hpa@linux.intel.com>
> 

I going to send out a v5 with the arm bits dropped and Ack-bys added.
There is still some work left there, so I think I'll redo the arm bits
separately after once the common bits are in the kernel.

Peter, is your Acked-by only for "[3/6] x86: use generic early_ioremap"?
Or did you intend "[1/6] x86/mm: sparse warning fix for early_memremap"
and/or "[2/6] mm: create generic early_ioremap() support" also?

  parent reply	other threads:[~2014-03-03 22:29 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-12 20:56 [PATCH v4 0/6] generic early_ioremap support Mark Salter
2014-02-12 20:56 ` Mark Salter
2014-02-12 20:56 ` [PATCH v4 1/6] x86/mm: sparse warning fix for early_memremap Mark Salter
2014-02-12 20:56 ` [PATCH v4 2/6] mm: create generic early_ioremap() support Mark Salter
2014-02-12 20:56   ` Mark Salter
2014-02-12 20:56 ` [PATCH v4 3/6] x86: use generic early_ioremap Mark Salter
2014-02-12 20:56 ` [PATCH v4 4/6] arm: add early_ioremap support Mark Salter
2014-02-12 20:56   ` Mark Salter
2014-02-26  5:48   ` Rob Herring
2014-02-26  5:48     ` Rob Herring
2014-02-26  9:38     ` Leif Lindholm
2014-02-26  9:38       ` Leif Lindholm
2014-02-26 14:59     ` Mark Salter
2014-02-26 14:59       ` Mark Salter
2014-02-26 15:56       ` Rob Herring
2014-02-26 15:56         ` Rob Herring
2014-02-12 20:56 ` [PATCH v4 5/6] arm64: initialize pgprot info earlier in boot Mark Salter
2014-02-12 20:56   ` Mark Salter
2014-02-12 20:56 ` [PATCH v4 6/6] arm64: add early_ioremap support Mark Salter
2014-02-12 20:56   ` Mark Salter
2014-02-25 14:10 ` [PATCH v4 0/6] generic " Mark Salter
2014-02-25 14:10   ` Mark Salter
2014-02-25 18:30   ` Will Deacon
2014-02-25 18:30     ` Will Deacon
2014-02-25 18:45     ` Mark Salter
2014-02-25 18:45       ` Mark Salter
2014-02-25 19:42       ` H. Peter Anvin
2014-02-25 19:42         ` H. Peter Anvin
2014-02-25 23:04         ` Catalin Marinas
2014-02-25 23:04           ` Catalin Marinas
2014-02-25 23:05           ` H. Peter Anvin
2014-02-25 23:05             ` H. Peter Anvin
2014-03-03 22:29         ` Mark Salter [this message]
2014-03-03 22:29           ` Mark Salter
2014-03-04  1:30           ` H. Peter Anvin
2014-03-04  1:30             ` H. Peter Anvin

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=1393885748.5094.14.camel@deneb.redhat.com \
    --to=msalter@redhat.com \
    --cc=Catalin.Marinas@arm.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=dyoung@redhat.com \
    --cc=hpa@zytor.com \
    --cc=leif.lindholm@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mingo@kernel.org \
    --cc=patches@linaro.org \
    --cc=robherring2@gmail.com \
    --cc=tglx@linutronix.de \
    --cc=will.deacon@arm.com \
    --cc=x86@kernel.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 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.