From: "Hadli, Manjunath" <manjunath.hadli@ti.com>
To: "'Jon Povey'" <Jon.Povey@racelogic.co.uk>,
"davinci-linux-open-source@linux.davincidsp.com"
<davinci-linux-open-source@linux.davincidsp.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Nori, Sekhar" <nsekhar@ti.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] davinci: fix DM365 EVM video input mux bits
Date: Tue, 19 Jul 2011 12:55:13 +0530 [thread overview]
Message-ID: <B85A65D85D7EB246BE421B3FB0FBB593024BCEF73F@dbde02.ent.ti.com> (raw)
In-Reply-To: <70E876B0EA86DD4BAF101844BC814DFE0B4E0859D7@Cloud.RL.local>
Will not be able to give you a sub-patch as it is combined as part of a larger implementation.
Since the bug fix needs to go into 3.0, I am Ok if you fix the bug, and the macros can be substituted later.
-Manju
On Tue, Jul 19, 2011 at 11:58:19, Jon Povey wrote:
> Hadli, Manjunath wrote:
> > Jon,
> >
> > The fix looks correct. As a part of a different implementation which
> > will go soon upstream, this has been taken care of, where we have used
> > macros
> > CPLD_VIDEO_INPUT_MUX_TVP7002 0x1
> > CPLD_VIDEO_INPUT_MUX_IMAGER 0x2
> >
> > So, if you can do the same, it will look better.
>
> If you have a patch you can split out that has your defines where and how you want them then great.
>
> Otherwise I'd suggest just getting this or something equivalent in to fix the bug first, and reimplement it later.
>
> --
> Jon Povey
> jon.povey@racelogic.co.uk
>
> Racelogic is a limited company registered in England. Registered number 2743719 .
> Registered Office Unit 10, Swan Business Centre, Osier Way, Buckingham, Bucks, MK18 1TB .
>
> The information contained in this electronic mail transmission is intended by Racelogic Ltd for the use of the named individual or entity to which it is directed and may contain information that is confidential or privileged. If you have received this electronic mail transmission in error, please delete it from your system without copying or forwarding it, and notify the sender of the error by reply email so that the sender's address records can be corrected. The views expressed by the sender of this communication do not necessarily represent those of Racelogic Ltd. Please note that Racelogic reserves the right to monitor e-mail communications passing through its network
>
>
>
next prev parent reply other threads:[~2011-07-19 7:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-19 3:30 Jon Povey
2011-07-19 5:29 ` Hadli, Manjunath
2011-07-19 6:28 ` Jon Povey
2011-07-19 7:25 ` Hadli, Manjunath [this message]
2011-07-19 9:00 ` Nori, Sekhar
2011-07-19 10:24 ` Hadli, Manjunath
2011-07-19 8:56 ` Nori, Sekhar
2011-07-19 10:55 ` Russell King - ARM Linux
2011-07-20 16:40 ` Nori, Sekhar
2011-07-20 16:48 ` Russell King - ARM Linux
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=B85A65D85D7EB246BE421B3FB0FBB593024BCEF73F@dbde02.ent.ti.com \
--to=manjunath.hadli@ti.com \
--cc=Jon.Povey@racelogic.co.uk \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nsekhar@ti.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
all inboxes | Powered by JetHome®