From: "Cousson, Benoit" <b-cousson@ti.com>
To: "Guruswamy, Senthilvadivu" <svadivu@ti.com>
Cc: "Premi, Sanjeev" <premi@ti.com>,
"khilman@deeprootsystems.com" <khilman@deeprootsystems.com>,
"tomi.valkeinen@nokia.com" <tomi.valkeinen@nokia.com>,
"paul@pwsan.com" <paul@pwsan.com>,
"Hiremath, Vaibhav" <hvaibhav@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH v1 12/16] OMAP3: hwmod DSS: DISPC Move init,exit to driver
Date: Thu, 7 Oct 2010 11:04:17 +0200 [thread overview]
Message-ID: <4CAD8D11.2050500@ti.com> (raw)
In-Reply-To: <FCCFB4CDC6E5564B9182F639FC356087034B94AE77@dbde02.ent.ti.com>
On 10/7/2010 10:44 AM, Guruswamy, Senthilvadivu wrote:
>
>> From: Cousson, Benoit
>> Sent: Thursday, October 07, 2010 12:47 PM
>>
>> Hi Senthil,
>>
>> On 10/7/2010 8:16 AM, Guruswamy, Senthilvadivu wrote:
>>>
>>>> From: Premi, Sanjeev
>>>>
>>>>> From: linux-omap-owner@vger.kernel.org
>>>>>
>>>>> From: Senthilvadivu Guruswamy<svadivu@ti.com>
>>>>>
>>>>> Move init exit methods to its driver probe,remove.
>>>>> pdev member has to be maintained by its own drivers.
>>>>
>>>> [sp] How is this change related to hwmod mentioned in the
>>>> subject line?
>>> [Senthil] As part of the hwmod design, dispc is made as platform driver.
>>> Hence the dispc_init and dispc_exit has to be moved from core
>> "omapdisplay"
>>> Driver to "dss_dispc" platform driver. Pdev is the platform device
>> structure maintained in dss_dispc driver containing silicon specific info
>> like baseaddr, irqs of DISPC HW.
>>
>> It is still not a reason to put hwmod in the subject. That is valid for
>> most patches of this series.
>> You have to put the plaform name then the subsystem if this is related
>> to the OMAP arch directory, which is DSS, not hwmod DSS.
>>
>> In the case of DSS driver changes, then you should start with video:
>> DSS:, or maybe DSS is enough if there is no possible confusion.
>>
>> The goal of that is just to highlight in the subject what part of the
>> kernel you are changing, since the maintainers are not necessarily the
>> same.
> [Senthil] If "hwmod" is creating confusion, it could be removed.
> Is it an ack for this patch series considering that "change in the header" is the only comment to be incorporated?
Mmm, not really, but since it is the subject, this is the very first
things you see. That why it is important to provide good subject :-)
I'll have a look at this series before the end of the week.
Benoit
next prev parent reply other threads:[~2010-10-07 9:04 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-06 11:14 [PATCH v1 00/16] OMAP3: hwmod DSS Adaptation Guruswamy Senthilvadivu
2010-10-06 11:14 ` [PATCH v1 01/16] OMAP2420: hwmod data: add DSS DISPC RFBI VENC Guruswamy Senthilvadivu
2010-10-06 11:14 ` [PATCH v1 02/16] OMAP2430: " Guruswamy Senthilvadivu
2010-10-06 11:14 ` [PATCH v1 03/16] OMAP3: hwmod data: add DSS DISPC RFBI DSI VENC Guruswamy Senthilvadivu
2010-10-06 11:14 ` [PATCH v1 04/16] OMAP3: hwmod data: change dss_hwmod to dss_dss_hwmod Guruswamy Senthilvadivu
2010-10-06 11:14 ` [PATCH v1 05/16] OMAP3 DSS Driver register moved to mach_omap2 Guruswamy Senthilvadivu
2010-10-06 11:14 ` [PATCH v1 06/16] OMAP3: hwmod DSS: Build omap_device for each DSS HWIP Guruswamy Senthilvadivu
2010-10-06 11:14 ` [PATCH v1 07/16] OMAP3: hwmod DSS: Create platform_driver for each DSS HW IP Guruswamy Senthilvadivu
2010-10-06 11:14 ` [PATCH v1 08/16] OMAP3: clock data: change dss driver name Guruswamy Senthilvadivu
2010-10-06 11:14 ` [PATCH v1 09/16] OMAP3: hwmod DSS: Move clocks from core driver to dss driver Guruswamy Senthilvadivu
2010-10-06 11:14 ` [PATCH v1 10/16] OMAP3: hwmod DSS: DSS Move init,exit to driver Guruswamy Senthilvadivu
2010-10-06 11:14 ` [PATCH v1 11/16] OMAP3: hwmod DSS: RFBI " Guruswamy Senthilvadivu
2010-10-06 11:14 ` [PATCH v1 12/16] OMAP3: hwmod DSS: DISPC " Guruswamy Senthilvadivu
2010-10-06 11:14 ` [PATCH v1 13/16] OMAP3: hwmod DSS: VENC " Guruswamy Senthilvadivu
2010-10-06 11:14 ` [PATCH v1 14/16] OMAP3: hwmod DSS: DSI Move init, exit " Guruswamy Senthilvadivu
2010-10-06 11:14 ` [PATCH v1 15/16] OMAP3: hwmod DSS: Use platform device to get baseaddr Guruswamy Senthilvadivu
2010-10-06 11:14 ` [PATCH v1 16/16] OMAP3: hwmod DSS: Get DSS IRQ from platform device Guruswamy Senthilvadivu
2010-10-07 20:00 ` [PATCH v1 14/16] OMAP3: hwmod DSS: DSI Move init, exit to driver Thomas Petazzoni
2010-10-07 19:57 ` [PATCH v1 13/16] OMAP3: hwmod DSS: VENC Move init,exit " Thomas Petazzoni
2010-10-08 7:09 ` Guruswamy, Senthilvadivu
2010-10-06 14:19 ` [PATCH v1 12/16] OMAP3: hwmod DSS: DISPC " Premi, Sanjeev
2010-10-07 6:16 ` Guruswamy, Senthilvadivu
2010-10-07 7:17 ` Cousson, Benoit
2010-10-07 8:44 ` Guruswamy, Senthilvadivu
2010-10-07 9:04 ` Cousson, Benoit [this message]
2010-10-07 19:48 ` Thomas Petazzoni
2010-10-07 19:47 ` [PATCH v1 11/16] OMAP3: hwmod DSS: RFBI " Thomas Petazzoni
2010-10-08 7:13 ` Guruswamy, Senthilvadivu
2010-10-07 19:47 ` [PATCH v1 07/16] OMAP3: hwmod DSS: Create platform_driver for each DSS HW IP Thomas Petazzoni
2010-10-07 19:49 ` Thomas Petazzoni
2010-10-08 7:11 ` Guruswamy, Senthilvadivu
2010-10-08 7:43 ` Thomas Petazzoni
2010-10-07 19:30 ` [PATCH v1 06/16] OMAP3: hwmod DSS: Build omap_device for each DSS HWIP Thomas Petazzoni
2010-10-07 19:06 ` [PATCH v1 05/16] OMAP3 DSS Driver register moved to mach_omap2 Thomas Petazzoni
2010-10-08 6:54 ` Guruswamy, Senthilvadivu
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=4CAD8D11.2050500@ti.com \
--to=b-cousson@ti.com \
--cc=hvaibhav@ti.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=premi@ti.com \
--cc=svadivu@ti.com \
--cc=tomi.valkeinen@nokia.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).