From: "stanley.miao" <stanley.miao@windriver.com>
To: "Syed Mohammed, Khasim" <khasim@ti.com>
Cc: Tony Lindgren <tony@atomide.com>,
Kevin Hilman <khilman@deeprootsystems.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Which directory should OMAP-L137/L138's code in ?
Date: Fri, 12 Jun 2009 20:09:44 +0800 [thread overview]
Message-ID: <4A324588.3010406@windriver.com> (raw)
In-Reply-To: <0680EC522D0CC943BC586913CF3768C00378B66E47@dbde02.ent.ti.com>
Thanks a lot.
Stanley.
Syed Mohammed, Khasim wrote:
> Hi,
>
>
>> -----Original Message-----
>> From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-owner@vger.kernel.org] On Behalf Of Tony
>> Lindgren
>> Sent: Friday, June 12, 2009 4:02 PM
>> To: stanley.miao; Kevin Hilman
>> Cc: linux-omap@vger.kernel.org
>> Subject: Re: Which directory should OMAP-L137/L138's code in ?
>>
>> * stanley.miao <stanley.miao@windriver.com> [090612 02:53]:
>>
>>> I am developing on the board OMAP-L137/L138, which is similar with
>>> Davinci series board. Should I put its platform file in the directory
>>> arch/arm/mach-davinci ? or create a new direcory arch/arch/mach-L1xx for
>>> it ?
>>>
>>> Any suggestions ?
>>>
>> If it uses DaVinci core code to me it sounds like it should be under
>> mach-davinci. Kevin?
>>
>>
>
> The TI code for OMAP L 13x is part of mach-davinci. And the platform specific patches to be submitted to Davinci mailing list for upstream submissions.
>
> Regards,
> Khasim
>
>
next prev parent reply other threads:[~2009-06-12 12:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 9:56 Which directory should OMAP-L137/L138's code in ? stanley.miao
2009-06-12 10:32 ` Tony Lindgren
2009-06-12 10:46 ` Syed Mohammed, Khasim
2009-06-12 12:09 ` stanley.miao [this message]
2009-06-12 14:23 ` Kevin Hilman
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=4A324588.3010406@windriver.com \
--to=stanley.miao@windriver.com \
--cc=khasim@ti.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox