From: michael@walle.cc (Michael Walle)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Add lsxhl machine type to mach-types
Date: Sun, 13 Nov 2011 00:40:42 +0100 [thread overview]
Message-ID: <201111130040.42616.michael@walle.cc> (raw)
In-Reply-To: <20111112230157.GB27746@n2100.arm.linux.org.uk>
Am Sonntag 13 November 2011, 00:01:57 schrieb Russell King - ARM Linux:
> Please read the comments at the top of the file:
sorry, read that over.
> # This is a cut-down version of the file; it contains only machines that
> # are merged into mainline or have been edited in the machine database
> # within the last 12 months. References to machine_is_NAME() do not count!
>
> It gives you the criteria for entries being removed from the file.
>
> What guarantee do we have that support for this platform will be found
> to be acceptable (in it's non-DT form) and will be accepted into mainline
> (which is the basic requirement for the entry staying in the kernel's
> version of this file.)
ok, if only non-dt machine entries will stay in this file, this request is
already obsolete. my initial non-dt support patch was NAK'ed because the
kirkwood arch doesn't accept old-fashioned board support patches anymore.
then, i guess, the problem is on the uboot side, at least if they want to
support both device tree based and old-fashioned setup code (eg. backported
device support.)
--
Michael
next prev parent reply other threads:[~2011-11-12 23:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 20:54 [PATCH] ARM: Add lsxhl machine type to mach-types Michael Walle
2011-11-12 16:02 ` Michael Walle
2011-11-12 23:01 ` Russell King - ARM Linux
2011-11-12 23:40 ` Michael Walle [this message]
2011-11-12 23:55 ` Russell King - ARM Linux
2011-11-13 0:29 ` Marek Vasut
2011-11-13 8:28 ` Russell King - ARM Linux
2011-11-13 16:20 ` Marek Vasut
2011-11-13 21:06 ` Russell King - ARM Linux
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=201111130040.42616.michael@walle.cc \
--to=michael@walle.cc \
--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).