From: Nathan Chancellor <nathan@kernel.org>
To: gregkh@linuxfoundation.org
Cc: samitolvanen@google.com, tpgxyz@gmail.com, tzimmermann@suse.de,
stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] drm/simpledrm: Fix return type of" failed to apply to 6.0-stable tree
Date: Mon, 17 Oct 2022 11:09:54 -0700 [thread overview]
Message-ID: <Y02acmLNms9UygZL@dev-arch.thelio-3990X> (raw)
In-Reply-To: <166593672329153@kroah.com>
On Sun, Oct 16, 2022 at 06:12:03PM +0200, gregkh@linuxfoundation.org wrote:
>
> The patch below does not apply to the 6.0-stable tree.
> If someone wants it applied there, or to any other stable or longterm
> tree, then please email the backport, including the original git commit
> id to <stable@vger.kernel.org>.
>
> Possible dependencies:
>
> f9929f69de94 ("drm/simpledrm: Fix return type of simpledrm_simple_display_pipe_mode_valid()")
>
> thanks,
>
> greg k-h
>
> ------------------ original commit in Linus's tree ------------------
>
> From f9929f69de94212f98b3ad72a3e81c3bd3d333e0 Mon Sep 17 00:00:00 2001
> From: Nathan Chancellor <nathan@kernel.org>
> Date: Mon, 25 Jul 2022 16:36:29 -0700
> Subject: [PATCH] drm/simpledrm: Fix return type of
> simpledrm_simple_display_pipe_mode_valid()
Just for the record, this change is already in the stable trees it is
relevant for, as it was a part of 5.19:
5.19 and 6.0: 0c09bc33aa8e ("drm/simpledrm: Fix return type of simpledrm_simple_display_pipe_mode_valid()")
5.15: 11c1cc3f6e42 ("drm/simpledrm: Fix return type of simpledrm_simple_display_pipe_mode_valid()")
I am not sure how a second copy (f9929f69de94) ended up in the tree
during the 6.1 cycle, I am guessing it was cherry picked to a
development branch from a fixes branch, rather than backmerged.
TL;DR: Nothing for stable to do here.
Cheers,
Nathan
next prev parent reply other threads:[~2022-10-17 18:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-16 16:12 FAILED: patch "[PATCH] drm/simpledrm: Fix return type of" failed to apply to 6.0-stable tree gregkh
2022-10-17 18:09 ` Nathan Chancellor [this message]
2022-10-18 5:16 ` 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=Y02acmLNms9UygZL@dev-arch.thelio-3990X \
--to=nathan@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=samitolvanen@google.com \
--cc=stable@vger.kernel.org \
--cc=tpgxyz@gmail.com \
--cc=tzimmermann@suse.de \
/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.