From: Will Deacon <will.deacon@arm.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
"linux@roeck-us.net" <linux@roeck-us.net>,
"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
"matt@codeblueprint.co.uk" <matt@codeblueprint.co.uk>,
"Yu, Fenghua" <fenghua.yu@intel.com>
Subject: Re: [PATCH v2 1/2] ia64: split off early_ioremap() declarations into asm/early_ioremap.h
Date: Wed, 13 Jan 2016 10:34:55 +0000 [thread overview]
Message-ID: <20160113103454.GD25458@arm.com> (raw)
In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F39FAC179@ORSMSX114.amr.corp.intel.com>
On Tue, Jan 12, 2016 at 09:33:46PM +0000, Luck, Tony wrote:
> > So create a <asm/early_ioremap.h> for ia64, and move the existing
> > definitions into it.
>
> These look OK.
>
> Acked-by: Tony Luck <toy.luck@intel.com>
s/toy/tony/ ;)
> Can you put them into the same tree where the pending breakage is sitting?
> Then I don't have to worry about coordinating pull requests from the ia64
> tree.
The arm trees have already been pulled, so the breakage is in mainline.
I think it makes the most sense to fix this either via the ia64 or the
efi tree, but I'll queue something at -rc1 if it's still not resolved by
then.
Will
next prev parent reply other threads:[~2016-01-13 10:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 13:22 [PATCH v2 1/2] ia64: split off early_ioremap() declarations into asm/early_ioremap.h Ard Biesheuvel
2016-01-12 13:22 ` Ard Biesheuvel
[not found] ` <1452604966-9905-1-git-send-email-ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-01-12 13:22 ` [PATCH v2 2/2] efi: include asm/early_ioremap.h not asm/efi.h to get early_memremap Ard Biesheuvel
2016-01-12 13:22 ` Ard Biesheuvel
2016-01-12 21:33 ` [PATCH v2 1/2] ia64: split off early_ioremap() declarations into asm/early_ioremap.h Luck, Tony
2016-01-12 21:33 ` Luck, Tony
2016-01-13 10:34 ` Will Deacon [this message]
2016-01-13 21:36 ` Luck, Tony
2016-01-14 7:19 ` Ard Biesheuvel
2016-01-14 7:19 ` Ard Biesheuvel
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=20160113103454.GD25458@arm.com \
--to=will.deacon@arm.com \
--cc=ard.biesheuvel@linaro.org \
--cc=fenghua.yu@intel.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=matt@codeblueprint.co.uk \
--cc=tony.luck@intel.com \
/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.