From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jani Nikula <jani.nikula@intel.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [Intel-gfx] v5.19 & v6.0 stable backport request
Date: Wed, 19 Oct 2022 08:55:55 +0200 [thread overview]
Message-ID: <Y0+fex0i0vmBL6QX@kroah.com> (raw)
In-Reply-To: <87k04xiedr.fsf@intel.com>
On Tue, Oct 18, 2022 at 02:02:08PM +0300, Jani Nikula wrote:
>
> Hello stable team, please backport these two commits to stable kernels
> v5.19 and v6.0:
>
> 4e78d6023c15 ("drm/i915/bios: Validate fp_timing terminator presence")
Does not apply to 5.19.y, can you provide a working backport?
> d3a7051841f0 ("drm/i915/bios: Use hardcoded fp_timing size for generating LFP data pointers")
Queued up to both trees now, thanks.
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jani Nikula <jani.nikula@intel.com>
Cc: stable@vger.kernel.org, intel-gfx@lists.freedesktop.org,
linux-kernel@vger.kernel.org, Hans de Goede <hdegoede@redhat.com>,
ville.syrjala@linux.intel.com
Subject: Re: v5.19 & v6.0 stable backport request
Date: Wed, 19 Oct 2022 08:55:55 +0200 [thread overview]
Message-ID: <Y0+fex0i0vmBL6QX@kroah.com> (raw)
In-Reply-To: <87k04xiedr.fsf@intel.com>
On Tue, Oct 18, 2022 at 02:02:08PM +0300, Jani Nikula wrote:
>
> Hello stable team, please backport these two commits to stable kernels
> v5.19 and v6.0:
>
> 4e78d6023c15 ("drm/i915/bios: Validate fp_timing terminator presence")
Does not apply to 5.19.y, can you provide a working backport?
> d3a7051841f0 ("drm/i915/bios: Use hardcoded fp_timing size for generating LFP data pointers")
Queued up to both trees now, thanks.
greg k-h
next prev parent reply other threads:[~2022-10-19 6:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 11:02 [Intel-gfx] v5.19 & v6.0 stable backport request Jani Nikula
2022-10-18 11:02 ` Jani Nikula
2022-10-19 6:55 ` Greg Kroah-Hartman [this message]
2022-10-19 6:55 ` Greg Kroah-Hartman
2022-10-19 7:06 ` [Intel-gfx] " Greg Kroah-Hartman
2022-10-19 7:06 ` Greg Kroah-Hartman
2022-10-19 16:39 ` [Intel-gfx] " Jani Nikula
2022-10-19 16:39 ` Jani Nikula
2022-10-19 8:01 ` [Intel-gfx] [PATCH stable-5.19+ 1/2] drm/i915/bios: Validate fp_timing terminator presence Ville Syrjala
2022-10-19 8:01 ` Ville Syrjala
2022-10-19 8:01 ` [Intel-gfx] [PATCH stable-5.19+ 2/2] drm/i915/bios: Use hardcoded fp_timing size for generating LFP data pointers Ville Syrjala
2022-10-19 8:01 ` Ville Syrjala
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=Y0+fex0i0vmBL6QX@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=linux-kernel@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 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.