From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: "Cousson, Benoit" <b-cousson@ti.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/1] ARM: OMAP4: Remove un-used control module headers and defines.
Date: Mon, 16 Apr 2012 15:04:37 +0530 [thread overview]
Message-ID: <4F8BE7AD.2040505@ti.com> (raw)
In-Reply-To: <4F86D124.8050405@ti.com>
On Thursday 12 April 2012 06:27 PM, Cousson, Benoit wrote:
> Hi Santosh,
>
> On 4/12/2012 12:31 PM, Santosh Shilimkar wrote:
>> Benoit,
>>
>> On Monday 27 February 2012 04:02 PM, Santosh Shilimkar wrote:
>>> Most of the OMAP4 control module register defines are not used and
>>> can be removed. Keep only needed defines and move them to common
>>> control module header just like other OMAP versions.
>>>
>>> Signed-off-by: Santosh Shilimkar<santosh.shilimkar@ti.com>
>>> ---
>>
>> What do you think about this patch ?
>
> I'm fine with it. I'm just wondering if we have to send it right now or
> along with the control module driver implementation we've just started.
>
Let's do that as part of the driver implementation.
Regards
Santosh
WARNING: multiple messages have this Message-ID (diff)
From: santosh.shilimkar@ti.com (Santosh Shilimkar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] ARM: OMAP4: Remove un-used control module headers and defines.
Date: Mon, 16 Apr 2012 15:04:37 +0530 [thread overview]
Message-ID: <4F8BE7AD.2040505@ti.com> (raw)
In-Reply-To: <4F86D124.8050405@ti.com>
On Thursday 12 April 2012 06:27 PM, Cousson, Benoit wrote:
> Hi Santosh,
>
> On 4/12/2012 12:31 PM, Santosh Shilimkar wrote:
>> Benoit,
>>
>> On Monday 27 February 2012 04:02 PM, Santosh Shilimkar wrote:
>>> Most of the OMAP4 control module register defines are not used and
>>> can be removed. Keep only needed defines and move them to common
>>> control module header just like other OMAP versions.
>>>
>>> Signed-off-by: Santosh Shilimkar<santosh.shilimkar@ti.com>
>>> ---
>>
>> What do you think about this patch ?
>
> I'm fine with it. I'm just wondering if we have to send it right now or
> along with the control module driver implementation we've just started.
>
Let's do that as part of the driver implementation.
Regards
Santosh
next prev parent reply other threads:[~2012-04-16 9:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1330338743-24097-1-git-send-email-santosh.shilimkar@ti.com>
2012-04-12 10:31 ` [PATCH 1/1] ARM: OMAP4: Remove un-used control module headers and defines Santosh Shilimkar
2012-04-12 10:31 ` Santosh Shilimkar
2012-04-12 12:57 ` Cousson, Benoit
2012-04-12 12:57 ` Cousson, Benoit
2012-04-16 9:34 ` Santosh Shilimkar [this message]
2012-04-16 9:34 ` Santosh Shilimkar
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=4F8BE7AD.2040505@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=b-cousson@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.