linux-kernel - RE: [PATCH] davinci: fix DM365 EVM video input mux bits

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 19 Jul 2011 14:26:50 +0530
From:	"Nori, Sekhar" <nsekhar@...com>
To:	Jon Povey <jon.povey@...elogic.co.uk>,
	"davinci-linux-open-source@...ux.davincidsp.com" 
	<davinci-linux-open-source@...ux.davincidsp.com>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Hilman, Kevin" <khilman@...com>
Subject: RE: [PATCH] davinci: fix DM365 EVM video input mux bits

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@...elogic.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@...nel.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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/