From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: omap: complete removal of machine_desc.io_pg_offst and .phys_io
Date: Mon, 18 Oct 2010 15:12:30 +0100 [thread overview]
Message-ID: <20101018141230.GD12449@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1287406656-24133-1-git-send-email-gadiyar@ti.com>
On Mon, Oct 18, 2010 at 06:27:36PM +0530, Anand Gadiyar wrote:
> Commit 861bd81ee6 in linux-next as of 20101018 (arm: remove
> machine_desc.io_pg_offst and .phys_io) missed out on updating
> a few boards. This causes the build of omap2plus_defconfig
> to fail. Fix this.
Not quite true. The patch merged into my tree eliminates io_pg_offst and
phys_io for everything that is in my tree.
For new board support code which isn't in my tree, there is a problem -
patches to it can't be applied to my tree.
However, applying these patches to the trees which have the new code in
won't have the other changes related to the removal of io_pg_offst, and
so the support code will subtly break until it's all merged together.
There's two solutions to this. One is to wait merging new board code
until after this merge window. The other is to ensure that new board
code is in _my_ tree before the io_pg_offst changes were submitted...
next prev parent reply other threads:[~2010-10-18 14:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-18 12:57 [PATCH] arm: omap: complete removal of machine_desc.io_pg_offst and .phys_io Anand Gadiyar
2010-10-18 14:12 ` Russell King - ARM Linux [this message]
2010-10-18 14:21 ` Russell King - ARM Linux
2010-10-18 21:45 ` Tony Lindgren
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=20101018141230.GD12449@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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