linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@secretlab.ca>
To: Anton Vorontsov <avorontsov@ru.mvista.com>
Cc: Linuxppc-dev@ozlabs.org, Timur Tabi <timur@freescale.com>,
	i2c@lm-sensors.org
Subject: Re: [PATCH 1/2] Convert i2c-mpc from a platform driver into a of_platform driver, V4
Date: Fri, 11 Jul 2008 12:54:23 -0600	[thread overview]
Message-ID: <20080711185423.GA15828@secretlab.ca> (raw)
In-Reply-To: <20080711184556.GA14368@polina.dev.rtsoft.ru>

On Fri, Jul 11, 2008 at 10:45:56PM +0400, Anton Vorontsov wrote:
> On Fri, Jul 11, 2008 at 12:12:14PM -0600, Grant Likely wrote:
> > On Thu, Jul 10, 2008 at 12:36:58PM -0400, Timur Tabi wrote:
> > >
> > > On Jul 9, 2008, at 1:22 PM, Grant Likely wrote:
> > >
> > >> On Mon, Jun 30, 2008 at 5:01 PM, Jon Smirl <jonsmirl@gmail.com> wrote:
> > >>> Convert i2c-mpc to an of_platform driver. Utilize the code in  
> > >>> drivers/of-i2c.c to make i2c modules dynamically loadable by the  
> > >>> device tree.
> > >>
> > >> Timur, can you please test this one on an 83xx platform?  It works on
> > >> 5200, but I want to make sure 83xx doesn't break before I pick it up.
> > >
> > > I'm on vacation this week, so I'll have to deal with it next week, after 
> > > I've handled higher-priority issues.
> > 
> > Kumar, is there anyone else who can test this out before the merge
> > window opens?
> 
> FWIW, they seem to work for me. At least RTC still works.

Good enough for me.  Unless someone screams really loudly I'm going to
go ahead and pick it up.

Cheers,
g.

      reply	other threads:[~2008-07-11 18:54 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-30 23:01 [PATCH 1/2] Convert i2c-mpc from a platform driver into a of_platform driver, V4 Jon Smirl
2008-06-30 23:01 ` [PATCH 2/2] Add the of_find_i2c_device_by_node function, V4 Jon Smirl
2008-07-01 15:05   ` Jean Delvare
2008-07-01 15:12     ` Jon Smirl
2008-07-01 16:29       ` Jean Delvare
2008-07-01 16:38         ` Jon Smirl
2008-07-01 16:44           ` Jean Delvare
2008-07-01 16:45         ` Grant Likely
2008-07-01 17:01           ` Jean Delvare
2008-07-01 17:06             ` Jon Smirl
2008-07-01 18:24               ` Jean Delvare
2008-07-01 16:43       ` Grant Likely
2008-07-01 17:00         ` Jon Smirl
2008-07-01 17:12           ` Jean Delvare
2008-07-01 17:27             ` Jon Smirl
2008-07-01 18:18               ` Jon Smirl
2008-07-01 18:51               ` Jean Delvare
2008-07-01 15:48     ` Jochen Friedrich
2008-07-01 16:29     ` Jon Smirl
2008-07-01 16:35       ` Jean Delvare
2008-07-01 16:14 ` [PATCH 1/2] Convert i2c-mpc from a platform driver into a of_platform driver, V4 Jean Delvare
2008-07-02 13:33   ` [i2c] " Wolfram Sang
2008-07-02 14:36     ` Jean Delvare
2008-07-09 17:22 ` Grant Likely
2008-07-10 16:36   ` Timur Tabi
2008-07-11 18:12     ` Grant Likely
2008-07-11 18:45       ` Anton Vorontsov
2008-07-11 18:54         ` Grant Likely [this message]

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=20080711185423.GA15828@secretlab.ca \
    --to=grant.likely@secretlab.ca \
    --cc=Linuxppc-dev@ozlabs.org \
    --cc=avorontsov@ru.mvista.com \
    --cc=i2c@lm-sensors.org \
    --cc=timur@freescale.com \
    /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).