linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
	Helge Deller <deller@gmx.de>, Shawn Guo <shawnguo@kernel.org>,
	linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
	NXP Linux Team <linux-imx@nxp.com>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/4] video: fb: imxfb: Drop platform data support
Date: Sat, 23 Jul 2022 21:23:43 +0200	[thread overview]
Message-ID: <YtxKv0ZUbg6V+a2w@ravnborg.org> (raw)
In-Reply-To: <20220723175720.76933-1-u.kleine-koenig@pengutronix.de>

Hi Uwe,

On Sat, Jul 23, 2022 at 07:57:17PM +0200, Uwe Kleine-König wrote:
> No source file but the driver itself includes the header containing the
> platform data definition. The last user is gone since commit
> 8485adf17a15 ("ARM: imx: Remove imx device directory").
> 
> So we can safely drop platform data support.
> 
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>

Do imxfb offer something that is not supported by the DRM drivers?
If yes then the clean-up is good, if not then we could drop the driver?

	Sam

  parent reply	other threads:[~2022-07-23 19:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-23 17:57 [PATCH 1/4] video: fb: imxfb: Drop platform data support Uwe Kleine-König
2022-07-23 17:57 ` [PATCH 2/4] video: fb: imxfb: Drop unused symbols from header Uwe Kleine-König
2022-07-23 17:57 ` [PATCH 3/4] video: fb: imxfb: Fold <linux/platform_data/video-imxfb.h> into only user Uwe Kleine-König
2022-07-23 17:57 ` [PATCH 4/4] video: fb: imxfb: Convert request_mem_region + ioremap to devm_ioremap_resource Uwe Kleine-König
2022-07-23 19:23 ` Sam Ravnborg [this message]
2022-07-23 22:02   ` [PATCH 1/4] video: fb: imxfb: Drop platform data support Uwe Kleine-König
2022-07-24  9:40     ` Sam Ravnborg
2022-07-24  9:46       ` Sam Ravnborg
2022-07-26  7:08 ` Helge Deller

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=YtxKv0ZUbg6V+a2w@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=deller@gmx.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-imx@nxp.com \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=u.kleine-koenig@pengutronix.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;
as well as URLs for NNTP newsgroup(s).