From: Sasha Levin <sashal@kernel.org>
To: Jani Nikula <jani.nikula@intel.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
intel-gfx@lists.freedesktop.org, stable@vger.kernel.org
Subject: Re: [Intel-gfx] v6.1 stable backport request
Date: Thu, 26 Jan 2023 21:10:09 -0500 [thread overview]
Message-ID: <Y9MygXR2Z112ttJ2@sashalap> (raw)
In-Reply-To: <878rhs6ij9.fsf@intel.com>
On Tue, Jan 24, 2023 at 05:47:54PM +0200, Jani Nikula wrote:
>
>Stable team, please backport these two commits to v6.1:
>
>2bd0db4b3f0b ("drm/i915: Allow panel fixed modes to have differing sync polarities")
>55cfeecc2197 ("drm/i915: Allow alternate fixed modes always for eDP")
>
>Reference for posterity: https://gitlab.freedesktop.org/drm/intel/-/issues/7841
Queued up, thanks!
--
Thanks,
Sasha
WARNING: multiple messages have this Message-ID (diff)
From: Sasha Levin <sashal@kernel.org>
To: Jani Nikula <jani.nikula@intel.com>
Cc: stable@vger.kernel.org, Greg KH <gregkh@linuxfoundation.org>,
intel-gfx@lists.freedesktop.org
Subject: Re: v6.1 stable backport request
Date: Thu, 26 Jan 2023 21:10:09 -0500 [thread overview]
Message-ID: <Y9MygXR2Z112ttJ2@sashalap> (raw)
In-Reply-To: <878rhs6ij9.fsf@intel.com>
On Tue, Jan 24, 2023 at 05:47:54PM +0200, Jani Nikula wrote:
>
>Stable team, please backport these two commits to v6.1:
>
>2bd0db4b3f0b ("drm/i915: Allow panel fixed modes to have differing sync polarities")
>55cfeecc2197 ("drm/i915: Allow alternate fixed modes always for eDP")
>
>Reference for posterity: https://gitlab.freedesktop.org/drm/intel/-/issues/7841
Queued up, thanks!
--
Thanks,
Sasha
next prev parent reply other threads:[~2023-01-27 2:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 15:47 [Intel-gfx] v6.1 stable backport request Jani Nikula
2023-01-24 15:47 ` Jani Nikula
2023-01-27 2:10 ` Sasha Levin [this message]
2023-01-27 2:10 ` Sasha Levin
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=Y9MygXR2Z112ttJ2@sashalap \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.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.