All of lore.kernel.org
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/6] ux500: Export SoC information and some platform clean-up
Date: Thu, 26 Jan 2012 16:56:35 -0800	[thread overview]
Message-ID: <20120127005635.GA32478@kroah.com> (raw)
In-Reply-To: <201201261520.43176.arnd@arndb.de>

On Thu, Jan 26, 2012 at 03:20:43PM +0000, Arnd Bergmann wrote:
> On Wednesday 25 January 2012, Lee Jones wrote:
> > >>> Everyone else, who is planning to use the infrastructure besides ux500?
> > >>
> > >> I can easily see this being used in the ARM reference designs
> > >> (Integrator, Versatile, RealView and Versatile Express) some of them
> > >> I can possibly patch myself even. OMAP has expressed interest
> > >> in "some way of getting the SoC ID out", and I guess this is
> > >> the means to that end.
> > > 
> > > Ah, good. Once these patches are merged, we can easily refer anyone
> > > to this infrastructure if they try to add a different way of finding
> > > a SoC ID.
> > 
> > Okay, so this sounds promising. Which route are the patches likely to
> > take? Will they go up through your SoC tree Arnd?
> 
> That's probably the best way. Of course you need to have Acks
> from Greg (for the bus) and Linus Walleij (for the ux500 stuff)
> before I can merge them. Linus can decide whether he wants to
> submit them to me through a pull request from his ux500 tree
> (with Signed-off-by) or whether I should apply them myself
> (with Ack).

I'll try to review these again tomorrow...

  reply	other threads:[~2012-01-27  0:56 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-21 17:08 [PATCH 0/6] ux500: Export SoC information and some platform clean-up Lee Jones
2012-01-21 17:08 ` [PATCH 1/6] mach-ux500: pass parent pointer to each platform device Lee Jones
2012-01-21 17:08 ` [PATCH 2/6] drivers/base: add bus for System-on-Chip devices Lee Jones
2012-01-28  1:05   ` Greg KH
2012-01-30 17:58     ` Arnd Bergmann
2012-01-30 18:34       ` Greg KH
2012-01-21 17:08 ` [PATCH 3/6] Documentation: add information for new sysfs soc bus functionality Lee Jones
2012-01-21 17:08 ` [PATCH 4/6] mach-ux500: export System-on-Chip information ux500 via sysfs Lee Jones
2012-01-21 17:08 ` [PATCH 5/6] mach-ux500: move top level platform devices in sysfs to /sys/devices/socX Lee Jones
2012-01-21 17:08 ` [PATCH 6/6] mach-ux500: remove intermediary add_platform_device* functions Lee Jones
2012-01-23 15:58 ` [PATCH 0/6] ux500: Export SoC information and some platform clean-up 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 [this message]
2012-01-27 14:00           ` Linus Walleij
  -- strict thread matches above, loose matches on Subject: below --
2012-02-06 19:22 Lee Jones
2012-02-06 19:33 ` Linus Walleij
2012-02-10 19:43 ` Greg KH
2012-02-13  6:28   ` Arnd Bergmann
2012-02-13 19:54     ` Linus Walleij
2012-02-01  9:23 Lee Jones
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=20120127005635.GA32478@kroah.com \
    --to=greg@kroah.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 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.