From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Mark Brown" <broonie@kernel.org>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"DRM XE List" <intel-xe@lists.freedesktop.org>,
dri-devel@lists.freedesktop.org
Cc: linux-kernel@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: Unexpected files in the drm-xe tree
Date: Mon, 10 Aug 2026 15:54:19 +0300 [thread overview]
Message-ID: <23d8ccf32c09ab940ea03a62b9827283df945854@intel.com> (raw)
In-Reply-To: <annCRqegoQ9PBClJ@sirena.org.uk>
On Mon, 10 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
Thanks for the report. Fix at [1].
BR,
Jani.
[1] https://lore.kernel.org/r/20260810125204.3258447-1-jani.nikula@intel.com
--
Jani Nikula, Intel
prev parent reply other threads:[~2026-08-10 12:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-10 12:21 Unexpected files in the drm-xe tree Mark Brown
2026-08-10 12:54 ` Jani Nikula [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=23d8ccf32c09ab940ea03a62b9827283df945854@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=broonie@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=thomas.hellstrom@linux.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