From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH][RFC] arm: Add basic support for VIA/WonderMedia SoC's
Date: Tue, 13 Jul 2010 08:24:07 +0100 [thread overview]
Message-ID: <20100713072407.GB19839@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <alpine.LFD.2.00.1007121855470.10598@xanadu.home>
On Mon, Jul 12, 2010 at 08:38:26PM -0400, Nicolas Pitre wrote:
> Versatile and RealView are development boards where things like MMU-less
> builds of Linux are tested.
That's not the reason they invented IO_ADDRESS - that exists because
I never pressed the issue early on when the Integrator port was merged,
and their use has spread and become more or less acceptable.
It's just the same as your io_p2v() macro that you used in your SA1100
port.
> I think what you did is OK. It is best to include the whole file as
> generated from the machine registry database when you need it. This way
> the merge conflict can easily be resolved by simply keeping the latest
> version from either merged branches.
Not quite - I'm now undoing some of the changes a mach-types update would
bring because people aren't talking to me to fix stuff in the machine
registry. So I'm no longer just committing the updated file off the
website.
The problem is that git will automatically merge those "updates", which
makes it much more difficult to sort out.
next prev parent reply other threads:[~2010-07-13 7:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 16:50 [PATCH][RFC] arm: Add basic support for VIA/WonderMedia SoC's Alexey Charkov
2010-07-12 17:06 ` Marek Vasut
2010-07-12 17:41 ` Alexey Charkov
2010-07-12 17:51 ` Alexey Charkov
2010-07-12 19:22 ` Arnd Bergmann
2010-07-12 20:03 ` Alexey Charkov
2010-07-13 0:38 ` Nicolas Pitre
2010-07-13 7:24 ` Russell King - ARM Linux [this message]
2010-07-13 8:26 ` Alexey Charkov
2010-07-13 8:29 ` Russell King - ARM Linux
2010-07-13 8:23 ` Alexey Charkov
2010-07-13 12:02 ` Alexey Charkov
2010-07-15 19:31 ` [PATCH v2][RFC] " Alexey Charkov
2010-07-16 11:13 ` Arnd Bergmann
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=20100713072407.GB19839@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