From: richardcochran@gmail.com (Richard Cochran)
To: linux-arm-kernel@lists.infradead.org
Subject: READ THIS: the next mach-types update
Date: Fri, 16 Sep 2011 12:27:54 +0200 [thread overview]
Message-ID: <20110916102754.GA6205@netboy.at.omicron.at> (raw)
In-Reply-To: <20110915102528.GI6267@n2100.arm.linux.org.uk>
On Thu, Sep 15, 2011 at 11:25:28AM +0100, Russell King - ARM Linux wrote:
> -devixp MACH_DEVIXP DEVIXP 2885
> -miccpt MACH_MICCPT MICCPT 2886
> -mic256 MACH_MIC256 MIC256 2887
Russell,
I had posted support for these some time ago, and shortly thereafter
the whole "clean up the ARM mess" campaign started. I did not follow
up on posting a second time, for fear of adding more churn.
So, my question is, what can I do to keep these in the list?
Can I get plain old board setup files merged (like three of the
following) ...
arch/arm/mach-ixp4xx/Kconfig | 8 +
arch/arm/mach-ixp4xx/Makefile | 2 +
arch/arm/mach-ixp4xx/include/mach/uncompress.h | 2 +-
arch/arm/mach-ixp4xx/miccpt-pci.c | 78 +++++++++
arch/arm/mach-ixp4xx/miccpt-setup.c | 219 ++++++++++++++++++++++++
5 files changed, 308 insertions(+), 1 deletions(-)
or would I have to somehow upgrade to DT?
Thanks,
Richard
next prev parent reply other threads:[~2011-09-16 10:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-15 10:25 READ THIS: the next mach-types update Russell King - ARM Linux
2011-09-15 14:50 ` Jean-Christophe PLAGNIOL-VILLARD
2011-09-16 7:31 ` Russell King - ARM Linux
2011-09-17 2:51 ` Jean-Christophe PLAGNIOL-VILLARD
2011-09-15 15:26 ` Arnd Bergmann
2011-09-15 19:11 ` Russell King - ARM Linux
2011-09-15 19:32 ` Nicolas Pitre
2011-09-15 18:05 ` Olof Johansson
2011-09-16 10:27 ` Richard Cochran [this message]
2011-09-18 15:44 ` Arnd Bergmann
2011-09-19 15:51 ` Richard Cochran
2011-09-17 14:28 ` Pedanekar, Hemant
2011-09-17 14:34 ` Russell King - ARM Linux
2011-09-19 14:51 ` Pedanekar, Hemant
2011-09-19 23:13 ` H Hartley Sweeten
2011-10-17 10:56 ` Russell King - ARM Linux
2011-10-17 11:22 ` Arnd Bergmann
2011-10-17 16:57 ` H Hartley Sweeten
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=20110916102754.GA6205@netboy.at.omicron.at \
--to=richardcochran@gmail.com \
--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).