From: Greg KH <gregkh@linuxfoundation.org>
To: Christoph Niedermaier <cniedermaier@dh-electronics.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: Missing fixes commit on linux-4.19.y
Date: Sat, 28 Nov 2020 15:52:01 +0100 [thread overview]
Message-ID: <X8JkEd1pRewMee3q@kroah.com> (raw)
In-Reply-To: <87296404bad145d2a84173edcfd5a231@dh-electronics.com>
On Fri, Nov 27, 2020 at 05:56:24PM +0000, Christoph Niedermaier wrote:
> From: Greg KH [mailto:gregkh@linuxfoundation.org]
> Sent: Friday, November 27, 2020 3:09 PM
>
> Hello Greg,
>
> >> Is it possible to apply the following commit on the branch linux-4.19.y?
> >> de9f8eea5a44 ("drm/atomic_helper: Stop modesets on unregistered connectors harder")
> >>
> >> This commit is applied to the other LTS kernels, but is missing on
> >> linux-4.19.y.
> >
> > I see it showing up in the 4.20 release, so of course anything newer
> > than that will work, what other trees do you see this applied in?
>
> I think it's only the 4.19 tree that misses this patch, because it fixes
> "drm/atomic_helper: Disallow new modesets on unregistered connectors"
> and
> "drm/atomic_helper: Allow DPMS On<->Off changes for unregistered connectors"
> If I am right this two commits aren't on 4.14 / 4.9 / 4.4
>
> >> Without this patch my i.MX6ULL SoM doesn't initialize
> >> the display correctly after booting.
> >
> > It does not apply cleanly to the 4.19.y tree, can you provide a working
> > backport so that we could apply it?
>
> A working backport is below.
Looks good, now queued up, thanks.
greg k-h
prev parent reply other threads:[~2020-11-28 22:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 13:50 Missing fixes commit on linux-4.19.y Christoph Niedermaier
2020-11-27 14:09 ` Greg KH
2020-11-27 17:56 ` Christoph Niedermaier
2020-11-28 14:52 ` Greg KH [this message]
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=X8JkEd1pRewMee3q@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=cniedermaier@dh-electronics.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.