From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-omap@vger.kernel.org
Subject: Re: OMAP4 HDMI PHY bug work-around for stable
Date: Wed, 29 Feb 2012 11:07:24 +0200 [thread overview]
Message-ID: <1330506444.1934.20.camel@deskari> (raw)
In-Reply-To: <20120228164702.GB11021@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 964 bytes --]
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
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-02-29 9:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 11:44 OMAP4 HDMI PHY bug work-around for stable Tomi Valkeinen
2012-02-28 8:03 ` Tomi Valkeinen
2012-02-28 16:47 ` Greg KH
2012-02-29 9:07 ` Tomi Valkeinen [this message]
2012-02-29 14:57 ` Greg KH
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=1330506444.1934.20.camel@deskari \
--to=tomi.valkeinen@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).