From: Jani Nikula <jani.nikula@intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
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 19:39:02 +0300 [thread overview]
Message-ID: <87pmenhiop.fsf@intel.com> (raw)
In-Reply-To: <Y0+h++6NReFAZhrv@kroah.com>
On Wed, 19 Oct 2022, Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> On Wed, Oct 19, 2022 at 08:55:55AM +0200, Greg Kroah-Hartman wrote:
>> 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.
>
> No, wait, that breaks the build!
>
> How did you test this? I'm dropping both of these now.
>
> Please resubmit a set of tested patches if you wish to have them applied
> to the tree. These were obviously not even attempted, which just wastes
> all of our time :(
Apologies, misunderstanding on my part about them being applicable
as-is.
Ville has provided the backports. Thanks!
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2022-10-19 16:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 11:02 v5.19 & v6.0 stable backport request Jani Nikula
2022-10-19 6:55 ` Greg Kroah-Hartman
2022-10-19 7:06 ` Greg Kroah-Hartman
2022-10-19 16:39 ` Jani Nikula [this message]
2022-10-19 8:01 ` [PATCH stable-5.19+ 1/2] drm/i915/bios: Validate fp_timing terminator presence Ville Syrjala
2022-10-19 8:01 ` [PATCH stable-5.19+ 2/2] drm/i915/bios: Use hardcoded fp_timing size for generating LFP data pointers 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=87pmenhiop.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=ville.syrjala@linux.intel.com \
/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