From: Sergei Shtylyov <sshtylyov@mvista.com>
To: "Karicheri, Muralidharan" <m-karicheri2@ti.com>
Cc: "Hadli, Manjunath" <manjunath.hadli@ti.com>,
dlos <davinci-linux-open-source@linux.davincidsp.com>,
Mauro Carvalho Chehab <mchehab@redhat.com>,
LMML <linux-media@vger.kernel.org>
Subject: Re: [PATCH v6 5/7] davinci vpbe: platform specific additions
Date: Thu, 16 Dec 2010 14:14:15 +0300 [thread overview]
Message-ID: <4D09F487.4010906@mvista.com> (raw)
In-Reply-To: <A69FA2915331DC488A831521EAE36FE401BE4AC794@dlee06.ent.ti.com>
Hello.
On 15-12-2010 18:54, Karicheri, Muralidharan wrote:
>> I think the DM644x EVM board changes should be in a separate patch.
> Any reason?
The resaon is simple: you shouldn't mix SoC-level and board-level changes.
> Murali Karicheri
> Software Design Engineer
> Texas Instruments Inc.
> Germantown, MD 20874
WBR, Sergei
prev parent reply other threads:[~2010-12-16 11:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-15 9:11 [PATCH v6 5/7] davinci vpbe: platform specific additions Manjunath Hadli
2010-12-15 11:20 ` Sergei Shtylyov
2010-12-15 15:54 ` Karicheri, Muralidharan
2010-12-16 11:14 ` Sergei Shtylyov [this message]
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=4D09F487.4010906@mvista.com \
--to=sshtylyov@mvista.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=linux-media@vger.kernel.org \
--cc=m-karicheri2@ti.com \
--cc=manjunath.hadli@ti.com \
--cc=mchehab@redhat.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