From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/6] ux500: Export SoC information and some platform clean-up
Date: Mon, 13 Feb 2012 06:28:00 +0000 [thread overview]
Message-ID: <201202130628.01081.arnd@arndb.de> (raw)
In-Reply-To: <20120210194358.GA5537@kroah.com>
On Friday 10 February 2012, Greg KH wrote:
> On Mon, Feb 06, 2012 at 11:22:20AM -0800, Lee Jones wrote:
> > This patch-set satisfies 4 objectives:
> > 1. Ensures each platform device can specify a suitable parent
> > 2. Provides a bus for SoC devices as a means to export information
> > 3. Allows ux500 to make use of the new SoC bus
> > 4. Cleans up unnecessary complexity from ux500 code
>
> I've applied the driver-core bits, nice job in sticking with this. I'll
> let the other bits trickle through the arch-specific trees.
Ok, very good. Thanks both of you for your patience. I'm looking forward
to many good patches from Lee now that he has made it through this.
IIRC it was mostly an attempt for Lee to start contributing one of the
"simpler" patches from the st-ericsson internal tree in order to get
started. My feeling is that almost any other patch would have been easier
because it does not involve infrastructure and APIs, but this was certainly
a learning experience ;-).
I've applied the ux500 patches onto the ux500/soc branch of the arm-soc
tree now and added the current head of the driver-core tree as the
next/driver-core branch in the same tree. I will keep track of this
and send out the ux500 patches during the next merge window after the
core changes have been merged. Other platforms are very welcome to
send patches based on the same interface for 3.4. I know from working
with Greg that he does not rebase his trees, so I assume this is the
best approach.
Arnd
next prev parent reply other threads:[~2012-02-13 6:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-06 19:22 [PATCH 0/6] ux500: Export SoC information and some platform clean-up Lee Jones
2012-02-06 19:22 ` [PATCH 1/6] mach-ux500: pass parent pointer to each platform device Lee Jones
2012-02-06 19:22 ` [PATCH 2/6] drivers/base: add bus for System-on-Chip devices Lee Jones
2012-02-06 19:22 ` [PATCH 3/6] Documentation: add information for new sysfs soc bus functionality Lee Jones
2012-02-06 19:22 ` [PATCH 4/6] mach-ux500: export System-on-Chip information ux500 via sysfs Lee Jones
2012-02-06 19:22 ` [PATCH 5/6] mach-ux500: move top level platform devices in sysfs to /sys/devices/socX Lee Jones
2012-02-06 19:22 ` [PATCH 6/6] mach-ux500: remove intermediary add_platform_device* functions Lee Jones
2012-02-06 19:33 ` [PATCH 0/6] ux500: Export SoC information and some platform clean-up Linus Walleij
2012-02-10 19:43 ` Greg KH
2012-02-13 6:28 ` Arnd Bergmann [this message]
2012-02-13 19:54 ` Linus Walleij
-- strict thread matches above, loose matches on Subject: below --
2012-02-01 9:23 Lee Jones
2012-01-21 17:08 Lee Jones
2012-01-23 15:58 ` Arnd Bergmann
2012-01-23 16:03 ` Arnd Bergmann
2012-01-24 22:53 ` Linus Walleij
2012-01-25 15:01 ` Arnd Bergmann
2012-01-25 17:16 ` Lee Jones
2012-01-26 15:20 ` Arnd Bergmann
2012-01-27 0:56 ` Greg KH
2012-01-27 14:00 ` Linus Walleij
2012-01-20 16:10 Lee Jones
2011-10-17 11:52 Lee Jones
2011-10-17 11:52 ` Lee Jones
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=201202130628.01081.arnd@arndb.de \
--to=arnd@arndb.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.