Re: Fixes tags need work in the drm-intel tree

On Wed, Aug 19, 2026 at 10:09:39AM +0300, Joonas Lahtinen wrote:

> You may want to include the repository name in the body of the message,
> not just title. The full repo name would help, too.

It's whatever the tree is called in -next; I think the general hope is
that if you have included a tree that is -next you'll be aware of what
it is.  As a reminder the trees I currently have you (amost others) as a
contact for are:

   drm-intel-fixes:
       https://gitlab.freedesktop.org/drm/i915/kernel.git for-linux-next-fixes

   drm-intel:
       https://gitlab.freedesktop.org/drm/i915/kernel.git for-linux-next

> As there's no drm-intel tree, one would assume drm-intel-next, the
> below commit is not there. Seems to be from drm-misc-next.

> It seems to also be drm-intel-next-fixes tree which has been reset to
> equal drm/drm-next to prepare for -next-fixes PRs.

> Maybe you want to only send the notification once per unique HEAD
> (ignoring merges)? That'd then target the original commit and
> any cherry-picks.

That's what happens currently, these notifications are generated based
on checks done on the new non-mainline commits that appear in your tree
each day.

Are you sure this isn't something that you've picked up in one of your
inter-tree DRM merges?  There's a general pattern of DRM trees sending
unadressed issues to their upstream and being slow with sending the
fixes, then the same issue appearing in all the other DRM trees as you
the various DRM branches cross merge with each other.  For Fixes stuff
that's just going to happen unfortunately given that you don't rebase.
The common case here is that downstreams are sending things to their
upstreams, in general it is useful for the upstream maintainers to get
notified about issues.

Please don't top post, reply in line with needed context.  This allows
readers to readily follow the flow of conversation and understand what
you are talking about and also helps ensure that everything in the
discussion is being addressed.

-----BEGIN PGP SIGNATURE-----

iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmqFj/EACgkQJNaLcl1U
h9DM2Af9FgJW5i0Z0Hu16HAqh/sx9HUY4QHlpumj3HjmsVNADXw5lOSB4LpqsrXR
6AOrrvKuY3Z1g3bEwmgYnXwXo66fQRbkXnAsqxtkAVnpZCBwiHL2RZtiFJk8dlNL
Tc2Ap0OMM/ndC77gshvMPnhGwbPos2hqd+FNDnHL7HSf+JEdeLTLEmsTyCoihI8E
Ia6B0a7N+kgGE9zh/m+lZ1RSzhkRhx8I8LwIZEI5MtzdVStlW0cEs9+QyKctS1kz
XmTEcsMMYufkMkb9d1Z4XuO4ltJgm2hjmNCy0tm11IE+5LHGF9QKUnshQF43tuCo
89gwCxX2Jj8TH5bYnB6SMqdBmAt6qQ==
=eTpw
-----END PGP SIGNATURE-----