From: "Nori, Sekhar" <nsekhar@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>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Hilman, Kevin" <khilman@ti.com>
Subject: RE: [PATCH] davinci: fix DM365 EVM video input mux bits
Date: Tue, 19 Jul 2011 14:26:50 +0530 [thread overview]
Message-ID: <B85A65D85D7EB246BE421B3FB0FBB593024DBDC68A@dbde02.ent.ti.com> (raw)
In-Reply-To: <1311046211-2849-1-git-send-email-jon.povey@racelogic.co.uk>
Hi Jon,
On Tue, Jul 19, 2011 at 09:00:11, Jon Povey wrote:
> Video input mux settings for tvp7002 and imager inputs were swapped.
> Comment was correct.
>
> Tested on EVM with tvp7002 input.
>
> Signed-off-by: Jon Povey <jon.povey@racelogic.co.uk>
Thanks for the fix.
Since this part of the code hasn't changed since it
was written, this is a good candidate for stable
kernel series. You can just add:
Cc: stable@kernel.org
Also, this way if the fix fails to make it to 3.0,
it can make it into its stable series. I will add
the Cc line when I queue this patch.
> ---
> As a bugfix maybe this should try to get into 3.0?
I am going queue this to Arnd for sending it for v3.0.
He hasn't yet picked up my earlier pull request yet so
keep fingers crossed :)
BTW, I changed the subject to:
"davinci: DM365 EVM: fix video input mux bits"
Nothing really wrong with what you had, just that
I prefer it this way.
Thanks,
Sekhar
next prev parent reply other threads:[~2011-07-19 8:57 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
2011-07-19 9:00 ` Nori, Sekhar
2011-07-19 10:24 ` Hadli, Manjunath
2011-07-19 8:56 ` Nori, Sekhar [this message]
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=B85A65D85D7EB246BE421B3FB0FBB593024DBDC68A@dbde02.ent.ti.com \
--to=nsekhar@ti.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=jon.povey@racelogic.co.uk \
--cc=khilman@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@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 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®