linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Grant Likely" <grant.likely@secretlab.ca>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linuxppc-dev@ozlabs.org, linux-next@vger.kernel.org,
	Paul Mackerras <paulus@samba.org>,
	Jean Delvare <khali@linux-fr.org>,
	Timur Tabi <timur@freescale.com>
Subject: Re: linux-next: manual merge of the powerpc tree
Date: Thu, 3 Jul 2008 08:22:18 -0400	[thread overview]
Message-ID: <9e4733910807030522h1aa0bl1801ecc5fc877c25@mail.gmail.com> (raw)
In-Reply-To: <20080703054739.GA643@secretlab.ca>

On 7/3/08, Grant Likely <grant.likely@secretlab.ca> wrote:
> On Thu, Jul 03, 2008 at 01:39:05PM +1000, Stephen Rothwell wrote:
>  > Hi Paul,
>  >
>  > Today's linux-next merge of the powerpc tree got a conflict in
>  > arch/powerpc/sysdev/fsl_soc.c between commit
>  > 4eac6a8b17ce5ebe66eb94b6a0b43aa3a2bf7ea6 ("i2c-mpc: Convert to an
>  > of_platform driver") from the i2c tree and commits
>
>
> It probably would have been better for this patch to go in via the
>  PowerPC tree.  It only touches powerpc-specific i2c code, not any i2c
>  core code.  There are quite a few MPCxxxx ports which use this driver,
>  I'd be happier to see it dropped from the i2c tree and merged in via
>  either Kumar or myself.
>
>  I'd also like to see some acks from people who have tested this patch
>  before it goes in.  (I'm just as guilty here; I'll apply it and test it
>  to my tree tomorrow).

I'm using it in my system. It doesn't change the function of the i2c
controller, only how drivers get loaded. So if you boot and your
devices are there it is working.

Testing was good when the patch was initially posted in January. In
the last six months the initial patch set has been sliced and diced
into a bunch of different pieces but the contents of this patch are
essentially unchanged.

I don't care which tree it uses to get to mainline, I'd just like to
see it get merged.


>
>
>  g.
>
>


-- 
Jon Smirl
jonsmirl@gmail.com

  reply	other threads:[~2008-07-03 12:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-03  3:39 linux-next: manual merge of the powerpc tree Stephen Rothwell
2008-07-03  5:47 ` Grant Likely
2008-07-03 12:22   ` Jon Smirl [this message]
2008-07-03 15:24     ` Grant Likely
2008-07-04  5:54       ` Grant Likely
2008-07-04  7:35         ` Jean Delvare
  -- strict thread matches above, loose matches on Subject: below --
2008-10-14  1:02 Stephen Rothwell
2008-10-14  1:02 Stephen Rothwell
2008-07-14  5:44 Stephen Rothwell
2008-07-15  1:24 ` Steven Rostedt
2008-07-07 13:07 Stephen Rothwell
2008-07-07 21:13 ` Daniel Walker
2008-07-11 19:01 ` Bartlomiej Zolnierkiewicz
2008-07-12  3:41   ` Benjamin Herrenschmidt
2008-07-01  6:48 Stephen Rothwell

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=9e4733910807030522h1aa0bl1801ecc5fc877c25@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=grant.likely@secretlab.ca \
    --cc=khali@linux-fr.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.org \
    --cc=sfr@canb.auug.org.au \
    --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).