All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@ti.com>
To: "Pedanekar, Hemant" <hemantp@ti.com>
Cc: Paul Walmsley <paul@pwsan.com>, "Grosen, Mark" <mgrosen@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"tony@atomide.com" <tony@atomide.com>,
	"linux@arm.linux.org.uk" <linux@arm.linux.org.uk>,
	"Cousson, Benoit" <b-cousson@ti.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: RE: [PATCH 1/2] TI816X: Add minimal hwmod data
Date: Thu, 14 Jul 2011 14:58:10 -0700	[thread overview]
Message-ID: <1310680690.8322.41.camel@vence> (raw)
In-Reply-To: <2A3DCF3DA181AD40BDE86A3150B27B6B03AB5FAAAB@dbde02.ent.ti.com>

Hi Hemant,

On Wed, 2011-07-13 at 05:07 +0530, Pedanekar, Hemant wrote:

> Any comments on the hwmod and clock patch sets?

I just discovered that other devices in this family are coming along
which will require changing the names/macros/etc. from 816x to 81xx[1].

Merging this series, followed shortly by another series that renames
everything is the type of churn we are trying to avoid.

To avoid this kind of churn, I recommend starting from the broader
family name first.

Kevin

http://arago-project.org/git/projects/?p=linux-omap3.git;a=commit;h=ce17fa2f527ed614399e577fc2fd5cd3624ee501


WARNING: multiple messages have this Message-ID (diff)
From: khilman@ti.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] TI816X: Add minimal hwmod data
Date: Thu, 14 Jul 2011 14:58:10 -0700	[thread overview]
Message-ID: <1310680690.8322.41.camel@vence> (raw)
In-Reply-To: <2A3DCF3DA181AD40BDE86A3150B27B6B03AB5FAAAB@dbde02.ent.ti.com>

Hi Hemant,

On Wed, 2011-07-13 at 05:07 +0530, Pedanekar, Hemant wrote:

> Any comments on the hwmod and clock patch sets?

I just discovered that other devices in this family are coming along
which will require changing the names/macros/etc. from 816x to 81xx[1].

Merging this series, followed shortly by another series that renames
everything is the type of churn we are trying to avoid.

To avoid this kind of churn, I recommend starting from the broader
family name first.

Kevin

http://arago-project.org/git/projects/?p=linux-omap3.git;a=commit;h=ce17fa2f527ed614399e577fc2fd5cd3624ee501

  reply	other threads:[~2011-07-14 21:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-27 16:33 [PATCH 1/2] TI816X: Add minimal hwmod data Hemant Pedanekar
2011-04-27 16:33 ` Hemant Pedanekar
2011-04-28 22:35 ` Paul Walmsley
2011-04-28 22:35   ` Paul Walmsley
2011-04-28 22:44   ` Grosen, Mark
2011-04-28 22:44     ` Grosen, Mark
2011-04-29  2:58     ` Paul Walmsley
2011-04-29  2:58       ` Paul Walmsley
2011-07-12 23:37       ` Pedanekar, Hemant
2011-07-12 23:37         ` Pedanekar, Hemant
2011-07-14 21:58         ` Kevin Hilman [this message]
2011-07-14 21:58           ` Kevin Hilman
2011-07-15  0:45           ` Pedanekar, Hemant
2011-07-15  0:45             ` Pedanekar, Hemant
2011-07-16  8:08         ` Paul Walmsley
2011-07-16  8:08           ` Paul Walmsley
2011-08-04 17:23           ` Pedanekar, Hemant
2011-08-04 17:23             ` Pedanekar, Hemant

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=1310680690.8322.41.camel@vence \
    --to=khilman@ti.com \
    --cc=b-cousson@ti.com \
    --cc=hemantp@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mgrosen@ti.com \
    --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 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.