From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: S3C64XX: Initial support for Wolfson/Simtec Cragganmore/Banff
Date: Wed, 13 Apr 2011 18:24:08 -0700 [thread overview]
Message-ID: <20110414012406.GA3789@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <01bd01cbfa2e$1afae140$50f0a3c0$%kim@samsung.com>
On Thu, Apr 14, 2011 at 07:56:22AM +0900, Kukjin Kim wrote:
> But I'm not sure this can be sent to upstream during the next merge window.
> Because of Linus' complaint, Russell does not want to add new stuff now,
> maybe you know. Basically my tree was sent to upstream via RMK when merge
> window.
Hrm, right. I had thought that the restriction there applied to the
trees that Russell manages directly himself (the core ARM code) rather
than those subtrees which he pulls in for the subarchitectures.
> Hmm...for now I will make some branch for new stuff like this and keep it
> until everyone is happy. Of course, if any consolidation work in Linux ARM
> world, I will update.
> Or...if any good idea, please let me know :)
A separate tree, ideally merged into -next would be good (though of
course that's not really the -next rules...) if we are going to stop
doing any updates to machines.
I guess the other question is how is the device tree work for the
Samsung CPUs going? Grant mentioned that you guys were actively working
on this but I've not found any patches yet (and of course everything
there is blocked on the core ARM device tree work).
next prev parent reply other threads:[~2011-04-14 1:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 14:48 [PATCH] ARM: S3C64XX: Initial support for Wolfson/Simtec Cragganmore/Banff Mark Brown
2011-04-13 22:56 ` Kukjin Kim
2011-04-14 1:24 ` Mark Brown [this message]
2011-04-14 10:14 ` Russell King - ARM Linux
2011-04-14 13:56 ` Mark Brown
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=20110414012406.GA3789@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.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).