Re: Unexpected files in the drm-intel tree
Mark Brown <[email protected]>
| Newsgroups | org.kernel.vger.linux-next,org.freedesktop.lists.dri-devel,org.freedesktop.lists.intel-gfx,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <[email protected]> |
On Wed, Aug 19, 2026 at 12:31:07PM +0300, Jani Nikula wrote: > On Tue, 18 Aug 2026, Mark Brown <[email protected]> wrote: > > Commit > > ac3baea883dab ("drm/panel: find_panel_by_fwnode() return a counted reference") > > added this unexpected file: > > drivers/gpu/drm/drm_panel.c.orig > So this has been reported before for drm-misc [1] and drm-xe [2] trees, > and has been fixed in the drm-misc tree by commit 651b0bd0922b > ("drm/panel: remove accidentally committed .orig file"). > Similar to what Joonas said in [3], this should really only be reported > once for the tree *and* branch where it originated. There's not a lot of > value in reporting again whenever something gets merged somewhere else. There's no database of issues here, the check that's being done is based purely on the new commits and diffstat that just appeared when we fetched the tree. Deduplicating things is in general a depresssingly hard problem even for basic stuff (eg, is this a new issue or a recurrance of an old issue?), and the much more common case is that there's downstream trees sending problematic commits to their upstreams which the upstreams would like to know about. DRM is quite unusual in the amount of sideways merging that goes on between parallel trees, and can also be on the higher side for the length of time issues get left for once they've been merged into other trees. What I would have hoped would have happened here is that whichever tree originally had the issue would have fixed it before they sent it to be merged elsewhere, then it wouldn't pop up in all the other trees, or if the original issue already got merged then a fix would be sent promptly before other trees start picking things up. In this case it looks like -next first saw this on July 21st and the fix wasn't posted until 10th August (then applied on the 11th) so there was unfortunately plenty of time for things to propagate around.
signature.asc
(application/pgp-signature, 488 B)
-----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmqFnbYACgkQJNaLcl1U h9C7iAf6AgNJhQWTkBsSQw4F+7KObOf+iJAyNGSkX6TUOXpmUvGy4Vr1zUCG1OJV NtSctTaq1X8BzQibvSyclAA/oGrVjzs3JfST1D81jqZRqZT4+OwCmnhpMyn6CXYh s7hY5FmHRLaREqf4Q8mrAJ+d18YMSg0kYqFIllPGRDX6F7erkAe8hEB0pHL9Q6+/ Qe3zz78PtU+GZMSF+ySBFVC3i/wmtO+rLEH9n/2YWFT+DMqGMxsLiY7CRUqHxGXY SsecaPhoR0Rh5o37Zu1S844oJlKOHYc22DQaeywEEuhG8H+FiqzxzTp/0ym/zQqE FvF63lygNB3OwigjdGan5Sm/lRtWPQ== =/bmt -----END PGP SIGNATURE-----