All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benoit Cousson <b-cousson@ti.com>
To: Jon Hunter <jon-hunter@ti.com>
Cc: device-tree <devicetree-discuss@lists.ozlabs.org>,
	linux-omap <linux-omap@vger.kernel.org>,
	linux-arm <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 0/3] ARM: dts: OMAP4/5 device-tree timer updates
Date: Thu, 1 Nov 2012 17:14:26 +0100	[thread overview]
Message-ID: <50929FE2.9090602@ti.com> (raw)
In-Reply-To: <1351784967-32520-1-git-send-email-jon-hunter@ti.com>

Hi Jon,

On 11/01/2012 04:49 PM, Jon Hunter wrote:
> A few device tree timer updates for OMAP4/5 devices.
> 
> This series adds ...
> 1. MPU private addresses for OMAP4 timers
> 2. Timer nodes for OMAP5
> 3. 32kHz counter node for OMAP5

Great, thanks for that update. Just in time before the pull request.

> This is based upon of Benoit Cousson's OMAP device-tree branch for v3.8.
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/bcousson/linux-omap-dt.git for_3.8/dts
> 
> Jon Hunter (3):
>   ARM: dts: Update OMAP4 timer addresses
>   ARM: dts: Add OMAP5 timer nodes
>   ARM: dts: Add OMAP5 counter node

I've just updated slightly the subjects:

3b3132f ARM: dts: OMAP5: Add counter node
df692a9 ARM: dts: OMAP5: Add timer nodes
d03a93b ARM: dts: OMAP4: Update timer addresses

There are now in my for_3.8/dts branch.

Thanks,
Benoit

WARNING: multiple messages have this Message-ID (diff)
From: b-cousson@ti.com (Benoit Cousson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] ARM: dts: OMAP4/5 device-tree timer updates
Date: Thu, 1 Nov 2012 17:14:26 +0100	[thread overview]
Message-ID: <50929FE2.9090602@ti.com> (raw)
In-Reply-To: <1351784967-32520-1-git-send-email-jon-hunter@ti.com>

Hi Jon,

On 11/01/2012 04:49 PM, Jon Hunter wrote:
> A few device tree timer updates for OMAP4/5 devices.
> 
> This series adds ...
> 1. MPU private addresses for OMAP4 timers
> 2. Timer nodes for OMAP5
> 3. 32kHz counter node for OMAP5

Great, thanks for that update. Just in time before the pull request.

> This is based upon of Benoit Cousson's OMAP device-tree branch for v3.8.
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/bcousson/linux-omap-dt.git for_3.8/dts
> 
> Jon Hunter (3):
>   ARM: dts: Update OMAP4 timer addresses
>   ARM: dts: Add OMAP5 timer nodes
>   ARM: dts: Add OMAP5 counter node

I've just updated slightly the subjects:

3b3132f ARM: dts: OMAP5: Add counter node
df692a9 ARM: dts: OMAP5: Add timer nodes
d03a93b ARM: dts: OMAP4: Update timer addresses

There are now in my for_3.8/dts branch.

Thanks,
Benoit

  parent reply	other threads:[~2012-11-01 16:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-01 15:49 [PATCH 0/3] ARM: dts: OMAP4/5 device-tree timer updates Jon Hunter
2012-11-01 15:49 ` Jon Hunter
2012-11-01 15:49 ` [PATCH 1/3] ARM: dts: Update OMAP4 timer addresses Jon Hunter
2012-11-01 15:49   ` Jon Hunter
2012-11-01 15:49 ` [PATCH 2/3] ARM: dts: Add OMAP5 timer nodes Jon Hunter
2012-11-01 15:49   ` Jon Hunter
2012-11-01 15:49 ` [PATCH 3/3] ARM: dts: Add OMAP5 counter node Jon Hunter
2012-11-01 15:49   ` Jon Hunter
2012-11-01 16:14 ` Benoit Cousson [this message]
2012-11-01 16:14   ` [PATCH 0/3] ARM: dts: OMAP4/5 device-tree timer updates Benoit Cousson

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=50929FE2.9090602@ti.com \
    --to=b-cousson@ti.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=jon-hunter@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.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.