Re: FAILED: patch "[PATCH] drm/i915: Never return 0 if not all requests retired" failed to apply to 5.10-stable tree

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxxxxxxxxxxx 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



[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux