From: "Luca Ceresoli" <luca.ceresoli@bootlin.com>
To: "Kory Maincent" <kory.maincent@bootlin.com>,
"Maxime Ripard" <mripard@kernel.org>,
<linux-kernel@vger.kernel.org>, <dri-devel@lists.freedesktop.org>
Cc: "Bajjuri Praneeth" <praneeth@ti.com>,
<thomas.petazzoni@bootlin.com>, "Jyri Sarha" <jyri.sarha@iki.fi>,
"Tomi Valkeinen" <tomi.valkeinen@ideasonboard.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>
Subject: Re: [PATCH] drm/tilcdc: Remove tilcdc_panel driver reintroduced by a merge
Date: Fri, 13 Mar 2026 17:57:00 +0100 [thread overview]
Message-ID: <DH1TA9U2BXUU.2Z470IEKJH0SQ@bootlin.com> (raw)
In-Reply-To: <20260305155921.659550-1-kory.maincent@bootlin.com>
On Thu Mar 5, 2026 at 4:59 PM CET, Kory Maincent wrote:
> From: "Kory Maincent (TI)" <kory.maincent@bootlin.com>
>
> The tilcdc_panel driver was removed by commit 8f1e1ab9c794 ("drm/tilcdc:
> Remove tilcdc panel driver"), but was inadvertently reintroduced by the
> merge commit 8b85987d3cf5 ("Merge drm/drm-next into drm-misc-next").
>
> The regression went unnoticed because standard git commands such as
> 'git show' do not expose the change. It was only spotted via
> 'git show --stat':
>
> git show --stat 8b85987d3cf5 | grep tilcdc
> drivers/gpu/drm/tilcdc/tilcdc_panel.c | 408 +
>
> git show 8b85987d3cf5 | grep tilcdc
> (no output)
>
> Remove tilcdc_panel.c again to restore the previously intended state.
>
> Fixes: 8b85987d3cf5 ("Merge drm/drm-next into drm-misc-next")
> Signed-off-by: Kory Maincent (TI) <kory.maincent@bootlin.com>
Reviewed-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-03-13 16:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 15:59 Kory Maincent
2026-03-13 16:57 ` Luca Ceresoli [this message]
2026-03-17 16:42 ` Luca Ceresoli
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=DH1TA9U2BXUU.2Z470IEKJH0SQ@bootlin.com \
--to=luca.ceresoli@bootlin.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jyri.sarha@iki.fi \
--cc=kory.maincent@bootlin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=praneeth@ti.com \
--cc=simona@ffwll.ch \
--cc=thomas.petazzoni@bootlin.com \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=tzimmermann@suse.de \
/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
all inboxes | Powered by JetHome®