From: Tony Lindgren <tony@atomide.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: Hemant Pedanekar <hemantp@ti.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Kevin Hilman <khilman@ti.com>
Subject: Re: [RFC PATCH v2 0/6] TI81XX: Add clock and hwmod data
Date: Wed, 14 Sep 2011 17:33:25 -0700 [thread overview]
Message-ID: <20110915003325.GD30941@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1108301246170.26173@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [110830 11:13]:
> On Tue, 23 Aug 2011, Hemant Pedanekar wrote:
>
> > This patch set is the v2 of TI816X clock and hwmods patches sent earlier.
> >
> > The clock data is currently added only for TI816X, while minimal hwmod data
> > common for TI816X and TI814X is added.
> >
> > This patch set depends on following patches:
> > TI81XX: Prepare for addition of TI814X support
> > TI814X: Add cpu type macros and detection support
> > TI814X: Create board support and enable build for TI8148 EVM
> >
> > Please note that CHIP_IS_TI816X/CHIP_IS_TI814X are still being used and I will
> > send update once SoC list usage is available.
>
> Thanks - am working away on these patches & hope to have them out soon.
Hemant, can you please rebase your patches on Paul's CHIP_IS
removal branch?
It's available at:
git://git.pwsan.com/linux-2.6 omap_chip_remove_cleanup_3.2
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH v2 0/6] TI81XX: Add clock and hwmod data
Date: Wed, 14 Sep 2011 17:33:25 -0700 [thread overview]
Message-ID: <20110915003325.GD30941@atomide.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1108301246170.26173@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [110830 11:13]:
> On Tue, 23 Aug 2011, Hemant Pedanekar wrote:
>
> > This patch set is the v2 of TI816X clock and hwmods patches sent earlier.
> >
> > The clock data is currently added only for TI816X, while minimal hwmod data
> > common for TI816X and TI814X is added.
> >
> > This patch set depends on following patches:
> > TI81XX: Prepare for addition of TI814X support
> > TI814X: Add cpu type macros and detection support
> > TI814X: Create board support and enable build for TI8148 EVM
> >
> > Please note that CHIP_IS_TI816X/CHIP_IS_TI814X are still being used and I will
> > send update once SoC list usage is available.
>
> Thanks - am working away on these patches & hope to have them out soon.
Hemant, can you please rebase your patches on Paul's CHIP_IS
removal branch?
It's available at:
git://git.pwsan.com/linux-2.6 omap_chip_remove_cleanup_3.2
Regards,
Tony
next prev parent reply other threads:[~2011-09-15 0:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-23 17:13 [RFC PATCH v2 0/6] TI81XX: Add clock and hwmod data Hemant Pedanekar
2011-08-23 17:13 ` Hemant Pedanekar
2011-08-30 18:46 ` Paul Walmsley
2011-08-30 18:46 ` Paul Walmsley
2011-09-15 0:33 ` Tony Lindgren [this message]
2011-09-15 0:33 ` Tony Lindgren
2011-09-15 1:41 ` Pedanekar, Hemant
2011-09-15 1:41 ` Pedanekar, Hemant
2011-10-04 9:24 ` Paul Walmsley
2011-10-04 9:24 ` Paul Walmsley
2011-10-05 1:58 ` Pedanekar, Hemant
2011-10-05 1:58 ` Pedanekar, Hemant
2011-10-05 17:37 ` Paul Walmsley
2011-10-05 17:37 ` Paul Walmsley
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=20110915003325.GD30941@atomide.com \
--to=tony@atomide.com \
--cc=hemantp@ti.com \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.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 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.