linux-kernel - Re: OMAP4 HDMI PHY bug work-around for stable

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Wed, 29 Feb 2012 11:07:24 +0200
From:	Tomi Valkeinen <tomi.valkeinen@...com>
To:	Greg KH <gregkh@...uxfoundation.org>
Cc:	stable@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-omap@...r.kernel.org
Subject: Re: OMAP4 HDMI PHY bug work-around for stable

On Tue, 2012-02-28 at 08:47 -0800, Greg KH wrote:

> Sorry, but I don't accept pull requests.  I need patches in email form,
> as described in the file, Documentation/stable_kernel_rules.txt.  Please
> feel free to send them from your git tree that way.

Ah, I somehow missed that txt when googling about the stable kernel.
Thanks for pointing it out.

> That seems like a lot of backporting for a single fix, but I'll be glad
> to review them when you send them.

This is something that is not quite clear to me:

Should I strive for keeping the patches for stable as close as possible
to the ones in mainline, and thus possibly being forced to take other
extra patches with the actual fix as I did here

or

should I just rather cook up a new patch which just fixes the problem
without caring about any cleanups etc. that are in the mainline, and
thus possibly creating a rather different patch compared to mainline's
version?

 Tomi


Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)