From: Greg KH <gregkh@linuxfoundation.org>
To: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
Cc: andrzej.hajda@intel.com, rodrigo.vivi@intel.com,
tvrtko.ursulin@intel.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] drm/i915: Never return 0 if not all requests retired" failed to apply to 5.10-stable tree
Date: Wed, 4 Jan 2023 17:14:42 +0100 [thread overview]
Message-ID: <Y7Wl8rDMIBFd1vNX@kroah.com> (raw)
In-Reply-To: <13175047.uLZWGnKmhe@jkrzyszt-mobl1.ger.corp.intel.com>
On Wed, Jan 04, 2023 at 05:02:10PM +0100, Janusz Krzysztofik wrote:
> Hi Greg,
>
> On Wednesday, 4 January 2023 15:39:15 CET gregkh@linuxfoundation.org wrote:
> >
> > The patch below does not apply to the 5.10-stable tree.
>
> FYI, I can see it already added to v5.10.158, commit
> 648b92e5760721fbf230e242950182d7e9222143. The same for other stable trees
> as well as my other fixes for which I received such failure reports from you
> today.
Then why is it coming in with a different git id into Linus's tree?
This is really really annoying, as I have been saying for years.
There's no way for me to know the difference between "this didn't apply
for some reason" and "this did not apply because it is already in
Linus's tree and has been backported already". So I end up with loads
of failures and you end up with an inbox full of junk.
And then the _real_ failures that we need backports for get lost in the
noise.
There's no reason why the DRM subsystem is somehow so special that it is
the only one broken this way...
{sigh}
greg k-h
prev parent reply other threads:[~2023-01-04 16:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 14:39 FAILED: patch "[PATCH] drm/i915: Never return 0 if not all requests retired" failed to apply to 5.10-stable tree gregkh
2023-01-04 16:02 ` Janusz Krzysztofik
2023-01-04 16:14 ` 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=Y7Wl8rDMIBFd1vNX@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andrzej.hajda@intel.com \
--cc=janusz.krzysztofik@linux.intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=stable@vger.kernel.org \
--cc=tvrtko.ursulin@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