linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matt Porter <mporter@ti.com>
To: "Cousson, Benoit" <b-cousson@ti.com>
Cc: "tony@atomide.com" <tony@atomide.com>,
	'paul Walmsley' <paul@pwsan.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"AnilKumar, Chimata" <anilkumar@ti.com>
Subject: Re: [PATCH RESEND 0/5] ARM: dts: AM33XX: Add device tree data
Date: Fri, 28 Sep 2012 16:48:16 -0400	[thread overview]
Message-ID: <20120928204816.GI5641@beef> (raw)
In-Reply-To: <505A3D4C.4090502@ti.com>

On Wed, Sep 19, 2012 at 04:46:52PM -0500, Benoit Cousson wrote:
> + Matt
> 
> On 9/19/2012 4:28 PM, AnilKumar, Chimata wrote:
> >On Thu, Sep 20, 2012 at 02:53:38, Cousson, Benoit wrote:
> >>+ Paul
> >>
> >>Hi Anil,
> >>
> >>Thanks for the rebase / repost. I'll pulled the full series if Paul is OK with
> >>   ARM: OMAP2+: AM33XX: Add clock entries to omap_clk data
> >>
> 
> What about Matt's series to fix the I2C number? Should it be applied
> on top of that one?

I had the series to fix the GPIO numbering [1]. It's dependent on this
series which carries the led dts patch. Pantelis has a patch for i2c
dts numbering in his i2c series [2]. A hunk in that patch has support
for his i2c pinctrl series mixed in (not sure where that one is due to
the change to early init) so it doesn't apply cleanly alone on top of
for_3.7/dts_part2. If you're willing to pick up that i2c renumbering by
itself I can drop you a patch just for that part.

-Matt

[1] https://patchwork.kernel.org/patch/1433481/
    https://patchwork.kernel.org/patch/1433471/

[2] https://patchwork.kernel.org/patch/1474001/

> 
> Regards,
> Benoit
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2012-09-28 20:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-19 21:19 [PATCH RESEND 0/5] ARM: dts: AM33XX: Add device tree data AnilKumar Ch
2012-09-19 21:19 ` [PATCH RESEND v7 1/5] ARM: dts: AM33XX: Add basic pinctrl " AnilKumar Ch
2012-09-19 21:19 ` [PATCH RESEND v7 2/5] ARM: dts: AM33XX: Add D_CAN " AnilKumar Ch
2012-09-19 21:19 ` [PATCH RESEND 3/5] ARM: OMAP2+: AM33XX: Add clock entries to omap_clk data AnilKumar Ch
2012-09-19 21:24   ` Paul Walmsley
2012-09-19 21:27     ` AnilKumar, Chimata
2012-09-19 21:19 ` [PATCH RESEND v3 4/5] ARM: dts: AM33XX: Add lis331dlh device tree data to am335x-evm AnilKumar Ch
2012-09-19 21:19 ` [PATCH RESEND 5/5] ARM: dts: AM33XX: Add temperature sensor " AnilKumar Ch
2012-09-19 21:23 ` [PATCH RESEND 0/5] ARM: dts: AM33XX: Add device tree data Cousson, Benoit
2012-09-19 21:26   ` Paul Walmsley
2012-09-19 21:36     ` Cousson, Benoit
2012-09-19 21:28   ` AnilKumar, Chimata
2012-09-19 21:46     ` Cousson, Benoit
2012-09-28 20:48       ` Matt Porter [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=20120928204816.GI5641@beef \
    --to=mporter@ti.com \
    --cc=anilkumar@ti.com \
    --cc=b-cousson@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=tony@atomide.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).