From: Jani Nikula <jani.nikula@linux.intel.com>
To: Mark Brown <broonie@kernel.org>,
Simona Vetter <simona.vetter@ffwll.ch>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Intel Graphics <intel-gfx@lists.freedesktop.org>,
DRI <dri-devel@lists.freedesktop.org>
Cc: linux-kernel@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: Unexpected files in the drm-intel tree
Date: Wed, 19 Aug 2026 12:31:07 +0300 [thread overview]
Message-ID: <cbd77031f484d0c044666c4fc11fd3ef273459bb@intel.com> (raw)
In-Reply-To: <aoR9fNYRhmWDNJtz@sirena.org.uk>
On Tue, 18 Aug 2026, Mark Brown <broonie@kernel.org> 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.
BR,
Jani.
[1] https://lore.kernel.org/r/al9cE1PAYd9jyCfZ@sirena.org.uk
[2] https://lore.kernel.org/r/annCRqegoQ9PBClJ@sirena.org.uk
[3] https://lore.kernel.org/r/178712337932.24680.17671628229026350089@jlahtine-mobl
--
Jani Nikula, Intel
next prev parent reply other threads:[~2026-08-19 9:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 15:42 Unexpected files in the drm-intel tree Mark Brown
2026-08-19 9:31 ` Jani Nikula [this message]
2026-08-19 12:12 ` Mark Brown
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=cbd77031f484d0c044666c4fc11fd3ef273459bb@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=broonie@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=simona.vetter@ffwll.ch \
/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