From: shc_work@mail.ru (Alexander Shiyan)
To: linux-arm-kernel@lists.infradead.org
Subject: Question: Multiple board support is broken
Date: Sat, 8 Dec 2012 15:59:38 +0400 [thread overview]
Message-ID: <20121208155938.8faa133640a42ba33921f7f7@mail.ru> (raw)
In-Reply-To: <20121208112353.GD14363@n2100.arm.linux.org.uk>
On Sat, 8 Dec 2012 11:23:53 +0000
Russell King - ARM Linux <linux@arm.linux.org.uk> wrote:
> On Sat, Dec 08, 2012 at 03:18:59PM +0400, Alexander Shiyan wrote:
> > Well, I understand your position on optimization. Can we at least replace
> > definition machine_arch_type by variable __machine_arch_type, which is passed
> > to the function setup_machine_tags() in setup_arch() procedure? Or have I
> > misunderstood something again?
>
> Err, no I don't think you have. Looks like the initial erroring out got
> broken by the addition of DT support and all the changes that happened
> after that.
>
> Given that the initial assembly code which errored out on non-supported
> platforms seems to have been deleted, that does need to be changed.
> Please send a patch just for that.
Do it now, please check the following patch.
--
Alexander Shiyan <shc_work@mail.ru>
next prev parent reply other threads:[~2012-12-08 11:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 15:31 Question: Multiple board support is broken Alexander Shiyan
2012-12-07 16:17 ` Russell King - ARM Linux
2012-12-08 8:28 ` Alexander Shiyan
2012-12-08 9:26 ` Russell King - ARM Linux
2012-12-08 9:58 ` Alexander Shiyan
2012-12-08 10:38 ` Russell King - ARM Linux
2012-12-08 11:18 ` Alexander Shiyan
2012-12-08 11:23 ` Russell King - ARM Linux
2012-12-08 11:59 ` Alexander Shiyan [this message]
2012-12-08 12:02 ` [PATCH] ARM: Do not use definition "machine_arch_type" outside mach-types.h Alexander Shiyan
2012-12-08 12:14 ` Russell King - ARM Linux
2012-12-09 5:21 ` [PATCH] ARM: Pass real "__machine_arch_type" variable to setup_machine_tags() procedure Alexander Shiyan
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=20121208155938.8faa133640a42ba33921f7f7@mail.ru \
--to=shc_work@mail.ru \
--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).